draft-ietf-core-senml-13.txt   draft-ietf-core-senml-14.txt 
Network Working Group C. Jennings Network Working Group C. Jennings
Internet-Draft Cisco Internet-Draft Cisco
Intended status: Standards Track Z. Shelby Intended status: Standards Track Z. Shelby
Expires: September 3, 2018 ARM Expires: October 4, 2018 ARM
J. Arkko J. Arkko
A. Keranen A. Keranen
Ericsson Ericsson
C. Bormann C. Bormann
Universitaet Bremen TZI Universitaet Bremen TZI
March 02, 2018 April 2, 2018
Media Types for Sensor Measurement Lists (SenML) Media Types for Sensor Measurement Lists (SenML)
draft-ietf-core-senml-13 draft-ietf-core-senml-14
Abstract Abstract
This specification defines media types for representing simple sensor This specification defines media types for representing simple sensor
measurements and device parameters in the Sensor Measurement Lists measurements and device parameters in the Sensor Measurement Lists
(SenML). Representations are defined in JavaScript Object Notation (SenML). Representations are defined in JavaScript Object Notation
(JSON), Concise Binary Object Representation (CBOR), eXtensible (JSON), Concise Binary Object Representation (CBOR), Extensible
Markup Language (XML), and Efficient XML Interchange (EXI), which Markup Language (XML), and Efficient XML Interchange (EXI), which
share the common SenML data model. A simple sensor, such as a share the common SenML data model. A simple sensor, such as a
temperature sensor, could use one of these media types in protocols temperature sensor, could use one of these media types in protocols
such as HTTP or CoAP to transport the measurements of the sensor or such as HTTP or CoAP to transport the measurements of the sensor or
to be configured. to be configured.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
skipping to change at page 1, line 44 skipping to change at page 1, line 44
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 September 3, 2018. This Internet-Draft will expire on October 4, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 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
skipping to change at page 3, line 9 skipping to change at page 3, line 9
11. CDDL . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 11. CDDL . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 27 12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 27
12.1. Units Registry . . . . . . . . . . . . . . . . . . . . . 27 12.1. Units Registry . . . . . . . . . . . . . . . . . . . . . 27
12.2. SenML Label Registry . . . . . . . . . . . . . . . . . . 31 12.2. SenML Label Registry . . . . . . . . . . . . . . . . . . 31
12.3. Media Type Registrations . . . . . . . . . . . . . . . . 32 12.3. Media Type Registrations . . . . . . . . . . . . . . . . 32
12.3.1. senml+json Media Type Registration . . . . . . . . . 33 12.3.1. senml+json Media Type Registration . . . . . . . . . 33
12.3.2. sensml+json Media Type Registration . . . . . . . . 34 12.3.2. sensml+json Media Type Registration . . . . . . . . 34
12.3.3. senml+cbor Media Type Registration . . . . . . . . . 35 12.3.3. senml+cbor Media Type Registration . . . . . . . . . 35
12.3.4. sensml+cbor Media Type Registration . . . . . . . . 36 12.3.4. sensml+cbor Media Type Registration . . . . . . . . 36
12.3.5. senml+xml Media Type Registration . . . . . . . . . 37 12.3.5. senml+xml Media Type Registration . . . . . . . . . 37
12.3.6. sensml+xml Media Type Registration . . . . . . . . . 38 12.3.6. sensml+xml Media Type Registration . . . . . . . . . 39
12.3.7. senml-exi Media Type Registration . . . . . . . . . 40 12.3.7. senml-exi Media Type Registration . . . . . . . . . 40
12.3.8. sensml-exi Media Type Registration . . . . . . . . . 41 12.3.8. sensml-exi Media Type Registration . . . . . . . . . 41
12.4. XML Namespace Registration . . . . . . . . . . . . . . . 42 12.4. XML Namespace Registration . . . . . . . . . . . . . . . 42
12.5. CoAP Content-Format Registration . . . . . . . . . . . . 42 12.5. CoAP Content-Format Registration . . . . . . . . . . . . 42
13. Security Considerations . . . . . . . . . . . . . . . . . . . 43 13. Security Considerations . . . . . . . . . . . . . . . . . . . 43
14. Privacy Considerations . . . . . . . . . . . . . . . . . . . 43 14. Privacy Considerations . . . . . . . . . . . . . . . . . . . 43
15. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 43 15. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 44
16. References . . . . . . . . . . . . . . . . . . . . . . . . . 44 16. References . . . . . . . . . . . . . . . . . . . . . . . . . 44
16.1. Normative References . . . . . . . . . . . . . . . . . . 44 16.1. Normative References . . . . . . . . . . . . . . . . . . 44
16.2. Informative References . . . . . . . . . . . . . . . . . 46 16.2. Informative References . . . . . . . . . . . . . . . . . 46
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 48 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 48
1. Overview 1. Overview
Connecting sensors to the Internet is not new, and there have been Connecting sensors to the Internet is not new, and there have been
many protocols designed to facilitate it. This specification defines many protocols designed to facilitate it. This specification defines
new media types for carrying simple sensor information in a protocol new media types for carrying simple sensor information in a protocol
skipping to change at page 9, line 28 skipping to change at page 9, line 28
Although it is RECOMMENDED that concatenated names are represented as Although it is RECOMMENDED that concatenated names are represented as
URIs [RFC3986] or URNs [RFC8141], the restricted character set URIs [RFC3986] or URNs [RFC8141], the restricted character set
specified above puts strict limits on the URI schemes and URN specified above puts strict limits on the URI schemes and URN
namespaces that can be used. As a result, implementers need to take namespaces that can be used. As a result, implementers need to take
care in choosing the naming scheme for concatenated names, because care in choosing the naming scheme for concatenated names, because
such names both need to be unique and need to conform to the such names both need to be unique and need to conform to the
restricted character set. One approach is to include a bit string restricted character set. One approach is to include a bit string
that has guaranteed uniqueness (such as a 1-wire address). Some of that has guaranteed uniqueness (such as a 1-wire address). Some of
the examples within this document use the device URN namespace as the examples within this document use the device URN namespace as
specified in [I-D.arkko-core-dev-urn]. UUIDs [RFC4122] are another specified in [I-D.ietf-core-dev-urn]. UUIDs [RFC4122] are another
way to generate a unique name. However, the restricted character set way to generate a unique name. However, the restricted character set
does not allow the use of many URI schemes, such as the 'tag' scheme does not allow the use of many URI schemes, such as the 'tag' scheme
[RFC4151] and the 'ni' scheme [RFC6920], in names as such. The use [RFC4151] and the 'ni' scheme [RFC6920], in names as such. The use
of URIs with characters incompatible with this set, and possible of URIs with characters incompatible with this set, and possible
mapping rules between the two, are outside of the scope of the mapping rules between the two, are outside of the scope of the
present document. present document.
If the Record has no Unit, the Base Unit is used as the Unit. Having If the Record has no Unit, the Base Unit is used as the Unit. Having
no Unit and no Base Unit is allowed. no Unit and no Base Unit is allowed.
skipping to change at page 15, line 49 skipping to change at page 15, line 49
[ [
{"bn":"urn:dev:ow:10e2073a01080063:","n":"temp","u":"Cel","v":23.1}, {"bn":"urn:dev:ow:10e2073a01080063:","n":"temp","u":"Cel","v":23.1},
{"n":"label","vs":"Machine Room"}, {"n":"label","vs":"Machine Room"},
{"n":"open","vb":false}, {"n":"open","vb":false},
{"n":"nfv-reader","vd":"aGkgCg"} {"n":"nfv-reader","vd":"aGkgCg"}
] ]
5.1.6. Collection of Resources 5.1.6. Collection of Resources
The following example shows the results from a query to one device The following example shows the results from a query to one device
that aggregates multiple measurements from another devices. The that aggregates multiple measurements from other devices. The
example assumes that a client has fetched information from a device example assumes that a client has fetched information from a device
at 2001:db8::2 by performing a GET operation on http://[2001:db8::2] at 2001:db8::2 by performing a GET operation on http://[2001:db8::2]
at Mon Oct 31 16:27:09 UTC 2011, and has gotten two separate values at Mon Oct 31 16:27:09 UTC 2011, and has gotten two separate values
as a result, a temperature and humidity measurement as well as the as a result, a temperature and humidity measurement as well as the
results from another device at http://[2001:db8::1] that also had a results from another device at http://[2001:db8::1] that also had a
temperature and humidity. Note that the last record would use the temperature and humidity. Note that the last record would use the
Base Name from the 3rd record but the Base Time from the first Base Name from the 3rd record but the Base Time from the first
record. record.
[ [
skipping to change at page 23, line 33 skipping to change at page 23, line 33
The compressed form, using the byte alignment option of EXI, for the The compressed form, using the byte alignment option of EXI, for the
above XML is the following: above XML is the following:
0000 a0 00 48 80 6c 20 01 06 1d 75 72 6e 3a 64 65 76 |..H.l ...urn:dev| 0000 a0 00 48 80 6c 20 01 06 1d 75 72 6e 3a 64 65 76 |..H.l ...urn:dev|
0010 3a 6f 77 3a 31 30 65 32 30 37 33 61 30 31 30 38 |:ow:10e2073a0108| 0010 3a 6f 77 3a 31 30 65 32 30 37 33 61 30 31 30 38 |:ow:10e2073a0108|
0020 30 30 36 33 02 05 43 65 6c 01 00 e7 01 01 00 03 |0063..Cel.......| 0020 30 30 36 33 02 05 43 65 6c 01 00 e7 01 01 00 03 |0063..Cel.......|
0030 01 |.| 0030 01 |.|
0031 0031
A small temperature sensor device that only generates this one EXI A small temperature sensor device that only generates this one EXI
file does not really need an full EXI implementation. It can simply file does not really need a full EXI implementation. It can simply
hard code the output replacing the 1-wire device ID starting at byte hard code the output replacing the 1-wire device ID starting at byte
0x20 and going to byte 0x2F with it's device ID, and replacing the 0x14 and going to byte 0x23 with its device ID, and replacing the
value "0xe7 0x01" at location 0x37 and 0x38 with the current value "0xe7 0x01" at location 0x31 and 0x32 with the current
temperature. The EXI Specification [W3C.REC-exi-20140211] contains temperature. The EXI Specification [W3C.REC-exi-20140211] contains
the full information on how floating point numbers are represented, the full information on how floating point numbers are represented,
but for the purpose of this sensor, the temperature can be converted but for the purpose of this sensor, the temperature can be converted
to an integer in tenths of degrees (231 in this example). EXI stores to an integer in tenths of degrees (231 in this example). EXI stores
7 bits of the integer in each byte with the top bit set to one if 7 bits of the integer in each byte with the top bit set to one if
there are further bytes. So the first bytes at is set to low 7 bits there are further bytes. So the first bytes at is set to low 7 bits
of the integer temperature in tenths of degrees plus 0x80. In this of the integer temperature in tenths of degrees plus 0x80. In this
example 231 & 0x7F + 0x80 = 0xE7. The second byte is set to the example 231 & 0x7F + 0x80 = 0xE7. The second byte is set to the
integer temperature in tenths of degrees right shifted 7 bits. In integer temperature in tenths of degrees right shifted 7 bits. In
this example 231 >> 7 = 0x01. this example 231 >> 7 = 0x01.
skipping to change at page 27, line 34 skipping to change at page 27, line 34
binary-value = bstr binary-value = bstr
Figure 3: CBOR-specific CDDL specification for SenML Figure 3: CBOR-specific CDDL specification for SenML
12. IANA Considerations 12. IANA Considerations
Note to RFC Editor: Please replace all occurrences of "RFC-AAAA" with Note to RFC Editor: Please replace all occurrences of "RFC-AAAA" with
the RFC number of this specification. the RFC number of this specification.
IANA will create a new registry for "Sensor Measurement Lists (SenML)
Parameters". The sub-registries defined in Section 12.1 and
Section 12.2 will be created inside this registry.
12.1. Units Registry 12.1. Units Registry
IANA will create a registry of SenML unit symbols. The primary IANA will create a registry of SenML unit symbols. The primary
purpose of this registry is to make sure that symbols uniquely map to purpose of this registry is to make sure that symbols uniquely map to
give type of measurement. Definitions for many of these units can be give type of measurement. Definitions for many of these units can be
found in location such as [NIST811] and [BIPM]. Units marked with an found in location such as [NIST811] and [BIPM]. Units marked with an
asterisk are NOT RECOMMENDED to be produced by new implementations, asterisk are NOT RECOMMENDED to be produced by new implementations,
but are in active use and SHOULD be implemented by consumers that can but are in active use and SHOULD be implemented by consumers that can
use the related base units. use the related base units.
skipping to change at page 32, line 20 skipping to change at page 32, line 23
types. types.
New entries can be added to the registration by Expert Review as New entries can be added to the registration by Expert Review as
defined in [RFC8126]. Experts should exercise their own good defined in [RFC8126]. Experts should exercise their own good
judgment but need to consider that shorter labels should have more judgment but need to consider that shorter labels should have more
strict review. New entries should not be made that counteract the strict review. New entries should not be made that counteract the
advice at the end of Section 4.4. advice at the end of Section 4.4.
All new SenML labels that have "base" semantics (see Section 4.1) All new SenML labels that have "base" semantics (see Section 4.1)
MUST start with the character 'b'. Regular labels MUST NOT start MUST start with the character 'b'. Regular labels MUST NOT start
with that character. with that character. All new SenML labels with Value semantics (see
Section 4.2) MUST have "Value" in their (long form) name.
Extensions that add a label that is intended for use with XML need to Extensions that add a label that is intended for use with XML need to
create a new RelaxNG scheme that includes all the labels in the IANA create a new RelaxNG scheme that includes all the labels in the IANA
registry. registry.
Extensions that add a label that is intended for use with EXI need to Extensions that add a label that is intended for use with EXI need to
create a new XSD Schema that includes all the labels in the IANA create a new XSD Schema that includes all the labels in the IANA
registry and then allocate a new EXI schemaId value. Moving to the registry and then allocate a new EXI schemaId value. Moving to the
next letter in the alphabet is the suggested way to create the new next letter in the alphabet is the suggested way to create the new
value for the EXI schemaId. Any labels with previously blank ID value for the EXI schemaId. Any labels with previously blank ID
skipping to change at page 34, line 48 skipping to change at page 35, line 6
level of functionality needed by the creator of the JSON object. level of functionality needed by the creator of the JSON object.
Published specification: RFC-AAAA Published specification: RFC-AAAA
Applications that use this media type: The type is used by systems Applications that use this media type: The type is used by systems
that report e.g., electrical power usage and environmental that report e.g., electrical power usage and environmental
information such as temperature and humidity. It can be used for a information such as temperature and humidity. It can be used for a
wide range of sensor reporting systems. wide range of sensor reporting systems.
Fragment identifier considerations: Fragment identification for Fragment identifier considerations: Fragment identification for
application/senml+json is supported by using fragment identifiers as application/sensml+json is supported by using fragment identifiers as
specified by RFC-AAAA. specified by RFC-AAAA.
Additional information: Additional information:
Magic number(s): none Magic number(s): none
File extension(s): sensml File extension(s): sensml
Macintosh file type code(s): none Macintosh file type code(s): none
skipping to change at page 37, line 13 skipping to change at page 37, line 17
functionality needed by the creator of the CBOR object. functionality needed by the creator of the CBOR object.
Published specification: RFC-AAAA Published specification: RFC-AAAA
Applications that use this media type: The type is used by systems Applications that use this media type: The type is used by systems
that report e.g., electrical power usage and environmental that report e.g., electrical power usage and environmental
information such as temperature and humidity. It can be used for a information such as temperature and humidity. It can be used for a
wide range of sensor reporting systems. wide range of sensor reporting systems.
Fragment identifier considerations: Fragment identification for Fragment identifier considerations: Fragment identification for
application/senml+cbor is supported by using fragment identifiers as application/sensml+cbor is supported by using fragment identifiers as
specified by RFC-AAAA. specified by RFC-AAAA.
Additional information: Additional information:
Magic number(s): none Magic number(s): none
File extension(s): sensmlc File extension(s): sensmlc
Macintosh file type code(s): none Macintosh file type code(s): none
skipping to change at page 39, line 27 skipping to change at page 39, line 36
needed by the creator of the XML SenML Pack. needed by the creator of the XML SenML Pack.
Published specification: RFC-AAAA Published specification: RFC-AAAA
Applications that use this media type: The type is used by systems Applications that use this media type: The type is used by systems
that report e.g., electrical power usage and environmental that report e.g., electrical power usage and environmental
information such as temperature and humidity. It can be used for a information such as temperature and humidity. It can be used for a
wide range of sensor reporting systems. wide range of sensor reporting systems.
Fragment identifier considerations: Fragment identification for Fragment identifier considerations: Fragment identification for
application/senml+xml is supported by using fragment identifiers as application/sensml+xml is supported by using fragment identifiers as
specified by RFC-AAAA. specified by RFC-AAAA.
Additional information: Additional information:
Magic number(s): none Magic number(s): none
File extension(s): sensmlx File extension(s): sensmlx
Macintosh file type code(s): none Macintosh file type code(s): none
skipping to change at page 41, line 44 skipping to change at page 41, line 50
using schemas to guide the EXI can be found in RFC-AAAA. using schemas to guide the EXI can be found in RFC-AAAA.
Published specification: RFC-AAAA Published specification: RFC-AAAA
Applications that use this media type: The type is used by systems Applications that use this media type: The type is used by systems
that report e.g., electrical power usage and environmental that report e.g., electrical power usage and environmental
information such as temperature and humidity. It can be used for a information such as temperature and humidity. It can be used for a
wide range of sensor reporting systems. wide range of sensor reporting systems.
Fragment identifier considerations: Fragment identification for Fragment identifier considerations: Fragment identification for
application/senml-exi is supported by using fragment identifiers as application/sensml-exi is supported by using fragment identifiers as
specified by RFC-AAAA. specified by RFC-AAAA.
Additional information: Additional information:
Magic number(s): none Magic number(s): none
File extension(s): sensmle File extension(s): sensmle
Macintosh file type code(s): none Macintosh file type code(s): none
Person & email address to contact for further information: Cullen Person & email address to contact for further information: Cullen
Jennings <fluffy@iii.ca> Jennings <fluffy@iii.ca>
Intended usage: COMMON Intended usage: COMMON
Restrictions on usage: None Restrictions on usage: None
Author: Cullen Jennings <fluffy@iii.ca> Author: Cullen Jennings <fluffy@iii.ca>
skipping to change at page 42, line 32 skipping to change at page 42, line 39
URI: urn:ietf:params:xml:ns:senml URI: urn:ietf:params:xml:ns:senml
Registrant Contact: The IESG. Registrant Contact: The IESG.
XML: N/A, the requested URIs are XML namespaces XML: N/A, the requested URIs are XML namespaces
12.5. CoAP Content-Format Registration 12.5. CoAP Content-Format Registration
IANA is requested to assign CoAP Content-Format IDs for the SenML IANA is requested to assign CoAP Content-Format IDs for the SenML
media types in the "CoAP Content-Formats" sub-registry, within the media types in the "CoAP Content-Formats" sub-registry, within the
"CoRE Parameters" registry [RFC7252]. All IDs are assigned from the "CoRE Parameters" registry [RFC7252]. IDs for the JSON, CBOR, and
"Expert Review" (0-255) range. The assigned IDs are show in Table 8. EXI Content-Formats are assigned from the "Expert Review" (0-255)
range and for the XML Content-Format from the "IETF Review or IESG
Approval" range. The assigned IDs are shown in Table 8.
+-------------------------+-----+ +-------------------------+-----+
| Media type | ID | | Media type | ID |
+-------------------------+-----+ +-------------------------+-----+
| application/senml+json | TBD | | application/senml+json | TBD |
| application/sensml+json | TBD | | application/sensml+json | TBD |
| application/senml+cbor | TBD | | application/senml+cbor | TBD |
| application/sensml+cbor | TBD | | application/sensml+cbor | TBD |
| application/senml+xml | TBD |
| application/sensml+xml | TBD |
| application/senml-exi | TBD | | application/senml-exi | TBD |
| application/sensml-exi | TBD | | application/sensml-exi | TBD |
| application/senml+xml | TBD |
| application/sensml+xml | TBD |
+-------------------------+-----+ +-------------------------+-----+
Table 8: CoAP Content-Format IDs Table 8: CoAP Content-Format IDs
13. Security Considerations 13. Security Considerations
Sensor data can contain a wide range of information ranging from Sensor data can contain a wide range of information ranging from
information that is very public, such as the outside temperature in a information that is very public, such as the outside temperature in a
given city, to very private information that requires integrity and given city, to very private information that requires integrity and
confidentiality protection, such as patient health information. The confidentiality protection, such as patient health information. The
skipping to change at page 43, line 47 skipping to change at page 44, line 14
used with care or avoided as for example described for IPv6 addresses used with care or avoided as for example described for IPv6 addresses
in [RFC7721]. in [RFC7721].
15. Acknowledgement 15. Acknowledgement
We would like to thank Alexander Pelov, Alexey Melnikov, Andrew We would like to thank Alexander Pelov, Alexey Melnikov, Andrew
McClure, Andrew McGregor, Bjoern Hoehrmann, Christian Amsuess, McClure, Andrew McGregor, Bjoern Hoehrmann, Christian Amsuess,
Christian Groves, Daniel Peintner, Jan-Piet Mens, Jim Schaad, Joe Christian Groves, Daniel Peintner, Jan-Piet Mens, Jim Schaad, Joe
Hildebrand, John Klensin, Karl Palsson, Lennart Duhrsen, Lisa Hildebrand, John Klensin, Karl Palsson, Lennart Duhrsen, Lisa
Dusseault, Lyndsay Campbell, Martin Thomson, Michael Koster, Peter Dusseault, Lyndsay Campbell, Martin Thomson, Michael Koster, Peter
Saint-Andre, and Stephen Farrell, for their review comments. Saint-Andre, Roni Even, and Stephen Farrell, for their review
comments.
16. References 16. References
16.1. Normative References 16.1. Normative References
[BIPM] Bureau International des Poids et Mesures, "The [BIPM] Bureau International des Poids et Mesures, "The
International System of Units (SI)", 8th edition, 2006. International System of Units (SI)", 8th edition, 2006.
[IEEE.754.1985] [IEEE.754.1985]
Institute of Electrical and Electronics Engineers, Institute of Electrical and Electronics Engineers,
skipping to change at page 46, line 14 skipping to change at page 46, line 28
[W3C.REC-xmlschema-1-20041028] [W3C.REC-xmlschema-1-20041028]
Thompson, H., Beech, D., Maloney, M., and N. Mendelsohn, Thompson, H., Beech, D., Maloney, M., and N. Mendelsohn,
"XML Schema Part 1: Structures Second Edition", World Wide "XML Schema Part 1: Structures Second Edition", World Wide
Web Consortium Recommendation REC-xmlschema-1-20041028, Web Consortium Recommendation REC-xmlschema-1-20041028,
October 2004, October 2004,
<http://www.w3.org/TR/2004/REC-xmlschema-1-20041028>. <http://www.w3.org/TR/2004/REC-xmlschema-1-20041028>.
16.2. Informative References 16.2. Informative References
[I-D.arkko-core-dev-urn]
Arkko, J., Jennings, C., and Z. Shelby, "Uniform Resource
Names for Device Identifiers", draft-arkko-core-dev-urn-05
(work in progress), October 2017.
[I-D.ietf-cbor-cddl] [I-D.ietf-cbor-cddl]
Birkholz, H., Vigano, C., and C. Bormann, "Concise data Birkholz, H., Vigano, C., and C. Bormann, "Concise data
definition language (CDDL): a notational convention to definition language (CDDL): a notational convention to
express CBOR data structures", draft-ietf-cbor-cddl-02 express CBOR data structures", draft-ietf-cbor-cddl-02
(work in progress), February 2018. (work in progress), February 2018.
[I-D.ietf-core-dev-urn]
Arkko, J., Jennings, C., and Z. Shelby, "Uniform Resource
Names for Device Identifiers", draft-ietf-core-dev-urn-01
(work in progress), March 2018.
[I-D.ietf-core-interfaces] [I-D.ietf-core-interfaces]
Shelby, Z., Vial, M., Koster, M., Groves, C., Zhu, J., and Shelby, Z., Vial, M., Koster, M., Groves, C., Zhu, J., and
B. Silverajan, "Reusable Interface Definitions for B. Silverajan, "Reusable Interface Definitions for
Constrained RESTful Environments", draft-ietf-core- Constrained RESTful Environments", draft-ietf-core-
interfaces-10 (work in progress), September 2017. interfaces-11 (work in progress), March 2018.
[IEEE802.1as-2011] [IEEE802.1as-2011]
IEEE, "IEEE Standard for Local and Metropolitan Area IEEE, "IEEE Standard for Local and Metropolitan Area
Networks - Timing and Synchronization for Time-Sensitive Networks - Timing and Synchronization for Time-Sensitive
Applications in Bridged Local Area Networks", 2011. Applications in Bridged Local Area Networks", 2011.
[IEEE802.1ba-2011] [IEEE802.1ba-2011]
IEEE, "IEEE Standard for Local and metropolitan area IEEE, "IEEE Standard for Local and metropolitan area
networks--Audio Video Bridging (AVB) Systems", 2011. networks--Audio Video Bridging (AVB) Systems", 2011.
 End of changes. 25 change blocks. 
28 lines changed or deleted 37 lines changed or added

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