--- 1/draft-ietf-core-resource-directory-05.txt 2016-03-21 15:22:17.513558180 -0700 +++ 2/draft-ietf-core-resource-directory-06.txt 2016-03-21 15:22:17.781564803 -0700 @@ -1,22 +1,22 @@ CoRE Z. Shelby Internet-Draft M. Koster Intended status: Standards Track ARM -Expires: April 18, 2016 C. Bormann +Expires: September 22, 2016 C. Bormann Universitaet Bremen TZI P. van der Stok consultant - October 16, 2015 + March 21, 2016 CoRE Resource Directory - draft-ietf-core-resource-directory-05 + draft-ietf-core-resource-directory-06 Abstract In many M2M applications, direct discovery of resources is not practical due to sleeping nodes, disperse networks, or networks where multicast traffic is inefficient. These problems can be solved by employing an entity called a Resource Directory (RD), which hosts descriptions of resources held on other servers, allowing lookups to be performed for those resources. This document specifies the web interfaces that a Resource Directory supports in order for web @@ -32,25 +32,25 @@ 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 April 18, 2016. + This Internet-Draft will expire on September 22, 2016. Copyright Notice - Copyright (c) 2015 IETF Trust and the persons identified as the + Copyright (c) 2016 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 @@ -842,20 +842,24 @@ Req: GET /rd/4521 Res: 2.01 Content Payload: ;ct=41;rt="temperature-c";if="sensor", ;ct=41;rt="light-lux";if="sensor" 5.6. Update Endpoint Links + [This section will be removed before or as a result of a working- + group last-call if the PATCH methods do not achieve the same level of + consensus as the present document.] + A PATCH update adds, removes or changes links for the endpoint by including link update information in the payload of the update as a merge-patch+json format [RFC7396] document. One or more links are selected for update by using query filtering as specified in [RFC6690] Section 4.1 The query filter selects the links to be modified or deleted, by matching the query parameter values to the values of the link attributes. @@ -2232,21 +2236,26 @@ Srdjan Krco, Szymon Sasin, Kerry Lynn, Esko Dijk, Anders Brandt, Matthieu Vial, Mohit Sethi, Sampo Ukkola and Linyi Tian have provided helpful comments, discussions and ideas to improve and shape this document. Zach would also like to thank his colleagues from the EU FP7 SENSEI project, where many of the resource directory concepts were originally developed. 14. Changelog - changes from -04 to -05 + Changes from -05 to -06 + + o added note that the PATCH section is contingent on the progress of + the PATCH method + + Changes from -04 to -05 o added Update Endpoint Links using PATCH o http access made explicit in interface specification o Added http examples Changes from -03 to -04: o Added http response codes @@ -2358,22 +2366,22 @@ o Changed the lookup interface to accept endpoint and Domain as query string parameters to control the scope of a lookup. 15. References 15.1. Normative References [I-D.ietf-core-links-json] Li, K., Rahman, A., and C. Bormann, "Representing CoRE - Formats in JSON and CBOR", draft-ietf-core-links-json-03 - (work in progress), July 2015. + Formats in JSON and CBOR", draft-ietf-core-links-json-04 + (work in progress), November 2015. [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, . [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform Resource Identifier (URI): Generic Syntax", STD 66, RFC 3986, DOI 10.17487/RFC3986, January 2005, . @@ -2407,23 +2415,23 @@ Discovery", RFC 6763, DOI 10.17487/RFC6763, February 2013, . [RFC7396] Hoffman, P. and J. Snell, "JSON Merge Patch", RFC 7396, DOI 10.17487/RFC7396, October 2014, . 15.2. Informative References [I-D.ietf-core-interfaces] - Shelby, Z., Vial, M., and M. Koster, "CoRE Interfaces", - draft-ietf-core-interfaces-03 (work in progress), July - 2015. + Shelby, Z., Vial, M., and M. Koster, "Reusable Interface + Definitions for Constrained RESTful Environments", draft- + ietf-core-interfaces-04 (work in progress), October 2015. [RFC1034] Mockapetris, P., "Domain names - concepts and facilities", STD 13, RFC 1034, DOI 10.17487/RFC1034, November 1987, . [RFC1123] Braden, R., Ed., "Requirements for Internet Hosts - Application and Support", STD 3, RFC 1123, DOI 10.17487/RFC1123, October 1989, .