--- 1/draft-ietf-core-dynlink-10.txt 2020-07-13 12:13:20.669564437 -0700 +++ 2/draft-ietf-core-dynlink-11.txt 2020-07-13 12:13:20.797567674 -0700 @@ -1,25 +1,19 @@ -CoRE Working Group Z. Shelby -Internet-Draft ARM -Intended status: Informational M. Koster -Expires: January 23, 2020 SmartThings - C. Groves - - J. Zhu - Huawei - B. Silverajan, Ed. - Tampere University - July 22, 2019 +CoRE Working Group M. Koster +Internet-Draft SmartThings +Intended status: Informational B. Silverajan, Ed. +Expires: January 14, 2021 Tampere University + July 13, 2020 Dynamic Resource Linking for Constrained RESTful Environments - draft-ietf-core-dynlink-10 + draft-ietf-core-dynlink-11 Abstract This specification defines Link Bindings, which provide dynamic linking of state updates between resources, either on an endpoint or between endpoints, for systems using CoAP (RFC7252). This specification also defines Conditional Notification Attributes that work with Link Bindings or with CoAP Observe (RFC7641). Editor note @@ -35,69 +29,69 @@ 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 https://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 January 23, 2020. + This Internet-Draft will expire on January 14, 2021. Copyright Notice - Copyright (c) 2019 IETF Trust and the persons identified as the + Copyright (c) 2020 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 (https://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. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. Conditional Notification Attributes . . . . . . . . . . . . . 4 3.1. Attribute Definitions . . . . . . . . . . . . . . . . . . 4 3.1.1. Minimum Period (pmin) . . . . . . . . . . . . . . . . 5 - 3.1.2. Maximum Period (pmax) . . . . . . . . . . . . . . . . 6 - 3.1.3. Change Step (st) . . . . . . . . . . . . . . . . . . 6 + 3.1.2. Maximum Period (pmax) . . . . . . . . . . . . . . . . 5 + 3.1.3. Change Step (st) . . . . . . . . . . . . . . . . . . 5 3.1.4. Greater Than (gt) . . . . . . . . . . . . . . . . . . 6 - 3.1.5. Less Than (lt) . . . . . . . . . . . . . . . . . . . 7 - 3.1.6. Notification Band (band) . . . . . . . . . . . . . . 7 + 3.1.5. Less Than (lt) . . . . . . . . . . . . . . . . . . . 6 + 3.1.6. Notification Band (band) . . . . . . . . . . . . . . 6 3.2. Server processing of Conditional Notification Attributes 8 - 4. Link Bindings . . . . . . . . . . . . . . . . . . . . . . . . 9 - 4.1. The "bind" attribute and Binding Methods . . . . . . . . 10 - 4.1.1. Polling . . . . . . . . . . . . . . . . . . . . . . . 11 - 4.1.2. Observe . . . . . . . . . . . . . . . . . . . . . . . 11 - 4.1.3. Push . . . . . . . . . . . . . . . . . . . . . . . . 12 - 4.1.4. Execute . . . . . . . . . . . . . . . . . . . . . . . 12 - 4.2. Link Relation . . . . . . . . . . . . . . . . . . . . . . 12 - 5. Binding Table . . . . . . . . . . . . . . . . . . . . . . . . 13 - 6. Implementation Considerations . . . . . . . . . . . . . . . . 14 - 7. Security Considerations . . . . . . . . . . . . . . . . . . . 15 - 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15 - 8.1. Resource Type value 'core.bnd' . . . . . . . . . . . . . 15 - 8.2. Link Relation Type . . . . . . . . . . . . . . . . . . . 15 - 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 16 - 10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 16 + 4. Link Bindings . . . . . . . . . . . . . . . . . . . . . . . . 8 + 4.1. The "bind" attribute and Binding Methods . . . . . . . . 9 + 4.1.1. Polling . . . . . . . . . . . . . . . . . . . . . . . 10 + 4.1.2. Observe . . . . . . . . . . . . . . . . . . . . . . . 10 + 4.1.3. Push . . . . . . . . . . . . . . . . . . . . . . . . 11 + 4.1.4. Execute . . . . . . . . . . . . . . . . . . . . . . . 11 + 4.2. Link Relation . . . . . . . . . . . . . . . . . . . . . . 11 + 5. Binding Table . . . . . . . . . . . . . . . . . . . . . . . . 12 + 6. Implementation Considerations . . . . . . . . . . . . . . . . 13 + 7. Security Considerations . . . . . . . . . . . . . . . . . . . 14 + 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14 + 8.1. Resource Type value 'core.bnd' . . . . . . . . . . . . . 14 + 8.2. Link Relation Type . . . . . . . . . . . . . . . . . . . 14 + 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 15 + 10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 15 11. Changelog . . . . . . . . . . . . . . . . . . . . . . . . . . 16 12. References . . . . . . . . . . . . . . . . . . . . . . . . . 18 12.1. Normative References . . . . . . . . . . . . . . . . . . 18 - 12.2. Informative References . . . . . . . . . . . . . . . . . 19 + 12.2. Informative References . . . . . . . . . . . . . . . . . 18 Appendix A. Examples . . . . . . . . . . . . . . . . . . . . . . 19 A.1. Minimum Period (pmin) example . . . . . . . . . . . . . . 19 A.2. Maximum Period (pmax) example . . . . . . . . . . . . . . 20 A.3. Greater Than (gt) example . . . . . . . . . . . . . . . . 21 A.4. Greater Than (gt) and Period Max (pmax) example . . . . . 22 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 23 1. Introduction IETF Standards for machine to machine communication in constrained @@ -666,30 +661,50 @@ Sasin, Cedric Chauvenet, Daniel Gavelle and Carsten Bormann who have provided useful discussion and input to the concepts in this specification. Christian Amsuss supplied a comprehensive review of draft -06. Hannes Tschofenig and Mert Ocak highlighted syntactical corrections in the usage of pmax and pmin in a query. Discussions with Ari Keraenen led to the addition of an extra binding method supporting POST operations. 10. Contributors + Christian Groves + Australia + email: cngroves.std@gmail.com + + Zach Shelby + ARM + Vuokatti + FINLAND + phone: +358 40 7796297 + email: zach.shelby@arm.com + Matthieu Vial Schneider-Electric Grenoble France + phone: +33 (0)47657 6522 + eMail: matthieu.vial@schneider-electric.com - Phone: +33 (0)47657 6522 - EMail: matthieu.vial@schneider-electric.com + Jintao Zhu + Huawei + Xi'an, Shaanxi Province + China + email: jintao.zhu@huawei.com 11. Changelog + draft-ietf-core-dynlink-11 + + o Updates to author list + draft-ietf-core-dynlink-10 o Binding methods now support both POST and PUT operations for server push. draft-ietf-core-dynlink-09 o Corrections in Table 1, Table 2, Figure 2. o Clarifications for additional operations to binding table added in @@ -717,23 +733,20 @@ draft-ietf-core-dynlink-06 o Document restructure and refactoring into three main sections o Clarifications on band usage o Implementation considerations introduced o Additional text on security considerations - - draft-ietf-core-dynlink-05 - o Addition of a band modifier for gt and lt, adapted from draft- groves-core-obsattr o Removed statement prescribing gt MUST be greater than lt draft-ietf-core-dynlink-03 o General: Reverted to using "gt" and "lt" from "gth" and "lth" for this draft owing to concerns raised that the attributes are already used in LwM2M with the original names "gt" and "lt". @@ -806,21 +819,21 @@ [RFC8288] Nottingham, M., "Web Linking", RFC 8288, DOI 10.17487/RFC8288, October 2017, . 12.2. Informative References [I-D.irtf-t2trg-rest-iot] Keranen, A., Kovatsch, M., and K. Hartke, "RESTful Design for Internet of Things Systems", draft-irtf-t2trg-rest- - iot-04 (work in progress), July 2019. + iot-06 (work in progress), May 2020. [RFC7252] Shelby, Z., Hartke, K., and C. Bormann, "The Constrained Application Protocol (CoAP)", RFC 7252, DOI 10.17487/RFC7252, June 2014, . [RFC7641] Hartke, K., "Observing Resources in the Constrained Application Protocol (CoAP)", RFC 7641, DOI 10.17487/RFC7641, September 2015, . @@ -1000,46 +1013,24 @@ 40 | | Payload: "26 Cel" 41 | | 42 | | Figure 6: Client registers and receives one notification of the current state, one when pmax time expires and one of a new state when it passes through the greater than threshold of 25. Authors' Addresses - Zach Shelby - ARM - Kidekuja 2 - Vuokatti 88600 - FINLAND - - Phone: +358407796297 - Email: zach.shelby@arm.com Michael Koster SmartThings 665 Clyde Avenue Mountain View 94043 USA Email: michael.koster@smartthings.com - - Christian Groves - Australia - - Email: cngroves.std@gmail.com - - Jintao Zhu - Huawei - No.127 Jinye Road, Huawei Base, High-Tech Development District - Xi'an, Shaanxi Province - China - - Email: jintao.zhu@huawei.com - Bilhanan Silverajan (editor) Tampere University Kalevantie 4 Tampere FI-33100 Finland Email: bilhanan.silverajan@tuni.fi