draft-ietf-core-interfaces-01.txt   draft-ietf-core-interfaces-02.txt 
CoRE Z. Shelby CoRE Z. Shelby
Internet-Draft ARM Internet-Draft ARM
Intended status: Informational M. Vial Intended status: Informational M. Vial
Expires: June 14, 2014 Schneider-Electric Expires: May 13, 2015 Schneider-Electric
December 11, 2013 November 9, 2014
CoRE Interfaces CoRE Interfaces
draft-ietf-core-interfaces-01 draft-ietf-core-interfaces-02
Abstract Abstract
This document defines well-known REST interface descriptions for This document defines well-known REST interface descriptions for
Batch, Sensor, Parameter and Actuator types for use in contrained web Batch, Sensor, Parameter and Actuator types for use in contrained web
servers using the CoRE Link Format. A short reference is provided servers using the CoRE Link Format. A short reference is provided
for each type that can be efficiently included in the interface for each type that can be efficiently included in the interface
description attribute of the CoRE Link Format. These descriptions description attribute of the CoRE Link Format. These descriptions
are intended to be for general use in resource designs or for are intended to be for general use in resource designs or for
inclusion in more specific interface profiles. In addition, this inclusion in more specific interface profiles. In addition, this
skipping to change at page 1, line 41 skipping to change at page 1, line 41
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on June 14, 2014. This Internet-Draft will expire on May 13, 2015.
Copyright Notice Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the Copyright (c) 2014 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 2, line 28 skipping to change at page 2, line 28
3.1.1. Path template . . . . . . . . . . . . . . . . . . . . 5 3.1.1. Path template . . . . . . . . . . . . . . . . . . . . 5
3.1.2. Resource Type . . . . . . . . . . . . . . . . . . . . 5 3.1.2. Resource Type . . . . . . . . . . . . . . . . . . . . 5
3.1.3. Interface Description . . . . . . . . . . . . . . . . 5 3.1.3. Interface Description . . . . . . . . . . . . . . . . 5
3.1.4. Data type . . . . . . . . . . . . . . . . . . . . . . 6 3.1.4. Data type . . . . . . . . . . . . . . . . . . . . . . 6
3.2. Discovery . . . . . . . . . . . . . . . . . . . . . . . . 6 3.2. Discovery . . . . . . . . . . . . . . . . . . . . . . . . 6
3.3. Versioning . . . . . . . . . . . . . . . . . . . . . . . . 6 3.3. Versioning . . . . . . . . . . . . . . . . . . . . . . . . 6
4. Bindings . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 4. Bindings . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
4.1. Format . . . . . . . . . . . . . . . . . . . . . . . . . . 7 4.1. Format . . . . . . . . . . . . . . . . . . . . . . . . . . 7
4.2. Binding methods . . . . . . . . . . . . . . . . . . . . . 8 4.2. Binding methods . . . . . . . . . . . . . . . . . . . . . 8
4.3. Binding table . . . . . . . . . . . . . . . . . . . . . . 9 4.3. Binding table . . . . . . . . . . . . . . . . . . . . . . 9
5. Interface Descriptions . . . . . . . . . . . . . . . . . . . . 10 5. Interface Descriptions . . . . . . . . . . . . . . . . . . . . 9
5.1. Link List . . . . . . . . . . . . . . . . . . . . . . . . 11 5.1. Link List . . . . . . . . . . . . . . . . . . . . . . . . 11
5.2. Batch . . . . . . . . . . . . . . . . . . . . . . . . . . 11 5.2. Batch . . . . . . . . . . . . . . . . . . . . . . . . . . 11
5.3. Linked Batch . . . . . . . . . . . . . . . . . . . . . . . 12 5.3. Linked Batch . . . . . . . . . . . . . . . . . . . . . . . 12
5.4. Sensor . . . . . . . . . . . . . . . . . . . . . . . . . . 13 5.4. Sensor . . . . . . . . . . . . . . . . . . . . . . . . . . 13
5.5. Parameter . . . . . . . . . . . . . . . . . . . . . . . . 14 5.5. Parameter . . . . . . . . . . . . . . . . . . . . . . . . 14
5.6. Read-only Parameter . . . . . . . . . . . . . . . . . . . 14 5.6. Read-only Parameter . . . . . . . . . . . . . . . . . . . 14
5.7. Actuator . . . . . . . . . . . . . . . . . . . . . . . . . 15 5.7. Actuator . . . . . . . . . . . . . . . . . . . . . . . . . 15
5.8. Binding . . . . . . . . . . . . . . . . . . . . . . . . . 15 5.8. Binding . . . . . . . . . . . . . . . . . . . . . . . . . 15
5.9. Resource Observation Attributes . . . . . . . . . . . . . 16 5.9. Resource Observation Attributes . . . . . . . . . . . . . 16
5.10. Future Interfaces . . . . . . . . . . . . . . . . . . . . 18 5.10. Future Interfaces . . . . . . . . . . . . . . . . . . . . 17
5.11. WADL Description . . . . . . . . . . . . . . . . . . . . . 18 5.11. WADL Description . . . . . . . . . . . . . . . . . . . . . 17
6. Security Considerations . . . . . . . . . . . . . . . . . . . 22 6. Security Considerations . . . . . . . . . . . . . . . . . . . 21
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 22 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 21
8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 22 8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 21
9. Changelog . . . . . . . . . . . . . . . . . . . . . . . . . . 22 9. Changelog . . . . . . . . . . . . . . . . . . . . . . . . . . 21
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 23 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 22
10.1. Normative References . . . . . . . . . . . . . . . . . . . 23 10.1. Normative References . . . . . . . . . . . . . . . . . . . 22
10.2. Informative References . . . . . . . . . . . . . . . . . . 23 10.2. Informative References . . . . . . . . . . . . . . . . . . 23
Appendix A. Profile example . . . . . . . . . . . . . . . . . . . 24 Appendix A. Profile example . . . . . . . . . . . . . . . . . . . 23
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 25 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 24
1. Introduction 1. Introduction
The Constrained RESTful Environments (CoRE) working group aims at The Constrained RESTful Environments (CoRE) working group aims at
realizing the REST architecture in a suitable form for the most realizing the REST architecture in a suitable form for the most
constrained nodes (e.g. 8-bit microcontrollers with limited RAM and constrained nodes (e.g. 8-bit microcontrollers with limited RAM and
ROM) and networks (e.g. 6LoWPAN). CoRE is aimed at machine-to- ROM) and networks (e.g. 6LoWPAN). CoRE is aimed at machine-to-
machine (M2M) applications such as smart energy and building machine (M2M) applications such as smart energy and building
automation. automation.
The discovery of resources offered by a constrained server is very The discovery of resources offered by a constrained server is very
important in machine-to-machine applications where there are no important in machine-to-machine applications where there are no
humans in the loop and static interfaces result in fragility. The humans in the loop and static interfaces result in fragility. The
discovery of resources provided by an HTTP Web Server is typically discovery of resources provided by an HTTP Web Server is typically
called Web Linking [RFC5988]. The use of Web Linking for the called Web Linking [RFC5988]. The use of Web Linking for the
description and discovery of resources hosted by constrained web description and discovery of resources hosted by constrained web
servers is specified by the CoRE Link Format servers is specified by the CoRE Link Format [RFC6690] and can be
[I-D.ietf-core-link-format] and can be used by CoAP used by CoAP [RFC7252] or HTTP servers. The CoRE Link Format defines
[I-D.ietf-core-coap] or HTTP servers. The CoRE Link Format defines
an attribute that can be used to describe the REST interface of a an attribute that can be used to describe the REST interface of a
resource, and may include a link to a description document. This resource, and may include a link to a description document. This
memo describes how other specifications can combine resources with a memo describes how other specifications can combine resources with a
well-known interface to create new CoRE RESTful profiles. A CoRE well-known interface to create new CoRE RESTful profiles. A CoRE
profile is based on the concept of Function Set, which is a group of profile is based on the concept of Function Set, which is a group of
REST resources providing a service in a distributed system. In REST resources providing a service in a distributed system. In
addition, the notion of Binding is introduced in order to create a addition, the notion of Binding is introduced in order to create a
synchronization link between two resources. This document also synchronization link between two resources. This document also
defines well-known interface descriptions for Batch, Sensor, defines well-known interface descriptions for Batch, Sensor,
Parameter and Actuator types to compose new Function Sets or for Parameter and Actuator types to compose new Function Sets or for
skipping to change at page 3, line 44 skipping to change at page 3, line 43
provided for each type that can be efficiently included in the provided for each type that can be efficiently included in the
interface description (if=) attribute of the CoRE Link Format. interface description (if=) attribute of the CoRE Link Format.
2. Terminology 2. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
This specification requires readers to be familiar with all the terms This specification requires readers to be familiar with all the terms
and concepts that are discussed in [RFC5988] and and concepts that are discussed in [RFC5988] and [RFC6690]. This
[I-D.ietf-core-link-format]. This specification makes use of the specification makes use of the following additional terminology:
following additional terminology:
Function Set: A group of well-known REST resources that provides a Function Set: A group of well-known REST resources that provides a
particular service. particular service.
Profile: A group of well-known Function Sets defined by a Profile: A group of well-known Function Sets defined by a
specification. specification.
Device: An IP smart object running a web server that hosts a group Device: An IP smart object running a web server that hosts a group
of Function Set instances from a profile. of Function Set instances from a profile.
skipping to change at page 5, line 35 skipping to change at page 5, line 32
template. All other path segments should be fixed. template. All other path segments should be fixed.
3.1.2. Resource Type 3.1.2. Resource Type
Each root resource of a Function Set is assigned a Resource Type Each root resource of a Function Set is assigned a Resource Type
parameter, therefore making it possible to discover it. Each sub- parameter, therefore making it possible to discover it. Each sub-
resource of a Function Set is also assigned a Resource Type resource of a Function Set is also assigned a Resource Type
parameter. This Resource Type is used for resource discovery and is parameter. This Resource Type is used for resource discovery and is
usually necessary to discover optional resources supported on a usually necessary to discover optional resources supported on a
specific device. The Resource Type of a Function Set may also be specific device. The Resource Type of a Function Set may also be
used for service discovery and can be exported to DNS-SD used for service discovery and can be exported to DNS-SD [RFC6763]
[I-D.cheshire-dnsext-dns-sd] for example. for example.
The Resource Type parameter defines the value that should be included The Resource Type parameter defines the value that should be included
in the rt= field of the CoRE Link Format when describing a link to in the rt= field of the CoRE Link Format when describing a link to
this resource. The value SHOULD be in the form "namespace.type" for this resource. The value SHOULD be in the form "namespace.type" for
root resources and "namespace.type.subtype" for sub-resources. This root resources and "namespace.type.subtype" for sub-resources. This
naming convention facilitates resource type filtering with the naming convention facilitates resource type filtering with the
/.well-known/core resource. However a profile could allow mixing in /.well-known/core resource. However a profile could allow mixing in
foreign namespace references within a Function Set to import external foreign namespace references within a Function Set to import external
references from other object models (e.g. SenML and UCUM). references from other object models (e.g. SenML and UCUM).
skipping to change at page 6, line 28 skipping to change at page 6, line 24
that is returned in response to a GET for that resource or accepted that is returned in response to a GET for that resource or accepted
with a PUT. The interfaces defined in Section 5 make use of plain with a PUT. The interfaces defined in Section 5 make use of plain
text and SenML Media types for the actual format of this data. A text and SenML Media types for the actual format of this data. A
profile may restrict the list of supported content types for the CoRE profile may restrict the list of supported content types for the CoRE
interfaces or define new interfaces with new content types. interfaces or define new interfaces with new content types.
3.2. Discovery 3.2. Discovery
A device conforming to a profile SHOULD make its resources A device conforming to a profile SHOULD make its resources
discoverable by providing links to the resources on the path /.well- discoverable by providing links to the resources on the path /.well-
known/core as defined in [I-D.ietf-core-link-format]. All resources known/core as defined in [RFC6690]. All resources hosted on a device
hosted on a device SHOULD be discoverable either with a direct link SHOULD be discoverable either with a direct link in /.well-known/core
in /.well-known/core or by following successive links starting from or by following successive links starting from /.well-known/core.
/.well-known/core.
The root path of a Function Set instance SHOULD be directly The root path of a Function Set instance SHOULD be directly
referenced in /.well-known/core in order to offer discovery at the referenced in /.well-known/core in order to offer discovery at the
first discovery stage. A device with more than 10 individual first discovery stage. A device with more than 10 individual
resources SHOULD only expose Function Set instances in /.well-known/ resources SHOULD only expose Function Set instances in /.well-known/
core to limit the size of this resource. core to limit the size of this resource.
In addition, a device MAY register its resources to a Resource In addition, a device MAY register its resources to a Resource
Directory using the registration interface defined in Directory using the registration interface defined in
[I-D.ietf-core-resource-directory] if such a directory is available. [I-D.ietf-core-resource-directory] if such a directory is available.
skipping to change at page 12, line 30 skipping to change at page 12, line 20
{ "n": "humidity", "v": 80, "u": "%RH" }], { "n": "humidity", "v": 80, "u": "%RH" }],
} }
5.3. Linked Batch 5.3. Linked Batch
The Linked Batch interface is an extension of the Batch interface. The Linked Batch interface is an extension of the Batch interface.
Contrary to the basic Batch which is a collection statically defined Contrary to the basic Batch which is a collection statically defined
by the web server, a Linked Batch is dynamically controlled by a web by the web server, a Linked Batch is dynamically controlled by a web
client. A Linked Batch resource has no sub-resources. Instead the client. A Linked Batch resource has no sub-resources. Instead the
resources forming the batch are referenced using Web Linking resources forming the batch are referenced using Web Linking
[RFC5988] and the CoRE Link Format [I-D.ietf-core-link-format]. A [RFC5988] and the CoRE Link Format [RFC6690]. A request with a POST
request with a POST method and a content type of application/ method and a content type of application/link-format simply appends
link-format simply appends new resources to the collection. The new resources to the collection. The links in the payload MUST
links in the payload MUST reference a resource on the web server with reference a resource on the web server with an absolute path. A
an absolute path. A DELETE request empties the current collection of DELETE request empties the current collection of links. All other
links. All other requests available for a basic Batch are still requests available for a basic Batch are still valid for a Linked
valid for a Linked Batch. Batch.
The following example interacts with a Linked Batch /l and creates a The following example interacts with a Linked Batch /l and creates a
collection containing /s/light, /s/temp and /s/humidity in 2 steps. collection containing /s/light, /s/temp and /s/humidity in 2 steps.
Req: POST /l (Content-type: application/link-format) Req: POST /l (Content-type: application/link-format)
</s/light>,</s/temp> </s/light>,</s/temp>
Res: 2.04 Changed Res: 2.04 Changed
Req: GET /l Req: GET /l
Res: 2.05 Content (application/senml+json) Res: 2.05 Content (application/senml+json)
skipping to change at page 16, line 40 skipping to change at page 16, line 40
its link description SHOULD support these observation parameters. its link description SHOULD support these observation parameters.
The Change Step parameter can only be supported on resources with an The Change Step parameter can only be supported on resources with an
atomic numeric value. atomic numeric value.
These query parameters MUST be treated as resources that are read These query parameters MUST be treated as resources that are read
using GET and set using PUT, and MUST NOT be included in the Observe using GET and set using PUT, and MUST NOT be included in the Observe
request. Multiple parameters MAY be set at the same time by request. Multiple parameters MAY be set at the same time by
including the values in the query string of a PUT. Before being set, including the values in the query string of a PUT. Before being set,
these parameters have no default value. these parameters have no default value.
+--------------------+------------------+------------------+ +--------------+----------------+------------------+
| Resource | Parameter | Data Format | | Resource | Parameter | Data Format |
+--------------------+------------------+------------------+ +--------------+----------------+------------------+
| Minimum Period (s) | /{resource}?pmin | xsd:integer (>0) | | Change Step | /{resource}?st | xsd:decimal (>0) |
| Maximum Period (s) | /{resource}?pmax | xsd:integer (>0) | | Less Than | /{resource}?lt | xsd:decimal |
| Change Step | /{resource}?st | xsd:decimal (>0) | | Greater Than | /{resource}?gt | xsd:decimal |
| Less Than | /{resource}?lt | xsd:decimal | +--------------+----------------+------------------+
| Greater Than | /{resource}?gt | xsd:decimal |
+--------------------+------------------+------------------+
Minimum Period: When set, the minimum period indicates the minimum
time in seconds the server SHOULD wait between sending
notifications. In the absence of this parameter, the minimum
period is up to the server.
Maximum Period: When set, the maximum period indicated the maximum
time in seconds the server SHOULD wait between sending
notifications (regardless if it has changed). In the absence of
this parameter, the maximum period is up to the server. The
maximum period MUST be greater than the minimum period parameter
(if present).
Change Step: When set, the change step indicates how much the value Change Step: When set, the change step indicates how much the value
of a resource SHOULD change before sending a new notification of a resource SHOULD change before sending a new notification
(compared to the value of the last notification). This parameter (compared to the value of the last notification). This parameter
has lower priority than the period parameters, thus even if the has lower priority than the period parameters, thus even if the
change step has been fulfilled, the time since the last change step has been fulfilled, the time since the last
notification SHOULD be between pmin and pmax. notification SHOULD be between pmin and pmax.
Less Than: When set, the value of the resource MUST be less than Less Than: When set, the value of the resource MUST be less than
this parameter in order to send a new notification. This this parameter in order to send a new notification. This
parameter has lower priority than the period parameters. parameter has lower priority than the period parameters.
Greater Than: When set, the value of the resource MUST be greater Greater Than: When set, the value of the resource MUST be greater
than this parameter in order to send a new notification. This than this parameter in order to send a new notification. This
parameter has lower priority than the period parameters. parameter has lower priority than the period parameters.
The following example shows an Observation request using these query
parameters. Here the value of Observe indicates the number of
seconds since the observation was made to show the time.
Req PUT /s/temp?pmin=10&pmax=60&st=1
Res: 2.04 Changed
Req: GET Observe /s/temp
Res: 2.05 Content Observe:0 (text/plain)
23.2
Res: 2.05 Content Observe:60 (text/plain)
23.0
Res: 2.05 Content Observe:80 (text/plain)
22.0
Res: 2.05 Content Observe:140 (text/plain)
21.8
The following example shows a request to check the current value of
the pmin attribute of the Observable resource from the last example.
Req: GET /s/temp?pmin
Res: 2.05 Content (text/plain)
10
5.10. Future Interfaces 5.10. Future Interfaces
It is expected that further interface descriptions will be defined in It is expected that further interface descriptions will be defined in
this and other specifications. Potential interfaces to be considered this and other specifications. Potential interfaces to be considered
for this specifications include: for this specifications include:
Collection: This resource would be a container that allows sub- Collection: This resource would be a container that allows sub-
resources to be added or removed. resources to be added or removed.
5.11. WADL Description 5.11. WADL Description
skipping to change at page 22, line 38 skipping to change at page 21, line 44
Acknowledgement is given to colleagues from the SENSEI project who Acknowledgement is given to colleagues from the SENSEI project who
were critical in the initial development of the well-known REST were critical in the initial development of the well-known REST
interface concept, to members of the IPSO Alliance where further interface concept, to members of the IPSO Alliance where further
requirements for interface types have been discussed, and to Szymon requirements for interface types have been discussed, and to Szymon
Sasin, Cedric Chauvenet, Daniel Gavelle and Carsten Bormann who have Sasin, Cedric Chauvenet, Daniel Gavelle and Carsten Bormann who have
provided useful discussion and input to the concepts in this provided useful discussion and input to the concepts in this
document. document.
9. Changelog 9. Changelog
Changes from -01 to -02
o Updated the date and version, fixed references.
o Removed pmin and pmax observe parameters [Ticket #336]
Changes from -00 to WG Document -01 Changes from -00 to WG Document -01
o Improvements to the Function Set section. o Improvements to the Function Set section.
Changes from -05 to WG Document -00 Changes from -05 to WG Document -00
o Updated the date and version. o Updated the date and version.
Changes from -04 to -05 Changes from -04 to -05
o Made the Observation control parameters to be treated as resources o Made the Observation control parameters to be treated as resources
rather than Observe query parameters. Added Less Than and Greater rather than Observe query parameters. Added Less Than and Greater
Than parameters. Than parameters.
Changes from -03 to -04 Changes from -03 to -04
o Draft refresh o Draft refresh
Changes from -02 to -03 Changes from -02 to -03
skipping to change at page 23, line 34 skipping to change at page 22, line 48
o Added the Linked Batch interface. o Added the Linked Batch interface.
o Improved the WADL interface definition. o Improved the WADL interface definition.
o Added a simple profile example. o Added a simple profile example.
10. References 10. References
10.1. Normative References 10.1. Normative References
[I-D.ietf-core-link-format]
Shelby, Z., "CoRE Link Format",
draft-ietf-core-link-format-14 (work in progress),
June 2012.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC5988] Nottingham, M., "Web Linking", RFC 5988, October 2010. [RFC5988] Nottingham, M., "Web Linking", RFC 5988, October 2010.
10.2. Informative References [RFC6690] Shelby, Z., "Constrained RESTful Environments (CoRE) Link
Format", RFC 6690, August 2012.
[I-D.cheshire-dnsext-dns-sd]
Cheshire, S. and M. Krochmal, "DNS-Based Service
Discovery", draft-cheshire-dnsext-dns-sd-11 (work in
progress), December 2011.
[I-D.ietf-core-coap] 10.2. Informative References
Shelby, Z., Hartke, K., and C. Bormann, "Constrained
Application Protocol (CoAP)", draft-ietf-core-coap-18
(work in progress), June 2013.
[I-D.ietf-core-observe] [I-D.ietf-core-observe]
Hartke, K., "Observing Resources in CoAP", Hartke, K., "Observing Resources in CoAP",
draft-ietf-core-observe-11 (work in progress), draft-ietf-core-observe-15 (work in progress),
October 2013. October 2014.
[I-D.ietf-core-resource-directory] [I-D.ietf-core-resource-directory]
Shelby, Z., Krco, S., and C. Bormann, "CoRE Resource Shelby, Z., Bormann, C., and S. Krco, "CoRE Resource
Directory", draft-ietf-core-resource-directory-00 (work in Directory", draft-ietf-core-resource-directory-01 (work in
progress), June 2013. progress), December 2013.
[RFC6763] Cheshire, S. and M. Krochmal, "DNS-Based Service
Discovery", RFC 6763, February 2013.
[RFC7252] Shelby, Z., Hartke, K., and C. Bormann, "The Constrained
Application Protocol (CoAP)", RFC 7252, June 2014.
Appendix A. Profile example Appendix A. Profile example
The following is a short definition of simple profile. This The following is a short definition of simple profile. This
simplistic profile is for use in the examples of this document. simplistic profile is for use in the examples of this document.
+--------------------+-----------+------------+---------+ +--------------------+-----------+------------+---------+
| Function Set | Root Path | RT | IF | | Function Set | Root Path | RT | IF |
+--------------------+-----------+------------+---------+ +--------------------+-----------+------------+---------+
| Device Description | /d | simple.dev | core.ll | | Device Description | /d | simple.dev | core.ll |
 End of changes. 21 change blocks. 
102 lines changed or deleted 59 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/