--- 1/draft-ietf-6tisch-coap-00.txt 2014-07-04 10:14:39.157685485 -0700 +++ 2/draft-ietf-6tisch-coap-01.txt 2014-07-04 10:14:39.189686251 -0700 @@ -1,104 +1,111 @@ 6TiSCH R. Sudhaakar, Ed. Internet-Draft Cisco Intended status: Standards Track P. Zand -Expires: November 7, 2014 University of Twente - May 6, 2014 +Expires: January 4, 2015 University of Twente + July 3, 2014 6TiSCH Resource Management and Interaction using CoAP - draft-ietf-6tisch-coap-00 + draft-ietf-6tisch-coap-01 Abstract The [IEEE802154e] standardizes the TSCH mode of operation and defines the mechanisms for layer 2 communication between conforming devices. 6top defines a set of commands to monitor and manage the TSCH schedule. To realize the full functionality of sensor networks and allow their adoption and use in real applications we need additional mechanisms. Specifically, we need to define how to interact with 6top, control and modify schedules, monitor parameters etc. Higher layers monitoring and management entities are then able to use these capabilities to create feedback loops. Although, there have been many custom implementations of such feedback loops between the routing, transport and MAC layers in sensor network deployments, there has been a lack of standards based approaches. The goal of the memo is to define the messaging between monitoring and management entities and the 6top layer and a mapping to the 6top commands. The document also presents a particular implementation of the generic - data model specified in [I-D.wang-6tisch-6top-interface] based on + data model specified in [I-D.ietf-6tisch-6top-interface] based on CoAP and CBOR. +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 RFC + 2119 [RFC2119]. + 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 November 7, 2014. + This Internet-Draft will expire on January 4, 2015. Copyright Notice Copyright (c) 2014 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. Table of Contents - 1. Requirements notation . . . . . . . . . . . . . . . . . . . . 2 + 1. Requirements notation . . . . . . . . . . . . . . . . . . . . 3 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 3. Scope of the document . . . . . . . . . . . . . . . . . . . . 3 4. Data Model definition for CoAP . . . . . . . . . . . . . . . 4 4.1. Naming Convention for URI schemes . . . . . . . . . . . . 4 4.2. Convention for accessing URIs . . . . . . . . . . . . . . 4 4.3. 6TiSCH Resources . . . . . . . . . . . . . . . . . . . . 5 4.3.1. Management Resources . . . . . . . . . . . . . . . . 5 4.3.2. Informational Resources . . . . . . . . . . . . . . . 7 4.3.3. Message Formats . . . . . . . . . . . . . . . . . . . 7 4.3.4. Extensible Resources . . . . . . . . . . . . . . . . 9 4.4. Example . . . . . . . . . . . . . . . . . . . . . . . . . 10 4.4.1. Request-Response . . . . . . . . . . . . . . . . . . 10 4.4.2. Publish-Subscribe . . . . . . . . . . . . . . . . . . 11 5. References . . . . . . . . . . . . . . . . . . . . . . . . . 12 5.1. Normative References . . . . . . . . . . . . . . . . . . 12 5.2. Informative References . . . . . . . . . . . . . . . . . 12 - 5.3. External Informative References . . . . . . . . . . . . . 13 - Appendix A. . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 - Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 13 + 5.3. External Informative References . . . . . . . . . . . . . 14 + Appendix A. . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 + Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 14 1. Requirements notation The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119]. 2. Introduction - The 6TiSCH Operation Sublayer (6top) [I-D.wang-6tisch-6top-interface] + The 6TiSCH Operation Sublayer (6top) [I-D.ietf-6tisch-6top-interface] describes the main commands provided to higher layers that allow them to build TSCH schedules, make routing decisions, perform TSCH configuration and control procedures and supports centralized and decentralized scheduling policies among other functionalities. However, there is still a need for specifying the methods, including message exchanges and message formats that higher layers use to invoke these command described by 6top. +------------------------------------+ | Higher Layers | @@ -122,21 +129,21 @@ well as between 6top nodes. This document also specifies an implementation of this generic message exchange and data model using CoAP as the transport mechanism. 3. Scope of the document This draft defines the communication mechanism between PCE and 6top nodes using COAP. We use the generic YANG data model defined in - [I-D.wang-6tisch-6top-interface] to define the various CoAP messages + [I-D.ietf-6tisch-6top-interface] to define the various CoAP messages and payloads. The payload used CBOR for the encoding format. The document also defines the URIs that used to identify the resources exposed by 6top. This document also defines how users can install custom resources that allow them to extend the basic resource exposed by 6top. 4. Data Model definition for CoAP 4.1. Naming Convention for URI schemes @@ -163,21 +170,21 @@ 5. Typographical conventions as described in A SHOULD be followed These guidelines MUST be followed by users who install extensible resources. It SHOULD be followed for future extensions of the data model in order to provide consistency. 4.2. Convention for accessing URIs We use the GET, POST and DELETE methods described by CoAP. These methods MUST be used in accordance with their definition in Sec. 5.8 - of [I-D.ietf-core-coap]. We have no need for the PUT method as the + of [RFC7252]. We have no need for the PUT method as the functionality of the POST method can be used for all situations that need updating or modification of a resource. The CoAP methods are mapped to 6top commands as shown in the figure below. +-------------+--------------+-------------------------+ | CoAP method | 6top command | Description | +-------------+--------------+-------------------------+ | GET | READ | Retrieves 6top resources| +-------------+--------------+-------------------------+ | POST | CREATE / | Creates/Updates a new | @@ -190,21 +197,21 @@ Figure 2: Mapping between CoAP methods and 6top commands The GET method may use queries to allow higher layer entities to perform conditional GETs or filter the results of a GET on resource that is a collection. The POST method is used in all situations where an argument needs to be passed to the 6top layer. The Content-Type option is set to 'application/cbor'. The payload is encoded using CBOR format as - described in [I-D.bormann-cbor]. + described in [RFC7049]. The DELETE method is used to invoke the 6top DELETE command on a particular resource. The GET method may use queries to allow higher layer entities to perform conditional GETs or filter the results of a GET on resource that is a collection. 4.3. 6TiSCH Resources @@ -311,29 +318,29 @@ Figure 6: Example GET message Since this resources points to the entire neighbor list, the response returns all the entries (the list of neighbors of that node) and all fields in each entry (i.e. entry for a neighbor) of the list in CBOR format. A request with a Uri-Query option may be used to retrieve only specific entries in the list. The value of Uri-Query MUST be in the ABNF format as described in [RFC5234]. - Resources that point to collection within a list, such as '/6t/ - Neighbor/TargetNodeAddr', returns only the values in the + Resources that point to collection within a list, such as + '/6t/Neighbor/TargetNodeAddr', returns only the values in the TargetNodeAddr column of the Neighbor list. The usage of the Uri- Query option has the same effect of filtering on the result. The endpoint MUST appropriately respond with a 2.05 Content or 4.04 - Not Found message as defined in [I-D.ietf-core-coap]. If the - resource is found then the payload of the response MUST contain a - CBOR representation of the data that is referenced by the URI. + Not Found message as defined in [RFC7252]. If the resource is found + then the payload of the response MUST contain a CBOR representation + of the data that is referenced by the URI. To create or update a Neighbor, the CoAP client MUST send a POST message as shown in Figure 7. The payload MUST describe the argument that is passed to 6top in CBOR format. +-------------------------------------+ Header | POST | +-------------------------------------+ Uri-Path| /6t/Neighbor | +-------------------------------------+ @@ -530,46 +537,75 @@ 5. References 5.1. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. 5.2. Informative References - [I-D.bormann-cbor] - Bormann, C. and P. Hoffman, "Concise Binary Object - Representation (CBOR)", draft-bormann-cbor-09 (work in - progress), September 2013. + [I-D.ietf-6tisch-6top-interface] + Wang, Q., Vilajosana, X., and T. Watteyne, "6TiSCH + Operation Sublayer (6top) Interface", draft-ietf-6tisch- + 6top-interface-00 (work in progress), March 2014. - [I-D.ietf-core-coap] - Shelby, Z., Hartke, K., and C. Bormann, "Constrained - Application Protocol (CoAP)", draft-ietf-core-coap-18 - (work in progress), June 2013. + [I-D.ietf-6tisch-architecture] + Thubert, P., Watteyne, T., and R. Assimiti, "An + Architecture for IPv6 over the TSCH mode of IEEE + 802.15.4e", draft-ietf-6tisch-architecture-02 (work in + progress), June 2014. + + [I-D.ietf-6tisch-coap] + Sudhaakar, R. and P. Zand, "6TiSCH Resource Management and + Interaction using CoAP", draft-ietf-6tisch-coap-00 (work + in progress), May 2014. + + [I-D.ietf-6tisch-minimal] + Vilajosana, X. and K. Pister, "Minimal 6TiSCH + Configuration", draft-ietf-6tisch-minimal-01 (work in + progress), June 2014. + + [I-D.ietf-6tisch-terminology] + Palattella, M., Thubert, P., Watteyne, T., and Q. Wang, + "Terminology in IPv6 over the TSCH mode of IEEE + 802.15.4e", draft-ietf-6tisch-terminology-01 (work in + progress), February 2014. + + [I-D.ietf-6tisch-tsch] + Watteyne, T., Palattella, M., and L. Grieco, "Using + IEEE802.15.4e TSCH in an LLN context: Overview, Problem + Statement and Goals", draft-ietf-6tisch-tsch-00 (work in + progress), November 2013. [I-D.ietf-core-observe] Hartke, K., "Observing Resources in CoAP", draft-ietf- - core-observe-11 (work in progress), October 2013. + core-observe-14 (work in progress), June 2014. - [I-D.wang-6tisch-6top-interface] + [I-D.wang-6tisch-6top-sublayer] Wang, Q., Vilajosana, X., and T. Watteyne, "6TiSCH - Operation Sublayer (6top) Interface", draft-wang-6tisch- - 6top-interface-02 (work in progress), February 2014. + Operation Sublayer (6top)", draft-wang-6tisch-6top- + sublayer-00 (work in progress), February 2014. [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform Resource Identifier (URI): Generic Syntax", STD 66, RFC 3986, January 2005. [RFC5234] Crocker, D. and P. Overell, "Augmented BNF for Syntax Specifications: ABNF", STD 68, RFC 5234, January 2008. + [RFC7049] Bormann, C. and P. Hoffman, "Concise Binary Object + Representation (CBOR)", RFC 7049, October 2013. + + [RFC7252] Shelby, Z., Hartke, K., and C. Bormann, "The Constrained + Application Protocol (CoAP)", RFC 7252, June 2014. + 5.3. External Informative References [IEEE802154e] IEEE standard for Information Technology, "IEEE std. 802.15.4e, Part. 15.4: Low-Rate Wireless Personal Area Networks (LR-WPANs) Amendment 1: MAC sublayer", April 2012. Appendix A.