Re: [core] Binding Attributes in draft-groves-core-dynlink-02

"Carey, Timothy (Nokia - US)" <timothy.carey@nokia.com> Sun, 26 February 2017 19:17 UTC

Return-Path: <timothy.carey@nokia.com>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 35A31128AB0 for <core@ietfa.amsl.com>; Sun, 26 Feb 2017 11:17:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.001
X-Spam-Level:
X-Spam-Status: No, score=-5.001 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] 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 vgndtGxyVeHE for <core@ietfa.amsl.com>; Sun, 26 Feb 2017 11:17:11 -0800 (PST)
Received: from smtp-us.alcatel-lucent.com (us-hpswa-esg-01.alcatel-lucent.com [135.245.18.29]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6E105127601 for <core@ietf.org>; Sun, 26 Feb 2017 11:17:11 -0800 (PST)
Received: from us70uumx3.dmz.alcatel-lucent.com (unknown [135.245.18.15]) by Websense Email Security Gateway with ESMTPS id 2FE80C4B170A9; Sun, 26 Feb 2017 19:17:07 +0000 (GMT)
Received: from us70uusmtp3.zam.alcatel-lucent.com (us70uusmtp3.zam.alcatel-lucent.com [135.5.2.65]) by us70uumx3.dmz.alcatel-lucent.com (GMO) with ESMTP id v1QJH9tT008040 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sun, 26 Feb 2017 19:17:09 GMT
Received: from US70TWXCHHUB04.zam.alcatel-lucent.com (us70twxchhub04.zam.alcatel-lucent.com [135.5.2.36]) by us70uusmtp3.zam.alcatel-lucent.com (GMO) with ESMTP id v1QJGv88030309 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sun, 26 Feb 2017 19:17:08 GMT
Received: from US70UWXCHMBA05.zam.alcatel-lucent.com ([169.254.10.74]) by US70TWXCHHUB04.zam.alcatel-lucent.com ([135.5.2.36]) with mapi id 14.03.0301.000; Sun, 26 Feb 2017 14:17:07 -0500
From: "Carey, Timothy (Nokia - US)" <timothy.carey@nokia.com>
To: Michael Koster <michaeljohnkoster@gmail.com>, Carsten Bormann <cabo@tzi.org>
Thread-Topic: [core] Binding Attributes in draft-groves-core-dynlink-02
Thread-Index: AdKPhIJ5tHWhI/SMR/S1s5vXPdBMHQAN5/cAAALz8IAAGmyiIA==
Date: Sun, 26 Feb 2017 19:17:06 +0000
Message-ID: <9966516C6EB5FC4381E05BF80AA55F77012A865188@US70UWXCHMBA05.zam.alcatel-lucent.com>
References: <9966516C6EB5FC4381E05BF80AA55F77012A864782@US70UWXCHMBA05.zam.alcatel-lucent.com> <B92E9C86-68A6-47D0-933C-AE7D00B4DDCB@tzi.org> <A67EF331-E5E1-4774-B772-F96356A1CCCB@gmail.com>
In-Reply-To: <A67EF331-E5E1-4774-B772-F96356A1CCCB@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.5.27.17]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/UsKI-cx7OeuyD2mHWE1l9VIkOPE>
Cc: GARNIER Thierry <Thierry.Garnier@gemalto.com>, "core@ietf.org WG" <core@ietf.org>
Subject: Re: [core] Binding Attributes in draft-groves-core-dynlink-02
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/core>, <mailto:core-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/core/>
List-Post: <mailto:core@ietf.org>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 26 Feb 2017 19:17:13 -0000

Michael,

Well the IETF interfaces draft has been consistent - the step attribute is "st".
I went back and traced the change in LWM2M from "st" to "stp".
It occurred between: 
The February 2015 (OMA-TS-LightweightM2M-V1_0-20150228-D) has "stp" and the February 2015 version (OMA-TS-LightweightM2M-V1_0-20150225-D) has "st".
The agreed to cr that brought that change was OMA-DM-LightweightM2M-2015-0008R01-CR_Attributes_

I added Thierry into this email - maybe he can answer your question better since he brought the original CR but it looks to me to be an editorial problem when he restructured that part of the document and clarified the rules for use within LWM2M... Probably just a typo that needs corrected in the OMA spec...

BR,
Tim

-----Original Message-----
From: Michael Koster [mailto:michaeljohnkoster@gmail.com] 
Sent: Saturday, February 25, 2017 1:33 PM
To: Carsten Bormann <cabo@tzi.org>
Cc: Carey, Timothy (Nokia - US) <timothy.carey@nokia.com>; core@ietf.org WG <core@ietf.org>
Subject: Re: [core] Binding Attributes in draft-groves-core-dynlink-02

Hi Tim,

Is there a name collision with "st" that required OMA LWM2M to use "stp" instead? I used "st" in the mbed reference implementation in early 2015.

Best regards,

Michael

> On Feb 25, 2017, at 10:08 AM, Carsten Bormann <cabo@tzi.org> wrote:
> 
> (No chair hat.)
> 
>> On 25 Feb 2017, at 17:34, Carey, Timothy (Nokia - US) <timothy.carey@nokia.com> wrote:
>> 
>> Hi,
>> 
>> I noticed in the latest draft the binding attributes were changed.
>> The LWM2M uses the binding attributes in their specification that was recently published.
>> In LWM2M Greater than is gt; Less than is lt and Step is stp.
>> In the latest dynlink draft Greater than is gth; Less than is lth and Step is st
>> 
>> Do we know the reason for the change?
> 
> There was a naming issue with “lt” being used for both lifetime and less than.
> This is not a problem now, but could become one.
> Since lifetime was in use, attempts have been made to rename less than (and greater than analogously), but discussion took some time (maybe because lt and gt are the obvious names for anyone who has heard of FORTRAN).
> 
>> Is it possible to use lt; gt; stp as is specificed in LWM2M?
> 
> Maybe we have missed a window in which this change (avoiding the name collision) could have been net positive.
> 
> Grüße, Carsten
> 
> _______________________________________________
> core mailing list
> core@ietf.org
> https://www.ietf.org/mailman/listinfo/core