From nobody Tue Dec 13 02:34:41 2016 Return-Path: X-Original-To: core-parameters@ietfa.amsl.com Delivered-To: core-parameters@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D2D99129A5B for ; Tue, 13 Dec 2016 02:34:39 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.555 X-Spam-Level: X-Spam-Status: No, score=-3.555 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_SOFTFAIL=0.665] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U1WTgxRAwefW for ; Tue, 13 Dec 2016 02:34:38 -0800 (PST) Received: from p02c11o145.mxlogic.net (p02c11o145.mxlogic.net [208.65.144.78]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C3F99129A58 for ; Tue, 13 Dec 2016 02:34:37 -0800 (PST) Received: from unknown [67.207.217.103] (EHLO remote.omaorg.org) by p02c11o145.mxlogic.net(mxl_mta-8.5.0-1591) with ESMTP id dbecf485.2adf06409940.16348.00-592.39174.p02c11o145.mxlogic.net (envelope-from ); Tue, 13 Dec 2016 03:34:37 -0700 (MST) X-MXL-Hash: 584fcebd29651a91-c53220860940f00487658167fd64b919a3eb68bc Received: from unknown [67.207.217.103] (EHLO remote.omaorg.org) by p02c11o145.mxlogic.net(mxl_mta-8.5.0-1591) over TLS secured channel with ESMTP id 9becf485.0.16340.00-393.39147.p02c11o145.mxlogic.net (envelope-from ); Tue, 13 Dec 2016 03:34:34 -0700 (MST) X-MXL-Hash: 584fceba62e66dfa-0ff802329257d9df848770c433774a9f31788886 Received: from OMAS1.omaorg.local ([fe80::306c:440:acf0:cea1]) by OMAS1.omaorg.local ([fe80::306c:440:acf0:cea1%13]) with mapi; Tue, 13 Dec 2016 02:34:24 -0800 From: John Mudge To: "Dijk, Esko" , "core-parameters@ietf.org" Date: Tue, 13 Dec 2016 02:34:22 -0800 Thread-Topic: NEW RESOURCE TYPE - oma.lwm2m Thread-Index: AdI7dtiPWXQVzQaIQxOKVnZb+kYF9QAGCfPgAPAEpUAALH7AwAE2DV1QBBRhHtA= Message-ID: References: <261610e4e1a849869dd042502e0e4b06@HE1PR9001MB0170.MGDPHG.emi.philips.com> <61666927fb2d483fab607bdf2746e5e3@HE1PR9001MB0170.MGDPHG.emi.philips.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-AnalysisOut: [v=2.2 cv=P7NKvmIu c=1 sm=1 tr=0 a=awUsbprPsKFWkzCeit0qWg==] X-AnalysisOut: [:117 a=awUsbprPsKFWkzCeit0qWg==:17 a=kj9zAlcOel0A:10 a=xqW] X-AnalysisOut: [C_Br6kY4A:10 a=n5n_aSjo0skA:10 a=igp2tEblAAAA:8 a=5lX_Y-y2] X-AnalysisOut: [AAAA:8 a=48vgC7mUAAAA:8 a=ePjZ5FlyAAAA:8 a=OKRv1JDRyKsOtYQ] X-AnalysisOut: [2wdgA:9 a=S1Ew7GjEjM3NTbTJ:21 a=nud1v-niYd64w9q-:21 a=CjuI] X-AnalysisOut: [K1q_8ugA:10 a=1zGPN6_jfEwA:10 a=NX0l0kzPQhqatvdBvMyd:22 a=] X-AnalysisOut: [I7gXlfD7_t8F9Fmtm5Nf:22 a=w1C3t2QeGrPiZgrLijVG:22 a=eH1H-m] X-AnalysisOut: [T4XAzLHBZ0f_aA:22] X-Spam: [F=0.5695789426; CM=0.500; MH=0.569(2016121308); S=0.200(2015072901)] X-MAIL-FROM: X-SOURCE-IP: [67.207.217.103] Archived-At: Subject: Re: [core-parameters] NEW RESOURCE TYPE - oma.lwm2m X-BeenThere: core-parameters@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Expert review of CoAP parameters." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Dec 2016 10:34:40 -0000 Hi, As there seem to be no more comments, what are the next steps regarding thi= s registration request? The updated registration information is: o Attribute Value: oma.lwm2m o Description: Indicates this resource and all its sub-resources suppor= t the OMA Lightweight M2M protocol, i.e. contain OMA LWM2M objects and reso= urces. o Reference: "Lightweight Machine to Machine Technical Specification", = OMA-TS-LightweightM2M-V1_0, especially subsection 5.3.1, http://www.openmobilealliance.org/tech/extref/OMA-TS-LightweightM2M-V= 1_0.zip o Notes: N/A Thank you and kind regards, John -----Original Message----- From: John Mudge=20 Sent: 22 November 2016 16:09 To: 'Dijk, Esko' ; core-parameters@ietf.org Subject: RE: NEW RESOURCE TYPE - oma.lwm2m Dear Esko, Thank you, your revised description is fine. Kind regards, John -----Original Message----- From: Dijk, Esko [mailto:esko.dijk@philips.com]=20 Sent: 16 November 2016 12:14 To: John Mudge ; core-parameters@ietf.org Subject: RE: NEW RESOURCE TYPE - oma.lwm2m Dear John, Thanks; I still think this description could be clarified a bit more. Thoug= h the current text would also work, since the LWM2M spec reference defines = it properly anyhow. The Lightweight M2M 1.0 spec states that the resource type 'oma.lwm2m' is u= sed only for the resource that is acting as the top-level parent (i.e. ance= stor) for all the OMA Lightweight M2M Objects and Resources. So this rt can= not be used itself for tagging say a LWM2M Resource or an Object Instance. = It can only be used to identify a top-level entry point for the LWM2M resou= rce structure. So what about: o Description: Indicates this resource and all its sub-resources suppor= t the OMA Lightweight M2M protocol, i.e. contain OMA LWM2M objects and reso= urces. regards Esko -----Original Message----- From: John Mudge [mailto:JMudge@omaorg.org]=20 Sent: Tuesday, November 15, 2016 17:31 To: Dijk, Esko ; core-parameters@ietf.org Subject: RE: NEW RESOURCE TYPE - oma.lwm2m Thank you Esko for your comment and suggestion. The OMA DM working group have endeavoured to clarify the description and ha= ve proposed the following alternative text: o Description: Indicates the URI contents is for the OMA LwM2M protocol= e.g. OMA LwM2M objects and resources. Would this revised text be satisfactory? Thank you and kind regards, John -----Original Message----- From: Dijk, Esko [mailto:esko.dijk@philips.com]=20 Sent: 10 November 2016 20:19 To: John Mudge ; core-parameters@ietf.org Subject: RE: NEW RESOURCE TYPE - oma.lwm2m Hello, perhaps the description could be clarified a bit to e.g.: o Description: The OMA Lightweight M2M entry-point resource in the LWM2M= client (CoAP server). To clarify the term 'client' more. regards Esko Dijk -----Original Message----- From: core-parameters [mailto:core-parameters-bounces@ietf.org] On Behalf O= f John Mudge Sent: Thursday, November 10, 2016 18:52 To: core-parameters@ietf.org Subject: [core-parameters] NEW RESOURCE TYPE - oma.lwm2m Hi, This registration request proposes to add the value oma.lwm2m to the sub-re= gistry Resource Type (rt=3D) Link Target Attribute Values, within the Const= rained RESTful Environments (CoRE) Parameters registry. The completed registration template is as follows: o Attribute Value: oma.lwm2m o Description: This value denotes the OMA LightweightM2M application in= the client. o Reference: "Lightweight Machine to Machine Technical Specification", = OMA-TS-LightweightM2M-V1_0, especially subsection 5.3.1, http://www.openmobilealliance.org/tech/extref/OMA-TS-LightweightM2M-V= 1_0.zip o Notes: N/A Please let me know if you have any comments or questions. Thank you and kind regards, John ---------------------------------------- John Mudge Open Mobile Alliance Cell: (+44) (0)75 91 53 17 47 Email: jmudge@omaorg.org ---------------------------------------- _______________________________________________ core-parameters mailing list core-parameters@ietf.org https://www.ietf.org/mailman/listinfo/core-parameters ________________________________ The information contained in this message may be confidential and legally p= rotected under applicable law. The message is intended solely for the addre= ssee(s). If you are not the intended recipient, you are hereby notified tha= t any use, forwarding, dissemination, or reproduction of this message is st= rictly prohibited and may be unlawful. If you are not the intended recipien= t, please contact the sender by return e-mail and destroy all copies of the= original message.