Binding Attribute Scope
draft-groves-core-bas-01

Document Type Active Internet-Draft (individual)
Last updated 2017-03-13
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
CoRE Working Group                                             C. Groves
Internet-Draft                                                   W. Yang
Intended status: Standards Track                                  Huawei
Expires: September 14, 2017                               March 13, 2017

                        Binding Attribute Scope
                        draft-groves-core-bas-01

Abstract

   This document specifies an additional CoAP binding attribute that
   allows binding attributes to be scoped to an item (sub-resource) in a
   collection resource.  This allows synchronisation of multiple
   resources in a collection based on the value of one resource.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on September 14, 2017.

Copyright Notice

   Copyright (c) 2017 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Groves & Yang          Expires September 14, 2017               [Page 1]
Internet-Draft             Binding Att. Scope                 March 2017

Table of Contents

   1.  Requirements Language . . . . . . . . . . . . . . . . . . . .   2
   2.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     2.1.  Usage of a collection . . . . . . . . . . . . . . . . . .   3
     2.2.  Multiple Conditions . . . . . . . . . . . . . . . . . . .   3
   3.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   4
   4.  Binding Attributes  . . . . . . . . . . . . . . . . . . . . .   4
     4.1.  Binding Attribute Scope . . . . . . . . . . . . . . . . .   5
     4.2.  Interactions  . . . . . . . . . . . . . . . . . . . . . .   5
     4.3.  Examples  . . . . . . . . . . . . . . . . . . . . . . . .   5
       4.3.1.  Example 1 - Item Binding Attribute  . . . . . . . . .   6
       4.3.2.  Example 2 - Mutliple Observes . . . . . . . . . . . .   6
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   6
   8.  Changelog . . . . . . . . . . . . . . . . . . . . . . . . . .   7
   9.  Normative References  . . . . . . . . . . . . . . . . . . . .   7
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   8

1.  Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in
   [RFC2119].

2.  Introduction

   In some cases a CoAP client may require a notification of the value
   of a resource based on some condition associated with another
   resource.  For example: a client wants to be notified of the machine
   state once a temperature sensor threshold is crossed.  Currently the
   only way to implement this is for a client to be notified of the
   temperature resource change and then for the client to do a seperate
   read of the required resources.  It would be more efficient to
   provide the information in a single response.

   This document defines a new "Binding Attribute Scope" binding
   attribute to allow a client to request collection resource state
   synchronisation based on a conditional value of an item in the
   collection resource.

   The "Binding Attribute Scope" (bas) attribute is set on a collection
   and is used to indicate which item in a collection an Observe and
Show full document text