draft-ietf-core-dev-urn-06.txt   draft-ietf-core-dev-urn.txt 
Network Working Group J. Arkko Network Working Group J. Arkko
Internet-Draft Ericsson Internet-Draft Ericsson
Intended status: Informational C. Jennings Intended status: Informational C. Jennings
Expires: January 2, 2021 Cisco Expires: January 3, 2021 Cisco
Z. Shelby Z. Shelby
ARM ARM
July 1, 2020 July 2, 2020
Uniform Resource Names for Device Identifiers Uniform Resource Names for Device Identifiers
draft-ietf-core-dev-urn-06 draft-ietf-core-dev-urn-07
Abstract Abstract
This memo describes a new Uniform Resource Name (URN) namespace for This memo describes a new Uniform Resource Name (URN) namespace for
hardware device identifiers. A general representation of device hardware device identifiers. A general representation of device
identity can be useful in many applications, such as in sensor data identity can be useful in many applications, such as in sensor data
streams and storage, or equipment inventories. A URN-based streams and storage, or equipment inventories. A URN-based
representation can be easily passed along in any application that representation can be easily passed along in any application that
needs the information. needs the information.
skipping to change at page 1, line 38 skipping to change at page 1, line 38
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 January 2, 2021. This Internet-Draft will expire on January 3, 2021.
Copyright Notice Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the Copyright (c) 2020 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 2, line 38 skipping to change at page 2, line 38
4.5. Organization Product and Serial Numbers . . . . . . . . . 9 4.5. Organization Product and Serial Numbers . . . . . . . . . 9
5. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 9 5. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 9
6. Security Considerations . . . . . . . . . . . . . . . . . . . 10 6. Security Considerations . . . . . . . . . . . . . . . . . . . 10
6.1. Privacy . . . . . . . . . . . . . . . . . . . . . . . . . 11 6.1. Privacy . . . . . . . . . . . . . . . . . . . . . . . . . 11
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 11 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 11
8.1. Normative References . . . . . . . . . . . . . . . . . . 11 8.1. Normative References . . . . . . . . . . . . . . . . . . 11
8.2. Informative References . . . . . . . . . . . . . . . . . 12 8.2. Informative References . . . . . . . . . . . . . . . . . 12
Appendix A. Changes from Previous Version . . . . . . . . . . . 14 Appendix A. Changes from Previous Version . . . . . . . . . . . 14
Appendix B. Acknowledgments . . . . . . . . . . . . . . . . . . 16 Appendix B. Acknowledgments . . . . . . . . . . . . . . . . . . 16
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 16 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 17
1. Introduction 1. Introduction
This memo describes a new Uniform Resource Name (URN) [RFC8141] This memo describes a new Uniform Resource Name (URN) [RFC8141]
namespace for hardware device identifiers. A general representation namespace for hardware device identifiers. A general representation
of device identity can be useful in many applications, such as in of device identity can be useful in many applications, such as in
sensor data streams and storage [RFC8428], or equipment inventories sensor data streams and storage [RFC8428], or equipment inventories
[RFC7252], [I-D.ietf-core-resource-directory]. [RFC7252], [I-D.ietf-core-resource-directory].
A URN-based representation can be easily passed along in any A URN-based representation can be easily passed along in any
skipping to change at page 5, line 49 skipping to change at page 5, line 49
With the exception of the MAC-address and 1-Wire DEV URNs, each DEV With the exception of the MAC-address and 1-Wire DEV URNs, each DEV
URN may also contain optional colon-separated identifiers. These are URN may also contain optional colon-separated identifiers. These are
provided for extensibility. provided for extensibility.
There are no special character encoding rules or considerations for There are no special character encoding rules or considerations for
comforming with the URN syntax, beyond those applicable for URNs in comforming with the URN syntax, beyond those applicable for URNs in
general [RFC8141], or the context where these URNs are carried (e.g., general [RFC8141], or the context where these URNs are carried (e.g.,
inside JSON [RFC8259] or SenML [RFC8428]). inside JSON [RFC8259] or SenML [RFC8428]).
The lexical equivalence of the DEV URNs is defined as an exact and The DEV URN syntax allows both upper and lower case characters. The
case sensitive string match. Note that the subtypes defined in this lexical equivalence of the DEV URNs is defined as an exact and case
document do not require the specific case, however. Future types sensitive string match. Character case is not otherwise significant
for the DEV URN subtypes defined in this document. Future subtypes
might use identifiers that require other encodings that require a might use identifiers that require other encodings that require a
more full-blown character set (such as BASE64). For equivalance more full-blown character set (such as BASE64). To facilitate
checks, it is RECOMMENDED that lower case letters are used throughout equivalence checks, it is RECOMMENDED that implementations always use
by implementations unless there is a reason otherwise. lower case letters where they have a choice in case, unless there is
a reason otherwise. (Such a reason might be, for instance, the use
of a subtype that requires the use of both upper case and lower case
letters.)
DEV URNs do not use r-, q-, or f-components. DEV URNs do not use r-, q-, or f-components.
Specific subtypes of DEV URNs may be validated through mechanisms Specific subtypes of DEV URNs may be validated through mechanisms
discussed in Section 4. discussed in Section 4.
Finally, the string representation of the device identity URN and of Finally, the string representation of the device identity URN and of
the MEID sub namespace is fully compatible with the URN syntax. the MEID sub namespace is fully compatible with the URN syntax.
3.3. Assignment 3.3. Assignment
skipping to change at page 8, line 24 skipping to change at page 8, line 24
4.3. Organization-Defined Identifiers 4.3. Organization-Defined Identifiers
Device identifiers that have only a meaning within an organisation Device identifiers that have only a meaning within an organisation
can also be used to represent vendor-specific or experimental can also be used to represent vendor-specific or experimental
identifiers or identifiers designed for use within the context of an identifiers or identifiers designed for use within the context of an
organisation. organisation.
Organisations are identified by their Private Enterprise Number (PEN) Organisations are identified by their Private Enterprise Number (PEN)
[RFC2578]. These numbers can be obtained from IANA. Current PEN [RFC2578]. These numbers can be obtained from IANA. Current PEN
assignments can be viewed at https://www.iana.org/assignments/ assignments can be viewed at https://www.iana.org/assignments/
enterprise-numbers/enterprise-numbers and new assignemnts requested enterprise-numbers/enterprise-numbers and new assignments requested
at https://pen.iana.org/pen/PenApplication.page. at https://pen.iana.org/pen/PenApplication.page.
When included in an "org" DEV URN, the number MUST NOT be padded with When included in an "org" DEV URN, the number MUST NOT be padded with
extra leading zeroes. extra leading zeroes.
4.4. Organization Serial Numbers 4.4. Organization Serial Numbers
The "os" subtype specifies an organization and a serial number. The "os" subtype specifies an organization and a serial number.
Organizations are identified by their PEN. As with the organization- Organizations are identified by their PEN. As with the organization-
defined identifiers (Section 4.3), PEN number assignments are defined identifiers (Section 4.3), PEN number assignments are
skipping to change at page 14, line 24 skipping to change at page 14, line 24
DOI 10.17487/RFC8464, September 2018, <https://www.rfc- DOI 10.17487/RFC8464, September 2018, <https://www.rfc-
editor.org/info/rfc8464>. editor.org/info/rfc8464>.
[I-D.ietf-core-resource-directory] [I-D.ietf-core-resource-directory]
Shelby, Z., Koster, M., Bormann, C., Stok, P., and C. Shelby, Z., Koster, M., Bormann, C., Stok, P., and C.
Amsuess, "CoRE Resource Directory", draft-ietf-core- Amsuess, "CoRE Resource Directory", draft-ietf-core-
resource-directory-24 (work in progress), March 2020. resource-directory-24 (work in progress), March 2020.
Appendix A. Changes from Previous Version Appendix A. Changes from Previous Version
Version -07 of the WG draft took into account Carsten Bormann's
feedback, primarily on character case issues and editorials.
Version -06 of the WG draft took into account Marco Tiloca's feedback Version -06 of the WG draft took into account Marco Tiloca's feedback
before a second WGLC, primarily on further cleanup of references and before a second WGLC, primarily on further cleanup of references and
editorial issues. editorial issues.
Version -05 of the WG draft made some updates based on WGLC input: Version -05 of the WG draft made some updates based on WGLC input:
examples for MAC-48 and EUI-48, clarification with regards to leading examples for MAC-48 and EUI-48, clarification with regards to leading
zeroes, new recommendation with the use of lower-case letters to zeroes, new recommendation with the use of lower-case letters to
avoid comparison problems, small update of the RFC 8141 template avoid comparison problems, small update of the RFC 8141 template
usage, reference updates, and editorial corrections. usage, reference updates, and editorial corrections.
 End of changes. 9 change blocks. 
12 lines changed or deleted 19 lines changed or added

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