IETF Logo Mail Archive

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

Christian Groves <cngroves.std@gmail.com> Mon, 27 February 2017 03:36 UTC

Return-Path: <cngroves.std@gmail.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 058CC129668 for <core@ietfa.amsl.com>; Sun, 26 Feb 2017 19:36:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.332
X-Spam-Level:
X-Spam-Status: No, score=-0.332 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no 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 XlHa7bluXPwl for <core@ietfa.amsl.com>; Sun, 26 Feb 2017 19:36:26 -0800 (PST)
Received: from msh04.myshophosting.com (msh04.myshophosting.com [101.0.86.118]) (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 78E8A129665 for <core@ietf.org>; Sun, 26 Feb 2017 19:36:26 -0800 (PST)
Received: from ppp118-209-135-224.lns20.mel8.internode.on.net ([118.209.135.224]:59217 helo=[192.168.1.22]) by msh04.myshophosting.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.88) (envelope-from <cngroves.std@gmail.com>) id 1ciC6o-002C3U-PS for core@ietf.org; Mon, 27 Feb 2017 14:36:22 +1100
To: core@ietf.org
References: <9966516C6EB5FC4381E05BF80AA55F77012A864782@US70UWXCHMBA05.zam.alcatel-lucent.com> <B92E9C86-68A6-47D0-933C-AE7D00B4DDCB@tzi.org> <9966516C6EB5FC4381E05BF80AA55F77012A8651AB@US70UWXCHMBA05.zam.alcatel-lucent.com>
From: Christian Groves <cngroves.std@gmail.com>
Message-ID: <c59fa07f-182b-009a-5f01-f550503370d2@gmail.com>
Date: Mon, 27 Feb 2017 14:36:21 +1100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <9966516C6EB5FC4381E05BF80AA55F77012A8651AB@US70UWXCHMBA05.zam.alcatel-lucent.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - msh04.myshophosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - gmail.com
X-Get-Message-Sender-Via: msh04.myshophosting.com: authenticated_id: christian@kunstmade.com.au
X-Authenticated-Sender: msh04.myshophosting.com: christian@kunstmade.com.au
X-Source:
X-Source-Args:
X-Source-Dir:
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/cri4ITlRBjflUSVVFJoDX5kmDQo>
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: Mon, 27 Feb 2017 03:36:28 -0000

Hello Tim,

Given the overlap in "lt" it was either people's resource directory 
implementations or binding attribute implementations that would be 
impacted. It seemed that there were more resource directory 
implementations and draft-ietf-core-resource-directory was further along 
so it seemed the preference of the list was to change 
draft-ietf-core-dynlink.

As editor i'll leave it up to the Chairs to determine which should 
change. We could leave gt as it is and only change lt if it helps.

Regards, Christian


On 27/02/2017 6:18 AM, Carey, Timothy (Nokia - US) wrote:
> Carsten,
> Probably for gt and lt; they have been used in LWM2M since it looks like around 2013.
> Changing the values to gth and lth will probably affect implementations.
>
> BR,
> Tim
>
> -----Original Message-----
> From: Carsten Bormann [mailto:cabo@tzi.org]
> Sent: Saturday, February 25, 2017 12:09 PM
> To: Carey, Timothy (Nokia - US) <timothy.carey@nokia.com>
> Cc: core@ietf.org WG <core@ietf.org>
> Subject: Re: [core] Binding Attributes in draft-groves-core-dynlink-02
>
> (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

v2.23.0 | Report a Bug | By Email