Debian Codegraph @

rfc9039.html

raw
1 <!DOCTYPE html>
2 <html lang="en" class="RFC">
3 <head>
4 <meta charset="utf-8">
5 <meta content="Common,Latin" name="scripts">
6 <meta content="initial-scale=1.0" name="viewport">
7 <title>RFC 9039: Uniform Resource Names for Device Identifiers</title>
8 <meta content="Jari Arkko" name="author">
9 <meta content="Cullen Jennings" name="author">
10 <meta content="Zach Shelby" name="author">
11 <meta content="
12 This document describes a new Uniform Resource Name (URN) namespace for
13 hardware device identifiers. A general representation of device
14 identity can be useful in many applications, such as in sensor data
15 streams and storage or in equipment inventories. A URN-based
16 representation can be passed along in applications that
17 need the information.
18 " name="description">
19 <meta content="xml2rfc 3.9.1" name="generator">
20 <meta content="URN" name="keyword">
21 <meta content="device identifier" name="keyword">
22 <meta content="IMEI" name="keyword">
23 <meta content="1-Wire" name="keyword">
24 <meta content="MAC address" name="keyword">
25 <meta content="EUI-48" name="keyword">
26 <meta content="EUI-64" name="keyword">
27 <meta content="9039" name="rfc.number">
28 <!-- Generator version information:
29 xml2rfc 3.9.1
30 Python 3.6.10
31 appdirs 1.4.4
32 ConfigArgParse 1.2.3
33 google-i18n-address 2.3.5
34 html5lib 1.0.1
35 intervaltree 3.0.2
36 Jinja2 2.11.2
37 kitchen 1.2.6
38 lxml 4.4.2
39 pycairo 1.19.0
40 pycountry 19.8.18
41 pyflakes 2.1.1
42 PyYAML 5.3.1
43 requests 2.22.0
44 setuptools 40.6.2
45 six 1.14.0
46 WeasyPrint 51
47 -->
48 <link href="rfc9039.xml" rel="alternate" type="application/rfc+xml">
49 <link href="#copyright" rel="license">
50 <style type="text/css">/*
51
52 NOTE: Changes at the bottom of this file overrides some earlier settings.
53
54 Once the style has stabilized and has been adopted as an official RFC style,
55 this can be consolidated so that style settings occur only in one place, but
56 for now the contents of this file consists first of the initial CSS work as
57 provided to the RFC Formatter (xml2rfc) work, followed by itemized and
58 commented changes found necssary during the development of the v3
59 formatters.
60
61 */
62
63 /* fonts */
64 @import url('https://fonts.googleapis.com/css?family=Noto+Sans'); /* Sans-serif */
65 @import url('https://fonts.googleapis.com/css?family=Noto+Serif'); /* Serif (print) */
66 @import url('https://fonts.googleapis.com/css?family=Roboto+Mono'); /* Monospace */
67
68 @viewport {
69 zoom: 1.0;
70 width: extend-to-zoom;
71 }
72 @-ms-viewport {
73 width: extend-to-zoom;
74 zoom: 1.0;
75 }
76 /* general and mobile first */
77 html {
78 }
79 body {
80 max-width: 90%;
81 margin: 1.5em auto;
82 color: #222;
83 background-color: #fff;
84 font-size: 14px;
85 font-family: 'Noto Sans', Arial, Helvetica, sans-serif;
86 line-height: 1.6;
87 scroll-behavior: smooth;
88 }
89 .ears {
90 display: none;
91 }
92
93 /* headings */
94 #title, h1, h2, h3, h4, h5, h6 {
95 margin: 1em 0 0.5em;
96 font-weight: bold;
97 line-height: 1.3;
98 }
99 #title {
100 clear: both;
101 border-bottom: 1px solid #ddd;
102 margin: 0 0 0.5em 0;
103 padding: 1em 0 0.5em;
104 }
105 .author {
106 padding-bottom: 4px;
107 }
108 h1 {
109 font-size: 26px;
110 margin: 1em 0;
111 }
112 h2 {
113 font-size: 22px;
114 margin-top: -20px; /* provide offset for in-page anchors */
115 padding-top: 33px;
116 }
117 h3 {
118 font-size: 18px;
119 margin-top: -36px; /* provide offset for in-page anchors */
120 padding-top: 42px;
121 }
122 h4 {
123 font-size: 16px;
124 margin-top: -36px; /* provide offset for in-page anchors */
125 padding-top: 42px;
126 }
127 h5, h6 {
128 font-size: 14px;
129 }
130 #n-copyright-notice {
131 border-bottom: 1px solid #ddd;
132 padding-bottom: 1em;
133 margin-bottom: 1em;
134 }
135 /* general structure */
136 p {
137 padding: 0;
138 margin: 0 0 1em 0;
139 text-align: left;
140 }
141 div, span {
142 position: relative;
143 }
144 div {
145 margin: 0;
146 }
147 .alignRight.art-text {
148 background-color: #f9f9f9;
149 border: 1px solid #eee;
150 border-radius: 3px;
151 padding: 1em 1em 0;
152 margin-bottom: 1.5em;
153 }
154 .alignRight.art-text pre {
155 padding: 0;
156 }
157 .alignRight {
158 margin: 1em 0;
159 }
160 .alignRight > *:first-child {
161 border: none;
162 margin: 0;
163 float: right;
164 clear: both;
165 }
166 .alignRight > *:nth-child(2) {
167 clear: both;
168 display: block;
169 border: none;
170 }
171 svg {
172 display: block;
173 }
174 .alignCenter.art-text {
175 background-color: #f9f9f9;
176 border: 1px solid #eee;
177 border-radius: 3px;
178 padding: 1em 1em 0;
179 margin-bottom: 1.5em;
180 }
181 .alignCenter.art-text pre {
182 padding: 0;
183 }
184 .alignCenter {
185 margin: 1em 0;
186 }
187 .alignCenter > *:first-child {
188 border: none;
189 /* this isn't optimal, but it's an existence proof. PrinceXML doesn't
190 support flexbox yet.
191 */
192 display: table;
193 margin: 0 auto;
194 }
195
196 /* lists */
197 ol, ul {
198 padding: 0;
199 margin: 0 0 1em 2em;
200 }
201 ol ol, ul ul, ol ul, ul ol {
202 margin-left: 1em;
203 }
204 li {
205 margin: 0 0 0.25em 0;
206 }
207 .ulCompact li {
208 margin: 0;
209 }
210 ul.empty, .ulEmpty {
211 list-style-type: none;
212 }
213 ul.empty li, .ulEmpty li {
214 margin-top: 0.5em;
215 }
216 ul.ulBare, li.ulBare {
217 margin-left: 0em !important;
218 }
219 ul.compact, .ulCompact,
220 ol.compact, .olCompact {
221 line-height: 100%;
222 margin: 0 0 0 2em;
223 }
224
225 /* definition lists */
226 dl {
227 }
228 dl > dt {
229 float: left;
230 margin-right: 1em;
231 }
232 /*
233 dl.nohang > dt {
234 float: none;
235 }
236 */
237 dl > dd {
238 margin-bottom: .8em;
239 min-height: 1.3em;
240 }
241 dl.compact > dd, .dlCompact > dd {
242 margin-bottom: 0em;
243 }
244 dl > dd > dl {
245 margin-top: 0.5em;
246 margin-bottom: 0em;
247 }
248
249 /* links */
250 a {
251 text-decoration: none;
252 }
253 a[href] {
254 color: #22e; /* Arlen: WCAG 2019 */
255 }
256 a[href]:hover {
257 background-color: #f2f2f2;
258 }
259 figcaption a[href],
260 a[href].selfRef {
261 color: #222;
262 }
263 /* XXX probably not this:
264 a.selfRef:hover {
265 background-color: transparent;
266 cursor: default;
267 } */
268
269 /* Figures */
270 tt, code, pre, code {
271 background-color: #f9f9f9;
272 font-family: 'Roboto Mono', monospace;
273 }
274 pre {
275 border: 1px solid #eee;
276 margin: 0;
277 padding: 1em;
278 }
279 img {
280 max-width: 100%;
281 }
282 figure {
283 margin: 0;
284 }
285 figure blockquote {
286 margin: 0.8em 0.4em 0.4em;
287 }
288 figcaption {
289 font-style: italic;
290 margin: 0 0 1em 0;
291 }
292 @media screen {
293 pre {
294 overflow-x: auto;
295 max-width: 100%;
296 max-width: calc(100% - 22px);
297 }
298 }
299
300 /* aside, blockquote */
301 aside, blockquote {
302 margin-left: 0;
303 padding: 1.2em 2em;
304 }
305 blockquote {
306 background-color: #f9f9f9;
307 color: #111; /* Arlen: WCAG 2019 */
308 border: 1px solid #ddd;
309 border-radius: 3px;
310 margin: 1em 0;
311 }
312 cite {
313 display: block;
314 text-align: right;
315 font-style: italic;
316 }
317
318 /* tables */
319 table {
320 width: 100%;
321 margin: 0 0 1em;
322 border-collapse: collapse;
323 border: 1px solid #eee;
324 }
325 th, td {
326 text-align: left;
327 vertical-align: top;
328 padding: 0.5em 0.75em;
329 }
330 th {
331 text-align: left;
332 background-color: #e9e9e9;
333 }
334 tr:nth-child(2n+1) > td {
335 background-color: #f5f5f5;
336 }
337 table caption {
338 font-style: italic;
339 margin: 0;
340 padding: 0;
341 text-align: left;
342 }
343 table p {
344 /* XXX to avoid bottom margin on table row signifiers. If paragraphs should
345 be allowed within tables more generally, it would be far better to select on a class. */
346 margin: 0;
347 }
348
349 /* pilcrow */
350 a.pilcrow {
351 color: #666; /* Arlen: AHDJ 2019 */
352 text-decoration: none;
353 visibility: hidden;
354 user-select: none;
355 -ms-user-select: none;
356 -o-user-select:none;
357 -moz-user-select: none;
358 -khtml-user-select: none;
359 -webkit-user-select: none;
360 -webkit-touch-callout: none;
361 }
362 @media screen {
363 aside:hover > a.pilcrow,
364 p:hover > a.pilcrow,
365 blockquote:hover > a.pilcrow,
366 div:hover > a.pilcrow,
367 li:hover > a.pilcrow,
368 pre:hover > a.pilcrow {
369 visibility: visible;
370 }
371 a.pilcrow:hover {
372 background-color: transparent;
373 }
374 }
375
376 /* misc */
377 hr {
378 border: 0;
379 border-top: 1px solid #eee;
380 }
381 .bcp14 {
382 font-variant: small-caps;
383 }
384
385 .role {
386 font-variant: all-small-caps;
387 }
388
389 /* info block */
390 #identifiers {
391 margin: 0;
392 font-size: 0.9em;
393 }
394 #identifiers dt {
395 width: 3em;
396 clear: left;
397 }
398 #identifiers dd {
399 float: left;
400 margin-bottom: 0;
401 }
402 #identifiers .authors .author {
403 display: inline-block;
404 margin-right: 1.5em;
405 }
406 #identifiers .authors .org {
407 font-style: italic;
408 }
409
410 /* The prepared/rendered info at the very bottom of the page */
411 .docInfo {
412 color: #666; /* Arlen: WCAG 2019 */
413 font-size: 0.9em;
414 font-style: italic;
415 margin-top: 2em;
416 }
417 .docInfo .prepared {
418 float: left;
419 }
420 .docInfo .prepared {
421 float: right;
422 }
423
424 /* table of contents */
425 #toc {
426 padding: 0.75em 0 2em 0;
427 margin-bottom: 1em;
428 }
429 nav.toc ul {
430 margin: 0 0.5em 0 0;
431 padding: 0;
432 list-style: none;
433 }
434 nav.toc li {
435 line-height: 1.3em;
436 margin: 0.75em 0;
437 padding-left: 1.2em;
438 text-indent: -1.2em;
439 }
440 /* references */
441 .references dt {
442 text-align: right;
443 font-weight: bold;
444 min-width: 7em;
445 }
446 .references dd {
447 margin-left: 8em;
448 overflow: auto;
449 }
450
451 .refInstance {
452 margin-bottom: 1.25em;
453 }
454
455 .references .ascii {
456 margin-bottom: 0.25em;
457 }
458
459 /* index */
460 .index ul {
461 margin: 0 0 0 1em;
462 padding: 0;
463 list-style: none;
464 }
465 .index ul ul {
466 margin: 0;
467 }
468 .index li {
469 margin: 0;
470 text-indent: -2em;
471 padding-left: 2em;
472 padding-bottom: 5px;
473 }
474 .indexIndex {
475 margin: 0.5em 0 1em;
476 }
477 .index a {
478 font-weight: 700;
479 }
480 /* make the index two-column on all but the smallest screens */
481 @media (min-width: 600px) {
482 .index ul {
483 -moz-column-count: 2;
484 -moz-column-gap: 20px;
485 }
486 .index ul ul {
487 -moz-column-count: 1;
488 -moz-column-gap: 0;
489 }
490 }
491
492 /* authors */
493 address.vcard {
494 font-style: normal;
495 margin: 1em 0;
496 }
497
498 address.vcard .nameRole {
499 font-weight: 700;
500 margin-left: 0;
501 }
502 address.vcard .label {
503 font-family: "Noto Sans",Arial,Helvetica,sans-serif;
504 margin: 0.5em 0;
505 }
506 address.vcard .type {
507 display: none;
508 }
509 .alternative-contact {
510 margin: 1.5em 0 1em;
511 }
512 hr.addr {
513 border-top: 1px dashed;
514 margin: 0;
515 color: #ddd;
516 max-width: calc(100% - 16px);
517 }
518
519 /* temporary notes */
520 .rfcEditorRemove::before {
521 position: absolute;
522 top: 0.2em;
523 right: 0.2em;
524 padding: 0.2em;
525 content: "The RFC Editor will remove this note";
526 color: #9e2a00; /* Arlen: WCAG 2019 */
527 background-color: #ffd; /* Arlen: WCAG 2019 */
528 }
529 .rfcEditorRemove {
530 position: relative;
531 padding-top: 1.8em;
532 background-color: #ffd; /* Arlen: WCAG 2019 */
533 border-radius: 3px;
534 }
535 .cref {
536 background-color: #ffd; /* Arlen: WCAG 2019 */
537 padding: 2px 4px;
538 }
539 .crefSource {
540 font-style: italic;
541 }
542 /* alternative layout for smaller screens */
543 @media screen and (max-width: 1023px) {
544 body {
545 padding-top: 2em;
546 }
547 #title {
548 padding: 1em 0;
549 }
550 h1 {
551 font-size: 24px;
552 }
553 h2 {
554 font-size: 20px;
555 margin-top: -18px; /* provide offset for in-page anchors */
556 padding-top: 38px;
557 }
558 #identifiers dd {
559 max-width: 60%;
560 }
561 #toc {
562 position: fixed;
563 z-index: 2;
564 top: 0;
565 right: 0;
566 padding: 0;
567 margin: 0;
568 background-color: inherit;
569 border-bottom: 1px solid #ccc;
570 }
571 #toc h2 {
572 margin: -1px 0 0 0;
573 padding: 4px 0 4px 6px;
574 padding-right: 1em;
575 min-width: 190px;
576 font-size: 1.1em;
577 text-align: right;
578 background-color: #444;
579 color: white;
580 cursor: pointer;
581 }
582 #toc h2::before { /* css hamburger */
583 float: right;
584 position: relative;
585 width: 1em;
586 height: 1px;
587 left: -164px;
588 margin: 6px 0 0 0;
589 background: white none repeat scroll 0 0;
590 box-shadow: 0 4px 0 0 white, 0 8px 0 0 white;
591 content: "";
592 }
593 #toc nav {
594 display: none;
595 padding: 0.5em 1em 1em;
596 overflow: auto;
597 height: calc(100vh - 48px);
598 border-left: 1px solid #ddd;
599 }
600 }
601
602 /* alternative layout for wide screens */
603 @media screen and (min-width: 1024px) {
604 body {
605 max-width: 724px;
606 margin: 42px auto;
607 padding-left: 1.5em;
608 padding-right: 29em;
609 }
610 #toc {
611 position: fixed;
612 top: 42px;
613 right: 42px;
614 width: 25%;
615 margin: 0;
616 padding: 0 1em;
617 z-index: 1;
618 }
619 #toc h2 {
620 border-top: none;
621 border-bottom: 1px solid #ddd;
622 font-size: 1em;
623 font-weight: normal;
624 margin: 0;
625 padding: 0.25em 1em 1em 0;
626 }
627 #toc nav {
628 display: block;
629 height: calc(90vh - 84px);
630 bottom: 0;
631 padding: 0.5em 0 0;
632 overflow: auto;
633 }
634 img { /* future proofing */
635 max-width: 100%;
636 height: auto;
637 }
638 }
639
640 /* pagination */
641 @media print {
642 body {
643
644 width: 100%;
645 }
646 p {
647 orphans: 3;
648 widows: 3;
649 }
650 #n-copyright-notice {
651 border-bottom: none;
652 }
653 #toc, #n-introduction {
654 page-break-before: always;
655 }
656 #toc {
657 border-top: none;
658 padding-top: 0;
659 }
660 figure, pre {
661 page-break-inside: avoid;
662 }
663 figure {
664 overflow: scroll;
665 }
666 h1, h2, h3, h4, h5, h6 {
667 page-break-after: avoid;
668 }
669 h2+*, h3+*, h4+*, h5+*, h6+* {
670 page-break-before: avoid;
671 }
672 pre {
673 white-space: pre-wrap;
674 word-wrap: break-word;
675 font-size: 10pt;
676 }
677 table {
678 border: 1px solid #ddd;
679 }
680 td {
681 border-top: 1px solid #ddd;
682 }
683 }
684
685 /* This is commented out here, as the string-set: doesn't
686 pass W3C validation currently */
687 /*
688 .ears thead .left {
689 string-set: ears-top-left content();
690 }
691
692 .ears thead .center {
693 string-set: ears-top-center content();
694 }
695
696 .ears thead .right {
697 string-set: ears-top-right content();
698 }
699
700 .ears tfoot .left {
701 string-set: ears-bottom-left content();
702 }
703
704 .ears tfoot .center {
705 string-set: ears-bottom-center content();
706 }
707
708 .ears tfoot .right {
709 string-set: ears-bottom-right content();
710 }
711 */
712
713 @page :first {
714 padding-top: 0;
715 @top-left {
716 content: normal;
717 border: none;
718 }
719 @top-center {
720 content: normal;
721 border: none;
722 }
723 @top-right {
724 content: normal;
725 border: none;
726 }
727 }
728
729 @page {
730 size: A4;
731 margin-bottom: 45mm;
732 padding-top: 20px;
733 /* The follwing is commented out here, but set appropriately by in code, as
734 the content depends on the document */
735 /*
736 @top-left {
737 content: 'Internet-Draft';
738 vertical-align: bottom;
739 border-bottom: solid 1px #ccc;
740 }
741 @top-left {
742 content: string(ears-top-left);
743 vertical-align: bottom;
744 border-bottom: solid 1px #ccc;
745 }
746 @top-center {
747 content: string(ears-top-center);
748 vertical-align: bottom;
749 border-bottom: solid 1px #ccc;
750 }
751 @top-right {
752 content: string(ears-top-right);
753 vertical-align: bottom;
754 border-bottom: solid 1px #ccc;
755 }
756 @bottom-left {
757 content: string(ears-bottom-left);
758 vertical-align: top;
759 border-top: solid 1px #ccc;
760 }
761 @bottom-center {
762 content: string(ears-bottom-center);
763 vertical-align: top;
764 border-top: solid 1px #ccc;
765 }
766 @bottom-right {
767 content: '[Page ' counter(page) ']';
768 vertical-align: top;
769 border-top: solid 1px #ccc;
770 }
771 */
772
773 }
774
775 /* Changes introduced to fix issues found during implementation */
776 /* Make sure links are clickable even if overlapped by following H* */
777 a {
778 z-index: 2;
779 }
780 /* Separate body from document info even without intervening H1 */
781 section {
782 clear: both;
783 }
784
785
786 /* Top align author divs, to avoid names without organization dropping level with org names */
787 .author {
788 vertical-align: top;
789 }
790
791 /* Leave room in document info to show Internet-Draft on one line */
792 #identifiers dt {
793 width: 8em;
794 }
795
796 /* Don't waste quite as much whitespace between label and value in doc info */
797 #identifiers dd {
798 margin-left: 1em;
799 }
800
801 /* Give floating toc a background color (needed when it's a div inside section */
802 #toc {
803 background-color: white;
804 }
805
806 /* Make the collapsed ToC header render white on gray also when it's a link */
807 @media screen and (max-width: 1023px) {
808 #toc h2 a,
809 #toc h2 a:link,
810 #toc h2 a:focus,
811 #toc h2 a:hover,
812 #toc a.toplink,
813 #toc a.toplink:hover {
814 color: white;
815 background-color: #444;
816 text-decoration: none;
817 }
818 }
819
820 /* Give the bottom of the ToC some whitespace */
821 @media screen and (min-width: 1024px) {
822 #toc {
823 padding: 0 0 1em 1em;
824 }
825 }
826
827 /* Style section numbers with more space between number and title */
828 .section-number {
829 padding-right: 0.5em;
830 }
831
832 /* prevent monospace from becoming overly large */
833 tt, code, pre, code {
834 font-size: 95%;
835 }
836
837 /* Fix the height/width aspect for ascii art*/
838 pre.sourcecode,
839 .art-text pre {
840 line-height: 1.12;
841 }
842
843
844 /* Add styling for a link in the ToC that points to the top of the document */
845 a.toplink {
846 float: right;
847 margin-right: 0.5em;
848 }
849
850 /* Fix the dl styling to match the RFC 7992 attributes */
851 dl > dt,
852 dl.dlParallel > dt {
853 float: left;
854 margin-right: 1em;
855 }
856 dl.dlNewline > dt {
857 float: none;
858 }
859
860 /* Provide styling for table cell text alignment */
861 table td.text-left,
862 table th.text-left {
863 text-align: left;
864 }
865 table td.text-center,
866 table th.text-center {
867 text-align: center;
868 }
869 table td.text-right,
870 table th.text-right {
871 text-align: right;
872 }
873
874 /* Make the alternative author contact informatio look less like just another
875 author, and group it closer with the primary author contact information */
876 .alternative-contact {
877 margin: 0.5em 0 0.25em 0;
878 }
879 address .non-ascii {
880 margin: 0 0 0 2em;
881 }
882
883 /* With it being possible to set tables with alignment
884 left, center, and right, { width: 100%; } does not make sense */
885 table {
886 width: auto;
887 }
888
889 /* Avoid reference text that sits in a block with very wide left margin,
890 because of a long floating dt label.*/
891 .references dd {
892 overflow: visible;
893 }
894
895 /* Control caption placement */
896 caption {
897 caption-side: bottom;
898 }
899
900 /* Limit the width of the author address vcard, so names in right-to-left
901 script don't end up on the other side of the page. */
902
903 address.vcard {
904 max-width: 30em;
905 margin-right: auto;
906 }
907
908 /* For address alignment dependent on LTR or RTL scripts */
909 address div.left {
910 text-align: left;
911 }
912 address div.right {
913 text-align: right;
914 }
915
916 /* Provide table alignment support. We can't use the alignX classes above
917 since they do unwanted things with caption and other styling. */
918 table.right {
919 margin-left: auto;
920 margin-right: 0;
921 }
922 table.center {
923 margin-left: auto;
924 margin-right: auto;
925 }
926 table.left {
927 margin-left: 0;
928 margin-right: auto;
929 }
930
931 /* Give the table caption label the same styling as the figcaption */
932 caption a[href] {
933 color: #222;
934 }
935
936 @media print {
937 .toplink {
938 display: none;
939 }
940
941 /* avoid overwriting the top border line with the ToC header */
942 #toc {
943 padding-top: 1px;
944 }
945
946 /* Avoid page breaks inside dl and author address entries */
947 .vcard {
948 page-break-inside: avoid;
949 }
950
951 }
952 /* Tweak the bcp14 keyword presentation */
953 .bcp14 {
954 font-variant: small-caps;
955 font-weight: bold;
956 font-size: 0.9em;
957 }
958 /* Tweak the invisible space above H* in order not to overlay links in text above */
959 h2 {
960 margin-top: -18px; /* provide offset for in-page anchors */
961 padding-top: 31px;
962 }
963 h3 {
964 margin-top: -18px; /* provide offset for in-page anchors */
965 padding-top: 24px;
966 }
967 h4 {
968 margin-top: -18px; /* provide offset for in-page anchors */
969 padding-top: 24px;
970 }
971 /* Float artwork pilcrow to the right */
972 @media screen {
973 .artwork a.pilcrow {
974 display: block;
975 line-height: 0.7;
976 margin-top: 0.15em;
977 }
978 }
979 /* Make pilcrows on dd visible */
980 @media screen {
981 dd:hover > a.pilcrow {
982 visibility: visible;
983 }
984 }
985 /* Make the placement of figcaption match that of a table's caption
986 by removing the figure's added bottom margin */
987 .alignLeft.art-text,
988 .alignCenter.art-text,
989 .alignRight.art-text {
990 margin-bottom: 0;
991 }
992 .alignLeft,
993 .alignCenter,
994 .alignRight {
995 margin: 1em 0 0 0;
996 }
997 /* In print, the pilcrow won't show on hover, so prevent it from taking up space,
998 possibly even requiring a new line */
999 @media print {
1000 a.pilcrow {
1001 display: none;
1002 }
1003 }
1004 /* Styling for the external metadata */
1005 div#external-metadata {
1006 background-color: #eee;
1007 padding: 0.5em;
1008 margin-bottom: 0.5em;
1009 display: none;
1010 }
1011 div#internal-metadata {
1012 padding: 0.5em; /* to match the external-metadata padding */
1013 }
1014 /* Styling for title RFC Number */
1015 h1#rfcnum {
1016 clear: both;
1017 margin: 0 0 -1em;
1018 padding: 1em 0 0 0;
1019 }
1020 /* Make .olPercent look the same as <ol><li> */
1021 dl.olPercent > dd {
1022 margin-bottom: 0.25em;
1023 min-height: initial;
1024 }
1025 /* Give aside some styling to set it apart */
1026 aside {
1027 border-left: 1px solid #ddd;
1028 margin: 1em 0 1em 2em;
1029 padding: 0.2em 2em;
1030 }
1031 aside > dl,
1032 aside > ol,
1033 aside > ul,
1034 aside > table,
1035 aside > p {
1036 margin-bottom: 0.5em;
1037 }
1038 /* Additional page break settings */
1039 @media print {
1040 figcaption, table caption {
1041 page-break-before: avoid;
1042 }
1043 }
1044 /* Font size adjustments for print */
1045 @media print {
1046 body { font-size: 10pt; line-height: normal; max-width: 96%; }
1047 h1 { font-size: 1.72em; padding-top: 1.5em; } /* 1*1.2*1.2*1.2 */
1048 h2 { font-size: 1.44em; padding-top: 1.5em; } /* 1*1.2*1.2 */
1049 h3 { font-size: 1.2em; padding-top: 1.5em; } /* 1*1.2 */
1050 h4 { font-size: 1em; padding-top: 1.5em; }
1051 h5, h6 { font-size: 1em; margin: initial; padding: 0.5em 0 0.3em; }
1052 }
1053 /* Sourcecode margin in print, when there's no pilcrow */
1054 @media print {
1055 .artwork,
1056 .sourcecode {
1057 margin-bottom: 1em;
1058 }
1059 }
1060 /* Avoid narrow tables forcing too narrow table captions, which may render badly */
1061 table {
1062 min-width: 20em;
1063 }
1064 /* ol type a */
1065 ol.type-a { list-style-type: lower-alpha; }
1066 ol.type-A { list-style-type: upper-alpha; }
1067 ol.type-i { list-style-type: lower-roman; }
1068 ol.type-I { list-style-type: lower-roman; }
1069 /* Apply the print table and row borders in general, on request from the RPC,
1070 and increase the contrast between border and odd row background sligthtly */
1071 table {
1072 border: 1px solid #ddd;
1073 }
1074 td {
1075 border-top: 1px solid #ddd;
1076 }
1077 tr:nth-child(2n+1) > td {
1078 background-color: #f8f8f8;
1079 }
1080 /* Use style rules to govern display of the TOC. */
1081 @media screen and (max-width: 1023px) {
1082 #toc nav { display: none; }
1083 #toc.active nav { display: block; }
1084 }
1085 /* Add support for keepWithNext */
1086 .keepWithNext {
1087 break-after: avoid-page;
1088 break-after: avoid-page;
1089 }
1090 /* Add support for keepWithPrevious */
1091 .keepWithPrevious {
1092 break-before: avoid-page;
1093 }
1094 /* Change the approach to avoiding breaks inside artwork etc. */
1095 figure, pre, table, .artwork, .sourcecode {
1096 break-before: avoid-page;
1097 break-after: auto;
1098 }
1099 /* Avoid breaks between <dt> and <dd> */
1100 dl {
1101 break-before: auto;
1102 break-inside: auto;
1103 }
1104 dt {
1105 break-before: auto;
1106 break-after: avoid-page;
1107 }
1108 dd {
1109 break-before: avoid-page;
1110 break-after: auto;
1111 orphans: 3;
1112 widows: 3
1113 }
1114 span.break, dd.break {
1115 margin-bottom: 0;
1116 min-height: 0;
1117 break-before: auto;
1118 break-inside: auto;
1119 break-after: auto;
1120 }
1121 /* Undo break-before ToC */
1122 @media print {
1123 #toc {
1124 break-before: auto;
1125 }
1126 }
1127 /* Text in compact lists should not get extra bottim margin space,
1128 since that would makes the list not compact */
1129 ul.compact p, .ulCompact p,
1130 ol.compact p, .olCompact p {
1131 margin: 0;
1132 }
1133 /* But the list as a whole needs the extra space at the end */
1134 section ul.compact,
1135 section .ulCompact,
1136 section ol.compact,
1137 section .olCompact {
1138 margin-bottom: 1em; /* same as p not within ul.compact etc. */
1139 }
1140 /* The tt and code background above interferes with for instance table cell
1141 backgrounds. Changed to something a bit more selective. */
1142 tt, code {
1143 background-color: transparent;
1144 }
1145 p tt, p code, li tt, li code {
1146 background-color: #f8f8f8;
1147 }
1148 /* Tweak the pre margin -- 0px doesn't come out well */
1149 pre {
1150 margin-top: 0.5px;
1151 }
1152 /* Tweak the comact list text */
1153 ul.compact, .ulCompact,
1154 ol.compact, .olCompact,
1155 dl.compact, .dlCompact {
1156 line-height: normal;
1157 }
1158 /* Don't add top margin for nested lists */
1159 li > ul, li > ol, li > dl,
1160 dd > ul, dd > ol, dd > dl,
1161 dl > dd > dl {
1162 margin-top: initial;
1163 }
1164 /* Elements that should not be rendered on the same line as a <dt> */
1165 /* This should match the element list in writer.text.TextWriter.render_dl() */
1166 dd > div.artwork:first-child,
1167 dd > aside:first-child,
1168 dd > figure:first-child,
1169 dd > ol:first-child,
1170 dd > div:first-child > pre.sourcecode,
1171 dd > table:first-child,
1172 dd > ul:first-child {
1173 clear: left;
1174 }
1175 /* fix for weird browser behaviour when <dd/> is empty */
1176 dt+dd:empty::before{
1177 content: "\00a0";
1178 }
1179 /* Make paragraph spacing inside <li> smaller than in body text, to fit better within the list */
1180 li > p {
1181 margin-bottom: 0.5em
1182 }
1183 /* Don't let p margin spill out from inside list items */
1184 li > p:last-of-type {
1185 margin-bottom: 0;
1186 }
1187 </style>
1188 <link href="rfc-local.css" rel="stylesheet" type="text/css">
1189 <link href="https://dx.doi.org/10.17487/rfc9039" rel="alternate">
1190 <link href="urn:issn:2070-1721" rel="alternate">
1191 <link href="https://datatracker.ietf.org/doc/draft-ietf-core-dev-urn-11" rel="prev">
1192 </head>
1193 <body>
1194 <script src="https://www.rfc-editor.org/js/metadata.min.js"></script>
1195 <table class="ears">
1196 <thead><tr>
1197 <td class="left">RFC 9039</td>
1198 <td class="center">DEV URN</td>
1199 <td class="right">June 2021</td>
1200 </tr></thead>
1201 <tfoot><tr>
1202 <td class="left">Arkko, et al.</td>
1203 <td class="center">Standards Track</td>
1204 <td class="right">[Page]</td>
1205 </tr></tfoot>
1206 </table>
1207 <div id="external-metadata" class="document-information"></div>
1208 <div id="internal-metadata" class="document-information">
1209 <dl id="identifiers">
1210 <dt class="label-stream">Stream:</dt>
1211 <dd class="stream">Internet Engineering Task Force (IETF)</dd>
1212 <dt class="label-rfc">RFC:</dt>
1213 <dd class="rfc"><a href="https://www.rfc-editor.org/rfc/rfc9039" class="eref">9039</a></dd>
1214 <dt class="label-category">Category:</dt>
1215 <dd class="category">Standards Track</dd>
1216 <dt class="label-published">Published:</dt>
1217 <dd class="published">
1218 <time datetime="2021-06" class="published">June 2021</time>
1219 </dd>
1220 <dt class="label-issn">ISSN:</dt>
1221 <dd class="issn">2070-1721</dd>
1222 <dt class="label-authors">Authors:</dt>
1223 <dd class="authors">
1224 <div class="author">
1225 <div class="author-name">J. Arkko</div>
1226 <div class="org">Ericsson</div>
1227 </div>
1228 <div class="author">
1229 <div class="author-name">C. Jennings</div>
1230 <div class="org">Cisco</div>
1231 </div>
1232 <div class="author">
1233 <div class="author-name">Z. Shelby</div>
1234 <div class="org">Edge Impulse</div>
1235 </div>
1236 </dd>
1237 </dl>
1238 </div>
1239 <h1 id="rfcnum">RFC 9039</h1>
1240 <h1 id="title">Uniform Resource Names for Device Identifiers</h1>
1241 <section id="section-abstract">
1242 <h2 id="abstract"><a href="#abstract" class="selfRef">Abstract</a></h2>
1243 <p id="section-abstract-1">This document describes a new Uniform Resource Name (URN) namespace for
1244 hardware device identifiers. A general representation of device
1245 identity can be useful in many applications, such as in sensor data
1246 streams and storage or in equipment inventories. A URN-based
1247 representation can be passed along in applications that
1248 need the information.<a href="#section-abstract-1" class="pilcrow">¶</a></p>
1249 </section>
1250 <div id="status-of-memo">
1251 <section id="section-boilerplate.1">
1252 <h2 id="name-status-of-this-memo">
1253 <a href="#name-status-of-this-memo" class="section-name selfRef">Status of This Memo</a>
1254 </h2>
1255 <p id="section-boilerplate.1-1">
1256 This is an Internet Standards Track document.<a href="#section-boilerplate.1-1" class="pilcrow">¶</a></p>
1257 <p id="section-boilerplate.1-2">
1258 This document is a product of the Internet Engineering Task Force
1259 (IETF). It represents the consensus of the IETF community. It has
1260 received public review and has been approved for publication by
1261 the Internet Engineering Steering Group (IESG). Further
1262 information on Internet Standards is available in Section 2 of
1263 RFC 7841.<a href="#section-boilerplate.1-2" class="pilcrow">¶</a></p>
1264 <p id="section-boilerplate.1-3">
1265 Information about the current status of this document, any
1266 errata, and how to provide feedback on it may be obtained at
1267 <span><a href="https://www.rfc-editor.org/info/rfc9039">https://www.rfc-editor.org/info/rfc9039</a></span>.<a href="#section-boilerplate.1-3" class="pilcrow">¶</a></p>
1268 </section>
1269 </div>
1270 <div id="copyright">
1271 <section id="section-boilerplate.2">
1272 <h2 id="name-copyright-notice">
1273 <a href="#name-copyright-notice" class="section-name selfRef">Copyright Notice</a>
1274 </h2>
1275 <p id="section-boilerplate.2-1">
1276 Copyright (c) 2021 IETF Trust and the persons identified as the
1277 document authors. All rights reserved.<a href="#section-boilerplate.2-1" class="pilcrow">¶</a></p>
1278 <p id="section-boilerplate.2-2">
1279 This document is subject to BCP 78 and the IETF Trust's Legal
1280 Provisions Relating to IETF Documents
1281 (<span><a href="https://trustee.ietf.org/license-info">https://trustee.ietf.org/license-info</a></span>) in effect on the date of
1282 publication of this document. Please review these documents
1283 carefully, as they describe your rights and restrictions with
1284 respect to this document. Code Components extracted from this
1285 document must include Simplified BSD License text as described in
1286 Section 4.e of the Trust Legal Provisions and are provided without
1287 warranty as described in the Simplified BSD License.<a href="#section-boilerplate.2-2" class="pilcrow">¶</a></p>
1288 </section>
1289 </div>
1290 <div id="toc">
1291 <section id="section-toc.1">
1292 <a href="#" onclick="scroll(0,0)" class="toplink">▲</a><h2 id="name-table-of-contents">
1293 <a href="#name-table-of-contents" class="section-name selfRef">Table of Contents</a>
1294 </h2>
1295 <nav class="toc"><ul class="toc ulEmpty compact ulBare">
1296 <li class="toc ulEmpty compact ulBare" id="section-toc.1-1.1">
1297 <p id="section-toc.1-1.1.1" class="keepWithNext"><a href="#section-1" class="xref">1</a>.  <a href="#name-introduction" class="xref">Introduction</a></p>
1298 </li>
1299 <li class="toc ulEmpty compact ulBare" id="section-toc.1-1.2">
1300 <p id="section-toc.1-1.2.1" class="keepWithNext"><a href="#section-2" class="xref">2</a>.  <a href="#name-requirements-language" class="xref">Requirements Language</a></p>
1301 </li>
1302 <li class="toc ulEmpty compact ulBare" id="section-toc.1-1.3">
1303 <p id="section-toc.1-1.3.1"><a href="#section-3" class="xref">3</a>.  <a href="#name-dev-urn-definition" class="xref">DEV URN Definition</a></p>
1304 <ul class="toc ulEmpty compact ulBare">
1305 <li class="toc ulEmpty compact ulBare" id="section-toc.1-1.3.2.1">
1306 <p id="section-toc.1-1.3.2.1.1" class="keepWithNext"><a href="#section-3.1" class="xref">3.1</a>.  <a href="#name-purpose" class="xref">Purpose</a></p>
1307 </li>
1308 <li class="toc ulEmpty compact ulBare" id="section-toc.1-1.3.2.2">
1309 <p id="section-toc.1-1.3.2.2.1"><a href="#section-3.2" class="xref">3.2</a>.  <a href="#name-syntax" class="xref">Syntax</a></p>
1310 <ul class="toc ulEmpty compact ulBare">
1311 <li class="toc ulEmpty compact ulBare" id="section-toc.1-1.3.2.2.2.1">
1312 <p id="section-toc.1-1.3.2.2.2.1.1"><a href="#section-3.2.1" class="xref">3.2.1</a>.  <a href="#name-character-case-and-urn-equi" class="xref">Character Case and URN-Equivalence</a></p>
1313 </li>
1314 </ul>
1315 </li>
1316 <li class="toc ulEmpty compact ulBare" id="section-toc.1-1.3.2.3">
1317 <p id="section-toc.1-1.3.2.3.1"><a href="#section-3.3" class="xref">3.3</a>.  <a href="#name-assignment" class="xref">Assignment</a></p>
1318 </li>
1319 <li class="toc ulEmpty compact ulBare" id="section-toc.1-1.3.2.4">
1320 <p id="section-toc.1-1.3.2.4.1"><a href="#section-3.4" class="xref">3.4</a>.  <a href="#name-security-and-privacy" class="xref">Security and Privacy</a></p>
1321 </li>
1322 <li class="toc ulEmpty compact ulBare" id="section-toc.1-1.3.2.5">
1323 <p id="section-toc.1-1.3.2.5.1"><a href="#section-3.5" class="xref">3.5</a>.  <a href="#name-interoperability" class="xref">Interoperability</a></p>
1324 </li>
1325 <li class="toc ulEmpty compact ulBare" id="section-toc.1-1.3.2.6">
1326 <p id="section-toc.1-1.3.2.6.1"><a href="#section-3.6" class="xref">3.6</a>.  <a href="#name-resolution" class="xref">Resolution</a></p>
1327 </li>
1328 <li class="toc ulEmpty compact ulBare" id="section-toc.1-1.3.2.7">
1329 <p id="section-toc.1-1.3.2.7.1"><a href="#section-3.7" class="xref">3.7</a>.  <a href="#name-documentation" class="xref">Documentation</a></p>
1330 </li>
1331 <li class="toc ulEmpty compact ulBare" id="section-toc.1-1.3.2.8">
1332 <p id="section-toc.1-1.3.2.8.1"><a href="#section-3.8" class="xref">3.8</a>.  <a href="#name-additional-information" class="xref">Additional Information</a></p>
1333 </li>
1334 <li class="toc ulEmpty compact ulBare" id="section-toc.1-1.3.2.9">
1335 <p id="section-toc.1-1.3.2.9.1"><a href="#section-3.9" class="xref">3.9</a>.  <a href="#name-revision-information" class="xref">Revision Information</a></p>
1336 </li>
1337 </ul>
1338 </li>
1339 <li class="toc ulEmpty compact ulBare" id="section-toc.1-1.4">
1340 <p id="section-toc.1-1.4.1"><a href="#section-4" class="xref">4</a>.  <a href="#name-dev-urn-subtypes" class="xref">DEV URN Subtypes</a></p>
1341 <ul class="toc ulEmpty compact ulBare">
1342 <li class="toc ulEmpty compact ulBare" id="section-toc.1-1.4.2.1">
1343 <p id="section-toc.1-1.4.2.1.1"><a href="#section-4.1" class="xref">4.1</a>.  <a href="#name-mac-addresses" class="xref">MAC Addresses</a></p>
1344 </li>
1345 <li class="toc ulEmpty compact ulBare" id="section-toc.1-1.4.2.2">
1346 <p id="section-toc.1-1.4.2.2.1"><a href="#section-4.2" class="xref">4.2</a>.  <a href="#name-1-wire-device-identifiers" class="xref">1-Wire Device Identifiers</a></p>
1347 </li>
1348 <li class="toc ulEmpty compact ulBare" id="section-toc.1-1.4.2.3">
1349 <p id="section-toc.1-1.4.2.3.1"><a href="#section-4.3" class="xref">4.3</a>.  <a href="#name-organization-defined-identi" class="xref">Organization-Defined Identifiers</a></p>
1350 </li>
1351 <li class="toc ulEmpty compact ulBare" id="section-toc.1-1.4.2.4">
1352 <p id="section-toc.1-1.4.2.4.1"><a href="#section-4.4" class="xref">4.4</a>.  <a href="#name-organization-serial-numbers" class="xref">Organization Serial Numbers</a></p>
1353 </li>
1354 <li class="toc ulEmpty compact ulBare" id="section-toc.1-1.4.2.5">
1355 <p id="section-toc.1-1.4.2.5.1"><a href="#section-4.5" class="xref">4.5</a>.  <a href="#name-organization-product-and-se" class="xref">Organization Product and Serial Numbers</a></p>
1356 </li>
1357 <li class="toc ulEmpty compact ulBare" id="section-toc.1-1.4.2.6">
1358 <p id="section-toc.1-1.4.2.6.1"><a href="#section-4.6" class="xref">4.6</a>.  <a href="#name-future-subtypes" class="xref">Future Subtypes</a></p>
1359 </li>
1360 </ul>
1361 </li>
1362 <li class="toc ulEmpty compact ulBare" id="section-toc.1-1.5">
1363 <p id="section-toc.1-1.5.1"><a href="#section-5" class="xref">5</a>.  <a href="#name-examples" class="xref">Examples</a></p>
1364 </li>
1365 <li class="toc ulEmpty compact ulBare" id="section-toc.1-1.6">
1366 <p id="section-toc.1-1.6.1"><a href="#section-6" class="xref">6</a>.  <a href="#name-security-considerations" class="xref">Security Considerations</a></p>
1367 <ul class="toc ulEmpty compact ulBare">
1368 <li class="toc ulEmpty compact ulBare" id="section-toc.1-1.6.2.1">
1369 <p id="section-toc.1-1.6.2.1.1"><a href="#section-6.1" class="xref">6.1</a>.  <a href="#name-privacy" class="xref">Privacy</a></p>
1370 </li>
1371 <li class="toc ulEmpty compact ulBare" id="section-toc.1-1.6.2.2">
1372 <p id="section-toc.1-1.6.2.2.1"><a href="#section-6.2" class="xref">6.2</a>.  <a href="#name-validity" class="xref">Validity</a></p>
1373 </li>
1374 </ul>
1375 </li>
1376 <li class="toc ulEmpty compact ulBare" id="section-toc.1-1.7">
1377 <p id="section-toc.1-1.7.1"><a href="#section-7" class="xref">7</a>.  <a href="#name-iana-considerations" class="xref">IANA Considerations</a></p>
1378 </li>
1379 <li class="toc ulEmpty compact ulBare" id="section-toc.1-1.8">
1380 <p id="section-toc.1-1.8.1"><a href="#section-8" class="xref">8</a>.  <a href="#name-references" class="xref">References</a></p>
1381 <ul class="toc ulEmpty compact ulBare">
1382 <li class="toc ulEmpty compact ulBare" id="section-toc.1-1.8.2.1">
1383 <p id="section-toc.1-1.8.2.1.1"><a href="#section-8.1" class="xref">8.1</a>.  <a href="#name-normative-references" class="xref">Normative References</a></p>
1384 </li>
1385 <li class="toc ulEmpty compact ulBare" id="section-toc.1-1.8.2.2">
1386 <p id="section-toc.1-1.8.2.2.1"><a href="#section-8.2" class="xref">8.2</a>.  <a href="#name-informative-references" class="xref">Informative References</a></p>
1387 </li>
1388 </ul>
1389 </li>
1390 <li class="toc ulEmpty compact ulBare" id="section-toc.1-1.9">
1391 <p id="section-toc.1-1.9.1"><a href="#appendix-A" class="xref"></a><a href="#name-acknowledgments" class="xref">Acknowledgments</a></p>
1392 </li>
1393 <li class="toc ulEmpty compact ulBare" id="section-toc.1-1.10">
1394 <p id="section-toc.1-1.10.1"><a href="#appendix-B" class="xref"></a><a href="#name-authors-addresses" class="xref">Authors' Addresses</a></p>
1395 </li>
1396 </ul>
1397 </nav>
1398 </section>
1399 </div>
1400 <div id="intro">
1401 <section id="section-1">
1402 <h2 id="name-introduction">
1403 <a href="#section-1" class="section-number selfRef">1. </a><a href="#name-introduction" class="section-name selfRef">Introduction</a>
1404 </h2>
1405 <p id="section-1-1">This document describes a new Uniform Resource Name (URN) <span>[<a href="#RFC8141" class="xref">RFC8141</a>]</span> namespace for hardware
1406 device identifiers. A general representation of device identity
1407 can be useful in many applications, such as in sensor data streams
1408 and storage
1409 or in equipment inventories <span>[<a href="#RFC7252" class="xref">RFC7252</a>]</span> <span>[<a href="#RFC8428" class="xref">RFC8428</a>]</span> <span>[<a href="#I-D.ietf-core-resource-directory" class="xref">CoRE-RD</a>]</span>.<a href="#section-1-1" class="pilcrow">¶</a></p>
1410 <p id="section-1-2">A URN-based representation can be passed along in applications
1411 that need the information. It fits particularly well for protocols
1412 mechanisms that are designed to carry URNs <span>[<a href="#RFC7230" class="xref">RFC7230</a>]</span> <span>[<a href="#RFC7540" class="xref">RFC7540</a>]</span> <span>[<a href="#RFC3261" class="xref">RFC3261</a>]</span> <span>[<a href="#RFC7252" class="xref">RFC7252</a>]</span>. Finally, URNs can
1413 also be easily carried and stored in formats such as XML <span>[<a href="#W3C.REC-xml-19980210" class="xref">W3C.REC-xml-19980210</a>]</span>, JSON <span>[<a href="#RFC8259" class="xref">RFC8259</a>]</span>, or
1414 SenML <span>[<a href="#RFC8428" class="xref">RFC8428</a>]</span>. Using URNs in these formats is
1415 often preferable as they are universally recognized and
1416 self-describing and therefore avoid the need to agree to
1417 interpret an octet string as a specific form of a Media Access Control (MAC) address, for
1418 instance. Passing URNs may consume additional bytes compared to,
1419 for instance, passing 4-byte binary IPv4 addresses, but the former offers
1420 some flexibility in return.<a href="#section-1-2" class="pilcrow">¶</a></p>
1421 <p id="section-1-3">This document defines identifier URN types for situations where no
1422 such convenient type already exists. For instance, <span>[<a href="#RFC6920" class="xref">RFC6920</a>]</span> defines cryptographic identifiers, <span>[<a href="#RFC7254" class="xref">RFC7254</a>]</span> defines International Mobile station Equipment
1423 Identity (IMEI) identifiers for use with 3GPP cellular systems,
1424 and <span>[<a href="#RFC8464" class="xref">RFC8464</a>]</span> defines Mobile
1425 Equipment Identity (MEID) identifiers for use with 3GPP2 cellular
1426 systems. Those URN types should be employed when such identifiers
1427 are transported; this document does not redefine these identifiers in
1428 any way.<a href="#section-1-3" class="pilcrow">¶</a></p>
1429 <p id="section-1-4">Universally Unique Identifier (UUID) URNs <span>[<a href="#RFC4122" class="xref">RFC4122</a>]</span> are another alternative way to represent
1430 device identifiers and already support MAC addresses as one type
1431 of identifier. However, UUIDs can be inconvenient in
1432 environments where it is important that the identifiers be as
1433 simple as possible and where additional requirements on stable
1434 storage, real-time clocks, and identifier length can be
1435 prohibitive. Often, UUID-based identifiers are preferred for
1436 general purpose uses instead of the MAC-based device URNs defined in
1437 this document. The device URNs are recommended for constrained
1438 environments.<a href="#section-1-4" class="pilcrow">¶</a></p>
1439 <p id="section-1-5">Future device identifier types can extend the device URN
1440 type defined in this document (see <a href="#iana" class="xref">Section 7</a>), or they can define their own URNs.<a href="#section-1-5" class="pilcrow">¶</a></p>
1441 <p id="section-1-6">Note that long-term stable unique identifiers are problematic
1442 for privacy reasons and should be used with care as
1443 described in <span>[<a href="#RFC7721" class="xref">RFC7721</a>]</span>.<a href="#section-1-6" class="pilcrow">¶</a></p>
1444 <p id="section-1-7">The rest of this document is organized as follows. <a href="#devurn" class="xref">Section 3</a> defines the "DEV" URN type, and <a href="#subtypes" class="xref">Section 4</a> defines subtypes for IEEE MAC-48, EUI-48 and
1445 EUI-64 addresses, and 1-Wire device identifiers. <a href="#ex" class="xref">Section 5</a> gives examples. <a href="#sec" class="xref">Section 6</a> discusses the
1446 security and privacy considerations of the new URN type. Finally, <a href="#iana" class="xref">Section 7</a> specifies the IANA registration for the new URN
1447 type and sets requirements for subtype allocations within this
1448 type.<a href="#section-1-7" class="pilcrow">¶</a></p>
1449 </section>
1450 </div>
1451 <div id="kwd">
1452 <section id="section-2">
1453 <h2 id="name-requirements-language">
1454 <a href="#section-2" class="section-number selfRef">2. </a><a href="#name-requirements-language" class="section-name selfRef">Requirements Language</a>
1455 </h2>
1456 <p id="section-2-1">
1457 The key words "<span class="bcp14">MUST</span>", "<span class="bcp14">MUST NOT</span>", "<span class="bcp14">REQUIRED</span>", "<span class="bcp14">SHALL</span>", "<span class="bcp14">SHALL NOT</span>", "<span class="bcp14">SHOULD</span>", "<span class="bcp14">SHOULD NOT</span>", "<span class="bcp14">RECOMMENDED</span>", "<span class="bcp14">NOT RECOMMENDED</span>",
1458 "<span class="bcp14">MAY</span>", and "<span class="bcp14">OPTIONAL</span>" in this document are to be interpreted as
1459 described in BCP 14 <span>[<a href="#RFC2119" class="xref">RFC2119</a>]</span> <span>[<a href="#RFC8174" class="xref">RFC8174</a>]</span>
1460 when, and only when, they appear in all capitals, as shown here.<a href="#section-2-1" class="pilcrow">¶</a></p>
1461 </section>
1462 </div>
1463 <div id="devurn">
1464 <section id="section-3">
1465 <h2 id="name-dev-urn-definition">
1466 <a href="#section-3" class="section-number selfRef">3. </a><a href="#name-dev-urn-definition" class="section-name selfRef">DEV URN Definition</a>
1467 </h2>
1468 <span class="break"></span><dl class="dlParallel" id="section-3-1">
1469 <dt id="section-3-1.1">Namespace Identifier:</dt>
1470 <dd style="margin-left: 1.5em" id="section-3-1.2">"dev"<a href="#section-3-1.2" class="pilcrow">¶</a>
1471 </dd>
1472 <dd class="break"></dd>
1473 <dt id="section-3-1.3">Version:</dt>
1474 <dd style="margin-left: 1.5em" id="section-3-1.4">1<a href="#section-3-1.4" class="pilcrow">¶</a>
1475 </dd>
1476 <dd class="break"></dd>
1477 <dt id="section-3-1.5">Date:</dt>
1478 <dd style="margin-left: 1.5em" id="section-3-1.6">2020-06-24<a href="#section-3-1.6" class="pilcrow">¶</a>
1479 </dd>
1480 <dd class="break"></dd>
1481 <dt id="section-3-1.7">Registrant:</dt>
1482 <dd style="margin-left: 1.5em" id="section-3-1.8">IETF and the CORE Working Group. Should the working
1483 group cease to exist, discussion should be directed to the
1484 Applications and Real-Time Area or general IETF discussion forums, or the IESG.<a href="#section-3-1.8" class="pilcrow">¶</a>
1485 </dd>
1486 <dd class="break"></dd>
1487 </dl>
1488 <section id="section-3.1">
1489 <h3 id="name-purpose">
1490 <a href="#section-3.1" class="section-number selfRef">3.1. </a><a href="#name-purpose" class="section-name selfRef">Purpose</a>
1491 </h3>
1492 <p id="section-3.1-1">The DEV URNs identify devices with device-specific
1493 identifiers such as network card hardware addresses. DEV URNs
1494 are scoped to be globally applicable (see <span>[<a href="#RFC8141" class="xref">RFC8141</a>], <a href="https://www.rfc-editor.org/rfc/rfc8141#section-6.4.1" class="relref">Section 6.4.1</a></span>) and, in general, enable
1495 systems to use these identifiers from multiple sources in an
1496 interoperable manner. Note that in some deployments, ensuring
1497 uniqueness requires care if manual or local assignment
1498 mechanisms are used, as discussed in <a href="#assignment" class="xref">Section 3.3</a>.<a href="#section-3.1-1" class="pilcrow">¶</a></p>
1499 <p id="section-3.1-2">
1500 Some typical DEV URN applications include equipment
1501 inventories and smart object systems.<a href="#section-3.1-2" class="pilcrow">¶</a></p>
1502 <p id="section-3.1-3">
1503 DEV URNs can be used in various ways in applications, software
1504 systems, and network components, in tasks ranging from
1505 discovery (for instance, when discovering 1-Wire network
1506 devices or detecting MAC-addressable devices on a LAN) to
1507 intrusion detection systems and simple catalogues of system
1508 information.<a href="#section-3.1-3" class="pilcrow">¶</a></p>
1509 <p id="section-3.1-4">
1510 While it is possible to implement resolution systems for specific
1511 applications or network locations, DEV URNs are typically not used in
1512 a way that requires resolution beyond direct observation of the
1513 relevant identifier fields in local link communication. However, it is
1514 often useful to be able to pass device identifier information in generic
1515 URN fields in databases or protocol fields, which makes the use of
1516 URNs for this purpose convenient.<a href="#section-3.1-4" class="pilcrow">¶</a></p>
1517 <p id="section-3.1-5">
1518 The DEV URN namespace complements existing namespaces such as those
1519 involving IMEI or UUID identifiers. DEV URNs are expected to be a part
1520 of the IETF-provided basic URN types, covering identifiers that have
1521 previously not been possible to use in URNs.<a href="#section-3.1-5" class="pilcrow">¶</a></p>
1522 </section>
1523 <div id="syntax">
1524 <section id="section-3.2">
1525 <h3 id="name-syntax">
1526 <a href="#section-3.2" class="section-number selfRef">3.2. </a><a href="#name-syntax" class="section-name selfRef">Syntax</a>
1527 </h3>
1528 <p id="section-3.2-1">The identifier is expressed in
1529 ASCII characters and has a hierarchical structure as
1530 follows:<a href="#section-3.2-1" class="pilcrow">¶</a></p>
1531 <div id="section-3.2-2">
1532 <pre class="sourcecode lang-abnf">
1533 devurn = "urn:dev:" body componentpart
1534 body = macbody / owbody / orgbody / osbody / opsbody / otherbody
1535 macbody = %s"mac:" hexstring
1536 owbody = %s"ow:" hexstring
1537 orgbody = %s"org:" posnumber "-" identifier *( ":" identifier )
1538 osbody = %s"os:" posnumber "-" serial *( ":" identifier )
1539 opsbody = %s"ops:" posnumber "-" product "-" serial
1540 *( ":" identifier )
1541 otherbody = subtype ":" identifier *( ":" identifier )
1542 subtype = LALPHA *(DIGIT / LALPHA)
1543 identifier = 1*devunreserved
1544 identifiernodash = 1*devunreservednodash
1545 product = identifiernodash
1546 serial = identifier
1547 componentpart = *( "_" identifier )
1548 devunreservednodash = ALPHA / DIGIT / "."
1549 devunreserved = devunreservednodash / "-"
1550 hexstring = 1*(hexdigit hexdigit)
1551 hexdigit = DIGIT / "a" / "b" / "c" / "d" / "e" / "f"
1552 posnumber = NZDIGIT *DIGIT
1553 ALPHA = %x41-5A / %x61-7A
1554 LALPHA = %x41-5A
1555 NZDIGIT = %x31-39
1556 DIGIT = %x30-39
1557 </pre><a href="#section-3.2-2" class="pilcrow">¶</a>
1558 </div>
1559 <p id="section-3.2-3">The above syntax is represented in Augmented Backus-Naur
1560 Form (ABNF) as defined in <span>[<a href="#RFC5234" class="xref">RFC5234</a>]</span> and
1561 <span>[<a href="#RFC7405" class="xref">RFC7405</a>]</span>. The syntax also copies the DIGIT and
1562 ALPHA rules originally defined in <span>[<a href="#RFC5234" class="xref">RFC5234</a>]</span>,
1563 exactly as defined there.<a href="#section-3.2-3" class="pilcrow">¶</a></p>
1564 <p id="section-3.2-4">The device identifier namespace includes five subtypes (see
1565 <a href="#subtypes" class="xref">Section 4</a>), and more may be defined in the future as
1566 specified in <a href="#iana" class="xref">Section 7</a>.<a href="#section-3.2-4" class="pilcrow">¶</a></p>
1567 <p id="section-3.2-5">The optional underscore-separated components at the end of
1568 the DEV URN depict individual aspects of a
1569 device. The specific strings and their semantics are up to the
1570 designers of the device but could be used to refer to
1571 specific interfaces or functions within the device.<a href="#section-3.2-5" class="pilcrow">¶</a></p>
1572 <p id="section-3.2-6">With the exception of the MAC address and 1-Wire DEV URNs,
1573 each DEV URN may also contain optional colon-separated
1574 identifiers. These are provided for extensibility.<a href="#section-3.2-6" class="pilcrow">¶</a></p>
1575 <p id="section-3.2-7">There are no special character encoding rules or
1576 considerations for conforming with the URN syntax beyond
1577 those applicable for URNs in general <span>[<a href="#RFC8141" class="xref">RFC8141</a>]</span>
1578 or the context where these URNs are carried (e.g., inside JSON
1579 <span>[<a href="#RFC8259" class="xref">RFC8259</a>]</span> or SenML <span>[<a href="#RFC8428" class="xref">RFC8428</a>]</span>). Due to the SenML rules in <span>[<a href="#RFC8428" class="xref">RFC8428</a>], <a href="https://www.rfc-editor.org/rfc/rfc8428#section-4.5.1" class="relref">Section 4.5.1</a></span>, it is not desirable to use percent-encoding in DEV
1580 URNs, and the subtypes defined in this specification do not
1581 really benefit from percent-encoding. However, this
1582 specification does not deviate from the general syntax of URNs
1583 or their processing and normalization rules as specified in
1584 <span>[<a href="#RFC3986" class="xref">RFC3986</a>]</span> and <span>[<a href="#RFC8141" class="xref">RFC8141</a>]</span>.<a href="#section-3.2-7" class="pilcrow">¶</a></p>
1585 <p id="section-3.2-8">DEV URNs do not use r-, q-, or f-components as defined in
1586 <span>[<a href="#RFC8141" class="xref">RFC8141</a>]</span>.<a href="#section-3.2-8" class="pilcrow">¶</a></p>
1587 <p id="section-3.2-9">Specific subtypes of DEV URNs may be validated through
1588 mechanisms discussed in <a href="#subtypes" class="xref">Section 4</a>.<a href="#section-3.2-9" class="pilcrow">¶</a></p>
1589 <p id="section-3.2-10">The string representation of the device
1590 identifier URN is fully compatible with
1591 the URN syntax.<a href="#section-3.2-10" class="pilcrow">¶</a></p>
1592 <section id="section-3.2.1">
1593 <h4 id="name-character-case-and-urn-equi">
1594 <a href="#section-3.2.1" class="section-number selfRef">3.2.1. </a><a href="#name-character-case-and-urn-equi" class="section-name selfRef">Character Case and URN-Equivalence</a>
1595 </h4>
1596 <p id="section-3.2.1-1">The DEV URN syntax allows both uppercase and lowercase
1597 characters. The URN-equivalence of the DEV URNs is defined per
1598 <span>[<a href="#RFC8141" class="xref">RFC8141</a>], <a href="https://www.rfc-editor.org/rfc/rfc8141#section-3.1" class="relref">Section 3.1</a></span>, i.e., two URNs are
1599 URN-equivalent if their assigned-name portions are
1600 octet-by-octet equal after applying case normalization to the
1601 URI scheme ("urn") and namespace identifier ("dev").
1602 The rest of the DEV URN is
1603 compared in a case-sensitive manner. It should be noted that
1604 URN-equivalence matching merely quickly shows that two URNs
1605 are definitely the same for the purposes of caching and other
1606 similar uses. Two DEV URNs may still refer to the same entity and may not be found to be URN-equivalent according to the <span>[<a href="#RFC8141" class="xref">RFC8141</a>]</span>
1607 definition. For instance, in ABNF, strings are
1608 case insensitive (see <span>[<a href="#RFC5234" class="xref">RFC5234</a>], <a href="https://www.rfc-editor.org/rfc/rfc5234#section-2.3" class="relref">Section 2.3</a></span>),
1609 and a MAC address could be represented either with uppercase
1610 or lowercase hexadecimal digits.<a href="#section-3.2.1-1" class="pilcrow">¶</a></p>
1611 <p id="section-3.2.1-2">Character case is not otherwise significant for the DEV URN
1612 subtypes defined in this document. However, future subtypes
1613 might include identifiers that use encodings such as base64,
1614 which encodes strings in a larger variety of characters and
1615 might even encode binary data.<a href="#section-3.2.1-2" class="pilcrow">¶</a></p>
1616 <p id="section-3.2.1-3">To facilitate equivalence checks, it is <span class="bcp14">RECOMMENDED</span> that
1617 implementations always use lowercase letters where they have
1618 a choice in case, unless there is a reason otherwise. (Such a
1619 reason might be, for instance, the use of a subtype that
1620 requires the use of both uppercase and lowercase
1621 letters.)<a href="#section-3.2.1-3" class="pilcrow">¶</a></p>
1622 </section>
1623 </section>
1624 </div>
1625 <div id="assignment">
1626 <section id="section-3.3">
1627 <h3 id="name-assignment">
1628 <a href="#section-3.3" class="section-number selfRef">3.3. </a><a href="#name-assignment" class="section-name selfRef">Assignment</a>
1629 </h3>
1630 <p id="section-3.3-1">The process for identifier
1631 assignment is dependent on the used subtype and is documented in the
1632 specific subsection under <a href="#subtypes" class="xref">Section 4</a>.<a href="#section-3.3-1" class="pilcrow">¶</a></p>
1633 <p id="section-3.3-2">Device identifiers are generally expected to identify a
1634 unique device,
1635 barring the accidental issue of multiple devices with the same
1636 identifiers. In many cases, device identifiers can also be
1637 changed by users or are sometimes assigned in an algorithmic
1638 or local fashion. Any potential conflicts arising from such
1639 assignments are not something that the DEV URNs as such
1640 manage; they simply are there to refer to a particular
1641 identifier. And, of course, a single device may (and often
1642 does) have multiple identifiers, e.g., identifiers associated
1643 with different link technologies it supports.<a href="#section-3.3-2" class="pilcrow">¶</a></p>
1644 <p id="section-3.3-3">The DEV URN type <span class="bcp14">SHOULD</span> only be used for
1645 hardware-based identifiers that are expected to be
1646 persistent (with some limits, as discussed above).<a href="#section-3.3-3" class="pilcrow">¶</a></p>
1647 </section>
1648 </div>
1649 <section id="section-3.4">
1650 <h3 id="name-security-and-privacy">
1651 <a href="#section-3.4" class="section-number selfRef">3.4. </a><a href="#name-security-and-privacy" class="section-name selfRef">Security and Privacy</a>
1652 </h3>
1653 <p id="section-3.4-1">As discussed in <a href="#sec" class="xref">Section 6</a>,
1654 care must be taken in the use of device-identifier-based
1655 identifiers due to their nature as long-term identifiers that
1656 are not normally changeable. Leakage of these identifiers
1657 outside systems where their use is justified should be
1658 controlled.<a href="#section-3.4-1" class="pilcrow">¶</a></p>
1659 </section>
1660 <section id="section-3.5">
1661 <h3 id="name-interoperability">
1662 <a href="#section-3.5" class="section-number selfRef">3.5. </a><a href="#name-interoperability" class="section-name selfRef">Interoperability</a>
1663 </h3>
1664 <p id="section-3.5-1">There are no specific interoperability
1665 concerns.<a href="#section-3.5-1" class="pilcrow">¶</a></p>
1666 </section>
1667 <section id="section-3.6">
1668 <h3 id="name-resolution">
1669 <a href="#section-3.6" class="section-number selfRef">3.6. </a><a href="#name-resolution" class="section-name selfRef">Resolution</a>
1670 </h3>
1671 <p id="section-3.6-1">The device identifiers are not expected to be globally
1672 resolvable. No identifier resolution system is expected. Systems may
1673 perform local matching of identifiers to previously seen identifiers
1674 or configured information, however.<a href="#section-3.6-1" class="pilcrow">¶</a></p>
1675 </section>
1676 <section id="section-3.7">
1677 <h3 id="name-documentation">
1678 <a href="#section-3.7" class="section-number selfRef">3.7. </a><a href="#name-documentation" class="section-name selfRef">Documentation</a>
1679 </h3>
1680 <p id="section-3.7-1">See RFC 9039.<a href="#section-3.7-1" class="pilcrow">¶</a></p>
1681 </section>
1682 <section id="section-3.8">
1683 <h3 id="name-additional-information">
1684 <a href="#section-3.8" class="section-number selfRef">3.8. </a><a href="#name-additional-information" class="section-name selfRef">Additional Information</a>
1685 </h3>
1686 <p id="section-3.8-1">See <a href="#intro" class="xref">Section 1</a> for a discussion of related namespaces.<a href="#section-3.8-1" class="pilcrow">¶</a></p>
1687 </section>
1688 <section id="section-3.9">
1689 <h3 id="name-revision-information">
1690 <a href="#section-3.9" class="section-number selfRef">3.9. </a><a href="#name-revision-information" class="section-name selfRef">Revision Information</a>
1691 </h3>
1692 <p id="section-3.9-1">This is the first version of this registration.<a href="#section-3.9-1" class="pilcrow">¶</a></p>
1693 </section>
1694 </section>
1695 </div>
1696 <div id="subtypes">
1697 <section id="section-4">
1698 <h2 id="name-dev-urn-subtypes">
1699 <a href="#section-4" class="section-number selfRef">4. </a><a href="#name-dev-urn-subtypes" class="section-name selfRef">DEV URN Subtypes</a>
1700 </h2>
1701 <div id="mac">
1702 <section id="section-4.1">
1703 <h3 id="name-mac-addresses">
1704 <a href="#section-4.1" class="section-number selfRef">4.1. </a><a href="#name-mac-addresses" class="section-name selfRef">MAC Addresses</a>
1705 </h3>
1706 <p id="section-4.1-1">DEV URNs of the "mac" subtype are based on the EUI-64 identifier
1707 <span>[<a href="#IEEE.EUI64" class="xref">IEEE.EUI64</a>]</span> derived from a device with a built-in
1708 64-bit EUI-64. The EUI-64 is formed from 24 or 36 bits of organization
1709 identifier followed by 40 or 28 bits of device-specific extension
1710 identifier assigned by that organization.<a href="#section-4.1-1" class="pilcrow">¶</a></p>
1711 <p id="section-4.1-2">In the DEV URN "mac" subtype, the hexstring is simply the full
1712 EUI-64 identifier represented as a hexadecimal string. It is always
1713 exactly 16 characters long.<a href="#section-4.1-2" class="pilcrow">¶</a></p>
1714 <p id="section-4.1-3">MAC-48 and EUI-48 identifiers are also supported by the same DEV
1715 URN subtype. To convert a MAC-48 address to an EUI-64 identifier, the
1716 Organizationally Unique Identifier (OUI) of the MAC-48 address (the first three octets) becomes the
1717 organization identifier of the EUI-64 (the first three octets). The
1718 fourth and fifth octets of the EUI are set to the fixed value 0xffff
1719 (hexadecimal). The last three octets of the MAC-48 address become the
1720 last three octets of the EUI-64. The same process is used to convert
1721 an EUI-48 identifier, but the fixed value 0xfffe is used instead.<a href="#section-4.1-3" class="pilcrow">¶</a></p>
1722 <p id="section-4.1-4">Identifier assignment for all of these identifiers rests within the
1723 IEEE Registration Authority.<a href="#section-4.1-4" class="pilcrow">¶</a></p>
1724 <p id="section-4.1-5">Note that where randomized MAC addresses are used, the resulting
1725 DEV URNs cannot be expected to have uniqueness, as discussed in <a href="#assignment" class="xref">Section 3.3</a>.<a href="#section-4.1-5" class="pilcrow">¶</a></p>
1726 </section>
1727 </div>
1728 <div id="s1wire">
1729 <section id="section-4.2">
1730 <h3 id="name-1-wire-device-identifiers">
1731 <a href="#section-4.2" class="section-number selfRef">4.2. </a><a href="#name-1-wire-device-identifiers" class="section-name selfRef">1-Wire Device Identifiers</a>
1732 </h3>
1733 <p id="section-4.2-1">The 1-Wire system is a device communications bus system designed
1734 by Dallas Semiconductor Corporation. (1-Wire is a registered trademark.) 1-Wire devices are identified by
1735 a 64-bit identifier that consists of an 8-bit family code, a 48-bit
1736 identifier unique within a family, and an 8-bit Cyclic Redundancy Check (CRC) code <span>[<a href="#OW" class="xref">OW</a>]</span>.<a href="#section-4.2-1" class="pilcrow">¶</a></p>
1737 <p id="section-4.2-2">In DEV URNs with the "ow" subtype, the hexstring is a representation
1738 of the full 64-bit identifier as a hexadecimal string. It is always
1739 exactly 16 characters long. Note that the last two characters
1740 represent the 8-bit CRC code. Implementations <span class="bcp14">MAY</span> check the validity
1741 of this code.<a href="#section-4.2-2" class="pilcrow">¶</a></p>
1742 <p id="section-4.2-3">Family code and identifier assignment for all 1-Wire devices rests
1743 with the manufacturers.<a href="#section-4.2-3" class="pilcrow">¶</a></p>
1744 </section>
1745 </div>
1746 <div id="org">
1747 <section id="section-4.3">
1748 <h3 id="name-organization-defined-identi">
1749 <a href="#section-4.3" class="section-number selfRef">4.3. </a><a href="#name-organization-defined-identi" class="section-name selfRef">Organization-Defined Identifiers</a>
1750 </h3>
1751 <p id="section-4.3-1">Device identifiers that have only a meaning within an
1752 organization can also be used to represent vendor-specific or
1753 experimental identifiers or identifiers designed for use within the
1754 context of an organization.<a href="#section-4.3-1" class="pilcrow">¶</a></p>
1755 <p id="section-4.3-2">Organizations are identified by their Private Enterprise Number
1756 (PEN) <span>[<a href="#RFC2578" class="xref">RFC2578</a>]</span>. These numbers can be obtained from
1757 IANA. Current PEN assignments can be viewed at <span>&lt;<a href="https://www.iana.org/assignments/enterprise-numbers/">https://www.iana.org/assignments/enterprise-numbers/</a>&gt;</span>,
1758 and new assignments are requested at <span>&lt;<a href="https://pen.iana.org/pen/PenApplication.page">https://pen.iana.org/pen/PenApplication.page</a>&gt;</span>.<a href="#section-4.3-2" class="pilcrow">¶</a></p>
1759 <p id="section-4.3-3">Note that when included in an "org" DEV URN, the number cannot
1760 be zero or have leading zeroes, as the ABNF requires the number to
1761 start with a non-zero digit.<a href="#section-4.3-3" class="pilcrow">¶</a></p>
1762 </section>
1763 </div>
1764 <div id="os">
1765 <section id="section-4.4">
1766 <h3 id="name-organization-serial-numbers">
1767 <a href="#section-4.4" class="section-number selfRef">4.4. </a><a href="#name-organization-serial-numbers" class="section-name selfRef">Organization Serial Numbers</a>
1768 </h3>
1769 <p id="section-4.4-1">The "os" subtype specifies an organization and serial
1770 number. Organizations are identified by their PEN. As with the
1771 organization-defined identifiers (<a href="#org" class="xref">Section 4.3</a>), PEN number
1772 assignments are maintained by IANA, and assignments for new
1773 organizations can be made easily.<a href="#section-4.4-1" class="pilcrow">¶</a></p>
1774 <aside id="section-4.4-2">
1775 <p id="section-4.4-2.1">
1776 Historical note: The "os" subtype was originally defined
1777 in the Open Mobile Alliance "Lightweight Machine to Machine"
1778 standard <span>[<a href="#LwM2M" class="xref">LwM2M</a>]</span> but has been incorporated here
1779 to collect all syntaxes associated with DEV URNs in one place. At
1780 the same time, the syntax of this subtype was changed to avoid
1781 the possibility of characters that are not allowed in the SenML Name
1782 field (see <span>[<a href="#RFC8428" class="xref">RFC8428</a>], <a href="https://www.rfc-editor.org/rfc/rfc8428#section-4.5.1" class="relref">Section 4.5.1</a></span>).<a href="#section-4.4-2.1" class="pilcrow">¶</a></p>
1783 </aside>
1784 <p id="section-4.4-3">Organization serial number DEV URNs consist of the PEN number and
1785 the serial number. As with other DEV URNs, for carrying additional
1786 information and extensibility, optional colon-separated identifiers
1787 and underscore-separated components may also be included. The serial
1788 numbers themselves are defined by the organization, and this
1789 specification does not specify how they are allocated.<a href="#section-4.4-3" class="pilcrow">¶</a></p>
1790 <p id="section-4.4-4">Organizations are also encouraged to select serial number formats
1791 that avoid the possibility of ambiguity in the form of leading zeroes
1792 or otherwise.<a href="#section-4.4-4" class="pilcrow">¶</a></p>
1793 </section>
1794 </div>
1795 <div id="ops">
1796 <section id="section-4.5">
1797 <h3 id="name-organization-product-and-se">
1798 <a href="#section-4.5" class="section-number selfRef">4.5. </a><a href="#name-organization-product-and-se" class="section-name selfRef">Organization Product and Serial Numbers</a>
1799 </h3>
1800 <p id="section-4.5-1">The DEV URN "ops" subtype was originally defined in the
1801 LwM2M standard but has been incorporated here to collect all syntaxes
1802 associated with DEV URNs in one place. The "ops" subtype specifies
1803 an organization, product class, and a serial number. Organizations
1804 are identified by their PEN. Again, as with the
1805 organization-defined identifiers (<a href="#org" class="xref">Section 4.3</a>), PEN number
1806 assignments are maintained by IANA.<a href="#section-4.5-1" class="pilcrow">¶</a></p>
1807 <aside id="section-4.5-2">
1808 <p id="section-4.5-2.1">
1809 Historical note: As with the "os" subtype, the "ops" subtype
1810 was originally defined in the Open Mobile Alliance "Lightweight Machine to Machine" standard <span>[<a href="#LwM2M" class="xref">LwM2M</a>]</span>.<a href="#section-4.5-2.1" class="pilcrow">¶</a></p>
1811 </aside>
1812 <p id="section-4.5-3">Organization product and serial number DEV URNs consist of the
1813 PEN number, product class, and the serial number. As with other DEV
1814 URNs, for carrying additional information and extensibility,
1815 optional colon-separated identifiers and underscore-separated
1816 components may also be included. Both the product class and serial
1817 numbers themselves are defined by the organization, and this
1818 specification does not specify how they are allocated.<a href="#section-4.5-3" class="pilcrow">¶</a></p>
1819 <p id="section-4.5-4">Organizations are also encouraged to select product and serial
1820 number formats that avoid possibility for ambiguity.<a href="#section-4.5-4" class="pilcrow">¶</a></p>
1821 </section>
1822 </div>
1823 <div id="futuresubtypes">
1824 <section id="section-4.6">
1825 <h3 id="name-future-subtypes">
1826 <a href="#section-4.6" class="section-number selfRef">4.6. </a><a href="#name-future-subtypes" class="section-name selfRef">Future Subtypes</a>
1827 </h3>
1828 <p id="section-4.6-1">Additional subtypes may be defined in future
1829 specifications. See <a href="#iana" class="xref">Section 7</a>.<a href="#section-4.6-1" class="pilcrow">¶</a></p>
1830 <p id="section-4.6-2">The DEV URN "example" subtype is reserved for use in examples. It
1831 has no specific requirements beyond those expressed by the ABNF in
1832 <a href="#syntax" class="xref">Section 3.2</a>.<a href="#section-4.6-2" class="pilcrow">¶</a></p>
1833 </section>
1834 </div>
1835 </section>
1836 </div>
1837 <div id="ex">
1838 <section id="section-5">
1839 <h2 id="name-examples">
1840 <a href="#section-5" class="section-number selfRef">5. </a><a href="#name-examples" class="section-name selfRef">Examples</a>
1841 </h2>
1842 <p id="section-5-1">The following provides some examples of DEV URNs:<a href="#section-5-1" class="pilcrow">¶</a></p>
1843 <table class="center" id="table-1">
1844 <caption><a href="#table-1" class="selfRef">Table 1</a></caption>
1845 <thead>
1846 <tr>
1847 <th class="text-left" rowspan="1" colspan="1">URN</th>
1848 <th class="text-left" rowspan="1" colspan="1">Description</th>
1849 </tr>
1850 </thead>
1851 <tbody>
1852 <tr>
1853 <td class="text-left" rowspan="1" colspan="1">urn:dev:mac:0024beffff804ff1</td>
1854 <td class="text-left" rowspan="1" colspan="1">The MAC-48 address of 0024be804ff1, converted to EUI-64 format</td>
1855 </tr>
1856 <tr>
1857 <td class="text-left" rowspan="1" colspan="1"> urn:dev:mac:0024befffe804ff1</td>
1858 <td class="text-left" rowspan="1" colspan="1"> The EUI-48 address of 0024be804ff1, converted to EUI-64 format</td>
1859 </tr>
1860 <tr>
1861 <td class="text-left" rowspan="1" colspan="1">urn:dev:mac:acde48234567019f</td>
1862 <td class="text-left" rowspan="1" colspan="1">The EUI-64 address of acde48234567019f
1863 </td>
1864 </tr>
1865 <tr>
1866 <td class="text-left" rowspan="1" colspan="1"> urn:dev:ow:10e2073a01080063</td>
1867 <td class="text-left" rowspan="1" colspan="1">A 1-Wire temperature sensor</td>
1868 </tr>
1869 <tr>
1870 <td class="text-left" rowspan="1" colspan="1">urn:dev:ow:264437f5000000ed_humidity</td>
1871 <td class="text-left" rowspan="1" colspan="1">The humidity part of a multi-sensor device </td>
1872 </tr>
1873 <tr>
1874 <td class="text-left" rowspan="1" colspan="1">urn:dev:ow:264437f5000000ed_temperature</td>
1875 <td class="text-left" rowspan="1" colspan="1">The temperature part of a multi-sensor device</td>
1876 </tr>
1877 <tr>
1878 <td class="text-left" rowspan="1" colspan="1">urn:dev:org:32473-foo</td>
1879 <td class="text-left" rowspan="1" colspan="1">An organization-specific URN in the example organization 32473 in <span>[<a href="#RFC5612" class="xref">RFC5612</a>]</span>
1880 </td>
1881 </tr>
1882 <tr>
1883 <td class="text-left" rowspan="1" colspan="1">urn:dev:os:32473-123456</td>
1884 <td class="text-left" rowspan="1" colspan="1">Device 123456 in the example organization in <span>[<a href="#RFC5612" class="xref">RFC5612</a>]</span>
1885 </td>
1886 </tr>
1887 <tr>
1888 <td class="text-left" rowspan="1" colspan="1">urn:dev:os:32473-12-34-56</td>
1889 <td class="text-left" rowspan="1" colspan="1">A serial number with dashes in it</td>
1890 </tr>
1891 <tr>
1892 <td class="text-left" rowspan="1" colspan="1">urn:dev:ops:32473-Refrigerator-5002</td>
1893 <td class="text-left" rowspan="1" colspan="1">Refrigerator serial number 5002 in the example organization in <span>[<a href="#RFC5612" class="xref">RFC5612</a>]</span>
1894 </td>
1895 </tr>
1896 <tr>
1897 <td class="text-left" rowspan="1" colspan="1">urn:dev:example:new-1-2-3_comp</td>
1898 <td class="text-left" rowspan="1" colspan="1">An example of something that is not defined today, and is not one of the mac, ow, os, or ops subtypes</td>
1899 </tr>
1900 </tbody>
1901 </table>
1902 <p id="section-5-3">The DEV URNs themselves can then appear in various contexts. A
1903 simple example of this is the use of DEV URNs in SenML data. This example from <span>[<a href="#RFC8428" class="xref">RFC8428</a>]</span> shows a
1904 measurement from a 1-Wire temperature gauge encoded in the JSON
1905 syntax:<a href="#section-5-3" class="pilcrow">¶</a></p>
1906 <div id="section-5-4">
1907 <pre class="sourcecode lang-json">
1908 [
1909 {"n":"urn:dev:ow:10e2073a01080063","u":"Cel","v":23.1}
1910 ]
1911 </pre><a href="#section-5-4" class="pilcrow">¶</a>
1912 </div>
1913 </section>
1914 </div>
1915 <div id="sec">
1916 <section id="section-6">
1917 <h2 id="name-security-considerations">
1918 <a href="#section-6" class="section-number selfRef">6. </a><a href="#name-security-considerations" class="section-name selfRef">Security Considerations</a>
1919 </h2>
1920 <p id="section-6-1">On most devices, the user can display device identifiers. Depending
1921 on circumstances, device identifiers may or may not be modified or
1922 tampered with by the user. An implementation of the DEV URN <span class="bcp14">MUST</span> preserve
1923 such limitations and behaviors associated with the device identifiers. In particular,
1924 a device identifier that is intended to be immutable should not become mutable
1925 as a part of implementing the DEV URN type. More generally, nothing in
1926 this document should be construed to override what the relevant device
1927 specifications have already said about the identifiers.<a href="#section-6-1" class="pilcrow">¶</a></p>
1928 <div id="priv">
1929 <section id="section-6.1">
1930 <h3 id="name-privacy">
1931 <a href="#section-6.1" class="section-number selfRef">6.1. </a><a href="#name-privacy" class="section-name selfRef">Privacy</a>
1932 </h3>
1933 <p id="section-6.1-1">Other devices in the same network may or may not be able to
1934 identify the device. For instance, on an Ethernet network, the MAC
1935 address of a device is visible to all other devices.<a href="#section-6.1-1" class="pilcrow">¶</a></p>
1936 <p id="section-6.1-2">DEV URNs often represent long-term stable unique identifiers for
1937 devices. Such identifiers may have privacy and security implications
1938 because they may enable correlating information about a specific
1939 device over a long period of time, location tracking, and device-specific vulnerability exploitation <span>[<a href="#RFC7721" class="xref">RFC7721</a>]</span>. Also, in
1940 some systems, there is no easy way to change the identifier. Therefore,
1941 these identifiers need to be used with care, and special care should
1942 be taken to avoid leaking identifiers outside of the system that is intended
1943 to use them.<a href="#section-6.1-2" class="pilcrow">¶</a></p>
1944 </section>
1945 </div>
1946 <div id="valid">
1947 <section id="section-6.2">
1948 <h3 id="name-validity">
1949 <a href="#section-6.2" class="section-number selfRef">6.2. </a><a href="#name-validity" class="section-name selfRef">Validity</a>
1950 </h3>
1951 <p id="section-6.2-1">Information about identifiers may have significant effects in some
1952 applications. For instance, in many sensor systems, the identifier
1953 information is used for deciding how to use the data carried in a
1954 measurement report. In some other systems, identifiers may be used in
1955 policy decisions.<a href="#section-6.2-1" class="pilcrow">¶</a></p>
1956 <p id="section-6.2-2">It is important that systems be designed to take into account the
1957 possibility of devices reporting incorrect identifiers (either
1958 accidentally or maliciously) and the manipulation of identifiers in
1959 communications by illegitimate entities. Integrity
1960 protection of communications or data objects, the use of trusted
1961 devices, and various management practices can help address these
1962 issues.<a href="#section-6.2-2" class="pilcrow">¶</a></p>
1963 <p id="section-6.2-3">Similar to the advice in <span>[<a href="#RFC4122" class="xref">RFC4122</a>], <a href="https://www.rfc-editor.org/rfc/rfc4122#section-6" class="relref">Section 6</a></span>:
1964 Do not assume that DEV URNs are hard to guess.<a href="#section-6.2-3" class="pilcrow">¶</a></p>
1965 </section>
1966 </div>
1967 </section>
1968 </div>
1969 <div id="iana">
1970 <section id="section-7">
1971 <h2 id="name-iana-considerations">
1972 <a href="#section-7" class="section-number selfRef">7. </a><a href="#name-iana-considerations" class="section-name selfRef">IANA Considerations</a>
1973 </h2>
1974 <p id="section-7-1">Per this document, IANA has registered a new URN namespace
1975 for "dev", as described in <a href="#devurn" class="xref">Section 3</a>.<a href="#section-7-1" class="pilcrow">¶</a></p>
1976 <p id="section-7-2">IANA has created a "DEV URN Subtypes" registry under "Device Identification". The initial values in this registry are as follows:<a href="#section-7-2" class="pilcrow">¶</a></p>
1977 <table class="center" id="table-2">
1978 <caption><a href="#table-2" class="selfRef">Table 2</a></caption>
1979 <thead>
1980 <tr>
1981 <th class="text-left" rowspan="1" colspan="1">Subtype</th>
1982 <th class="text-left" rowspan="1" colspan="1">Description</th>
1983 <th class="text-left" rowspan="1" colspan="1">Reference</th>
1984 </tr>
1985 </thead>
1986 <tbody>
1987 <tr>
1988 <td class="text-left" rowspan="1" colspan="1">mac</td>
1989 <td class="text-left" rowspan="1" colspan="1">MAC Addresses</td>
1990 <td class="text-left" rowspan="1" colspan="1">RFC 9039, <a href="#mac" class="xref">Section 4.1</a>
1991 </td>
1992 </tr>
1993 <tr>
1994 <td class="text-left" rowspan="1" colspan="1">ow</td>
1995 <td class="text-left" rowspan="1" colspan="1">1-Wire Device Identifiers</td>
1996 <td class="text-left" rowspan="1" colspan="1">RFC 9039, <a href="#s1wire" class="xref">Section 4.2</a>
1997 </td>
1998 </tr>
1999 <tr>
2000 <td class="text-left" rowspan="1" colspan="1">org</td>
2001 <td class="text-left" rowspan="1" colspan="1">Organization-Defined Identifiers</td>
2002 <td class="text-left" rowspan="1" colspan="1">RFC 9039, <a href="#org" class="xref">Section 4.3</a>
2003 </td>
2004 </tr>
2005 <tr>
2006 <td class="text-left" rowspan="1" colspan="1">os</td>
2007 <td class="text-left" rowspan="1" colspan="1">Organization Serial Numbers</td>
2008 <td class="text-left" rowspan="1" colspan="1">RFC 9039, <a href="#os" class="xref">Section 4.4</a>
2009 </td>
2010 </tr>
2011 <tr>
2012 <td class="text-left" rowspan="1" colspan="1">ops</td>
2013 <td class="text-left" rowspan="1" colspan="1">Organization Product and Serial Numbers</td>
2014 <td class="text-left" rowspan="1" colspan="1">RFC 9039, <a href="#ops" class="xref">Section 4.5</a>
2015 </td>
2016 </tr>
2017 <tr>
2018 <td class="text-left" rowspan="1" colspan="1">example</td>
2019 <td class="text-left" rowspan="1" colspan="1">Reserved for examples</td>
2020 <td class="text-left" rowspan="1" colspan="1">RFC 9039, <a href="#futuresubtypes" class="xref">Section 4.6</a>
2021 </td>
2022 </tr>
2023 </tbody>
2024 </table>
2025 <p id="section-7-4">Additional subtypes for DEV URNs can be defined through
2026 Specification Required or IESG Approval <span>[<a href="#RFC8126" class="xref">RFC8126</a>]</span>. These allocations are appropriate when there is
2027 a new namespace of some type of device identifier that is defined in
2028 a stable fashion and has a publicly available specification.<a href="#section-7-4" class="pilcrow">¶</a></p>
2029 <p id="section-7-5">Note that the organization (<a href="#org" class="xref">Section 4.3</a>) device
2030 identifiers can also be used in some cases, at least as a temporary
2031 measure. It is preferable, however, that long-term usage of a
2032 broadly employed device identifier be registered with IETF rather
2033 than used through the organization device identifier type.<a href="#section-7-5" class="pilcrow">¶</a></p>
2034 </section>
2035 </div>
2036 <section id="section-8">
2037 <h2 id="name-references">
2038 <a href="#section-8" class="section-number selfRef">8. </a><a href="#name-references" class="section-name selfRef">References</a>
2039 </h2>
2040 <section id="section-8.1">
2041 <h3 id="name-normative-references">
2042 <a href="#section-8.1" class="section-number selfRef">8.1. </a><a href="#name-normative-references" class="section-name selfRef">Normative References</a>
2043 </h3>
2044 <dl class="references">
2045 <dt id="IEEE.EUI64">[IEEE.EUI64]</dt>
2046 <dd>
2047 <span class="refAuthor">IEEE</span>, <span class="refTitle">"Guidelines for Use of Extended Unique Identifier (EUI), Organizationally Unique Identifier (OUI), and Company ID (CID)"</span>, <time datetime="2017-08" class="refDate">August 2017</time>, <span>&lt;<a href="https://standards.ieee.org/content/dam/ieee-standards/standards/web/documents/tutorials/eui.pdf">https://standards.ieee.org/content/dam/ieee-standards/standards/web/documents/tutorials/eui.pdf</a>&gt;</span>. </dd>
2048 <dd class="break"></dd>
2049 <dt id="OW">[OW]</dt>
2050 <dd>
2051 <span class="refAuthor">Maxim</span>, <span class="refTitle">"Guide to 1-Wire Communication"</span>, <time datetime="2008-06" class="refDate">June 2008</time>, <span>&lt;<a href="https://www.maximintegrated.com/en/design/technical-documents/tutorials/1/1796.html">https://www.maximintegrated.com/en/design/technical-documents/tutorials/1/1796.html</a>&gt;</span>. </dd>
2052 <dd class="break"></dd>
2053 <dt id="RFC2119">[RFC2119]</dt>
2054 <dd>
2055 <span class="refAuthor">Bradner, S.</span>, <span class="refTitle">"Key words for use in RFCs to Indicate Requirement Levels"</span>, <span class="seriesInfo">BCP 14</span>, <span class="seriesInfo">RFC 2119</span>, <span class="seriesInfo">DOI 10.17487/RFC2119</span>, <time datetime="1997-03" class="refDate">March 1997</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc2119">https://www.rfc-editor.org/info/rfc2119</a>&gt;</span>. </dd>
2056 <dd class="break"></dd>
2057 <dt id="RFC2578">[RFC2578]</dt>
2058 <dd>
2059 <span class="refAuthor">McCloghrie, K., Ed.</span>, <span class="refAuthor">Perkins, D., Ed.</span>, and <span class="refAuthor">J. Schoenwaelder, Ed.</span>, <span class="refTitle">"Structure of Management Information Version 2 (SMIv2)"</span>, <span class="seriesInfo">STD 58</span>, <span class="seriesInfo">RFC 2578</span>, <span class="seriesInfo">DOI 10.17487/RFC2578</span>, <time datetime="1999-04" class="refDate">April 1999</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc2578">https://www.rfc-editor.org/info/rfc2578</a>&gt;</span>. </dd>
2060 <dd class="break"></dd>
2061 <dt id="RFC3986">[RFC3986]</dt>
2062 <dd>
2063 <span class="refAuthor">Berners-Lee, T.</span>, <span class="refAuthor">Fielding, R.</span>, and <span class="refAuthor">L. Masinter</span>, <span class="refTitle">"Uniform Resource Identifier (URI): Generic Syntax"</span>, <span class="seriesInfo">STD 66</span>, <span class="seriesInfo">RFC 3986</span>, <span class="seriesInfo">DOI 10.17487/RFC3986</span>, <time datetime="2005-01" class="refDate">January 2005</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc3986">https://www.rfc-editor.org/info/rfc3986</a>&gt;</span>. </dd>
2064 <dd class="break"></dd>
2065 <dt id="RFC5234">[RFC5234]</dt>
2066 <dd>
2067 <span class="refAuthor">Crocker, D., Ed.</span> and <span class="refAuthor">P. Overell</span>, <span class="refTitle">"Augmented BNF for Syntax Specifications: ABNF"</span>, <span class="seriesInfo">STD 68</span>, <span class="seriesInfo">RFC 5234</span>, <span class="seriesInfo">DOI 10.17487/RFC5234</span>, <time datetime="2008-01" class="refDate">January 2008</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc5234">https://www.rfc-editor.org/info/rfc5234</a>&gt;</span>. </dd>
2068 <dd class="break"></dd>
2069 <dt id="RFC8126">[RFC8126]</dt>
2070 <dd>
2071 <span class="refAuthor">Cotton, M.</span>, <span class="refAuthor">Leiba, B.</span>, and <span class="refAuthor">T. Narten</span>, <span class="refTitle">"Guidelines for Writing an IANA Considerations Section in RFCs"</span>, <span class="seriesInfo">BCP 26</span>, <span class="seriesInfo">RFC 8126</span>, <span class="seriesInfo">DOI 10.17487/RFC8126</span>, <time datetime="2017-06" class="refDate">June 2017</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8126">https://www.rfc-editor.org/info/rfc8126</a>&gt;</span>. </dd>
2072 <dd class="break"></dd>
2073 <dt id="RFC8141">[RFC8141]</dt>
2074 <dd>
2075 <span class="refAuthor">Saint-Andre, P.</span> and <span class="refAuthor">J. Klensin</span>, <span class="refTitle">"Uniform Resource Names (URNs)"</span>, <span class="seriesInfo">RFC 8141</span>, <span class="seriesInfo">DOI 10.17487/RFC8141</span>, <time datetime="2017-04" class="refDate">April 2017</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8141">https://www.rfc-editor.org/info/rfc8141</a>&gt;</span>. </dd>
2076 <dd class="break"></dd>
2077 <dt id="RFC8174">[RFC8174]</dt>
2078 <dd>
2079 <span class="refAuthor">Leiba, B.</span>, <span class="refTitle">"Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words"</span>, <span class="seriesInfo">BCP 14</span>, <span class="seriesInfo">RFC 8174</span>, <span class="seriesInfo">DOI 10.17487/RFC8174</span>, <time datetime="2017-05" class="refDate">May 2017</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8174">https://www.rfc-editor.org/info/rfc8174</a>&gt;</span>. </dd>
2080 <dd class="break"></dd>
2081 </dl>
2082 </section>
2083 <section id="section-8.2">
2084 <h3 id="name-informative-references">
2085 <a href="#section-8.2" class="section-number selfRef">8.2. </a><a href="#name-informative-references" class="section-name selfRef">Informative References</a>
2086 </h3>
2087 <dl class="references">
2088 <dt id="I-D.ietf-core-resource-directory">[CoRE-RD]</dt>
2089 <dd>
2090 <span class="refAuthor">Amsüss, C., Ed.</span>, <span class="refAuthor">Shelby, Z.</span>, <span class="refAuthor">Koster, M.</span>, <span class="refAuthor">Bormann, C.</span>, and <span class="refAuthor">P. van der Stok</span>, <span class="refTitle">"CoRE Resource Directory"</span>, <span class="refContent">Work in Progress</span>, <span class="seriesInfo">Internet-Draft, draft-ietf-core-resource-directory-28</span>, <time datetime="2021-03-07" class="refDate">7 March 2021</time>, <span>&lt;<a href="https://datatracker.ietf.org/doc/html/draft-ietf-core-resource-directory-28">https://datatracker.ietf.org/doc/html/draft-ietf-core-resource-directory-28</a>&gt;</span>. </dd>
2091 <dd class="break"></dd>
2092 <dt id="LwM2M">[LwM2M]</dt>
2093 <dd>
2094 <span class="refAuthor">Alliance, O. M.</span>, <span class="refTitle">"OMA Lightweight Machine to Machine Requirements"</span>, <span class="seriesInfo">OMA Standard Candidate Version 1.2</span>, <time datetime="2019-01" class="refDate">January 2019</time>, <span>&lt;<a href="https://www.openmobilealliance.org/release/LightweightM2M/V1_2-20190124-C/OMA-RD-LightweightM2M-V1_2-20190124-C.pdf">https://www.openmobilealliance.org/release/LightweightM2M/V1_2-20190124-C/OMA-RD-LightweightM2M-V1_2-20190124-C.pdf</a>&gt;</span>. </dd>
2095 <dd class="break"></dd>
2096 <dt id="RFC3261">[RFC3261]</dt>
2097 <dd>
2098 <span class="refAuthor">Rosenberg, J.</span>, <span class="refAuthor">Schulzrinne, H.</span>, <span class="refAuthor">Camarillo, G.</span>, <span class="refAuthor">Johnston, A.</span>, <span class="refAuthor">Peterson, J.</span>, <span class="refAuthor">Sparks, R.</span>, <span class="refAuthor">Handley, M.</span>, and <span class="refAuthor">E. Schooler</span>, <span class="refTitle">"SIP: Session Initiation Protocol"</span>, <span class="seriesInfo">RFC 3261</span>, <span class="seriesInfo">DOI 10.17487/RFC3261</span>, <time datetime="2002-06" class="refDate">June 2002</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc3261">https://www.rfc-editor.org/info/rfc3261</a>&gt;</span>. </dd>
2099 <dd class="break"></dd>
2100 <dt id="RFC4122">[RFC4122]</dt>
2101 <dd>
2102 <span class="refAuthor">Leach, P.</span>, <span class="refAuthor">Mealling, M.</span>, and <span class="refAuthor">R. Salz</span>, <span class="refTitle">"A Universally Unique IDentifier (UUID) URN Namespace"</span>, <span class="seriesInfo">RFC 4122</span>, <span class="seriesInfo">DOI 10.17487/RFC4122</span>, <time datetime="2005-07" class="refDate">July 2005</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc4122">https://www.rfc-editor.org/info/rfc4122</a>&gt;</span>. </dd>
2103 <dd class="break"></dd>
2104 <dt id="RFC5612">[RFC5612]</dt>
2105 <dd>
2106 <span class="refAuthor">Eronen, P.</span> and <span class="refAuthor">D. Harrington</span>, <span class="refTitle">"Enterprise Number for Documentation Use"</span>, <span class="seriesInfo">RFC 5612</span>, <span class="seriesInfo">DOI 10.17487/RFC5612</span>, <time datetime="2009-08" class="refDate">August 2009</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc5612">https://www.rfc-editor.org/info/rfc5612</a>&gt;</span>. </dd>
2107 <dd class="break"></dd>
2108 <dt id="RFC6920">[RFC6920]</dt>
2109 <dd>
2110 <span class="refAuthor">Farrell, S.</span>, <span class="refAuthor">Kutscher, D.</span>, <span class="refAuthor">Dannewitz, C.</span>, <span class="refAuthor">Ohlman, B.</span>, <span class="refAuthor">Keranen, A.</span>, and <span class="refAuthor">P. Hallam-Baker</span>, <span class="refTitle">"Naming Things with Hashes"</span>, <span class="seriesInfo">RFC 6920</span>, <span class="seriesInfo">DOI 10.17487/RFC6920</span>, <time datetime="2013-04" class="refDate">April 2013</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc6920">https://www.rfc-editor.org/info/rfc6920</a>&gt;</span>. </dd>
2111 <dd class="break"></dd>
2112 <dt id="RFC7230">[RFC7230]</dt>
2113 <dd>
2114 <span class="refAuthor">Fielding, R., Ed.</span> and <span class="refAuthor">J. Reschke, Ed.</span>, <span class="refTitle">"Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing"</span>, <span class="seriesInfo">RFC 7230</span>, <span class="seriesInfo">DOI 10.17487/RFC7230</span>, <time datetime="2014-06" class="refDate">June 2014</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc7230">https://www.rfc-editor.org/info/rfc7230</a>&gt;</span>. </dd>
2115 <dd class="break"></dd>
2116 <dt id="RFC7252">[RFC7252]</dt>
2117 <dd>
2118 <span class="refAuthor">Shelby, Z.</span>, <span class="refAuthor">Hartke, K.</span>, and <span class="refAuthor">C. Bormann</span>, <span class="refTitle">"The Constrained Application Protocol (CoAP)"</span>, <span class="seriesInfo">RFC 7252</span>, <span class="seriesInfo">DOI 10.17487/RFC7252</span>, <time datetime="2014-06" class="refDate">June 2014</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc7252">https://www.rfc-editor.org/info/rfc7252</a>&gt;</span>. </dd>
2119 <dd class="break"></dd>
2120 <dt id="RFC7254">[RFC7254]</dt>
2121 <dd>
2122 <span class="refAuthor">Montemurro, M., Ed.</span>, <span class="refAuthor">Allen, A.</span>, <span class="refAuthor">McDonald, D.</span>, and <span class="refAuthor">P. Gosden</span>, <span class="refTitle">"A Uniform Resource Name Namespace for the Global System for Mobile Communications Association (GSMA) and the International Mobile station Equipment Identity (IMEI)"</span>, <span class="seriesInfo">RFC 7254</span>, <span class="seriesInfo">DOI 10.17487/RFC7254</span>, <time datetime="2014-05" class="refDate">May 2014</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc7254">https://www.rfc-editor.org/info/rfc7254</a>&gt;</span>. </dd>
2123 <dd class="break"></dd>
2124 <dt id="RFC7405">[RFC7405]</dt>
2125 <dd>
2126 <span class="refAuthor">Kyzivat, P.</span>, <span class="refTitle">"Case-Sensitive String Support in ABNF"</span>, <span class="seriesInfo">RFC 7405</span>, <span class="seriesInfo">DOI 10.17487/RFC7405</span>, <time datetime="2014-12" class="refDate">December 2014</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc7405">https://www.rfc-editor.org/info/rfc7405</a>&gt;</span>. </dd>
2127 <dd class="break"></dd>
2128 <dt id="RFC7540">[RFC7540]</dt>
2129 <dd>
2130 <span class="refAuthor">Belshe, M.</span>, <span class="refAuthor">Peon, R.</span>, and <span class="refAuthor">M. Thomson, Ed.</span>, <span class="refTitle">"Hypertext Transfer Protocol Version 2 (HTTP/2)"</span>, <span class="seriesInfo">RFC 7540</span>, <span class="seriesInfo">DOI 10.17487/RFC7540</span>, <time datetime="2015-05" class="refDate">May 2015</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc7540">https://www.rfc-editor.org/info/rfc7540</a>&gt;</span>. </dd>
2131 <dd class="break"></dd>
2132 <dt id="RFC7721">[RFC7721]</dt>
2133 <dd>
2134 <span class="refAuthor">Cooper, A.</span>, <span class="refAuthor">Gont, F.</span>, and <span class="refAuthor">D. Thaler</span>, <span class="refTitle">"Security and Privacy Considerations for IPv6 Address Generation Mechanisms"</span>, <span class="seriesInfo">RFC 7721</span>, <span class="seriesInfo">DOI 10.17487/RFC7721</span>, <time datetime="2016-03" class="refDate">March 2016</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc7721">https://www.rfc-editor.org/info/rfc7721</a>&gt;</span>. </dd>
2135 <dd class="break"></dd>
2136 <dt id="RFC8259">[RFC8259]</dt>
2137 <dd>
2138 <span class="refAuthor">Bray, T., Ed.</span>, <span class="refTitle">"The JavaScript Object Notation (JSON) Data Interchange Format"</span>, <span class="seriesInfo">STD 90</span>, <span class="seriesInfo">RFC 8259</span>, <span class="seriesInfo">DOI 10.17487/RFC8259</span>, <time datetime="2017-12" class="refDate">December 2017</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8259">https://www.rfc-editor.org/info/rfc8259</a>&gt;</span>. </dd>
2139 <dd class="break"></dd>
2140 <dt id="RFC8428">[RFC8428]</dt>
2141 <dd>
2142 <span class="refAuthor">Jennings, C.</span>, <span class="refAuthor">Shelby, Z.</span>, <span class="refAuthor">Arkko, J.</span>, <span class="refAuthor">Keranen, A.</span>, and <span class="refAuthor">C. Bormann</span>, <span class="refTitle">"Sensor Measurement Lists (SenML)"</span>, <span class="seriesInfo">RFC 8428</span>, <span class="seriesInfo">DOI 10.17487/RFC8428</span>, <time datetime="2018-08" class="refDate">August 2018</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8428">https://www.rfc-editor.org/info/rfc8428</a>&gt;</span>. </dd>
2143 <dd class="break"></dd>
2144 <dt id="RFC8464">[RFC8464]</dt>
2145 <dd>
2146 <span class="refAuthor">Atarius, R.</span>, <span class="refTitle">"A URN Namespace for Device Identity and Mobile Equipment Identity (MEID)"</span>, <span class="seriesInfo">RFC 8464</span>, <span class="seriesInfo">DOI 10.17487/RFC8464</span>, <time datetime="2018-09" class="refDate">September 2018</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8464">https://www.rfc-editor.org/info/rfc8464</a>&gt;</span>. </dd>
2147 <dd class="break"></dd>
2148 <dt id="W3C.REC-xml-19980210">[W3C.REC-xml-19980210]</dt>
2149 <dd>
2150 <span class="refAuthor">Sperberg-McQueen, C.</span>, <span class="refAuthor">Bray, T.</span>, and <span class="refAuthor">J. Paoli</span>, <span class="refTitle">"Extensible Markup Language (XML) 1.0"</span>, <span class="seriesInfo">W3C Recommendation</span>, <time datetime="1998-02" class="refDate">February 1998</time>, <span>&lt;<a href="http://www.w3.org/TR/1998/REC-xml-19980210">http://www.w3.org/TR/1998/REC-xml-19980210</a>&gt;</span>. </dd>
2151 <dd class="break"></dd>
2152 </dl>
2153 </section>
2154 </section>
2155 <section id="appendix-A">
2156 <h2 id="name-acknowledgments">
2157 <a href="#name-acknowledgments" class="section-name selfRef">Acknowledgments</a>
2158 </h2>
2159 <p id="appendix-A-1">The authors would like to thank <span class="contact-name">Ari Keränen</span>, <span class="contact-name">Stephen Farrell</span>,
2160 <span class="contact-name">Christer Holmberg</span>, <span class="contact-name">Peter Saint-Andre</span>, <span class="contact-name">Wouter Cloetens</span>, <span class="contact-name">Jaime Jimenez</span>, <span class="contact-name">Joseph Knapp</span>, <span class="contact-name">Padmakumar Subramani</span>, <span class="contact-name">Mert Ocak</span>, <span class="contact-name">Hannes Tschofenig</span>, <span class="contact-name">Jim Schaad</span>, <span class="contact-name">Thomas Fossati</span>, <span class="contact-name">Carsten Bormann</span>, <span class="contact-name">Marco Tiloca</span>, <span class="contact-name">Barry Leiba</span>, <span class="contact-name">Amanda Baber</span>, <span class="contact-name">Juha Hakala</span>, <span class="contact-name">Dale Worley</span>, <span class="contact-name">Warren Kumari</span>, <span class="contact-name">Benjamin Kaduk</span>, <span class="contact-name">Brian Weis</span>, <span class="contact-name">John Klensin</span>, <span class="contact-name">Dave Thaler</span>, <span class="contact-name">Russ Housley</span>, <span class="contact-name">Dan Romascanu</span>, <span class="contact-name">Éric Vyncke</span>, <span class="contact-name">Roman Danyliw</span>, and <span class="contact-name">Ahmad Muhanna</span> for their feedback and interesting discussions in this problem
2161 space. We would also like to note prior documents that focused on
2162 specific device identifiers, such as <span>[<a href="#RFC7254" class="xref">RFC7254</a>]</span> and
2163 <span>[<a href="#RFC8464" class="xref">RFC8464</a>]</span>.<a href="#appendix-A-1" class="pilcrow">¶</a></p>
2164 </section>
2165 <div id="authors-addresses">
2166 <section id="appendix-B">
2167 <h2 id="name-authors-addresses">
2168 <a href="#name-authors-addresses" class="section-name selfRef">Authors' Addresses</a>
2169 </h2>
2170 <address class="vcard">
2171 <div dir="auto" class="left"><span class="fn nameRole">Jari Arkko</span></div>
2172 <div dir="auto" class="left"><span class="org">Ericsson</span></div>
2173 <div dir="auto" class="left">FI-<span class="postal-code">02420</span> <span class="locality">Jorvas</span>
2174 </div>
2175 <div dir="auto" class="left"><span class="country-name">Finland</span></div>
2176 <div class="email">
2177 <span>Email:</span>
2178 <a href="mailto:[email protected]" class="email">[email protected]</a>
2179 </div>
2180 </address>
2181 <address class="vcard">
2182 <div dir="auto" class="left"><span class="fn nameRole">Cullen Jennings</span></div>
2183 <div dir="auto" class="left"><span class="org">Cisco</span></div>
2184 <div dir="auto" class="left"><span class="street-address">170 West Tasman Drive</span></div>
2185 <div dir="auto" class="left">
2186 <span class="locality">San Jose</span>, <span class="region">CA</span> <span class="postal-code">95134</span>
2187 </div>
2188 <div dir="auto" class="left"><span class="country-name">United States of America</span></div>
2189 <div class="tel">
2190 <span>Phone:</span>
2191 <a href="tel:+1%20408%20421-9990" class="tel">+1 408 421-9990</a>
2192 </div>
2193 <div class="email">
2194 <span>Email:</span>
2195 <a href="mailto:[email protected]" class="email">[email protected]</a>
2196 </div>
2197 </address>
2198 <address class="vcard">
2199 <div dir="auto" class="left"><span class="fn nameRole">Zach Shelby</span></div>
2200 <div dir="auto" class="left"><span class="org">Edge Impulse</span></div>
2201 <div dir="auto" class="left"><span class="street-address">3031 Tisch Way</span></div>
2202 <div dir="auto" class="left">
2203 <span class="locality">San Jose</span>, <span class="region">CA</span> <span class="postal-code">95128</span>
2204 </div>
2205 <div dir="auto" class="left"><span class="country-name">United States of America</span></div>
2206 <div class="email">
2207 <span>Email:</span>
2208 <a href="mailto:[email protected]" class="email">[email protected]</a>
2209 </div>
2210 </address>
2211 </section>
2212 </div>
2213 <script>const toc = document.getElementById("toc");
2214 toc.querySelector("h2").addEventListener("click", e => {
2215 toc.classList.toggle("active");
2216 });
2217 toc.querySelector("nav").addEventListener("click", e => {
2218 toc.classList.remove("active");
2219 });
2220 </script>
2221 </body>
2222 </html>