| 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 9238: Loading Manufacturer Usage Description (MUD) URLs from QR Codes</title> |
| 8 |
<meta content="Michael Richardson" name="author"> |
| 9 |
<meta content="Jacques Latour" name="author"> |
| 10 |
<meta content="Hassan Habibi Gharakheili" name="author"> |
| 11 |
<meta content=" |
| 12 |
This informational document details a protocol to load Manufacturer Usage Description (MUD) definitions from RFC 8520 |
| 13 |
for devices that do not have them integrated. |
| 14 |
This document is published to inform the Internet community of this mechanism to allow |
| 15 |
interoperability and to serve as a basis of other standards work if there is interest. |
| 16 |
" name="description"> |
| 17 |
<meta content="xml2rfc 3.12.6" name="generator"> |
| 18 |
<meta content="RLA" name="keyword"> |
| 19 |
<meta content="ISOIEC189004" name="keyword"> |
| 20 |
<meta content="ANSI MH10.8.2" name="keyword"> |
| 21 |
<meta content="9238" name="rfc.number"> |
| 22 |
<!-- Generator version information: |
| 23 |
xml2rfc 3.12.6 |
| 24 |
Python 3.6.15 |
| 25 |
appdirs 1.4.4 |
| 26 |
ConfigArgParse 1.4.1 |
| 27 |
google-i18n-address 2.4.0 |
| 28 |
html5lib 1.0.1 |
| 29 |
intervaltree 3.0.2 |
| 30 |
Jinja2 2.11.3 |
| 31 |
kitchen 1.2.6 |
| 32 |
lxml 4.4.2 |
| 33 |
MarkupSafe 2.0.1 |
| 34 |
pycairo 1.15.1 |
| 35 |
pycountry 19.8.18 |
| 36 |
pyflakes 2.1.1 |
| 37 |
PyYAML 5.4.1 |
| 38 |
requests 2.24.0 |
| 39 |
setuptools 40.5.0 |
| 40 |
six 1.14.0 |
| 41 |
WeasyPrint 52.5 |
| 42 |
--> |
| 43 |
<link href="rfc9238.xml" rel="alternate" type="application/rfc+xml"> |
| 44 |
<link href="#copyright" rel="license"> |
| 45 |
<style type="text/css">/* |
| 46 |
|
| 47 |
NOTE: Changes at the bottom of this file overrides some earlier settings. |
| 48 |
|
| 49 |
Once the style has stabilized and has been adopted as an official RFC style, |
| 50 |
this can be consolidated so that style settings occur only in one place, but |
| 51 |
for now the contents of this file consists first of the initial CSS work as |
| 52 |
provided to the RFC Formatter (xml2rfc) work, followed by itemized and |
| 53 |
commented changes found necssary during the development of the v3 |
| 54 |
formatters. |
| 55 |
|
| 56 |
*/ |
| 57 |
|
| 58 |
/* fonts */ |
| 59 |
@import url('https://fonts.googleapis.com/css?family=Noto+Sans'); /* Sans-serif */ |
| 60 |
@import url('https://fonts.googleapis.com/css?family=Noto+Serif'); /* Serif (print) */ |
| 61 |
@import url('https://fonts.googleapis.com/css?family=Roboto+Mono'); /* Monospace */ |
| 62 |
|
| 63 |
@viewport { |
| 64 |
zoom: 1.0; |
| 65 |
width: extend-to-zoom; |
| 66 |
} |
| 67 |
@-ms-viewport { |
| 68 |
width: extend-to-zoom; |
| 69 |
zoom: 1.0; |
| 70 |
} |
| 71 |
/* general and mobile first */ |
| 72 |
html { |
| 73 |
} |
| 74 |
body { |
| 75 |
max-width: 90%; |
| 76 |
margin: 1.5em auto; |
| 77 |
color: #222; |
| 78 |
background-color: #fff; |
| 79 |
font-size: 14px; |
| 80 |
font-family: 'Noto Sans', Arial, Helvetica, sans-serif; |
| 81 |
line-height: 1.6; |
| 82 |
scroll-behavior: smooth; |
| 83 |
} |
| 84 |
.ears { |
| 85 |
display: none; |
| 86 |
} |
| 87 |
|
| 88 |
/* headings */ |
| 89 |
#title, h1, h2, h3, h4, h5, h6 { |
| 90 |
margin: 1em 0 0.5em; |
| 91 |
font-weight: bold; |
| 92 |
line-height: 1.3; |
| 93 |
} |
| 94 |
#title { |
| 95 |
clear: both; |
| 96 |
border-bottom: 1px solid #ddd; |
| 97 |
margin: 0 0 0.5em 0; |
| 98 |
padding: 1em 0 0.5em; |
| 99 |
} |
| 100 |
.author { |
| 101 |
padding-bottom: 4px; |
| 102 |
} |
| 103 |
h1 { |
| 104 |
font-size: 26px; |
| 105 |
margin: 1em 0; |
| 106 |
} |
| 107 |
h2 { |
| 108 |
font-size: 22px; |
| 109 |
margin-top: -20px; /* provide offset for in-page anchors */ |
| 110 |
padding-top: 33px; |
| 111 |
} |
| 112 |
h3 { |
| 113 |
font-size: 18px; |
| 114 |
margin-top: -36px; /* provide offset for in-page anchors */ |
| 115 |
padding-top: 42px; |
| 116 |
} |
| 117 |
h4 { |
| 118 |
font-size: 16px; |
| 119 |
margin-top: -36px; /* provide offset for in-page anchors */ |
| 120 |
padding-top: 42px; |
| 121 |
} |
| 122 |
h5, h6 { |
| 123 |
font-size: 14px; |
| 124 |
} |
| 125 |
#n-copyright-notice { |
| 126 |
border-bottom: 1px solid #ddd; |
| 127 |
padding-bottom: 1em; |
| 128 |
margin-bottom: 1em; |
| 129 |
} |
| 130 |
/* general structure */ |
| 131 |
p { |
| 132 |
padding: 0; |
| 133 |
margin: 0 0 1em 0; |
| 134 |
text-align: left; |
| 135 |
} |
| 136 |
div, span { |
| 137 |
position: relative; |
| 138 |
} |
| 139 |
div { |
| 140 |
margin: 0; |
| 141 |
} |
| 142 |
.alignRight.art-text { |
| 143 |
background-color: #f9f9f9; |
| 144 |
border: 1px solid #eee; |
| 145 |
border-radius: 3px; |
| 146 |
padding: 1em 1em 0; |
| 147 |
margin-bottom: 1.5em; |
| 148 |
} |
| 149 |
.alignRight.art-text pre { |
| 150 |
padding: 0; |
| 151 |
} |
| 152 |
.alignRight { |
| 153 |
margin: 1em 0; |
| 154 |
} |
| 155 |
.alignRight > *:first-child { |
| 156 |
border: none; |
| 157 |
margin: 0; |
| 158 |
float: right; |
| 159 |
clear: both; |
| 160 |
} |
| 161 |
.alignRight > *:nth-child(2) { |
| 162 |
clear: both; |
| 163 |
display: block; |
| 164 |
border: none; |
| 165 |
} |
| 166 |
svg { |
| 167 |
display: block; |
| 168 |
} |
| 169 |
.alignCenter.art-text { |
| 170 |
background-color: #f9f9f9; |
| 171 |
border: 1px solid #eee; |
| 172 |
border-radius: 3px; |
| 173 |
padding: 1em 1em 0; |
| 174 |
margin-bottom: 1.5em; |
| 175 |
} |
| 176 |
.alignCenter.art-text pre { |
| 177 |
padding: 0; |
| 178 |
} |
| 179 |
.alignCenter { |
| 180 |
margin: 1em 0; |
| 181 |
} |
| 182 |
.alignCenter > *:first-child { |
| 183 |
border: none; |
| 184 |
/* this isn't optimal, but it's an existence proof. PrinceXML doesn't |
| 185 |
support flexbox yet. |
| 186 |
*/ |
| 187 |
display: table; |
| 188 |
margin: 0 auto; |
| 189 |
} |
| 190 |
|
| 191 |
/* lists */ |
| 192 |
ol, ul { |
| 193 |
padding: 0; |
| 194 |
margin: 0 0 1em 2em; |
| 195 |
} |
| 196 |
ol ol, ul ul, ol ul, ul ol { |
| 197 |
margin-left: 1em; |
| 198 |
} |
| 199 |
li { |
| 200 |
margin: 0 0 0.25em 0; |
| 201 |
} |
| 202 |
.ulCompact li { |
| 203 |
margin: 0; |
| 204 |
} |
| 205 |
ul.empty, .ulEmpty { |
| 206 |
list-style-type: none; |
| 207 |
} |
| 208 |
ul.empty li, .ulEmpty li { |
| 209 |
margin-top: 0.5em; |
| 210 |
} |
| 211 |
ul.ulBare, li.ulBare { |
| 212 |
margin-left: 0em !important; |
| 213 |
} |
| 214 |
ul.compact, .ulCompact, |
| 215 |
ol.compact, .olCompact { |
| 216 |
line-height: 100%; |
| 217 |
margin: 0 0 0 2em; |
| 218 |
} |
| 219 |
|
| 220 |
/* definition lists */ |
| 221 |
dl { |
| 222 |
} |
| 223 |
dl > dt { |
| 224 |
float: left; |
| 225 |
margin-right: 1em; |
| 226 |
} |
| 227 |
/* |
| 228 |
dl.nohang > dt { |
| 229 |
float: none; |
| 230 |
} |
| 231 |
*/ |
| 232 |
dl > dd { |
| 233 |
margin-bottom: .8em; |
| 234 |
min-height: 1.3em; |
| 235 |
} |
| 236 |
dl.compact > dd, .dlCompact > dd { |
| 237 |
margin-bottom: 0em; |
| 238 |
} |
| 239 |
dl > dd > dl { |
| 240 |
margin-top: 0.5em; |
| 241 |
margin-bottom: 0em; |
| 242 |
} |
| 243 |
|
| 244 |
/* links */ |
| 245 |
a { |
| 246 |
text-decoration: none; |
| 247 |
} |
| 248 |
a[href] { |
| 249 |
color: #22e; /* Arlen: WCAG 2019 */ |
| 250 |
} |
| 251 |
a[href]:hover { |
| 252 |
background-color: #f2f2f2; |
| 253 |
} |
| 254 |
figcaption a[href], |
| 255 |
a[href].selfRef { |
| 256 |
color: #222; |
| 257 |
} |
| 258 |
/* XXX probably not this: |
| 259 |
a.selfRef:hover { |
| 260 |
background-color: transparent; |
| 261 |
cursor: default; |
| 262 |
} */ |
| 263 |
|
| 264 |
/* Figures */ |
| 265 |
tt, code, pre, code { |
| 266 |
background-color: #f9f9f9; |
| 267 |
font-family: 'Roboto Mono', monospace; |
| 268 |
} |
| 269 |
pre { |
| 270 |
border: 1px solid #eee; |
| 271 |
margin: 0; |
| 272 |
padding: 1em; |
| 273 |
} |
| 274 |
img { |
| 275 |
max-width: 100%; |
| 276 |
} |
| 277 |
figure { |
| 278 |
margin: 0; |
| 279 |
} |
| 280 |
figure blockquote { |
| 281 |
margin: 0.8em 0.4em 0.4em; |
| 282 |
} |
| 283 |
figcaption { |
| 284 |
font-style: italic; |
| 285 |
margin: 0 0 1em 0; |
| 286 |
} |
| 287 |
@media screen { |
| 288 |
pre { |
| 289 |
overflow-x: auto; |
| 290 |
max-width: 100%; |
| 291 |
max-width: calc(100% - 22px); |
| 292 |
} |
| 293 |
} |
| 294 |
|
| 295 |
/* aside, blockquote */ |
| 296 |
aside, blockquote { |
| 297 |
margin-left: 0; |
| 298 |
padding: 1.2em 2em; |
| 299 |
} |
| 300 |
blockquote { |
| 301 |
background-color: #f9f9f9; |
| 302 |
color: #111; /* Arlen: WCAG 2019 */ |
| 303 |
border: 1px solid #ddd; |
| 304 |
border-radius: 3px; |
| 305 |
margin: 1em 0; |
| 306 |
} |
| 307 |
cite { |
| 308 |
display: block; |
| 309 |
text-align: right; |
| 310 |
font-style: italic; |
| 311 |
} |
| 312 |
|
| 313 |
/* tables */ |
| 314 |
table { |
| 315 |
width: 100%; |
| 316 |
margin: 0 0 1em; |
| 317 |
border-collapse: collapse; |
| 318 |
border: 1px solid #eee; |
| 319 |
} |
| 320 |
th, td { |
| 321 |
text-align: left; |
| 322 |
vertical-align: top; |
| 323 |
padding: 0.5em 0.75em; |
| 324 |
} |
| 325 |
th { |
| 326 |
text-align: left; |
| 327 |
background-color: #e9e9e9; |
| 328 |
} |
| 329 |
tr:nth-child(2n+1) > td { |
| 330 |
background-color: #f5f5f5; |
| 331 |
} |
| 332 |
table caption { |
| 333 |
font-style: italic; |
| 334 |
margin: 0; |
| 335 |
padding: 0; |
| 336 |
text-align: left; |
| 337 |
} |
| 338 |
table p { |
| 339 |
/* XXX to avoid bottom margin on table row signifiers. If paragraphs should |
| 340 |
be allowed within tables more generally, it would be far better to select on a class. */ |
| 341 |
margin: 0; |
| 342 |
} |
| 343 |
|
| 344 |
/* pilcrow */ |
| 345 |
a.pilcrow { |
| 346 |
color: #666; /* Arlen: AHDJ 2019 */ |
| 347 |
text-decoration: none; |
| 348 |
visibility: hidden; |
| 349 |
user-select: none; |
| 350 |
-ms-user-select: none; |
| 351 |
-o-user-select:none; |
| 352 |
-moz-user-select: none; |
| 353 |
-khtml-user-select: none; |
| 354 |
-webkit-user-select: none; |
| 355 |
-webkit-touch-callout: none; |
| 356 |
} |
| 357 |
@media screen { |
| 358 |
aside:hover > a.pilcrow, |
| 359 |
p:hover > a.pilcrow, |
| 360 |
blockquote:hover > a.pilcrow, |
| 361 |
div:hover > a.pilcrow, |
| 362 |
li:hover > a.pilcrow, |
| 363 |
pre:hover > a.pilcrow { |
| 364 |
visibility: visible; |
| 365 |
} |
| 366 |
a.pilcrow:hover { |
| 367 |
background-color: transparent; |
| 368 |
} |
| 369 |
} |
| 370 |
|
| 371 |
/* misc */ |
| 372 |
hr { |
| 373 |
border: 0; |
| 374 |
border-top: 1px solid #eee; |
| 375 |
} |
| 376 |
.bcp14 { |
| 377 |
font-variant: small-caps; |
| 378 |
} |
| 379 |
|
| 380 |
.role { |
| 381 |
font-variant: all-small-caps; |
| 382 |
} |
| 383 |
|
| 384 |
/* info block */ |
| 385 |
#identifiers { |
| 386 |
margin: 0; |
| 387 |
font-size: 0.9em; |
| 388 |
} |
| 389 |
#identifiers dt { |
| 390 |
width: 3em; |
| 391 |
clear: left; |
| 392 |
} |
| 393 |
#identifiers dd { |
| 394 |
float: left; |
| 395 |
margin-bottom: 0; |
| 396 |
} |
| 397 |
/* Fix PDF info block run off issue */ |
| 398 |
@media print { |
| 399 |
#identifiers dd { |
| 400 |
float: none; |
| 401 |
} |
| 402 |
} |
| 403 |
#identifiers .authors .author { |
| 404 |
display: inline-block; |
| 405 |
margin-right: 1.5em; |
| 406 |
} |
| 407 |
#identifiers .authors .org { |
| 408 |
font-style: italic; |
| 409 |
} |
| 410 |
|
| 411 |
/* The prepared/rendered info at the very bottom of the page */ |
| 412 |
.docInfo { |
| 413 |
color: #666; /* Arlen: WCAG 2019 */ |
| 414 |
font-size: 0.9em; |
| 415 |
font-style: italic; |
| 416 |
margin-top: 2em; |
| 417 |
} |
| 418 |
.docInfo .prepared { |
| 419 |
float: left; |
| 420 |
} |
| 421 |
.docInfo .prepared { |
| 422 |
float: right; |
| 423 |
} |
| 424 |
|
| 425 |
/* table of contents */ |
| 426 |
#toc { |
| 427 |
padding: 0.75em 0 2em 0; |
| 428 |
margin-bottom: 1em; |
| 429 |
} |
| 430 |
nav.toc ul { |
| 431 |
margin: 0 0.5em 0 0; |
| 432 |
padding: 0; |
| 433 |
list-style: none; |
| 434 |
} |
| 435 |
nav.toc li { |
| 436 |
line-height: 1.3em; |
| 437 |
margin: 0.75em 0; |
| 438 |
padding-left: 1.2em; |
| 439 |
text-indent: -1.2em; |
| 440 |
} |
| 441 |
/* references */ |
| 442 |
.references dt { |
| 443 |
text-align: right; |
| 444 |
font-weight: bold; |
| 445 |
min-width: 7em; |
| 446 |
} |
| 447 |
.references dd { |
| 448 |
margin-left: 8em; |
| 449 |
overflow: auto; |
| 450 |
} |
| 451 |
|
| 452 |
.refInstance { |
| 453 |
margin-bottom: 1.25em; |
| 454 |
} |
| 455 |
|
| 456 |
.references .ascii { |
| 457 |
margin-bottom: 0.25em; |
| 458 |
} |
| 459 |
|
| 460 |
/* index */ |
| 461 |
.index ul { |
| 462 |
margin: 0 0 0 1em; |
| 463 |
padding: 0; |
| 464 |
list-style: none; |
| 465 |
} |
| 466 |
.index ul ul { |
| 467 |
margin: 0; |
| 468 |
} |
| 469 |
.index li { |
| 470 |
margin: 0; |
| 471 |
text-indent: -2em; |
| 472 |
padding-left: 2em; |
| 473 |
padding-bottom: 5px; |
| 474 |
} |
| 475 |
.indexIndex { |
| 476 |
margin: 0.5em 0 1em; |
| 477 |
} |
| 478 |
.index a { |
| 479 |
font-weight: 700; |
| 480 |
} |
| 481 |
/* make the index two-column on all but the smallest screens */ |
| 482 |
@media (min-width: 600px) { |
| 483 |
.index ul { |
| 484 |
-moz-column-count: 2; |
| 485 |
-moz-column-gap: 20px; |
| 486 |
} |
| 487 |
.index ul ul { |
| 488 |
-moz-column-count: 1; |
| 489 |
-moz-column-gap: 0; |
| 490 |
} |
| 491 |
} |
| 492 |
|
| 493 |
/* authors */ |
| 494 |
address.vcard { |
| 495 |
font-style: normal; |
| 496 |
margin: 1em 0; |
| 497 |
} |
| 498 |
|
| 499 |
address.vcard .nameRole { |
| 500 |
font-weight: 700; |
| 501 |
margin-left: 0; |
| 502 |
} |
| 503 |
address.vcard .label { |
| 504 |
font-family: "Noto Sans",Arial,Helvetica,sans-serif; |
| 505 |
margin: 0.5em 0; |
| 506 |
} |
| 507 |
address.vcard .type { |
| 508 |
display: none; |
| 509 |
} |
| 510 |
.alternative-contact { |
| 511 |
margin: 1.5em 0 1em; |
| 512 |
} |
| 513 |
hr.addr { |
| 514 |
border-top: 1px dashed; |
| 515 |
margin: 0; |
| 516 |
color: #ddd; |
| 517 |
max-width: calc(100% - 16px); |
| 518 |
} |
| 519 |
|
| 520 |
/* temporary notes */ |
| 521 |
.rfcEditorRemove::before { |
| 522 |
position: absolute; |
| 523 |
top: 0.2em; |
| 524 |
right: 0.2em; |
| 525 |
padding: 0.2em; |
| 526 |
content: "The RFC Editor will remove this note"; |
| 527 |
color: #9e2a00; /* Arlen: WCAG 2019 */ |
| 528 |
background-color: #ffd; /* Arlen: WCAG 2019 */ |
| 529 |
} |
| 530 |
.rfcEditorRemove { |
| 531 |
position: relative; |
| 532 |
padding-top: 1.8em; |
| 533 |
background-color: #ffd; /* Arlen: WCAG 2019 */ |
| 534 |
border-radius: 3px; |
| 535 |
} |
| 536 |
.cref { |
| 537 |
background-color: #ffd; /* Arlen: WCAG 2019 */ |
| 538 |
padding: 2px 4px; |
| 539 |
} |
| 540 |
.crefSource { |
| 541 |
font-style: italic; |
| 542 |
} |
| 543 |
/* alternative layout for smaller screens */ |
| 544 |
@media screen and (max-width: 1023px) { |
| 545 |
body { |
| 546 |
padding-top: 2em; |
| 547 |
} |
| 548 |
#title { |
| 549 |
padding: 1em 0; |
| 550 |
} |
| 551 |
h1 { |
| 552 |
font-size: 24px; |
| 553 |
} |
| 554 |
h2 { |
| 555 |
font-size: 20px; |
| 556 |
margin-top: -18px; /* provide offset for in-page anchors */ |
| 557 |
padding-top: 38px; |
| 558 |
} |
| 559 |
#identifiers dd { |
| 560 |
max-width: 60%; |
| 561 |
} |
| 562 |
#toc { |
| 563 |
position: fixed; |
| 564 |
z-index: 2; |
| 565 |
top: 0; |
| 566 |
right: 0; |
| 567 |
padding: 0; |
| 568 |
margin: 0; |
| 569 |
background-color: inherit; |
| 570 |
border-bottom: 1px solid #ccc; |
| 571 |
} |
| 572 |
#toc h2 { |
| 573 |
margin: -1px 0 0 0; |
| 574 |
padding: 4px 0 4px 6px; |
| 575 |
padding-right: 1em; |
| 576 |
min-width: 190px; |
| 577 |
font-size: 1.1em; |
| 578 |
text-align: right; |
| 579 |
background-color: #444; |
| 580 |
color: white; |
| 581 |
cursor: pointer; |
| 582 |
} |
| 583 |
#toc h2::before { /* css hamburger */ |
| 584 |
float: right; |
| 585 |
position: relative; |
| 586 |
width: 1em; |
| 587 |
height: 1px; |
| 588 |
left: -164px; |
| 589 |
margin: 6px 0 0 0; |
| 590 |
background: white none repeat scroll 0 0; |
| 591 |
box-shadow: 0 4px 0 0 white, 0 8px 0 0 white; |
| 592 |
content: ""; |
| 593 |
} |
| 594 |
#toc nav { |
| 595 |
display: none; |
| 596 |
padding: 0.5em 1em 1em; |
| 597 |
overflow: auto; |
| 598 |
height: calc(100vh - 48px); |
| 599 |
border-left: 1px solid #ddd; |
| 600 |
} |
| 601 |
} |
| 602 |
|
| 603 |
/* alternative layout for wide screens */ |
| 604 |
@media screen and (min-width: 1024px) { |
| 605 |
body { |
| 606 |
max-width: 724px; |
| 607 |
margin: 42px auto; |
| 608 |
padding-left: 1.5em; |
| 609 |
padding-right: 29em; |
| 610 |
} |
| 611 |
#toc { |
| 612 |
position: fixed; |
| 613 |
top: 42px; |
| 614 |
right: 42px; |
| 615 |
width: 25%; |
| 616 |
margin: 0; |
| 617 |
padding: 0 1em; |
| 618 |
z-index: 1; |
| 619 |
} |
| 620 |
#toc h2 { |
| 621 |
border-top: none; |
| 622 |
border-bottom: 1px solid #ddd; |
| 623 |
font-size: 1em; |
| 624 |
font-weight: normal; |
| 625 |
margin: 0; |
| 626 |
padding: 0.25em 1em 1em 0; |
| 627 |
} |
| 628 |
#toc nav { |
| 629 |
display: block; |
| 630 |
height: calc(90vh - 84px); |
| 631 |
bottom: 0; |
| 632 |
padding: 0.5em 0 0; |
| 633 |
overflow: auto; |
| 634 |
} |
| 635 |
img { /* future proofing */ |
| 636 |
max-width: 100%; |
| 637 |
height: auto; |
| 638 |
} |
| 639 |
} |
| 640 |
|
| 641 |
/* pagination */ |
| 642 |
@media print { |
| 643 |
body { |
| 644 |
|
| 645 |
width: 100%; |
| 646 |
} |
| 647 |
p { |
| 648 |
orphans: 3; |
| 649 |
widows: 3; |
| 650 |
} |
| 651 |
#n-copyright-notice { |
| 652 |
border-bottom: none; |
| 653 |
} |
| 654 |
#toc, #n-introduction { |
| 655 |
page-break-before: always; |
| 656 |
} |
| 657 |
#toc { |
| 658 |
border-top: none; |
| 659 |
padding-top: 0; |
| 660 |
} |
| 661 |
figure, pre { |
| 662 |
page-break-inside: avoid; |
| 663 |
} |
| 664 |
figure { |
| 665 |
overflow: scroll; |
| 666 |
} |
| 667 |
pre.breakable { |
| 668 |
break-inside: auto; |
| 669 |
} |
| 670 |
h1, h2, h3, h4, h5, h6 { |
| 671 |
page-break-after: avoid; |
| 672 |
} |
| 673 |
h2+*, h3+*, h4+*, h5+*, h6+* { |
| 674 |
page-break-before: avoid; |
| 675 |
} |
| 676 |
pre { |
| 677 |
white-space: pre-wrap; |
| 678 |
word-wrap: break-word; |
| 679 |
font-size: 10pt; |
| 680 |
} |
| 681 |
table { |
| 682 |
border: 1px solid #ddd; |
| 683 |
} |
| 684 |
td { |
| 685 |
border-top: 1px solid #ddd; |
| 686 |
} |
| 687 |
} |
| 688 |
|
| 689 |
/* This is commented out here, as the string-set: doesn't |
| 690 |
pass W3C validation currently */ |
| 691 |
/* |
| 692 |
.ears thead .left { |
| 693 |
string-set: ears-top-left content(); |
| 694 |
} |
| 695 |
|
| 696 |
.ears thead .center { |
| 697 |
string-set: ears-top-center content(); |
| 698 |
} |
| 699 |
|
| 700 |
.ears thead .right { |
| 701 |
string-set: ears-top-right content(); |
| 702 |
} |
| 703 |
|
| 704 |
.ears tfoot .left { |
| 705 |
string-set: ears-bottom-left content(); |
| 706 |
} |
| 707 |
|
| 708 |
.ears tfoot .center { |
| 709 |
string-set: ears-bottom-center content(); |
| 710 |
} |
| 711 |
|
| 712 |
.ears tfoot .right { |
| 713 |
string-set: ears-bottom-right content(); |
| 714 |
} |
| 715 |
*/ |
| 716 |
|
| 717 |
@page :first { |
| 718 |
padding-top: 0; |
| 719 |
@top-left { |
| 720 |
content: normal; |
| 721 |
border: none; |
| 722 |
} |
| 723 |
@top-center { |
| 724 |
content: normal; |
| 725 |
border: none; |
| 726 |
} |
| 727 |
@top-right { |
| 728 |
content: normal; |
| 729 |
border: none; |
| 730 |
} |
| 731 |
} |
| 732 |
|
| 733 |
@page { |
| 734 |
size: A4; |
| 735 |
margin-bottom: 45mm; |
| 736 |
padding-top: 20px; |
| 737 |
/* The follwing is commented out here, but set appropriately by in code, as |
| 738 |
the content depends on the document */ |
| 739 |
/* |
| 740 |
@top-left { |
| 741 |
content: 'Internet-Draft'; |
| 742 |
vertical-align: bottom; |
| 743 |
border-bottom: solid 1px #ccc; |
| 744 |
} |
| 745 |
@top-left { |
| 746 |
content: string(ears-top-left); |
| 747 |
vertical-align: bottom; |
| 748 |
border-bottom: solid 1px #ccc; |
| 749 |
} |
| 750 |
@top-center { |
| 751 |
content: string(ears-top-center); |
| 752 |
vertical-align: bottom; |
| 753 |
border-bottom: solid 1px #ccc; |
| 754 |
} |
| 755 |
@top-right { |
| 756 |
content: string(ears-top-right); |
| 757 |
vertical-align: bottom; |
| 758 |
border-bottom: solid 1px #ccc; |
| 759 |
} |
| 760 |
@bottom-left { |
| 761 |
content: string(ears-bottom-left); |
| 762 |
vertical-align: top; |
| 763 |
border-top: solid 1px #ccc; |
| 764 |
} |
| 765 |
@bottom-center { |
| 766 |
content: string(ears-bottom-center); |
| 767 |
vertical-align: top; |
| 768 |
border-top: solid 1px #ccc; |
| 769 |
} |
| 770 |
@bottom-right { |
| 771 |
content: '[Page ' counter(page) ']'; |
| 772 |
vertical-align: top; |
| 773 |
border-top: solid 1px #ccc; |
| 774 |
} |
| 775 |
*/ |
| 776 |
|
| 777 |
} |
| 778 |
|
| 779 |
/* Changes introduced to fix issues found during implementation */ |
| 780 |
/* Make sure links are clickable even if overlapped by following H* */ |
| 781 |
a { |
| 782 |
z-index: 2; |
| 783 |
} |
| 784 |
/* Separate body from document info even without intervening H1 */ |
| 785 |
section { |
| 786 |
clear: both; |
| 787 |
} |
| 788 |
|
| 789 |
|
| 790 |
/* Top align author divs, to avoid names without organization dropping level with org names */ |
| 791 |
.author { |
| 792 |
vertical-align: top; |
| 793 |
} |
| 794 |
|
| 795 |
/* Leave room in document info to show Internet-Draft on one line */ |
| 796 |
#identifiers dt { |
| 797 |
width: 8em; |
| 798 |
} |
| 799 |
|
| 800 |
/* Don't waste quite as much whitespace between label and value in doc info */ |
| 801 |
#identifiers dd { |
| 802 |
margin-left: 1em; |
| 803 |
} |
| 804 |
|
| 805 |
/* Give floating toc a background color (needed when it's a div inside section */ |
| 806 |
#toc { |
| 807 |
background-color: white; |
| 808 |
} |
| 809 |
|
| 810 |
/* Make the collapsed ToC header render white on gray also when it's a link */ |
| 811 |
@media screen and (max-width: 1023px) { |
| 812 |
#toc h2 a, |
| 813 |
#toc h2 a:link, |
| 814 |
#toc h2 a:focus, |
| 815 |
#toc h2 a:hover, |
| 816 |
#toc a.toplink, |
| 817 |
#toc a.toplink:hover { |
| 818 |
color: white; |
| 819 |
background-color: #444; |
| 820 |
text-decoration: none; |
| 821 |
} |
| 822 |
} |
| 823 |
|
| 824 |
/* Give the bottom of the ToC some whitespace */ |
| 825 |
@media screen and (min-width: 1024px) { |
| 826 |
#toc { |
| 827 |
padding: 0 0 1em 1em; |
| 828 |
} |
| 829 |
} |
| 830 |
|
| 831 |
/* Style section numbers with more space between number and title */ |
| 832 |
.section-number { |
| 833 |
padding-right: 0.5em; |
| 834 |
} |
| 835 |
|
| 836 |
/* prevent monospace from becoming overly large */ |
| 837 |
tt, code, pre, code { |
| 838 |
font-size: 95%; |
| 839 |
} |
| 840 |
|
| 841 |
/* Fix the height/width aspect for ascii art*/ |
| 842 |
pre.sourcecode, |
| 843 |
.art-text pre { |
| 844 |
line-height: 1.12; |
| 845 |
} |
| 846 |
|
| 847 |
|
| 848 |
/* Add styling for a link in the ToC that points to the top of the document */ |
| 849 |
a.toplink { |
| 850 |
float: right; |
| 851 |
margin-right: 0.5em; |
| 852 |
} |
| 853 |
|
| 854 |
/* Fix the dl styling to match the RFC 7992 attributes */ |
| 855 |
dl > dt, |
| 856 |
dl.dlParallel > dt { |
| 857 |
float: left; |
| 858 |
margin-right: 1em; |
| 859 |
} |
| 860 |
dl.dlNewline > dt { |
| 861 |
float: none; |
| 862 |
} |
| 863 |
|
| 864 |
/* Provide styling for table cell text alignment */ |
| 865 |
table td.text-left, |
| 866 |
table th.text-left { |
| 867 |
text-align: left; |
| 868 |
} |
| 869 |
table td.text-center, |
| 870 |
table th.text-center { |
| 871 |
text-align: center; |
| 872 |
} |
| 873 |
table td.text-right, |
| 874 |
table th.text-right { |
| 875 |
text-align: right; |
| 876 |
} |
| 877 |
|
| 878 |
/* Make the alternative author contact informatio look less like just another |
| 879 |
author, and group it closer with the primary author contact information */ |
| 880 |
.alternative-contact { |
| 881 |
margin: 0.5em 0 0.25em 0; |
| 882 |
} |
| 883 |
address .non-ascii { |
| 884 |
margin: 0 0 0 2em; |
| 885 |
} |
| 886 |
|
| 887 |
/* With it being possible to set tables with alignment |
| 888 |
left, center, and right, { width: 100%; } does not make sense */ |
| 889 |
table { |
| 890 |
width: auto; |
| 891 |
} |
| 892 |
|
| 893 |
/* Avoid reference text that sits in a block with very wide left margin, |
| 894 |
because of a long floating dt label.*/ |
| 895 |
.references dd { |
| 896 |
overflow: visible; |
| 897 |
} |
| 898 |
|
| 899 |
/* Control caption placement */ |
| 900 |
caption { |
| 901 |
caption-side: bottom; |
| 902 |
} |
| 903 |
|
| 904 |
/* Limit the width of the author address vcard, so names in right-to-left |
| 905 |
script don't end up on the other side of the page. */ |
| 906 |
|
| 907 |
address.vcard { |
| 908 |
max-width: 30em; |
| 909 |
margin-right: auto; |
| 910 |
} |
| 911 |
|
| 912 |
/* For address alignment dependent on LTR or RTL scripts */ |
| 913 |
address div.left { |
| 914 |
text-align: left; |
| 915 |
} |
| 916 |
address div.right { |
| 917 |
text-align: right; |
| 918 |
} |
| 919 |
|
| 920 |
/* Provide table alignment support. We can't use the alignX classes above |
| 921 |
since they do unwanted things with caption and other styling. */ |
| 922 |
table.right { |
| 923 |
margin-left: auto; |
| 924 |
margin-right: 0; |
| 925 |
} |
| 926 |
table.center { |
| 927 |
margin-left: auto; |
| 928 |
margin-right: auto; |
| 929 |
} |
| 930 |
table.left { |
| 931 |
margin-left: 0; |
| 932 |
margin-right: auto; |
| 933 |
} |
| 934 |
|
| 935 |
/* Give the table caption label the same styling as the figcaption */ |
| 936 |
caption a[href] { |
| 937 |
color: #222; |
| 938 |
} |
| 939 |
|
| 940 |
@media print { |
| 941 |
.toplink { |
| 942 |
display: none; |
| 943 |
} |
| 944 |
|
| 945 |
/* avoid overwriting the top border line with the ToC header */ |
| 946 |
#toc { |
| 947 |
padding-top: 1px; |
| 948 |
} |
| 949 |
|
| 950 |
/* Avoid page breaks inside dl and author address entries */ |
| 951 |
.vcard { |
| 952 |
page-break-inside: avoid; |
| 953 |
} |
| 954 |
|
| 955 |
} |
| 956 |
/* Tweak the bcp14 keyword presentation */ |
| 957 |
.bcp14 { |
| 958 |
font-variant: small-caps; |
| 959 |
font-weight: bold; |
| 960 |
font-size: 0.9em; |
| 961 |
} |
| 962 |
/* Tweak the invisible space above H* in order not to overlay links in text above */ |
| 963 |
h2 { |
| 964 |
margin-top: -18px; /* provide offset for in-page anchors */ |
| 965 |
padding-top: 31px; |
| 966 |
} |
| 967 |
h3 { |
| 968 |
margin-top: -18px; /* provide offset for in-page anchors */ |
| 969 |
padding-top: 24px; |
| 970 |
} |
| 971 |
h4 { |
| 972 |
margin-top: -18px; /* provide offset for in-page anchors */ |
| 973 |
padding-top: 24px; |
| 974 |
} |
| 975 |
/* Float artwork pilcrow to the right */ |
| 976 |
@media screen { |
| 977 |
.artwork a.pilcrow { |
| 978 |
display: block; |
| 979 |
line-height: 0.7; |
| 980 |
margin-top: 0.15em; |
| 981 |
} |
| 982 |
} |
| 983 |
/* Make pilcrows on dd visible */ |
| 984 |
@media screen { |
| 985 |
dd:hover > a.pilcrow { |
| 986 |
visibility: visible; |
| 987 |
} |
| 988 |
} |
| 989 |
/* Make the placement of figcaption match that of a table's caption |
| 990 |
by removing the figure's added bottom margin */ |
| 991 |
.alignLeft.art-text, |
| 992 |
.alignCenter.art-text, |
| 993 |
.alignRight.art-text { |
| 994 |
margin-bottom: 0; |
| 995 |
} |
| 996 |
.alignLeft, |
| 997 |
.alignCenter, |
| 998 |
.alignRight { |
| 999 |
margin: 1em 0 0 0; |
| 1000 |
} |
| 1001 |
/* In print, the pilcrow won't show on hover, so prevent it from taking up space, |
| 1002 |
possibly even requiring a new line */ |
| 1003 |
@media print { |
| 1004 |
a.pilcrow { |
| 1005 |
display: none; |
| 1006 |
} |
| 1007 |
} |
| 1008 |
/* Styling for the external metadata */ |
| 1009 |
div#external-metadata { |
| 1010 |
background-color: #eee; |
| 1011 |
padding: 0.5em; |
| 1012 |
margin-bottom: 0.5em; |
| 1013 |
display: none; |
| 1014 |
} |
| 1015 |
div#internal-metadata { |
| 1016 |
padding: 0.5em; /* to match the external-metadata padding */ |
| 1017 |
} |
| 1018 |
/* Styling for title RFC Number */ |
| 1019 |
h1#rfcnum { |
| 1020 |
clear: both; |
| 1021 |
margin: 0 0 -1em; |
| 1022 |
padding: 1em 0 0 0; |
| 1023 |
} |
| 1024 |
/* Make .olPercent look the same as <ol><li> */ |
| 1025 |
dl.olPercent > dd { |
| 1026 |
margin-bottom: 0.25em; |
| 1027 |
min-height: initial; |
| 1028 |
} |
| 1029 |
/* Give aside some styling to set it apart */ |
| 1030 |
aside { |
| 1031 |
border-left: 1px solid #ddd; |
| 1032 |
margin: 1em 0 1em 2em; |
| 1033 |
padding: 0.2em 2em; |
| 1034 |
} |
| 1035 |
aside > dl, |
| 1036 |
aside > ol, |
| 1037 |
aside > ul, |
| 1038 |
aside > table, |
| 1039 |
aside > p { |
| 1040 |
margin-bottom: 0.5em; |
| 1041 |
} |
| 1042 |
/* Additional page break settings */ |
| 1043 |
@media print { |
| 1044 |
figcaption, table caption { |
| 1045 |
page-break-before: avoid; |
| 1046 |
} |
| 1047 |
} |
| 1048 |
/* Font size adjustments for print */ |
| 1049 |
@media print { |
| 1050 |
body { font-size: 10pt; line-height: normal; max-width: 96%; } |
| 1051 |
h1 { font-size: 1.72em; padding-top: 1.5em; } /* 1*1.2*1.2*1.2 */ |
| 1052 |
h2 { font-size: 1.44em; padding-top: 1.5em; } /* 1*1.2*1.2 */ |
| 1053 |
h3 { font-size: 1.2em; padding-top: 1.5em; } /* 1*1.2 */ |
| 1054 |
h4 { font-size: 1em; padding-top: 1.5em; } |
| 1055 |
h5, h6 { font-size: 1em; margin: initial; padding: 0.5em 0 0.3em; } |
| 1056 |
} |
| 1057 |
/* Sourcecode margin in print, when there's no pilcrow */ |
| 1058 |
@media print { |
| 1059 |
.artwork, |
| 1060 |
.sourcecode { |
| 1061 |
margin-bottom: 1em; |
| 1062 |
} |
| 1063 |
} |
| 1064 |
/* Avoid narrow tables forcing too narrow table captions, which may render badly */ |
| 1065 |
table { |
| 1066 |
min-width: 20em; |
| 1067 |
} |
| 1068 |
/* ol type a */ |
| 1069 |
ol.type-a { list-style-type: lower-alpha; } |
| 1070 |
ol.type-A { list-style-type: upper-alpha; } |
| 1071 |
ol.type-i { list-style-type: lower-roman; } |
| 1072 |
ol.type-I { list-style-type: lower-roman; } |
| 1073 |
/* Apply the print table and row borders in general, on request from the RPC, |
| 1074 |
and increase the contrast between border and odd row background sligthtly */ |
| 1075 |
table { |
| 1076 |
border: 1px solid #ddd; |
| 1077 |
} |
| 1078 |
td { |
| 1079 |
border-top: 1px solid #ddd; |
| 1080 |
} |
| 1081 |
tr:nth-child(2n+1) > td { |
| 1082 |
background-color: #f8f8f8; |
| 1083 |
} |
| 1084 |
/* Use style rules to govern display of the TOC. */ |
| 1085 |
@media screen and (max-width: 1023px) { |
| 1086 |
#toc nav { display: none; } |
| 1087 |
#toc.active nav { display: block; } |
| 1088 |
} |
| 1089 |
/* Add support for keepWithNext */ |
| 1090 |
.keepWithNext { |
| 1091 |
break-after: avoid-page; |
| 1092 |
break-after: avoid-page; |
| 1093 |
} |
| 1094 |
/* Add support for keepWithPrevious */ |
| 1095 |
.keepWithPrevious { |
| 1096 |
break-before: avoid-page; |
| 1097 |
} |
| 1098 |
/* Change the approach to avoiding breaks inside artwork etc. */ |
| 1099 |
figure, pre, table, .artwork, .sourcecode { |
| 1100 |
break-before: auto; |
| 1101 |
break-after: auto; |
| 1102 |
} |
| 1103 |
/* Avoid breaks between <dt> and <dd> */ |
| 1104 |
dl { |
| 1105 |
break-before: auto; |
| 1106 |
break-inside: auto; |
| 1107 |
} |
| 1108 |
dt { |
| 1109 |
break-before: auto; |
| 1110 |
break-after: avoid-page; |
| 1111 |
} |
| 1112 |
dd { |
| 1113 |
break-before: avoid-page; |
| 1114 |
break-after: auto; |
| 1115 |
orphans: 3; |
| 1116 |
widows: 3 |
| 1117 |
} |
| 1118 |
span.break, dd.break { |
| 1119 |
margin-bottom: 0; |
| 1120 |
min-height: 0; |
| 1121 |
break-before: auto; |
| 1122 |
break-inside: auto; |
| 1123 |
break-after: auto; |
| 1124 |
} |
| 1125 |
/* Undo break-before ToC */ |
| 1126 |
@media print { |
| 1127 |
#toc { |
| 1128 |
break-before: auto; |
| 1129 |
} |
| 1130 |
} |
| 1131 |
/* Text in compact lists should not get extra bottim margin space, |
| 1132 |
since that would makes the list not compact */ |
| 1133 |
ul.compact p, .ulCompact p, |
| 1134 |
ol.compact p, .olCompact p { |
| 1135 |
margin: 0; |
| 1136 |
} |
| 1137 |
/* But the list as a whole needs the extra space at the end */ |
| 1138 |
section ul.compact, |
| 1139 |
section .ulCompact, |
| 1140 |
section ol.compact, |
| 1141 |
section .olCompact { |
| 1142 |
margin-bottom: 1em; /* same as p not within ul.compact etc. */ |
| 1143 |
} |
| 1144 |
/* The tt and code background above interferes with for instance table cell |
| 1145 |
backgrounds. Changed to something a bit more selective. */ |
| 1146 |
tt, code { |
| 1147 |
background-color: transparent; |
| 1148 |
} |
| 1149 |
p tt, p code, li tt, li code { |
| 1150 |
background-color: #f8f8f8; |
| 1151 |
} |
| 1152 |
/* Tweak the pre margin -- 0px doesn't come out well */ |
| 1153 |
pre { |
| 1154 |
margin-top: 0.5px; |
| 1155 |
} |
| 1156 |
/* Tweak the comact list text */ |
| 1157 |
ul.compact, .ulCompact, |
| 1158 |
ol.compact, .olCompact, |
| 1159 |
dl.compact, .dlCompact { |
| 1160 |
line-height: normal; |
| 1161 |
} |
| 1162 |
/* Don't add top margin for nested lists */ |
| 1163 |
li > ul, li > ol, li > dl, |
| 1164 |
dd > ul, dd > ol, dd > dl, |
| 1165 |
dl > dd > dl { |
| 1166 |
margin-top: initial; |
| 1167 |
} |
| 1168 |
/* Elements that should not be rendered on the same line as a <dt> */ |
| 1169 |
/* This should match the element list in writer.text.TextWriter.render_dl() */ |
| 1170 |
dd > div.artwork:first-child, |
| 1171 |
dd > aside:first-child, |
| 1172 |
dd > figure:first-child, |
| 1173 |
dd > ol:first-child, |
| 1174 |
dd > div:first-child > pre.sourcecode, |
| 1175 |
dd > table:first-child, |
| 1176 |
dd > ul:first-child { |
| 1177 |
clear: left; |
| 1178 |
} |
| 1179 |
/* fix for weird browser behaviour when <dd/> is empty */ |
| 1180 |
dt+dd:empty::before{ |
| 1181 |
content: "\00a0"; |
| 1182 |
} |
| 1183 |
/* Make paragraph spacing inside <li> smaller than in body text, to fit better within the list */ |
| 1184 |
li > p { |
| 1185 |
margin-bottom: 0.5em |
| 1186 |
} |
| 1187 |
/* Don't let p margin spill out from inside list items */ |
| 1188 |
li > p:last-of-type { |
| 1189 |
margin-bottom: 0; |
| 1190 |
} |
| 1191 |
</style> |
| 1192 |
<link href="rfc-local.css" rel="stylesheet" type="text/css"> |
| 1193 |
<link href="https://dx.doi.org/10.17487/rfc9238" rel="alternate"> |
| 1194 |
<link href="urn:issn:2070-1721" rel="alternate"> |
| 1195 |
<link href="https://datatracker.ietf.org/doc/draft-richardson-mud-qrcode-07" rel="prev"> |
| 1196 |
</head> |
| 1197 |
<body> |
| 1198 |
<script src="https://www.rfc-editor.org/js/metadata.min.js"></script> |
| 1199 |
<table class="ears"> |
| 1200 |
<thead><tr> |
| 1201 |
<td class="left">RFC 9238</td> |
| 1202 |
<td class="center">Loading MUD URLs from QR Codes</td> |
| 1203 |
<td class="right">May 2022</td> |
| 1204 |
</tr></thead> |
| 1205 |
<tfoot><tr> |
| 1206 |
<td class="left">Richardson, et al.</td> |
| 1207 |
<td class="center">Informational</td> |
| 1208 |
<td class="right">[Page]</td> |
| 1209 |
</tr></tfoot> |
| 1210 |
</table> |
| 1211 |
<div id="external-metadata" class="document-information"></div> |
| 1212 |
<div id="internal-metadata" class="document-information"> |
| 1213 |
<dl id="identifiers"> |
| 1214 |
<dt class="label-stream">Stream:</dt> |
| 1215 |
<dd class="stream">Independent Submission</dd> |
| 1216 |
<dt class="label-rfc">RFC:</dt> |
| 1217 |
<dd class="rfc"><a href="https://www.rfc-editor.org/rfc/rfc9238" class="eref">9238</a></dd> |
| 1218 |
<dt class="label-category">Category:</dt> |
| 1219 |
<dd class="category">Informational</dd> |
| 1220 |
<dt class="label-published">Published:</dt> |
| 1221 |
<dd class="published"> |
| 1222 |
<time datetime="2022-05" class="published">May 2022</time> |
| 1223 |
</dd> |
| 1224 |
<dt class="label-issn">ISSN:</dt> |
| 1225 |
<dd class="issn">2070-1721</dd> |
| 1226 |
<dt class="label-authors">Authors:</dt> |
| 1227 |
<dd class="authors"> |
| 1228 |
<div class="author"> |
| 1229 |
<div class="author-name">M. Richardson</div> |
| 1230 |
<div class="org">Sandelman Software Works</div> |
| 1231 |
</div> |
| 1232 |
<div class="author"> |
| 1233 |
<div class="author-name">J. Latour</div> |
| 1234 |
<div class="org">CIRA Labs</div> |
| 1235 |
</div> |
| 1236 |
<div class="author"> |
| 1237 |
<div class="author-name">H. Habibi Gharakheili</div> |
| 1238 |
<div class="org">UNSW Sydney</div> |
| 1239 |
</div> |
| 1240 |
</dd> |
| 1241 |
</dl> |
| 1242 |
</div> |
| 1243 |
<h1 id="rfcnum">RFC 9238</h1> |
| 1244 |
<h1 id="title">Loading Manufacturer Usage Description (MUD) URLs from QR Codes</h1> |
| 1245 |
<section id="section-abstract"> |
| 1246 |
<h2 id="abstract"><a href="#abstract" class="selfRef">Abstract</a></h2> |
| 1247 |
<p id="section-abstract-1">This informational document details a protocol to load Manufacturer Usage Description (MUD) definitions from RFC 8520 |
| 1248 |
for devices that do not have them integrated.<a href="#section-abstract-1" class="pilcrow">¶</a></p> |
| 1249 |
<p id="section-abstract-2">This document is published to inform the Internet community of this mechanism to allow |
| 1250 |
interoperability and to serve as a basis of other standards work if there is interest.<a href="#section-abstract-2" class="pilcrow">¶</a></p> |
| 1251 |
</section> |
| 1252 |
<div id="status-of-memo"> |
| 1253 |
<section id="section-boilerplate.1"> |
| 1254 |
<h2 id="name-status-of-this-memo"> |
| 1255 |
<a href="#name-status-of-this-memo" class="section-name selfRef">Status of This Memo</a> |
| 1256 |
</h2> |
| 1257 |
<p id="section-boilerplate.1-1"> |
| 1258 |
This document is not an Internet Standards Track specification; it is |
| 1259 |
published for informational purposes.<a href="#section-boilerplate.1-1" class="pilcrow">¶</a></p> |
| 1260 |
<p id="section-boilerplate.1-2"> |
| 1261 |
This is a contribution to the RFC Series, independently of any |
| 1262 |
other RFC stream. The RFC Editor has chosen to publish this |
| 1263 |
document at its discretion and makes no statement about its value |
| 1264 |
for implementation or deployment. Documents approved for |
| 1265 |
publication by the RFC Editor are not candidates for any level of |
| 1266 |
Internet Standard; see Section 2 of RFC 7841.<a href="#section-boilerplate.1-2" class="pilcrow">¶</a></p> |
| 1267 |
<p id="section-boilerplate.1-3"> |
| 1268 |
Information about the current status of this document, any |
| 1269 |
errata, and how to provide feedback on it may be obtained at |
| 1270 |
<span><a href="https://www.rfc-editor.org/info/rfc9238">https://www.rfc-editor.org/info/rfc9238</a></span>.<a href="#section-boilerplate.1-3" class="pilcrow">¶</a></p> |
| 1271 |
</section> |
| 1272 |
</div> |
| 1273 |
<div id="copyright"> |
| 1274 |
<section id="section-boilerplate.2"> |
| 1275 |
<h2 id="name-copyright-notice"> |
| 1276 |
<a href="#name-copyright-notice" class="section-name selfRef">Copyright Notice</a> |
| 1277 |
</h2> |
| 1278 |
<p id="section-boilerplate.2-1"> |
| 1279 |
Copyright (c) 2022 IETF Trust and the persons identified as the |
| 1280 |
document authors. All rights reserved.<a href="#section-boilerplate.2-1" class="pilcrow">¶</a></p> |
| 1281 |
<p id="section-boilerplate.2-2"> |
| 1282 |
This document is subject to BCP 78 and the IETF Trust's Legal |
| 1283 |
Provisions Relating to IETF Documents |
| 1284 |
(<span><a href="https://trustee.ietf.org/license-info">https://trustee.ietf.org/license-info</a></span>) in effect on the date of |
| 1285 |
publication of this document. Please review these documents |
| 1286 |
carefully, as they describe your rights and restrictions with |
| 1287 |
respect to this document.<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="compact toc ulBare ulEmpty"> |
| 1296 |
<li class="compact toc ulBare ulEmpty" 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="compact toc ulBare ulEmpty" 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-terminology" class="xref">Terminology</a></p> |
| 1301 |
</li> |
| 1302 |
<li class="compact toc ulBare ulEmpty" 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-protocol" class="xref">Protocol</a></p> |
| 1304 |
<ul class="compact toc ulBare ulEmpty"> |
| 1305 |
<li class="compact toc ulBare ulEmpty" 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-the-sqrl-protocol" class="xref">The SQRL Protocol</a></p> |
| 1307 |
</li> |
| 1308 |
<li class="compact toc ulBare ulEmpty" 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-manufacturer-usage-descript" class="xref">Manufacturer Usage Descriptions in SQRL</a></p> |
| 1310 |
<ul class="compact toc ulBare ulEmpty"> |
| 1311 |
<li class="compact toc ulBare ulEmpty" 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-b000-company-name" class="xref">B000 Company Name</a></p> |
| 1313 |
</li> |
| 1314 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.3.2.2.2.2"> |
| 1315 |
<p id="section-toc.1-1.3.2.2.2.2.1"><a href="#section-3.2.2" class="xref">3.2.2</a>. <a href="#name-b001-product-name" class="xref">B001 Product Name</a></p> |
| 1316 |
</li> |
| 1317 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.3.2.2.2.3"> |
| 1318 |
<p id="section-toc.1-1.3.2.2.2.3.1"><a href="#section-3.2.3" class="xref">3.2.3</a>. <a href="#name-b002-model-number" class="xref">B002 Model Number</a></p> |
| 1319 |
</li> |
| 1320 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.3.2.2.2.4"> |
| 1321 |
<p id="section-toc.1-1.3.2.2.2.4.1"><a href="#section-3.2.4" class="xref">3.2.4</a>. <a href="#name-mud-url-data-record" class="xref">MUD URL Data Record</a></p> |
| 1322 |
</li> |
| 1323 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.3.2.2.2.5"> |
| 1324 |
<p id="section-toc.1-1.3.2.2.2.5.1"><a href="#section-3.2.5" class="xref">3.2.5</a>. <a href="#name-device-mac-address" class="xref">Device MAC Address</a></p> |
| 1325 |
</li> |
| 1326 |
</ul> |
| 1327 |
</li> |
| 1328 |
</ul> |
| 1329 |
</li> |
| 1330 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.4"> |
| 1331 |
<p id="section-toc.1-1.4.1"><a href="#section-4" class="xref">4</a>. <a href="#name-applicability" class="xref">Applicability</a></p> |
| 1332 |
</li> |
| 1333 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.5"> |
| 1334 |
<p id="section-toc.1-1.5.1"><a href="#section-5" class="xref">5</a>. <a href="#name-generic-url-or-version-spec" class="xref">Generic URL or Version-Specific URL</a></p> |
| 1335 |
</li> |
| 1336 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.6"> |
| 1337 |
<p id="section-toc.1-1.6.1"><a href="#section-6" class="xref">6</a>. <a href="#name-crowd-supply-of-mud-files" class="xref">Crowd Supply of MUD Files</a></p> |
| 1338 |
</li> |
| 1339 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.7"> |
| 1340 |
<p id="section-toc.1-1.7.1"><a href="#section-7" class="xref">7</a>. <a href="#name-privacy-considerations" class="xref">Privacy Considerations</a></p> |
| 1341 |
</li> |
| 1342 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.8"> |
| 1343 |
<p id="section-toc.1-1.8.1"><a href="#section-8" class="xref">8</a>. <a href="#name-security-considerations" class="xref">Security Considerations</a></p> |
| 1344 |
<ul class="compact toc ulBare ulEmpty"> |
| 1345 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.8.2.1"> |
| 1346 |
<p id="section-toc.1-1.8.2.1.1"><a href="#section-8.1" class="xref">8.1</a>. <a href="#name-qr-codes-are-not-assurances" class="xref">QR Codes Are Not Assurances</a></p> |
| 1347 |
</li> |
| 1348 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.8.2.2"> |
| 1349 |
<p id="section-toc.1-1.8.2.2.1"><a href="#section-8.2" class="xref">8.2</a>. <a href="#name-mud-files-can-have-signatur" class="xref">MUD Files Can Have Signatures</a></p> |
| 1350 |
</li> |
| 1351 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.8.2.3"> |
| 1352 |
<p id="section-toc.1-1.8.2.3.1"><a href="#section-8.3" class="xref">8.3</a>. <a href="#name-url-shortening-services-can" class="xref">URL Shortening Services Can Change Content</a></p> |
| 1353 |
</li> |
| 1354 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.8.2.4"> |
| 1355 |
<p id="section-toc.1-1.8.2.4.1"><a href="#section-8.4" class="xref">8.4</a>. <a href="#name-mud-qr-code-stickers-could-" class="xref">MUD QR Code Stickers Could Be Confused</a></p> |
| 1356 |
</li> |
| 1357 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.8.2.5"> |
| 1358 |
<p id="section-toc.1-1.8.2.5.1"><a href="#section-8.5" class="xref">8.5</a>. <a href="#name-qr-code-can-include-a-mac-a" class="xref">QR Code Can Include a MAC Address</a></p> |
| 1359 |
</li> |
| 1360 |
</ul> |
| 1361 |
</li> |
| 1362 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.9"> |
| 1363 |
<p id="section-toc.1-1.9.1"><a href="#section-9" class="xref">9</a>. <a href="#name-iana-considerations" class="xref">IANA Considerations</a></p> |
| 1364 |
</li> |
| 1365 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.10"> |
| 1366 |
<p id="section-toc.1-1.10.1"><a href="#section-10" class="xref">10</a>. <a href="#name-references" class="xref">References</a></p> |
| 1367 |
<ul class="compact toc ulBare ulEmpty"> |
| 1368 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.10.2.1"> |
| 1369 |
<p id="section-toc.1-1.10.2.1.1"><a href="#section-10.1" class="xref">10.1</a>. <a href="#name-normative-references" class="xref">Normative References</a></p> |
| 1370 |
</li> |
| 1371 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.10.2.2"> |
| 1372 |
<p id="section-toc.1-1.10.2.2.1"><a href="#section-10.2" class="xref">10.2</a>. <a href="#name-informative-references" class="xref">Informative References</a></p> |
| 1373 |
</li> |
| 1374 |
</ul> |
| 1375 |
</li> |
| 1376 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.11"> |
| 1377 |
<p id="section-toc.1-1.11.1"><a href="#appendix-A" class="xref"></a><a href="#name-acknowledgements" class="xref">Acknowledgements</a></p> |
| 1378 |
</li> |
| 1379 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.12"> |
| 1380 |
<p id="section-toc.1-1.12.1"><a href="#appendix-B" class="xref"></a><a href="#name-authors-addresses" class="xref">Authors' Addresses</a></p> |
| 1381 |
</li> |
| 1382 |
</ul> |
| 1383 |
</nav> |
| 1384 |
</section> |
| 1385 |
</div> |
| 1386 |
<div id="introduction"> |
| 1387 |
<section id="section-1"> |
| 1388 |
<h2 id="name-introduction"> |
| 1389 |
<a href="#section-1" class="section-number selfRef">1. </a><a href="#name-introduction" class="section-name selfRef">Introduction</a> |
| 1390 |
</h2> |
| 1391 |
<p id="section-1-1">The Manufacturer Usage Description (MUD) <span>[<a href="#RFC8520" class="xref">RFC8520</a>]</span> defines a YANG data model to express what sort of access a device requires to operate correctly. |
| 1392 |
That document additionally defines three ways for the device to |
| 1393 |
communicate the MUD URL (i.e., the URL of the resulting MUD file in JSON <span>[<a href="#RFC8259" class="xref">RFC8259</a>]</span>) to a network enforcement point: via DHCP, within an X.509 certificate extension, and via the Link Local Discovery Protocol (LLDP).<a href="#section-1-1" class="pilcrow">¶</a></p> |
| 1394 |
<p id="section-1-2">Each of the above mechanisms conveys the MUD URL in band and requires modifications to the device firmware. |
| 1395 |
Most small Internet of Things (IoT) devices do not have LLDP and often have very restricted DHCP clients. |
| 1396 |
Adding LLDP or DHCP options requires at least some minimal configuration change and possibly entirely new subsystems. |
| 1397 |
Meanwhile, use of the PKIX certification extension only makes sense as part of a larger deployment based on an Initial Device Identifier (IDevID) <span>[<a href="#IEEE802-1AR" class="xref">IEEE802-1AR</a>]</span>, for instance, as described in <span>[<a href="#RFC8995" class="xref">RFC8995</a>]</span>.<a href="#section-1-2" class="pilcrow">¶</a></p> |
| 1398 |
<p id="section-1-3">In the above cases, these mechanisms can only be implemented by persons with access to modify and update the firmware of the device.<a href="#section-1-3" class="pilcrow">¶</a></p> |
| 1399 |
<p id="section-1-4">In the meantime, there is a chicken or egg problem <span>[<a href="#chickenegg" class="xref">chickenegg</a>]</span>. That is, manufacturers are not motivated to (and thus likely do not) include MUD URLs in their products, as they believe that there are no gateways using those URLs. |
| 1400 |
At the same time, gateways have little incentive to (and thus likely do not) include code that processes MUD URLs, as it is believed that no products have or disseminate URLs.<a href="#section-1-4" class="pilcrow">¶</a></p> |
| 1401 |
<p id="section-1-5">The protocol described in this document allows any person with physical access to the device to affix a reference to a MUD URL that can later be scanned by an end user.<a href="#section-1-5" class="pilcrow">¶</a></p> |
| 1402 |
<p id="section-1-6">The QR-based protocol is presented as a convenient alternative when the mechanisms from <span>[<a href="#RFC8520" class="xref">RFC8520</a>]</span> are not available to use on the device or the gateway.<a href="#section-1-6" class="pilcrow">¶</a></p> |
| 1403 |
<p id="section-1-7">Affixing a sticker can be done by:<a href="#section-1-7" class="pilcrow">¶</a></p> |
| 1404 |
<ul class="normal"> |
| 1405 |
<li class="normal" id="section-1-8.1">the marketing department of the manufacturer,<a href="#section-1-8.1" class="pilcrow">¶</a> |
| 1406 |
</li> |
| 1407 |
<li class="normal" id="section-1-8.2">an outsourced assembler plant,<a href="#section-1-8.2" class="pilcrow">¶</a> |
| 1408 |
</li> |
| 1409 |
<li class="normal" id="section-1-8.3">value-added resellers (perhaps in response to a local request for proposal (RFP)),<a href="#section-1-8.3" class="pilcrow">¶</a> |
| 1410 |
</li> |
| 1411 |
<li class="normal" id="section-1-8.4">a company importing the product (possibly to comply with a local regulation),<a href="#section-1-8.4" class="pilcrow">¶</a> |
| 1412 |
</li> |
| 1413 |
<li class="normal" id="section-1-8.5">a network administrator (perhaps before sending devices home with employees or to remote sites), and<a href="#section-1-8.5" class="pilcrow">¶</a> |
| 1414 |
</li> |
| 1415 |
<li class="normal" id="section-1-8.6">a retailer as a value-added service.<a href="#section-1-8.6" class="pilcrow">¶</a> |
| 1416 |
</li> |
| 1417 |
</ul> |
| 1418 |
<p id="section-1-9">QR codes are informally described in <span>[<a href="#qrcode" class="xref">qrcode</a>]</span> and formally defined in <span>[<a href="#isoiec18004" class="xref">isoiec18004</a>]</span>. |
| 1419 |
The protocol described in this document uses a QR code to encode the MUD URL. Specifically, the protocol leverages the data format from the Reverse Logistics Association's Standardized Quick Response for Logistics <span>[<a href="#SQRL" class="xref">SQRL</a>]</span>.<a href="#section-1-9" class="pilcrow">¶</a></p> |
| 1420 |
<p id="section-1-10">SQRL codes are being put on devices via a sticker or via laser etching into the case in order to deal with many situations but specifically for end-of-life processing for the device. |
| 1421 |
An important idea behind the effort is that clearly identifying a product permits appropriate disposal, refurbishment, or recycling of the components of the product.<a href="#section-1-10" class="pilcrow">¶</a></p> |
| 1422 |
<p id="section-1-11">There are also use cases for SQRL in which the codes are used as part of regular maintenance for a product.<a href="#section-1-11" class="pilcrow">¶</a></p> |
| 1423 |
<p id="section-1-12">SQRL is an application of the 12N Data Identifier system specified by the ANSI MH10.8.2 Committee <span>[<a href="#mh10" class="xref">mh10</a>]</span> in a format appropriate for QR codes, as well as other things like Normalization Form C (NFC) transmissions.<a href="#section-1-12" class="pilcrow">¶</a></p> |
| 1424 |
<p id="section-1-13">QR code generators are available as web services |
| 1425 |
or as programs, such as <span>[<a href="#qrencode" class="xref">qrencode</a>]</span>.<a href="#section-1-13" class="pilcrow">¶</a></p> |
| 1426 |
<p id="section-1-14"><a href="#genericfirmware" class="xref">Section 5</a> summarizes the considerations contained in "Updating files vs Updating MUD URLs" (<span><a href="https://datatracker.ietf.org/doc/html/draft-ietf-opsawg-mud-acceptable-urls-04#section-7.1" class="relref">Section 7.1</a> of [<a href="#I-D.ietf-opsawg-mud-acceptable-urls" class="xref">MUD-URLS</a>]</span>). |
| 1427 |
Due to the immutable nature of the QR code, MUD URLs in this document will need to |
| 1428 |
be non-firmware specific.<a href="#section-1-14" class="pilcrow">¶</a></p> |
| 1429 |
</section> |
| 1430 |
</div> |
| 1431 |
<div id="Terminology"> |
| 1432 |
<section id="section-2"> |
| 1433 |
<h2 id="name-terminology"> |
| 1434 |
<a href="#section-2" class="section-number selfRef">2. </a><a href="#name-terminology" class="section-name selfRef">Terminology</a> |
| 1435 |
</h2> |
| 1436 |
<p id="section-2-1">Although this document is not an IETF Standards Track publication, it |
| 1437 |
adopts the conventions for normative language to provide clarity of |
| 1438 |
instructions to the implementer. |
| 1439 |
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>", |
| 1440 |
"<span class="bcp14">MAY</span>", and "<span class="bcp14">OPTIONAL</span>" in this document are to be interpreted as |
| 1441 |
described in BCP 14 <span>[<a href="#RFC2119" class="xref">RFC2119</a>]</span> <span>[<a href="#RFC8174" class="xref">RFC8174</a>]</span> |
| 1442 |
when, and only when, they appear in all capitals, as shown here.<a href="#section-2-1" class="pilcrow">¶</a></p> |
| 1443 |
<p id="section-2-2">Readers should be familiar with the terminology in <span>[<a href="#RFC8520" class="xref">RFC8520</a>]</span>, including: MUD file, MUD URL, manufacturer, MUD manager, and controller.<a href="#section-2-2" class="pilcrow">¶</a></p> |
| 1444 |
</section> |
| 1445 |
</div> |
| 1446 |
<div id="protocol"> |
| 1447 |
<section id="section-3"> |
| 1448 |
<h2 id="name-protocol"> |
| 1449 |
<a href="#section-3" class="section-number selfRef">3. </a><a href="#name-protocol" class="section-name selfRef">Protocol</a> |
| 1450 |
</h2> |
| 1451 |
<p id="section-3-1">The QR code protocol builds upon the work by <span>[<a href="#SQRL" class="xref">SQRL</a>]</span>. |
| 1452 |
That protocol is very briefly described in <a href="#sqrlsummary" class="xref">Section 3.1</a>. |
| 1453 |
Then, the list of needed Data Records to be filled in is explained.<a href="#section-3-1" class="pilcrow">¶</a></p> |
| 1454 |
<div id="sqrlsummary"> |
| 1455 |
<section id="section-3.1"> |
| 1456 |
<h3 id="name-the-sqrl-protocol"> |
| 1457 |
<a href="#section-3.1" class="section-number selfRef">3.1. </a><a href="#name-the-sqrl-protocol" class="section-name selfRef">The SQRL Protocol</a> |
| 1458 |
</h3> |
| 1459 |
<p id="section-3.1-1"><span>[<a href="#SQRL" class="xref">SQRL</a>]</span> documents an octet protocol that can be efficiently encoded into QR codes using a sequence of US-ASCII bytes, plus six control codes (see Section 3.1 of <span>[<a href="#SQRL" class="xref">SQRL</a>]</span>):<a href="#section-3.1-1" class="pilcrow">¶</a></p> |
| 1460 |
<ul class="normal"> |
| 1461 |
<li class="normal" id="section-3.1-2.1"><RS> Record Separator (US-ASCII 30)<a href="#section-3.1-2.1" class="pilcrow">¶</a> |
| 1462 |
</li> |
| 1463 |
<li class="normal" id="section-3.1-2.2"><EoT> End of Transmission (US-ASCII 4)<a href="#section-3.1-2.2" class="pilcrow">¶</a> |
| 1464 |
</li> |
| 1465 |
<li class="normal" id="section-3.1-2.3"><FS> Field Separator (US-ASCII 28)<a href="#section-3.1-2.3" class="pilcrow">¶</a> |
| 1466 |
</li> |
| 1467 |
<li class="normal" id="section-3.1-2.4"><GS> Group Separator (US-ASCII 29)<a href="#section-3.1-2.4" class="pilcrow">¶</a> |
| 1468 |
</li> |
| 1469 |
<li class="normal" id="section-3.1-2.5"><US> Unit Separator (US-ASCII 31)<a href="#section-3.1-2.5" class="pilcrow">¶</a> |
| 1470 |
</li> |
| 1471 |
<li class="normal" id="section-3.1-2.6">Concatenation Operator (US-ASCII 43: "+")<a href="#section-3.1-2.6" class="pilcrow">¶</a> |
| 1472 |
</li> |
| 1473 |
</ul> |
| 1474 |
<p id="section-3.1-3">Section 7.2 of <span>[<a href="#SQRL" class="xref">SQRL</a>]</span> gives the details, which can be summarized as:<a href="#section-3.1-3" class="pilcrow">¶</a></p> |
| 1475 |
<ol start="1" type="1" class="normal type-1" id="section-3.1-4"> |
| 1476 |
<li id="section-3.1-4.1"> |
| 1477 |
<p id="section-3.1-4.1.1">The QR code header starts with:<a href="#section-3.1-4.1.1" class="pilcrow">¶</a></p> |
| 1478 |
<div class="alignLeft art-text artwork" id="section-3.1-4.1.2"> |
| 1479 |
<pre> |
| 1480 |
"[)>" <RS> "06" <GS> "12N" |
| 1481 |
</pre><a href="#section-3.1-4.1.2" class="pilcrow">¶</a> |
| 1482 |
</div> |
| 1483 |
</li> |
| 1484 |
<li id="section-3.1-4.2">Include one or more Data Records. This consists of a four-letter Field Identifier, followed by US-ASCII characters terminated with a <Unit Separator>.<a href="#section-3.1-4.2" class="pilcrow">¶</a> |
| 1485 |
</li> |
| 1486 |
<li id="section-3.1-4.3"> |
| 1487 |
<p id="section-3.1-4.3.1">End with:<a href="#section-3.1-4.3.1" class="pilcrow">¶</a></p> |
| 1488 |
<div class="alignLeft art-text artwork" id="section-3.1-4.3.2"> |
| 1489 |
<pre> |
| 1490 |
<RS><EoT> |
| 1491 |
</pre><a href="#section-3.1-4.3.2" class="pilcrow">¶</a> |
| 1492 |
</div> |
| 1493 |
</li> |
| 1494 |
</ol> |
| 1495 |
<p id="section-3.1-5">Additionally, there are optional flags that may be present in every Data Record, as described in Section 7.4 of <span>[<a href="#SQRL" class="xref">SQRL</a>]</span>. |
| 1496 |
These flags have no bearing on MUD processing. |
| 1497 |
A parser that is only collecting MUD URLs will not need to parse those flags. |
| 1498 |
A general-purpose SQRL parser will need more complexity.<a href="#section-3.1-5" class="pilcrow">¶</a></p> |
| 1499 |
<p id="section-3.1-6">Field Separator characters are used in SQRL to signify the beginning of a new unit of data. |
| 1500 |
A MUD-specific parser that encounters a Field Separator and has not yet collected the right MUD information <span class="bcp14">MUST</span> ignore the characters collected so far and then restart.<a href="#section-3.1-6" class="pilcrow">¶</a></p> |
| 1501 |
<p id="section-3.1-7">Environment records, as described in Section 7.4 of <span>[<a href="#SQRL" class="xref">SQRL</a>]</span>, look and act exactly as fields, with a special Field Identifier. |
| 1502 |
They serve no purpose when looking for MUD information and <span class="bcp14">MAY</span> be ignored.<a href="#section-3.1-7" class="pilcrow">¶</a></p> |
| 1503 |
</section> |
| 1504 |
</div> |
| 1505 |
<div id="manufacturer-usage-descriptions-in-sqrl"> |
| 1506 |
<section id="section-3.2"> |
| 1507 |
<h3 id="name-manufacturer-usage-descript"> |
| 1508 |
<a href="#section-3.2" class="section-number selfRef">3.2. </a><a href="#name-manufacturer-usage-descript" class="section-name selfRef">Manufacturer Usage Descriptions in SQRL</a> |
| 1509 |
</h3> |
| 1510 |
<div id="b000-company-name"> |
| 1511 |
<section id="section-3.2.1"> |
| 1512 |
<h4 id="name-b000-company-name"> |
| 1513 |
<a href="#section-3.2.1" class="section-number selfRef">3.2.1. </a><a href="#name-b000-company-name" class="section-name selfRef">B000 Company Name</a> |
| 1514 |
</h4> |
| 1515 |
<p id="section-3.2.1-1">The B000 Data Record is mandatory in <span>[<a href="#SQRL" class="xref">SQRL</a>]</span>. |
| 1516 |
It <span class="bcp14">MUST</span> be in US-ASCII representation. |
| 1517 |
It should be a representation of the company or brand name. |
| 1518 |
It <span class="bcp14">SHOULD</span> match the ietf-mud/mud/mfg-name in the MUD file; however, the MUD file can contain arbitrary UTF-8 for this name, while the SQRL files are expected to be 7-bit US-ASCII.<a href="#section-3.2.1-1" class="pilcrow">¶</a></p> |
| 1519 |
</section> |
| 1520 |
</div> |
| 1521 |
<div id="b001-product-name"> |
| 1522 |
<section id="section-3.2.2"> |
| 1523 |
<h4 id="name-b001-product-name"> |
| 1524 |
<a href="#section-3.2.2" class="section-number selfRef">3.2.2. </a><a href="#name-b001-product-name" class="section-name selfRef">B001 Product Name</a> |
| 1525 |
</h4> |
| 1526 |
<p id="section-3.2.2-1">The B001 Data Record is optional in <span>[<a href="#SQRL" class="xref">SQRL</a>]</span>. |
| 1527 |
It is the Product Name in US-ASCII. |
| 1528 |
Its presence is <span class="bcp14">RECOMMENDED</span>. |
| 1529 |
Some third parties that create QR code stickers might not know the product name with 100% certainty and <span class="bcp14">MAY</span> prefer to omit this rather than create further confusion.<a href="#section-3.2.2-1" class="pilcrow">¶</a></p> |
| 1530 |
</section> |
| 1531 |
</div> |
| 1532 |
<div id="b002-model-number"> |
| 1533 |
<section id="section-3.2.3"> |
| 1534 |
<h4 id="name-b002-model-number"> |
| 1535 |
<a href="#section-3.2.3" class="section-number selfRef">3.2.3. </a><a href="#name-b002-model-number" class="section-name selfRef">B002 Model Number</a> |
| 1536 |
</h4> |
| 1537 |
<p id="section-3.2.3-1">The B002 Data Record is optional in <span>[<a href="#SQRL" class="xref">SQRL</a>]</span> but is MANDATORY in this profile. |
| 1538 |
It is the Model Name in US-ASCII. |
| 1539 |
It <span class="bcp14">SHOULD</span> match the optional ietf-mud/mud/model-name in the MUD file if that entry is present in the MUD file. MUD files can contain arbitrary UTF-8 for the model-name, while the SQRL files are expected to be 7-bit US-ASCII.<a href="#section-3.2.3-1" class="pilcrow">¶</a></p> |
| 1540 |
<p id="section-3.2.3-2">If a third party that is creating QR codes cannot locate an official model number when creating their MUD file and QR code, then the third party <span class="bcp14">SHOULD</span> make one up.<a href="#section-3.2.3-2" class="pilcrow">¶</a></p> |
| 1541 |
</section> |
| 1542 |
</div> |
| 1543 |
<div id="mudurl"> |
| 1544 |
<section id="section-3.2.4"> |
| 1545 |
<h4 id="name-mud-url-data-record"> |
| 1546 |
<a href="#section-3.2.4" class="section-number selfRef">3.2.4. </a><a href="#name-mud-url-data-record" class="section-name selfRef">MUD URL Data Record</a> |
| 1547 |
</h4> |
| 1548 |
<p id="section-3.2.4-1">A new Field Identifier has been assigned by the Reverse Logistics Association, which is "M180". |
| 1549 |
This record <span class="bcp14">MUST</span> be filled with the MUD URL.<a href="#section-3.2.4-1" class="pilcrow">¶</a></p> |
| 1550 |
<p id="section-3.2.4-2">Short URLs are easier to encode into a QR code because they require fewer pixels of |
| 1551 |
QR code. |
| 1552 |
More content in the QR code requires a bigger image.<a href="#section-3.2.4-2" class="pilcrow">¶</a></p> |
| 1553 |
<p id="section-3.2.4-3">Use of URL shortening services (see <span>[<a href="#URLshorten" class="xref">URLshorten</a>]</span>) can be useful, provided that the service is stable throughout the lifetime of the device and QR code and that the privacy stance of the service is well understood. |
| 1554 |
The Security Considerations section of <span>[<a href="#RFC3986" class="xref">RFC3986</a>]</span> applies, particularly Section <a href="https://www.rfc-editor.org/rfc/rfc3986#section-7.1" class="relref">7.1</a>.<a href="#section-3.2.4-3" class="pilcrow">¶</a></p> |
| 1555 |
<p id="section-3.2.4-4">Section 8.1 of <span>[<a href="#SQRL" class="xref">SQRL</a>]</span> also has some good advice on longevity concerns with URLs.<a href="#section-3.2.4-4" class="pilcrow">¶</a></p> |
| 1556 |
<p id="section-3.2.4-5">The URL provided <span class="bcp14">MUST NOT</span> have a query (?) portion present. |
| 1557 |
If one is present, the query portion <span class="bcp14">MUST</span> be removed before processing.<a href="#section-3.2.4-5" class="pilcrow">¶</a></p> |
| 1558 |
</section> |
| 1559 |
</div> |
| 1560 |
<div id="macaddress"> |
| 1561 |
<section id="section-3.2.5"> |
| 1562 |
<h4 id="name-device-mac-address"> |
| 1563 |
<a href="#section-3.2.5" class="section-number selfRef">3.2.5. </a><a href="#name-device-mac-address" class="section-name selfRef">Device MAC Address</a> |
| 1564 |
</h4> |
| 1565 |
<p id="section-3.2.5-1">If a Media Access Control (MAC) address is used as a unique device identifier (which is <span class="bcp14">RECOMMENDED</span> if possible), then it <span class="bcp14">MUST</span> be included in this Data Record.<a href="#section-3.2.5-1" class="pilcrow">¶</a></p> |
| 1566 |
<p id="section-3.2.5-2">Section 9.10 of <span>[<a href="#SQRL" class="xref">SQRL</a>]</span> defines the Data Record "M06C" as the MAC address. |
| 1567 |
No format for the MAC address is provided in that document.<a href="#section-3.2.5-2" class="pilcrow">¶</a></p> |
| 1568 |
<p id="section-3.2.5-3">In this document, it is <span class="bcp14">RECOMMENDED</span> that 12 (or 16) hex octets are used with no spaces or punctuation. |
| 1569 |
(16 octets are used in the IEEE 64-bit Extended Unique Identifier (EUI-64) format used in <span>[<a href="#IEEE.802.15.4" class="xref">IEEE.802.15.4</a>]</span> and some next generation Ethernet proposals). |
| 1570 |
In this document, it is <span class="bcp14">RECOMMENDED</span> that uppercase hexadecimal letters be used.<a href="#section-3.2.5-3" class="pilcrow">¶</a></p> |
| 1571 |
<p id="section-3.2.5-4">Parsers that find punctuation (such as colons (":"), dashes ("-"), US-ASCII Space (32), US-ASCII TAB (0), US-ASCII linefeed (10), or US-ASCII |
| 1572 |
carriage return (13)) <span class="bcp14">MUST</span> |
| 1573 |
skip over the punctuation. |
| 1574 |
Parsers <span class="bcp14">MUST</span> tolerate hexadecimal in uppercase, lowercase, and even mixed case. Systems <span class="bcp14">SHOULD</span> canonicalize it to uppercase.<a href="#section-3.2.5-4" class="pilcrow">¶</a></p> |
| 1575 |
</section> |
| 1576 |
</div> |
| 1577 |
</section> |
| 1578 |
</div> |
| 1579 |
</section> |
| 1580 |
</div> |
| 1581 |
<div id="applicability"> |
| 1582 |
<section id="section-4"> |
| 1583 |
<h2 id="name-applicability"> |
| 1584 |
<a href="#section-4" class="section-number selfRef">4. </a><a href="#name-applicability" class="section-name selfRef">Applicability</a> |
| 1585 |
</h2> |
| 1586 |
<p id="section-4-1">The use of stickers to convey MUD URLs would appear to have little value when the stickers are applied by the end-user organization and consumed by the same. |
| 1587 |
This is particularly the case when the QR code does not include the device MAC address. |
| 1588 |
In such a situation, the installer handling the device would scan the QR code to get the appropriate MUD file reference and have to input the associated MAC address as well.<a href="#section-4-1" class="pilcrow">¶</a></p> |
| 1589 |
<p id="section-4-2">In such a case, one might wonder why the installer couldn't just enter the appropriate MAC address and select the appropriate Access Control Lists (ACLs) for the device. Then a MUD file or QR code to convey the MAC |
| 1590 |
address would not be needed. However, the use of a MUD file (or |
| 1591 |
QR code or other way to convey the MAC address) is advantageous |
| 1592 |
because it offers several layers of indirection:<a href="#section-4-2" class="pilcrow">¶</a></p> |
| 1593 |
<ol start="1" type="1" class="normal type-1" id="section-4-3"> |
| 1594 |
<li id="section-4-3.1">The ACLs for a given device may be added or removed.<a href="#section-4-3.1" class="pilcrow">¶</a> |
| 1595 |
</li> |
| 1596 |
<li id="section-4-3.2">The ACLs may refer to DNS names, which may map to IPv4 or IPv6 addresses.<a href="#section-4-3.2" class="pilcrow">¶</a> |
| 1597 |
</li> |
| 1598 |
<li id="section-4-3.3">The entire file may be replaced and may also include supply chain information, such as Software Bill of Materials (SBOM).<a href="#section-4-3.3" class="pilcrow">¶</a> |
| 1599 |
</li> |
| 1600 |
</ol> |
| 1601 |
<p id="section-4-4">In addition, the mechanism to install a new device (MAC address) to MUD file mapping does not need to permit any other network security settings to be alterable by the person doing the installation.<a href="#section-4-4" class="pilcrow">¶</a></p> |
| 1602 |
</section> |
| 1603 |
</div> |
| 1604 |
<div id="genericfirmware"> |
| 1605 |
<section id="section-5"> |
| 1606 |
<h2 id="name-generic-url-or-version-spec"> |
| 1607 |
<a href="#section-5" class="section-number selfRef">5. </a><a href="#name-generic-url-or-version-spec" class="section-name selfRef">Generic URL or Version-Specific URL</a> |
| 1608 |
</h2> |
| 1609 |
<p id="section-5-1">MUD URLs that are communicated in band by the device and that are programmed into the device's firmware may provide a firmware-specific version of the MUD URL. The advantage of this is that the resulting ACLs enforced in the network are specific to the needs of that version of the firmware.<a href="#section-5-1" class="pilcrow">¶</a></p> |
| 1610 |
<p id="section-5-2">A MUD URL that is affixed to the device with a sticker or etched into the case cannot be changed.<a href="#section-5-2" class="pilcrow">¶</a></p> |
| 1611 |
<p id="section-5-3">Given the considerations of "Updating MUD URLs vs Updating MUD files" (<span><a href="https://datatracker.ietf.org/doc/html/draft-ietf-opsawg-mud-acceptable-urls-04#section-6.1" class="relref">Section 6.1</a> of [<a href="#I-D.ietf-opsawg-mud-acceptable-urls" class="xref">MUD-URLS</a>]</span>), it is prudent to use a MUD URL that points to a MUD file that will only have new features added over time and never have features removed. |
| 1612 |
To recap, if a feature is removed from the firmware and the MUD file still permits it, then there is a potential hole that could perhaps be exploited. |
| 1613 |
The opposite situation, where a MUD file wrongly forbids something, leads to false positives in the security system, and the evidence is that this results in the entire system being ignored. |
| 1614 |
Preventing attacks on core infrastructure may be more important than getting the ACL perfect.<a href="#section-5-3" class="pilcrow">¶</a></p> |
| 1615 |
<p id="section-5-4">When the firmware eventually receives built-in MUD URL support, then a more-specific URL may be used.<a href="#section-5-4" class="pilcrow">¶</a></p> |
| 1616 |
<p id="section-5-5">Note that in many cases, it will be third parties who are generating these QR codes, so the MUD file may be hosted by the third party.<a href="#section-5-5" class="pilcrow">¶</a></p> |
| 1617 |
</section> |
| 1618 |
</div> |
| 1619 |
<div id="crowd-supply-of-mud-files"> |
| 1620 |
<section id="section-6"> |
| 1621 |
<h2 id="name-crowd-supply-of-mud-files"> |
| 1622 |
<a href="#section-6" class="section-number selfRef">6. </a><a href="#name-crowd-supply-of-mud-files" class="section-name selfRef">Crowd Supply of MUD Files</a> |
| 1623 |
</h2> |
| 1624 |
<p id="section-6-1">At the time of writing, the IETF MUD is a new IETF Proposed Standard. |
| 1625 |
Hence, IoT device manufacturers have not yet provided MUD profiles for their devices. |
| 1626 |
A research group at the University of New South Wales (UNSW Sydney) has developed an open-source tool, called MUDgee <span>[<a href="#MUDgee" class="xref">MUDgee</a>]</span>, which automatically generates a MUD file (profile) for an IoT device from its traffic trace in order to make this process faster, easier, and more accurate. |
| 1627 |
Note that the generated profile completeness solely depends on the completeness of the input traffic traces. |
| 1628 |
MUDgee assumes that all the activity seen is intended and benign.<a href="#section-6-1" class="pilcrow">¶</a></p> |
| 1629 |
<p id="section-6-2">UNSW researchers have applied MUDgee to about 30 consumer IoT devices from their lab testbed and publicly released their MUD files <span>[<a href="#MUDfiles" class="xref">MUDfiles</a>]</span>. |
| 1630 |
MUDgee can assist IoT manufacturers in developing and verifying MUD profiles, while also helping adopters of these devices to ensure they are compatible with their organizational policies.<a href="#section-6-2" class="pilcrow">¶</a></p> |
| 1631 |
<p id="section-6-3">Similar processes have been done in a number of other public and private labs. |
| 1632 |
One of the strong motivations for this specification is to allow for this work to leave the lab and to be applied in the field.<a href="#section-6-3" class="pilcrow">¶</a></p> |
| 1633 |
</section> |
| 1634 |
</div> |
| 1635 |
<div id="privacy-considerations"> |
| 1636 |
<section id="section-7"> |
| 1637 |
<h2 id="name-privacy-considerations"> |
| 1638 |
<a href="#section-7" class="section-number selfRef">7. </a><a href="#name-privacy-considerations" class="section-name selfRef">Privacy Considerations</a> |
| 1639 |
</h2> |
| 1640 |
<p id="section-7-1">The presence of the MUD URL in the QR code reveals the manufacturer of the device, the type or model of the device, and possibly the firmware version of the device.<a href="#section-7-1" class="pilcrow">¶</a></p> |
| 1641 |
<p id="section-7-2">The MAC address of the device will also need to be present, and this is potentially Personally Identifiable Information (PII). |
| 1642 |
Such QR codes should not be placed on the outside of the packaging and only on the device itself, ideally on a non-prominent part of the device (e.g., the bottom).<a href="#section-7-2" class="pilcrow">¶</a></p> |
| 1643 |
<p id="section-7-3">The QR code sticker should not be placed on any part of the device that might become visible to machine vision systems in the same area. |
| 1644 |
This includes security systems, robotic vacuum cleaners, or anyone taking a picture with a camera. |
| 1645 |
Such systems may store the picture(s) in such a way that a future viewer of the image will be able to decode the QR code, possibly through an assembly of multiple pictures. |
| 1646 |
Of course, the QR code is not, however, a certain indicator that the device is present, only that the QR code sticker that came with the device is present.<a href="#section-7-3" class="pilcrow">¶</a></p> |
| 1647 |
<p id="section-7-4">The use of URL shorting services discussed in <a href="#mudurl" class="xref">Section 3.2.4</a> may result in trading convenience and efficiency with privacy, since the service provider might leverage per-device or per-customer, short URLs to track and correlate requests.<a href="#section-7-4" class="pilcrow">¶</a></p> |
| 1648 |
</section> |
| 1649 |
</div> |
| 1650 |
<div id="security-considerations"> |
| 1651 |
<section id="section-8"> |
| 1652 |
<h2 id="name-security-considerations"> |
| 1653 |
<a href="#section-8" class="section-number selfRef">8. </a><a href="#name-security-considerations" class="section-name selfRef">Security Considerations</a> |
| 1654 |
</h2> |
| 1655 |
<div id="qr-codes-are-not-assurances"> |
| 1656 |
<section id="section-8.1"> |
| 1657 |
<h3 id="name-qr-codes-are-not-assurances"> |
| 1658 |
<a href="#section-8.1" class="section-number selfRef">8.1. </a><a href="#name-qr-codes-are-not-assurances" class="section-name selfRef">QR Codes Are Not Assurances</a> |
| 1659 |
</h3> |
| 1660 |
<p id="section-8.1-1">The mere presence of a QR code on a device does not in itself create any security issues on its own. |
| 1661 |
Neither an attached paper sticker nor a laser-etched code in a plastic case will affect the device operation.<a href="#section-8.1-1" class="pilcrow">¶</a></p> |
| 1662 |
<p id="section-8.1-2">The QR code is not active; in general, it is not able to communicate using nearby networks. |
| 1663 |
It is conceivable that something more active is concealed in the sticker, e.g., an NFC or a Radio Frequency Identification (RFID) tag. |
| 1664 |
But, any sticker could contain such a thing, e.g., on some university campuses, stickers are often used as part of political campaigns and can be found attached all over the place.<a href="#section-8.1-2" class="pilcrow">¶</a></p> |
| 1665 |
<p id="section-8.1-3">Security issues that this protocol creates are related to assumptions that the presence of the QR code might imply. |
| 1666 |
The presence of the QR code may imply to some owners or network operators that the behavior of the device has been vetted by some authority. |
| 1667 |
It is here that some caution is required.<a href="#section-8.1-3" class="pilcrow">¶</a></p> |
| 1668 |
<p id="section-8.1-4">A possibly bigger risk from application of MUD file stickers to devices is that they may begin to convey a sense of safety to users of the device. |
| 1669 |
The presence of the sticker, possibly with the logo of the physical establishment in which the device is located, could convey to occupants of the establishment that this device is an official device, |
| 1670 |
for instance, a university that only deploys sensors on the university campus that have been vetted for compliance against a MUD definition.<a href="#section-8.1-4" class="pilcrow">¶</a></p> |
| 1671 |
<p id="section-8.1-5">The risk is then of social engineering, e.g., any device with a reasonable-looking QR code may be seen as a trusted device (even though such trust is not justified based on that evidence). |
| 1672 |
An attacker that wishes to infiltrate their own devices need only suitably camouflage the device with an appropriate sticker in order to convey legitimacy.<a href="#section-8.1-5" class="pilcrow">¶</a></p> |
| 1673 |
</section> |
| 1674 |
</div> |
| 1675 |
<div id="mud-files-can-have-signatures"> |
| 1676 |
<section id="section-8.2"> |
| 1677 |
<h3 id="name-mud-files-can-have-signatur"> |
| 1678 |
<a href="#section-8.2" class="section-number selfRef">8.2. </a><a href="#name-mud-files-can-have-signatur" class="section-name selfRef">MUD Files Can Have Signatures</a> |
| 1679 |
</h3> |
| 1680 |
<p id="section-8.2-1">The network operator who takes the MUD file designated by the QR code needs to be careful that they are validating the signature on the MUD file. |
| 1681 |
The network operator needs to verify that the file is intact and |
| 1682 |
that the signer of the file is authorized to sign MUD files |
| 1683 |
for that vendor, or if a MUD file is a crowd-sourced definition, |
| 1684 |
they need to establish if it can be trusted. |
| 1685 |
<span>[<a href="#RFC8520" class="xref">RFC8520</a>]</span> does not define any infrastructure to authenticate or authorize MUD file signers.<a href="#section-8.2-1" class="pilcrow">¶</a></p> |
| 1686 |
</section> |
| 1687 |
</div> |
| 1688 |
<div id="url-shortening-services-can-change-content"> |
| 1689 |
<section id="section-8.3"> |
| 1690 |
<h3 id="name-url-shortening-services-can"> |
| 1691 |
<a href="#section-8.3" class="section-number selfRef">8.3. </a><a href="#name-url-shortening-services-can" class="section-name selfRef">URL Shortening Services Can Change Content</a> |
| 1692 |
</h3> |
| 1693 |
<p id="section-8.3-1">If a URL shortening service is used, it is possible that the MUD controller will be redirected to another MUD file with different content. |
| 1694 |
The use of MUD signatures can detect attacks on the integrity of the file. |
| 1695 |
To do this, the MUD controller needs to be able to verify the signature on the file.<a href="#section-8.3-1" class="pilcrow">¶</a></p> |
| 1696 |
<p id="section-8.3-2">If a Trust-On-First-Use (TOFU) policy is used for signature trust anchors, then the URL shortening service can still attack if it substitutes content and signature on the first use. |
| 1697 |
MUD controllers and the people operating them need to be cautious when using TOFU.<a href="#section-8.3-2" class="pilcrow">¶</a></p> |
| 1698 |
</section> |
| 1699 |
</div> |
| 1700 |
<div id="mud-qr-code-stickers-could-be-confused"> |
| 1701 |
<section id="section-8.4"> |
| 1702 |
<h3 id="name-mud-qr-code-stickers-could-"> |
| 1703 |
<a href="#section-8.4" class="section-number selfRef">8.4. </a><a href="#name-mud-qr-code-stickers-could-" class="section-name selfRef">MUD QR Code Stickers Could Be Confused</a> |
| 1704 |
</h3> |
| 1705 |
<p id="section-8.4-1">Another issue with the stickers is that the wrong sticker could be applied to a device by a reseller or another trusted party, either in error or via some physical or socially engineered attack against that party. |
| 1706 |
The network operator now onboards a device and applies what they think is a legitimate network policy for the device in their hands, only it is in fact a policy for another kind of device.<a href="#section-8.4-1" class="pilcrow">¶</a></p> |
| 1707 |
<p id="section-8.4-2">Careful examination of stickers is in order!<a href="#section-8.4-2" class="pilcrow">¶</a></p> |
| 1708 |
</section> |
| 1709 |
</div> |
| 1710 |
<div id="qr-code-can-include-mac-address"> |
| 1711 |
<section id="section-8.5"> |
| 1712 |
<h3 id="name-qr-code-can-include-a-mac-a"> |
| 1713 |
<a href="#section-8.5" class="section-number selfRef">8.5. </a><a href="#name-qr-code-can-include-a-mac-a" class="section-name selfRef">QR Code Can Include a MAC Address</a> |
| 1714 |
</h3> |
| 1715 |
<p id="section-8.5-1">Inclusion of the device-specific MAC address (described in <a href="#macaddress" class="xref">Section 3.2.5</a>) in the QR code makes use of the MUD code much easier, as it identifies the device specifically. |
| 1716 |
If the MAC address is not included, then a network operator, having the device in their hands, has to associate the policy with the device through some other interface.<a href="#section-8.5-1" class="pilcrow">¶</a></p> |
| 1717 |
<p id="section-8.5-2">Despite the significant advantage of having the MAC address included, it is unlikely that third-party stickers will include it. |
| 1718 |
Including the MAC address requires that a unique sticker with a QR code be created for each device. |
| 1719 |
This is possible if the sticker is applied by a manufacturer; it is already common to have a serial number and MAC address on the outside of the device. |
| 1720 |
In that case, if the QR code is part of that sticker, then the customization problem is not that complex.<a href="#section-8.5-2" class="pilcrow">¶</a></p> |
| 1721 |
<p id="section-8.5-3">For cases where a third party has produced the QR code, it is likely that every device of a particular model will have the same QR code applied, omitting the MAC address. |
| 1722 |
This increases the possibility that the wrong policy will be applied to a device.<a href="#section-8.5-3" class="pilcrow">¶</a></p> |
| 1723 |
</section> |
| 1724 |
</div> |
| 1725 |
</section> |
| 1726 |
</div> |
| 1727 |
<div id="iana-considerations"> |
| 1728 |
<section id="section-9"> |
| 1729 |
<h2 id="name-iana-considerations"> |
| 1730 |
<a href="#section-9" class="section-number selfRef">9. </a><a href="#name-iana-considerations" class="section-name selfRef">IANA Considerations</a> |
| 1731 |
</h2> |
| 1732 |
<p id="section-9-1">This document has no IANA actions.<a href="#section-9-1" class="pilcrow">¶</a></p> |
| 1733 |
</section> |
| 1734 |
</div> |
| 1735 |
<section id="section-10"> |
| 1736 |
<h2 id="name-references"> |
| 1737 |
<a href="#section-10" class="section-number selfRef">10. </a><a href="#name-references" class="section-name selfRef">References</a> |
| 1738 |
</h2> |
| 1739 |
<section id="section-10.1"> |
| 1740 |
<h3 id="name-normative-references"> |
| 1741 |
<a href="#section-10.1" class="section-number selfRef">10.1. </a><a href="#name-normative-references" class="section-name selfRef">Normative References</a> |
| 1742 |
</h3> |
| 1743 |
<dl class="references"> |
| 1744 |
<dt id="RFC2119">[RFC2119]</dt> |
| 1745 |
<dd> |
| 1746 |
<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><<a href="https://www.rfc-editor.org/info/rfc2119">https://www.rfc-editor.org/info/rfc2119</a>></span>. </dd> |
| 1747 |
<dd class="break"></dd> |
| 1748 |
<dt id="RFC8174">[RFC8174]</dt> |
| 1749 |
<dd> |
| 1750 |
<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><<a href="https://www.rfc-editor.org/info/rfc8174">https://www.rfc-editor.org/info/rfc8174</a>></span>. </dd> |
| 1751 |
<dd class="break"></dd> |
| 1752 |
<dt id="RFC8520">[RFC8520]</dt> |
| 1753 |
<dd> |
| 1754 |
<span class="refAuthor">Lear, E.</span>, <span class="refAuthor">Droms, R.</span>, and <span class="refAuthor">D. Romascanu</span>, <span class="refTitle">"Manufacturer Usage Description Specification"</span>, <span class="seriesInfo">RFC 8520</span>, <span class="seriesInfo">DOI 10.17487/RFC8520</span>, <time datetime="2019-03" class="refDate">March 2019</time>, <span><<a href="https://www.rfc-editor.org/info/rfc8520">https://www.rfc-editor.org/info/rfc8520</a>></span>. </dd> |
| 1755 |
<dd class="break"></dd> |
| 1756 |
<dt id="SQRL">[SQRL]</dt> |
| 1757 |
<dd> |
| 1758 |
<span class="refAuthor">Reverse Logistics Association</span>, <span class="refTitle">"SQRL Codes: Standardized Quick Response for Logistics, Using the 12N Data Identifier"</span>, <time datetime="2017-02" class="refDate">February 2017</time>, <span><<a href="https://rla.org/resource/12n-documentation">https://rla.org/resource/12n-documentation</a>></span>. </dd> |
| 1759 |
<dd class="break"></dd> |
| 1760 |
</dl> |
| 1761 |
</section> |
| 1762 |
<section id="section-10.2"> |
| 1763 |
<h3 id="name-informative-references"> |
| 1764 |
<a href="#section-10.2" class="section-number selfRef">10.2. </a><a href="#name-informative-references" class="section-name selfRef">Informative References</a> |
| 1765 |
</h3> |
| 1766 |
<dl class="references"> |
| 1767 |
<dt id="chickenegg">[chickenegg]</dt> |
| 1768 |
<dd> |
| 1769 |
<span class="refAuthor">Wikipedia</span>, <span class="refTitle">"Chicken or the egg"</span>, <time datetime="2022-04" class="refDate">April 2022</time>, <span><<a href="https://en.wikipedia.org/w/index.php?title=Chicken_or_the_egg&oldid=1081728488">https://en.wikipedia.org/w/index.php?title=Chicken_or_the_egg&oldid=1081728488</a>></span>. </dd> |
| 1770 |
<dd class="break"></dd> |
| 1771 |
<dt id="IEEE.802.15.4">[IEEE.802.15.4]</dt> |
| 1772 |
<dd> |
| 1773 |
<span class="refAuthor">IEEE</span>, <span class="refTitle">"IEEE Standard for Low-Rate Wireless Networks"</span>, <span class="seriesInfo">IEEE Std. 802.15.4-2015</span>, <span class="seriesInfo">DOI 10.1109/IEEESTD.2016.7460875</span>, <time datetime="2016-04" class="refDate">April 2016</time>, <span><<a href="https://ieeexplore.ieee.org/document/7460875">https://ieeexplore.ieee.org/document/7460875</a>></span>. </dd> |
| 1774 |
<dd class="break"></dd> |
| 1775 |
<dt id="IEEE802-1AR">[IEEE802-1AR]</dt> |
| 1776 |
<dd> |
| 1777 |
<span class="refAuthor">IEEE</span>, <span class="refTitle">"IEEE Standard for Local and Metropolitan Area Networks - Secure Device Identity"</span>, <span class="seriesInfo">IEEE Std 802.1AR-2018</span>, <time datetime="2018-08" class="refDate">August 2018</time>, <span><<a href="https://standards.ieee.org/ieee/802.1AR/6995/">https://standards.ieee.org/ieee/802.1AR/6995/</a>></span>. </dd> |
| 1778 |
<dd class="break"></dd> |
| 1779 |
<dt id="isoiec18004">[isoiec18004]</dt> |
| 1780 |
<dd> |
| 1781 |
<span class="refAuthor">ISO/IEC</span>, <span class="refTitle">"Information technology - Automatic identification and data capture techniques - QR Code bar code symbology specification"</span>, <span class="seriesInfo">ISO/IEC 18004:2015</span>, <time datetime="2015-02" class="refDate">February 2015</time>. </dd> |
| 1782 |
<dd class="break"></dd> |
| 1783 |
<dt id="mh10">[mh10]</dt> |
| 1784 |
<dd> |
| 1785 |
<span class="refAuthor">ANSI</span>, <span class="refTitle">"Data Identifier and Application Identifier Standard"</span>, <span class="seriesInfo">ANSI MH10.8.2-2016</span>, <time datetime="2016-06" class="refDate">June 2016</time>, <span><<a href="https://webstore.ansi.org/Standards/MHIA/ANSIMH102016">https://webstore.ansi.org/Standards/MHIA/ANSIMH102016</a>></span>. </dd> |
| 1786 |
<dd class="break"></dd> |
| 1787 |
<dt id="I-D.ietf-opsawg-mud-acceptable-urls">[MUD-URLS]</dt> |
| 1788 |
<dd> |
| 1789 |
<span class="refAuthor">Richardson, M.</span>, <span class="refAuthor">Pan, W.</span>, and <span class="refAuthor">E. Lear</span>, <span class="refTitle">"Authorized update to MUD URLs"</span>, <span class="refContent">Work in Progress</span>, <span class="seriesInfo">Internet-Draft, draft-ietf-opsawg-mud-acceptable-urls-04</span>, <time datetime="2021-10-06" class="refDate">6 October 2021</time>, <span><<a href="https://datatracker.ietf.org/doc/html/draft-ietf-opsawg-mud-acceptable-urls-04">https://datatracker.ietf.org/doc/html/draft-ietf-opsawg-mud-acceptable-urls-04</a>></span>. </dd> |
| 1790 |
<dd class="break"></dd> |
| 1791 |
<dt id="MUDfiles">[MUDfiles]</dt> |
| 1792 |
<dd> |
| 1793 |
<span class="refAuthor">UNSW Sydney</span>, <span class="refTitle">"MUD Profiles"</span>, <span><<a href="https://iotanalytics.unsw.edu.au/mud/">https://iotanalytics.unsw.edu.au/mud/</a>></span>. </dd> |
| 1794 |
<dd class="break"></dd> |
| 1795 |
<dt id="MUDgee">[MUDgee]</dt> |
| 1796 |
<dd> |
| 1797 |
<span class="refTitle">"MUDgee"</span>, <span class="refContent">commit f63a88d</span>, <time datetime="2019-07" class="refDate">July 2019</time>, <span><<a href="https://github.com/ayyoob/mudgee">https://github.com/ayyoob/mudgee</a>></span>. </dd> |
| 1798 |
<dd class="break"></dd> |
| 1799 |
<dt id="qrcode">[qrcode]</dt> |
| 1800 |
<dd> |
| 1801 |
<span class="refAuthor">Wikipedia</span>, <span class="refTitle">"QR code"</span>, <time datetime="2022-04" class="refDate">April 2022</time>, <span><<a href="https://en.wikipedia.org/w/index.php?title=QR_code&oldid=1082559657">https://en.wikipedia.org/w/index.php?title=QR_code&oldid=1082559657</a>></span>. </dd> |
| 1802 |
<dd class="break"></dd> |
| 1803 |
<dt id="qrencode">[qrencode]</dt> |
| 1804 |
<dd> |
| 1805 |
<span class="refTitle">"libqrencode"</span>, <span class="refContent">commit 715e29f</span>, <time datetime="2020-09" class="refDate">September 2020</time>, <span><<a href="https://github.com/fukuchi/libqrencode">https://github.com/fukuchi/libqrencode</a>></span>. </dd> |
| 1806 |
<dd class="break"></dd> |
| 1807 |
<dt id="RFC3986">[RFC3986]</dt> |
| 1808 |
<dd> |
| 1809 |
<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><<a href="https://www.rfc-editor.org/info/rfc3986">https://www.rfc-editor.org/info/rfc3986</a>></span>. </dd> |
| 1810 |
<dd class="break"></dd> |
| 1811 |
<dt id="RFC8259">[RFC8259]</dt> |
| 1812 |
<dd> |
| 1813 |
<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><<a href="https://www.rfc-editor.org/info/rfc8259">https://www.rfc-editor.org/info/rfc8259</a>></span>. </dd> |
| 1814 |
<dd class="break"></dd> |
| 1815 |
<dt id="RFC8995">[RFC8995]</dt> |
| 1816 |
<dd> |
| 1817 |
<span class="refAuthor">Pritikin, M.</span>, <span class="refAuthor">Richardson, M.</span>, <span class="refAuthor">Eckert, T.</span>, <span class="refAuthor">Behringer, M.</span>, and <span class="refAuthor">K. Watsen</span>, <span class="refTitle">"Bootstrapping Remote Secure Key Infrastructure (BRSKI)"</span>, <span class="seriesInfo">RFC 8995</span>, <span class="seriesInfo">DOI 10.17487/RFC8995</span>, <time datetime="2021-05" class="refDate">May 2021</time>, <span><<a href="https://www.rfc-editor.org/info/rfc8995">https://www.rfc-editor.org/info/rfc8995</a>></span>. </dd> |
| 1818 |
<dd class="break"></dd> |
| 1819 |
<dt id="URLshorten">[URLshorten]</dt> |
| 1820 |
<dd> |
| 1821 |
<span class="refAuthor">Wikipedia</span>, <span class="refTitle">"URL shortening"</span>, <time datetime="2022-04" class="refDate">April 2022</time>, <span><<a href="https://en.wikipedia.org/w/index.php?title=URL_shorteningg&oldid=1084979184">https://en.wikipedia.org/w/index.php?title=URL_shorteningg&oldid=1084979184</a>></span>. </dd> |
| 1822 |
<dd class="break"></dd> |
| 1823 |
</dl> |
| 1824 |
</section> |
| 1825 |
</section> |
| 1826 |
<div id="acknowledgements"> |
| 1827 |
<section id="appendix-A"> |
| 1828 |
<h2 id="name-acknowledgements"> |
| 1829 |
<a href="#name-acknowledgements" class="section-name selfRef">Acknowledgements</a> |
| 1830 |
</h2> |
| 1831 |
<p id="appendix-A-1">This work was supported by the Canadian Internet Registration Authority (cira.ca).<a href="#appendix-A-1" class="pilcrow">¶</a></p> |
| 1832 |
</section> |
| 1833 |
</div> |
| 1834 |
<div id="authors-addresses"> |
| 1835 |
<section id="appendix-B"> |
| 1836 |
<h2 id="name-authors-addresses"> |
| 1837 |
<a href="#name-authors-addresses" class="section-name selfRef">Authors' Addresses</a> |
| 1838 |
</h2> |
| 1839 |
<address class="vcard"> |
| 1840 |
<div dir="auto" class="left"><span class="fn nameRole">Michael Richardson</span></div> |
| 1841 |
<div dir="auto" class="left"><span class="org">Sandelman Software Works</span></div> |
| 1842 |
<div class="email"> |
| 1843 |
<span>Email:</span> |
| 1844 |
<a href="mailto:[email protected]" class="email">[email protected]</a> |
| 1845 |
</div> |
| 1846 |
</address> |
| 1847 |
<address class="vcard"> |
| 1848 |
<div dir="auto" class="left"><span class="fn nameRole">Jacques Latour</span></div> |
| 1849 |
<div dir="auto" class="left"><span class="org">CIRA Labs</span></div> |
| 1850 |
<div class="email"> |
| 1851 |
<span>Email:</span> |
| 1852 |
<a href="mailto:[email protected]" class="email">[email protected]</a> |
| 1853 |
</div> |
| 1854 |
</address> |
| 1855 |
<address class="vcard"> |
| 1856 |
<div dir="auto" class="left"><span class="fn nameRole">Hassan Habibi Gharakheili</span></div> |
| 1857 |
<div dir="auto" class="left"><span class="org">UNSW Sydney</span></div> |
| 1858 |
<div class="email"> |
| 1859 |
<span>Email:</span> |
| 1860 |
<a href="mailto:[email protected]" class="email">[email protected]</a> |
| 1861 |
</div> |
| 1862 |
</address> |
| 1863 |
</section> |
| 1864 |
</div> |
| 1865 |
<script>const toc = document.getElementById("toc"); |
| 1866 |
toc.querySelector("h2").addEventListener("click", e => { |
| 1867 |
toc.classList.toggle("active"); |
| 1868 |
}); |
| 1869 |
toc.querySelector("nav").addEventListener("click", e => { |
| 1870 |
toc.classList.remove("active"); |
| 1871 |
}); |
| 1872 |
</script> |
| 1873 |
</body> |
| 1874 |
</html> |