[core] Binding attributes in draft-ietf-core-interfaces

Christian Groves <Christian.Groves@nteczone.com> Thu, 04 February 2016 06:48 UTC

Return-Path: <Christian.Groves@nteczone.com>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DD53A1ACCFC for <core@ietfa.amsl.com>; Wed, 3 Feb 2016 22:48:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.109
X-Spam-Level:
X-Spam-Status: No, score=0.109 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1, T_DKIM_INVALID=0.01] autolearn=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 euc2lgJFR-tw for <core@ietfa.amsl.com>; Wed, 3 Feb 2016 22:48:42 -0800 (PST)
Received: from msh03.myshophosting.com (msh03.myshophosting.com [101.0.109.158]) (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 EC7901ACCC7 for <core@ietf.org>; Wed, 3 Feb 2016 22:48:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=nteczone.com; s=default; h=Content-Transfer-Encoding:Content-Type: MIME-Version:Date:Message-ID:Subject:From:To; bh=EdjLRmYKLLmUPC1vJeJBjIt6dKjP0FAxax3vXjYhwkM=; b=JCggPZyuIUBKpUGMn0UXBtE7EL lSqMxtIvkCy4huzmUvRayRThc+jiJssK3OK3ne1m9H07Fk5idOMupvJv5n7Ze+s09qNWz1zn0TLGR B7xHcmUC6/wjnvx41VBuaMZ0ACC6Gx33/1+xpaSVhHPMbwcotqzm7nhwrhAbAZJ5WuMuf4Tb1FEvG Z8OfT0LLWHLfmaSalgVpwPwNs9N/4aQQJbJkSD4xoJ8iWAsynJdUCQQCrLBvFTiqpIqFgy90hUJiq aluH4aZ9FNqQc8orRNdmxlkoVKl+hZ0gLJTalMwXtrxdiSu68B2fovJH9kdi0jBPY6oIEgbFN2QdZ 6IBDradg==;
Received: from ppp118-209-220-84.lns20.mel8.internode.on.net ([118.209.220.84]:56534 helo=[192.168.1.22]) by msh03.myshophosting.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.86) (envelope-from <Christian.Groves@nteczone.com>) id 1aRDiY-004MK5-UL for core@ietf.org; Thu, 04 Feb 2016 17:48:38 +1100
To: core@ietf.org
From: Christian Groves <Christian.Groves@nteczone.com>
Message-ID: <56B2F440.3050506@nteczone.com>
Date: Thu, 04 Feb 2016 17:48:32 +1100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - msh03.myshophosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - nteczone.com
X-Get-Message-Sender-Via: msh03.myshophosting.com: authenticated_id: christian.groves@nteczone.com
X-Authenticated-Sender: msh03.myshophosting.com: christian.groves@nteczone.com
X-Source:
X-Source-Args:
X-Source-Dir:
Archived-At: <http://mailarchive.ietf.org/arch/msg/core/QjcUu4Tt2Ub6cwCvPIWJ-Bv2ckw>
Subject: [core] Binding attributes in draft-ietf-core-interfaces
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.15
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: Thu, 04 Feb 2016 06:48:44 -0000

Hello,

I'm reading clause 5.1/draft-ietf-core-interfaces on boundto attributes. 
It specifies the interaction between pmin/pmax attributes and the 
"change step", "Greater than" and "less than" attributes. The draft 
doesn't limit which attributes may appear so I take it its possible to 
specify all of them in a single binding. Is this correct?

If it is it leads to the issue of the interaction between the "change 
step" and "greater than" and "less than" attributes. I didn't see this 
described anywhere?

E.g. for a temperature reading if st=5, lt=10, gt=26 is set and the 
initial ambient temperature was 20 when set.
The temperature rises to 30.
I could assume there's a notification at 25 related to st=5
Then there's a notification at 26 related to gt=26
However is there a notification at 30?

The text for change step indicates "how much the value of a resource 
SHOULD change before sending a new notification (compared to the value 
of the last notification)". The last notification in this case is 26 
which would make the change step 31.

A possible alternate interpretation is that notifications only occur 
when the change step is below 10 or over 26. Alternatively a new change 
step notification above would seem superfluous if there's always a 
notification whenever the temperature changes above 26.

What was the intention with the attributes?

Regards, Christian G