idnits 2.17.1 draft-ietf-core-dev-urn-03.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document seems to lack the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. (The document does seem to have the reference to RFC 2119 which the ID-Checklist requires). -- The document date (October 22, 2018) is 2013 days in the past. Is this intentional? -- Found something which looks like a code comment -- if you have code sections in the document, please surround them with '' and '' lines. Checking references for intended status: Informational ---------------------------------------------------------------------------- ** Obsolete normative reference: RFC 3406 (Obsoleted by RFC 8141) ** Obsolete normative reference: RFC 5226 (Obsoleted by RFC 8126) -- Obsolete informational reference (is this intentional?): RFC 2616 (Obsoleted by RFC 7230, RFC 7231, RFC 7232, RFC 7233, RFC 7234, RFC 7235) -- Obsolete informational reference (is this intentional?): RFC 4627 (Obsoleted by RFC 7158, RFC 7159) Summary: 2 errors (**), 0 flaws (~~), 2 warnings (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group J. Arkko 3 Internet-Draft Ericsson 4 Intended status: Informational C. Jennings 5 Expires: April 25, 2019 Cisco 6 Z. Shelby 7 ARM 8 October 22, 2018 10 Uniform Resource Names for Device Identifiers 11 draft-ietf-core-dev-urn-03 13 Abstract 15 This memo describes a new Uniform Resource Name (URN) namespace for 16 hardware device identifiers. A general representation of device 17 identity can be useful in many applications, such as in sensor data 18 streams and storage, or equipment inventories. A URN-based 19 representation can be easily passed along in any application that 20 needs the information. 22 Status of This Memo 24 This Internet-Draft is submitted in full conformance with the 25 provisions of BCP 78 and BCP 79. 27 Internet-Drafts are working documents of the Internet Engineering 28 Task Force (IETF). Note that other groups may also distribute 29 working documents as Internet-Drafts. The list of current Internet- 30 Drafts is at http://datatracker.ietf.org/drafts/current/. 32 Internet-Drafts are draft documents valid for a maximum of six months 33 and may be updated, replaced, or obsoleted by other documents at any 34 time. It is inappropriate to use Internet-Drafts as reference 35 material or to cite them other than as "work in progress." 37 This Internet-Draft will expire on April 25, 2019. 39 Copyright Notice 41 Copyright (c) 2018 IETF Trust and the persons identified as the 42 document authors. All rights reserved. 44 This document is subject to BCP 78 and the IETF Trust's Legal 45 Provisions Relating to IETF Documents 46 (http://trustee.ietf.org/license-info) in effect on the date of 47 publication of this document. Please review these documents 48 carefully, as they describe your rights and restrictions with respect 49 to this document. Code Components extracted from this document must 50 include Simplified BSD License text as described in Section 4.e of 51 the Trust Legal Provisions and are provided without warranty as 52 described in the Simplified BSD License. 54 Table of Contents 56 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 57 2. Requirements language . . . . . . . . . . . . . . . . . . . . 3 58 3. DEV URN Definition . . . . . . . . . . . . . . . . . . . . . 4 59 3.1. Purpose . . . . . . . . . . . . . . . . . . . . . . . . . 4 60 3.2. Syntax . . . . . . . . . . . . . . . . . . . . . . . . . 5 61 3.3. Assignment . . . . . . . . . . . . . . . . . . . . . . . 6 62 3.4. Security and Privacy . . . . . . . . . . . . . . . . . . 6 63 3.5. Interoperability . . . . . . . . . . . . . . . . . . . . 6 64 3.6. Resolution . . . . . . . . . . . . . . . . . . . . . . . 6 65 3.7. Documentation . . . . . . . . . . . . . . . . . . . . . . 6 66 3.8. Additional Information . . . . . . . . . . . . . . . . . 7 67 3.9. Revision Information . . . . . . . . . . . . . . . . . . 7 68 4. DEV URN Subtypes . . . . . . . . . . . . . . . . . . . . . . 7 69 4.1. MAC Addresses . . . . . . . . . . . . . . . . . . . . . . 7 70 4.2. 1-Wire Device Identifiers . . . . . . . . . . . . . . . . 7 71 4.3. Organization-Defined Identifiers . . . . . . . . . . . . 8 72 4.4. Organization Serial Numbers . . . . . . . . . . . . . . . 8 73 4.5. Organization Product and Serial Numbers . . . . . . . . . 8 74 5. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 8 75 6. Security Considerations . . . . . . . . . . . . . . . . . . . 9 76 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10 77 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 10 78 8.1. Normative References . . . . . . . . . . . . . . . . . . 10 79 8.2. Informative References . . . . . . . . . . . . . . . . . 11 80 Appendix A. Changes from Previous Version . . . . . . . . . . . 13 81 Appendix B. Acknowledgments . . . . . . . . . . . . . . . . . . 14 82 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 14 84 1. Introduction 86 This memo describes a new Uniform Resource Name (URN) [RFC8141] 87 [RFC3406] namespace for hardware device identifiers. A general 88 representation of device identity can be useful in many applications, 89 such as in sensor data streams and storage, or equipment inventories 90 [RFC7252], [RFC8428]. A URN-based representation can be easily 91 passed along in any application that needs the information, as it 92 fits in protocols mechanisms that are designed to carry URNs 93 [RFC2616], [RFC3261], [RFC7252]. Finally, URNs can also be easily 94 carried and stored in formats such as XML [W3C.REC-xml-19980210] or 95 JSON [RFC8428] [RFC4627]. Using URNs in these formats is often 96 preferable as they are universally recognized, self-describing, and 97 therefore avoid the need for agreeing to interpret an octet string as 98 a specific form of a MAC address, for instance. 100 This memo defines identity URN types for situations where no such 101 convenient type already exist. For instance, [RFC6920] defines 102 cryptographic identifiers, [RFC7254] defines International Mobile 103 station Equipment Identity (IMEI) identifiers for use with 3GPP 104 cellular systems, and [I-D.atarius-dispatch-meid-urn] defines Mobile 105 Equipment Identity (MEID) identifiers for use with 3GPP2 cellular 106 systems. Those URN types should be employed when such identities are 107 transported; this memo does not redefine these identifiers in any 108 way. 110 Universally Unique IDentifier (UUID) URNs [RFC4122] are another 111 alternative way for representing device identifiers, and already 112 support MAC addresses as one of type of an identifier. However, 113 UUIDs can be inconvenient in environments where it is important that 114 the identifiers are as simple as possible and where additional 115 requirements on stable storage, real-time clocks, and identifier 116 length can be prohibitive. UUID-based identifiers are recommended 117 for all general purpose uses when MAC addresses are available as 118 identifiers. The device URN defined in this memo is recommended for 119 constrained environments. 121 Future device identifier types can extend the device device URN type 122 defined here, or define their own URNs. 124 Note that long-term stable unique identifiers are problematic for 125 privacy reasons and should be used with care or avoided as described 126 in [RFC7721]. 128 The rest of this memo is organized as follows. Section 3 defines the 129 "DEV" URN type, and Section 4 defines subtypes for IEEE MAC-48, 130 EUI-48 and EUI-64 addresses and 1-wire device identifiers. Section 5 131 gives examples. Section 6 discusses the security considerations of 132 the new URN type. Finally, Section 7 specifies the IANA registration 133 for the new URN type and sets requirements for subtype allocations 134 within this type. 136 2. Requirements language 138 In this document, the key words "MAY", "MUST, "MUST NOT", "OPTIONAL", 139 "RECOMMENDED", "SHOULD", and "SHOULD NOT", are to be interpreted as 140 described in [RFC2119]. 142 3. DEV URN Definition 144 Namespace Identifier: "dev" requested 146 Version: 1 148 Date: 2018-03-19 150 Registration Information: This is the first registration of this 151 namespace, 2018-03-19. 153 Registrant: IETF and the CORE working group. Should the working 154 group cease to exist, discussion should be directed to the general 155 IETF discussion forums or the IESG. 157 3.1. Purpose 159 Purpose: The DEV URNs identify devices with device-specific 160 identifiers such as network card hardware addresses. These URNs may 161 be used in any relevant networks that benefit from the ability to 162 refer to these identifiers in the form of URNs; DEV URN is global in 163 scope. 165 Some typical applications include equipment inventories and smart 166 object systems. 168 DEV URNs can be used in various ways in applications, software 169 systems, and network components, in tasks ranging from discovery (for 170 instance when discovering 1-wire network devices or detecting MAC- 171 addressable devices on a LAN) to intrusion detection systems and 172 simple catalogues of system information. 174 While it is possible to implement resolution systems for specific 175 applications or network locations, DEV URNs are typically not used in 176 a way that requires resolution beyond direct observation of the 177 relevant identity fields in local link communication. However, it is 178 often useful to be able to pass device identity information in 179 generic URN fields in databases or protocol fields, which makes the 180 use of URNs for this purpose convenient. 182 The DEV URN name space complements existing name spaces such as those 183 involving IMEI or UUID identifiers. DEV URNs are expeced to be a 184 part of the IETF-provided basic URN types, covering identifiers that 185 have previously not been possible to use in URNs. 187 3.2. Syntax 189 Syntax: The identifier is expressed in ASCII characters and has a 190 hierarchical structure as follows: 192 devurn = "urn:dev:" body componentpart 193 body = macbody / owbody / orgbody / osbody / opsbody / otherbody 194 macbody = "mac:" hexstring 195 owbody = "ow:" hexstring 196 orgbody = "org:" number "-" identifier 197 osbody = "os:" number "-" serial 198 opsbody = "ops:" number "-" product "-" serial 199 otherbody = subtype ":" identifier 200 subtype = ALPHA *(DIGIT / ALPHA) 201 identifier = 1*unreservednout 202 product = identifier 203 serial = identifier 204 unreservednout = ALPHA / DIGIT / "_" 205 componentpart = [ "_" component [ componentpart ]] 206 component = *1(DIGIT / ALPHA) 207 hexstring = hexbyte / 208 hexbyte hexstring 209 hexbyte = hexdigit hexdigit 210 hexdigit = DIGIT / hexletter 211 hexletter = "a" / "b" / "c" / "d" / "e" / "f" 212 number = *1DIGIT 214 The above Augmented Backus-Naur Form (ABNF) uses the DIGIT and ALPHA 215 rules defined in [RFC5234], which are not repeated here. The rule 216 for pct-encoding is defined in Section 2.1 of [RFC3986]. 218 The device identity namespace includes three subtypes (see Section 4, 219 and more may be defined in the future as specified in Section 7. 221 The optional components following the hexstring are strings depicting 222 individual aspects of a device. The specific strings and their 223 semantics are up to the designers of the device, but could be used to 224 refer to specific interfaces or functions within the device. 226 There are no special character encoding rules or considerations for 227 comforming with the URN syntax, beyond those applicable for URNs in 228 general [RFC8141], or the context where these URNs are carried (e.g., 229 inside JSON [RFC8259] or SenML [RFC8428]). 231 The lexical equivalence of the DEV URNs is defined as an exact and 232 case sensitive string match. Note that the two subtypes defined in 233 this document use only lower case letters, however. Future types 234 might use identifiers that require other encodings that require a 235 more full-blown character set (such as BASE64), however. 237 DEV URNs do not use r-, q-, or f-components. 239 Specific subtypes of DEV URNs may be validated through mechanisms 240 discussed in Section 4. 242 Finally, the string representation of the device identity URN and of 243 the MEID sub namespace is fully compatible with the URN syntax. 245 3.3. Assignment 247 Assignment: The process for identifier assignment is dependent on the 248 used subtype, and documented in the specific subsection under 249 Section 4. 251 Device identifiers are generally expected to be unique, barring the 252 accidental issue of multiple devices with the same identifiers. 254 This URN type SHOULD only be used for persistent identifiers, such as 255 hardware-based identifiers or cryptographic identifiers based on keys 256 intended for long-term usage. 258 3.4. Security and Privacy 260 Security and Privacy: As discussed in Section 6, care must be taken 261 to use device identifier-based identifiers due to their nature as a 262 long-term identifier that is often not changeable. Leakage of these 263 identifiers outside systems where their use is justfied should be 264 controlled. 266 3.5. Interoperability 268 Interoperability: There are no specific interoperability concerns. 270 3.6. Resolution 272 Resolution: The device identities are not expected to be globally 273 resolvable. No identity resolution system is expected. Systems may 274 perform local matching of identities to previously seen identities or 275 configured information, however. 277 3.7. Documentation 279 See RFC NNNN (RFC Editor: Please replace NNNN by a reference to the 280 RFC number of this document). 282 3.8. Additional Information 284 See Section 1 for a discussion of related name spaces. 286 3.9. Revision Information 288 Revision Information: This is the first version of this registration. 290 4. DEV URN Subtypes 292 4.1. MAC Addresses 294 DEV URNs of the "mac" subtype are based on the EUI-64 identifier 295 [IEEE.EUI64] derived from a device with a built-in 64-bit EUI-64. 296 The EUI-64 is formed from 24 or 36 bits of organization identifier 297 followed by 40 or 28 bits of device-specific extension identifier 298 assigned by that organization. 300 In the DEV URN "mac" subtype the hexstring is simply the full EUI-64 301 identifier represented as a hexadecimal string. It is always exactly 302 16 characters long. 304 MAC-48 and EUI-48 identifiers are also supported by the same DEV URN 305 subtype. To convert a MAC-48 address to an EUI-64 identifier, The 306 OUI of the Ethernet address (the first three octets) becomes the 307 organization identifier of the EUI-64 (the first three octets). The 308 fourth and fifth octets of the EUI are set to the fixed value FFFF 309 hexadecimal. The last three octets of the Ethernet address become 310 the last three octets of the EUI-64. The same process is used to 311 convert an EUI-48 identifier, but the fixed value FFFE is used 312 instead. 314 Identifier assignment for all of these identifiers rests within the 315 IEEE. 317 4.2. 1-Wire Device Identifiers 319 The 1-Wire* system is a device communications bus system designed by 320 Dallas Semiconductor Corporation. 1-Wire devices are identified by a 321 64-bit identifier that consists of 8 byte family code, 48 bit 322 identifier unique within a family, and 8 bit CRC code [OW]. 324 *) 1-Wire is a registered trademark. 326 In DEV URNs with the "ow" subtype the hexstring is a representation 327 of the full 64 bit identifier as a hexadecimal string. It is always 328 exactly 16 characters long. Note that the last two characters 329 represent the 8-bit CRC code. Implementations MAY check the validity 330 of this code. 332 Family code and identifier assignment for all 1-wire devices rests 333 with the manufacturers. 335 4.3. Organization-Defined Identifiers 337 Device identifiers that have only a meaning within an organisation 338 can also be used to represent vendor-specific or experimental 339 identifiers or identifiers designed for use within the context of an 340 organisation. Organisations are identified by their Private 341 Enterprise Number (PEN) [RFC2578]. 343 4.4. Organization Serial Numbers 345 The "os" subtype specifies an organization and a serial number. 346 Organizations are identified by their PEN. 348 Note: The DEV URN "os" subtype has originally been defined in the 349 LwM2M standard, but has been incorporated here to collect all 350 syntax associated with DEV URNs in one place. At the same time, 351 the syntax of this subtype was changed to avoid the possibility of 352 characters that are not allowed in SenML Name field (see [RFC8428] 353 Section 4.5.1). 355 4.5. Organization Product and Serial Numbers 357 The DEV URN "ops" subtype has originally been defined in the LwM2M 358 standard, but has been incorporated here to collect all syntax 359 associated with DEV URNs in one place. The "ops" subtype specifies 360 an organization, product class, and a serial number. Organizations 361 are identified by their PEN. 363 Note: As with the "os" subtype, the "ops" subtype has originally 364 been defined in the LwM2M standard, and its format has been 365 slightly changed. 367 5. Examples 369 The following three examples provide examples of MAC-based, 1-Wire, 370 and Cryptographic identifiers: 372 urn:dev:mac:0024befffe804ff1 # The MAC address of 373 # Jari's laptop 375 urn:dev:ow:10e2073a01080063 # The 1-Wire temperature 376 # sensor in Jari's 377 # kitchen 379 urn:dev:ow:264437f5000000ed_humidity # The laundry sensor's 380 # humidity part 382 urn:dev:ow:264437f5000000ed_temperature # The laundry sensor's 383 # temperature part 385 urn:dev:org:32473-123456 # Device 123456 in 386 # the RFC 5612 example 387 # organisation 389 urn:dev:ops:32473-Refrigerator-5002 # Refrigerator serial 390 # number 5002 in the 391 # RFC 5612 example 392 # organisation 394 6. Security Considerations 396 On most devices, the user can display device identifiers. Depending 397 on circumstances, device identifiers may or may not be modified or 398 tampered by the user. An implementation of the DEV URN MUST NOT 399 change these properties from what they were intended. In particular, 400 a device identifier that is intended to be immutable should not 401 become mutable as a part of implementing the DEV URN type. More 402 generally, nothing in this memo should be construed to override what 403 the relevant device specifications have already said about the 404 identifiers. 406 Other devices in the same network may or may not be able to identify 407 the device. For instance, on Ethernet network, the MAC address of a 408 device is visible to all other devices. 410 The URNs generated according to the rules defined in this document 411 result in long-term stable unique identifiers for the devices. Such 412 identifiers may have privacy and security implications because they 413 may enable correlating information about a specific device over a 414 long period of time, location tracking, and device specific 415 vulnerability exploitation [RFC7721]. Also, usually there is no easy 416 way to change the identifier. Therefore these identifiers need to be 417 used with care and especially care should be taken avoid leaking them 418 outside of the system that is intended to use the identifiers. 420 7. IANA Considerations 422 This document requests the registration of a new URN namespace for 423 "DEV", as described in Section 3. 425 Additional subtypes for DEV URNs can be defined through IETF Review 426 or IESG Approval [RFC5226]. 428 Such allocations are appropriate when there is a new namespace of 429 some type of device identifiers, defined in stable fashion and with a 430 publicly available specification that can be pointed to. 432 Note that the organisation (Section 4.3) device identifiers can also 433 be used in some cases, at least as a temporary measure. It is 434 preferrable, however, that long-term usage of a broadly employed 435 device identifier be registered with IETF rather than used through 436 the organisation device identifier type. 438 8. References 440 8.1. Normative References 442 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 443 Requirement Levels", BCP 14, RFC 2119, 444 DOI 10.17487/RFC2119, March 1997, . 447 [RFC8141] Saint-Andre, P. and J. Klensin, "Uniform Resource Names 448 (URNs)", RFC 8141, DOI 10.17487/RFC8141, April 2017, 449 . 451 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 452 Schoenwaelder, Ed., "Structure of Management Information 453 Version 2 (SMIv2)", STD 58, RFC 2578, 454 DOI 10.17487/RFC2578, April 1999, . 457 [RFC3406] Daigle, L., van Gulik, D., Iannella, R., and P. Faltstrom, 458 "Uniform Resource Names (URN) Namespace Definition 459 Mechanisms", RFC 3406, DOI 10.17487/RFC3406, October 2002, 460 . 462 [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform 463 Resource Identifier (URI): Generic Syntax", STD 66, 464 RFC 3986, DOI 10.17487/RFC3986, January 2005, 465 . 467 [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an 468 IANA Considerations Section in RFCs", RFC 5226, 469 DOI 10.17487/RFC5226, May 2008, . 472 [RFC5234] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax 473 Specifications: ABNF", STD 68, RFC 5234, 474 DOI 10.17487/RFC5234, January 2008, . 477 [IEEE.EUI64] 478 IEEE, "Guidelines For 64-bit Global Identifier (EUI-64)", 479 IEEE , unknown year, 480 . 482 [OW] IEEE, "Overview of 1-Wire(R) Technology and Its Use", 483 MAXIM 484 http://www.maxim-ic.com/app-notes/index.mvp/id/1796, June 485 2008, 486 . 488 8.2. Informative References 490 [RFC2616] Fielding, R., Gettys, J., Mogul, J., Frystyk, H., 491 Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext 492 Transfer Protocol -- HTTP/1.1", RFC 2616, 493 DOI 10.17487/RFC2616, June 1999, . 496 [RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, 497 A., Peterson, J., Sparks, R., Handley, M., and E. 498 Schooler, "SIP: Session Initiation Protocol", RFC 3261, 499 DOI 10.17487/RFC3261, June 2002, . 502 [RFC4122] Leach, P., Mealling, M., and R. Salz, "A Universally 503 Unique IDentifier (UUID) URN Namespace", RFC 4122, 504 DOI 10.17487/RFC4122, July 2005, . 507 [RFC4627] Crockford, D., "The application/json Media Type for 508 JavaScript Object Notation (JSON)", RFC 4627, 509 DOI 10.17487/RFC4627, July 2006, . 512 [RFC7721] Cooper, A., Gont, F., and D. Thaler, "Security and Privacy 513 Considerations for IPv6 Address Generation Mechanisms", 514 RFC 7721, DOI 10.17487/RFC7721, March 2016, 515 . 517 [RFC8259] Bray, T., Ed., "The JavaScript Object Notation (JSON) Data 518 Interchange Format", STD 90, RFC 8259, 519 DOI 10.17487/RFC8259, December 2017, . 522 [W3C.REC-xml-19980210] 523 Sperberg-McQueen, C., Bray, T., and J. Paoli, "XML 1.0 524 Recommendation", World Wide Web Consortium FirstEdition 525 REC-xml-19980210, February 1998, 526 . 528 [OUI] IEEE, SA., "Registration Authority", IEEE-SA webpage, 529 2018, . 531 [RFC7252] Shelby, Z., Hartke, K., and C. Bormann, "The Constrained 532 Application Protocol (CoAP)", RFC 7252, 533 DOI 10.17487/RFC7252, June 2014, . 536 [RFC8428] Jennings, C., Shelby, Z., Arkko, J., Keranen, A., and C. 537 Bormann, "Sensor Measurement Lists (SenML)", RFC 8428, 538 DOI 10.17487/RFC8428, August 2018, . 541 [RFC6920] Farrell, S., Kutscher, D., Dannewitz, C., Ohlman, B., 542 Keranen, A., and P. Hallam-Baker, "Naming Things with 543 Hashes", RFC 6920, DOI 10.17487/RFC6920, April 2013, 544 . 546 [RFC7254] Montemurro, M., Ed., Allen, A., McDonald, D., and P. 547 Gosden, "A Uniform Resource Name Namespace for the Global 548 System for Mobile Communications Association (GSMA) and 549 the International Mobile station Equipment Identity 550 (IMEI)", RFC 7254, DOI 10.17487/RFC7254, May 2014, 551 . 553 [I-D.atarius-dispatch-meid-urn] 554 Atarius, R., "A Uniform Resource Name Namespace for the 555 Device Identity and the Mobile Equipment Identity (MEID)", 556 draft-atarius-dispatch-meid-urn-18 (work in progress), 557 June 2018. 559 Appendix A. Changes from Previous Version 561 Version -03 of the WG draft removed some unnecessary references, 562 updated some other references, removed pct-encoding to ensure the DEV 563 URNs fit [RFC8428] Section 4.5.1 rules, and clarified that the 564 original source of the "os" and "ops" subtypes. 566 Version -02 of the WG draft folded in the "ops" and "os" branches of 567 the dev:urn syntax from LwM2M, as they seemed to match well what 568 already existed in this memo under the "org" branch. However, as a 569 part of this three changes were incorporated: 571 o The syntax for the "org:" changes to use "-" rather than ":" 572 between the OUI and the rest of the URN. 574 o The organizations for the "ops" and "os" branches have been 575 changed to use PEN numbers rather than OUI numbers [OUI]. The 576 reason for this is that PEN numbers are allocated through a 577 simpler and less costly process. However, this is a significant 578 change to how LwM2M identifiers were specified before. 580 o There were also changes to what general characters can be used in 581 the otherbody branch of the ABNF. 583 The rationale for all these changes is that it would be helpful for 584 the community collect and unify syntax between the different uses of 585 DEV URNs. If there is significant use of either the org:, os:, or 586 ops: subtypes, then changes at this point may not be warranted, but 587 otherwise unified syntax, as well as the use of PEN numbers would 588 probably be beneficial. Comments on this topic are appreciated. 590 Version -01 of the WG draft converted the draft to use the new URN 591 registration template from [RFC8141]. 593 Version -00 of the WG draft renamed the file name and fixed the ABNF 594 to correctly use "org:" rather than "dn:". 596 Version -05 made a change to the delimiter for parameters within a 597 DEV URN. Given discussions on allowed character sets in SenML 598 [RFC8428], we would like to suggest that the "_" character be used 599 instead of ";", to avoid the need to translate DEV URNs in SenML- 600 formatted communications or files. However, this reverses the 601 earlier decision to not use unreserved characters. This also means 602 that device IDs cannot use "_" characters, and have to employ other 603 characters instead. Feedback on this decision is sought. 605 Version -05 also introduced local or organisation-specific device 606 identifiers. Organisations are identified by their PEN number 607 (although we considered FQDNs as a potential alternative. The 608 authors belive an organisation-specific device identifier type will 609 make experiments and local use easier, but feedback on this point and 610 the choice of PEN numbers vs. other possible organisation identifiers 611 would be very welcome. 613 Version -05 also added some discussion of privacy concerns around 614 long-term stable identifiers. 616 Finally, version -05 clarified the situations when new allocations 617 within the registry of possible device identifier subtypes is 618 appropriate. 620 Version -04 is a refresh, as the need and interest for this 621 specification has re-emerged. And the editing author has emerged 622 back to actual engineering from the depths of IETF administration. 624 Version -02 introduced several changes. The biggest change is that 625 with the NI URNs [RFC6920], it was no longer necessary to define 626 cryptographic identifiers in this specification. Another change was 627 that we incorporated a more generic syntax for future extensions; 628 non-hexstring identifiers can now also be supported, if some future 629 device identifiers for some reason would, for instance, use BASE64. 630 As a part of this change, we also changed the component part 631 separator character from '-' to ';' so that the general format of the 632 rest of the URN can employ the unreserved characters [RFC3986]. 634 Appendix B. Acknowledgments 636 The authors would like to thank Ari Keranen, Stephen Farrell, 637 Christer Holmberg, Peter Saint-Andre, Wouter Cloetens, Jaime Jimenez, 638 Padmakumar Subramani, Mert Ocak, Hannes Tschofenig, and Ahmad Muhanna 639 for interesting discussions in this problem space. We would also 640 like to note prior documents that focused on specific device 641 identifiers, such as [RFC7254] or [I-D.atarius-dispatch-meid-urn]. 643 Authors' Addresses 645 Jari Arkko 646 Ericsson 647 Jorvas 02420 648 Finland 650 Email: jari.arkko@piuha.net 651 Cullen Jennings 652 Cisco 653 170 West Tasman Drive 654 San Jose, CA 95134 655 USA 657 Phone: +1 408 421-9990 658 Email: fluffy@cisco.com 660 Zach Shelby 661 ARM 662 Kidekuja 2 663 Vuokatti 88600 664 FINLAND 666 Phone: +358407796297 667 Email: Zach.Shelby@arm.com