| 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 8691: Basic Support for IPv6 Networks Operating Outside the Context of a Basic Service Set over IEEE Std 802.11</title> |
| 8 |
<meta content="Nabil Benamar" name="author"> |
| 9 |
<meta content="Jérôme Härri" name="author"> |
| 10 |
<meta content="Jong-Hyouk Lee" name="author"> |
| 11 |
<meta content="Thierry ERNST" name="author"> |
| 12 |
<meta content=" |
| 13 |
|
| 14 |
This document provides methods and settings |
| 15 |
for using IPv6 to communicate among nodes within range of one another |
| 16 |
over a single IEEE 802.11-OCB link. Support for these methods and |
| 17 |
settings require minimal changes to existing stacks. This document |
| 18 |
also describes limitations associated with using these methods. |
| 19 |
Optimizations and usage of IPv6 over more complex scenarios |
| 20 |
are not covered in this specification and are a subject for future work. |
| 21 |
|
| 22 |
" name="description"> |
| 23 |
<meta content="xml2rfc 2.37.3" name="generator"> |
| 24 |
<meta content="IPv6 over 802.11p" name="keyword"> |
| 25 |
<meta content="OCB" name="keyword"> |
| 26 |
<meta content="IPv6 over 802.11-OCB" name="keyword"> |
| 27 |
<meta content="8691" name="rfc.number"> |
| 28 |
<link href="rfc8691.xml" type="application/rfc+xml" rel="alternate"> |
| 29 |
<link href="#copyright" rel="license"> |
| 30 |
<style type="text/css">/* |
| 31 |
|
| 32 |
NOTE: Changes at the bottom of this file overrides some earlier settings. |
| 33 |
|
| 34 |
Once the style has stabilized and has been adopted as an official RFC style, |
| 35 |
this can be consolidated so that style settings occur only in one place, but |
| 36 |
for now the contents of this file consists first of the initial CSS work as |
| 37 |
provided to the RFC Formatter (xml2rfc) work, followed by itemized and |
| 38 |
commented changes found necssary during the development of the v3 |
| 39 |
formatters. |
| 40 |
|
| 41 |
*/ |
| 42 |
|
| 43 |
/* fonts */ |
| 44 |
@import url('https://fonts.googleapis.com/css?family=Noto+Sans'); /* Sans-serif */ |
| 45 |
@import url('https://fonts.googleapis.com/css?family=Noto+Serif'); /* Serif (print) */ |
| 46 |
@import url('https://fonts.googleapis.com/css?family=Roboto+Mono'); /* Monospace */ |
| 47 |
|
| 48 |
@viewport { |
| 49 |
zoom: 1.0; |
| 50 |
width: extend-to-zoom; |
| 51 |
} |
| 52 |
@-ms-viewport { |
| 53 |
width: extend-to-zoom; |
| 54 |
zoom: 1.0; |
| 55 |
} |
| 56 |
/* general and mobile first */ |
| 57 |
html { |
| 58 |
} |
| 59 |
body { |
| 60 |
max-width: 90%; |
| 61 |
margin: 1.5em auto; |
| 62 |
color: #222; |
| 63 |
background-color: #fff; |
| 64 |
font-size: 14px; |
| 65 |
font-family: 'Noto Sans', Arial, Helvetica, sans-serif; |
| 66 |
line-height: 1.6; |
| 67 |
scroll-behavior: smooth; |
| 68 |
} |
| 69 |
.ears { |
| 70 |
display: none; |
| 71 |
} |
| 72 |
|
| 73 |
/* headings */ |
| 74 |
#title, h1, h2, h3, h4, h5, h6 { |
| 75 |
margin: 1em 0 0.5em; |
| 76 |
font-weight: bold; |
| 77 |
line-height: 1.3; |
| 78 |
} |
| 79 |
#title { |
| 80 |
clear: both; |
| 81 |
border-bottom: 1px solid #ddd; |
| 82 |
margin: 0 0 0.5em 0; |
| 83 |
padding: 1em 0 0.5em; |
| 84 |
} |
| 85 |
.author { |
| 86 |
padding-bottom: 4px; |
| 87 |
} |
| 88 |
h1 { |
| 89 |
font-size: 26px; |
| 90 |
margin: 1em 0; |
| 91 |
} |
| 92 |
h2 { |
| 93 |
font-size: 22px; |
| 94 |
margin-top: -20px; /* provide offset for in-page anchors */ |
| 95 |
padding-top: 33px; |
| 96 |
} |
| 97 |
h3 { |
| 98 |
font-size: 18px; |
| 99 |
margin-top: -36px; /* provide offset for in-page anchors */ |
| 100 |
padding-top: 42px; |
| 101 |
} |
| 102 |
h4 { |
| 103 |
font-size: 16px; |
| 104 |
margin-top: -36px; /* provide offset for in-page anchors */ |
| 105 |
padding-top: 42px; |
| 106 |
} |
| 107 |
h5, h6 { |
| 108 |
font-size: 14px; |
| 109 |
} |
| 110 |
#n-copyright-notice { |
| 111 |
border-bottom: 1px solid #ddd; |
| 112 |
padding-bottom: 1em; |
| 113 |
margin-bottom: 1em; |
| 114 |
} |
| 115 |
/* general structure */ |
| 116 |
p { |
| 117 |
padding: 0; |
| 118 |
margin: 0 0 1em 0; |
| 119 |
text-align: left; |
| 120 |
} |
| 121 |
div, span { |
| 122 |
position: relative; |
| 123 |
} |
| 124 |
div { |
| 125 |
margin: 0; |
| 126 |
} |
| 127 |
.alignRight.art-text { |
| 128 |
background-color: #f9f9f9; |
| 129 |
border: 1px solid #eee; |
| 130 |
border-radius: 3px; |
| 131 |
padding: 1em 1em 0; |
| 132 |
margin-bottom: 1.5em; |
| 133 |
} |
| 134 |
.alignRight.art-text pre { |
| 135 |
padding: 0; |
| 136 |
} |
| 137 |
.alignRight { |
| 138 |
margin: 1em 0; |
| 139 |
} |
| 140 |
.alignRight > *:first-child { |
| 141 |
border: none; |
| 142 |
margin: 0; |
| 143 |
float: right; |
| 144 |
clear: both; |
| 145 |
} |
| 146 |
.alignRight > *:nth-child(2) { |
| 147 |
clear: both; |
| 148 |
display: block; |
| 149 |
border: none; |
| 150 |
} |
| 151 |
svg { |
| 152 |
display: block; |
| 153 |
} |
| 154 |
.alignCenter.art-text { |
| 155 |
background-color: #f9f9f9; |
| 156 |
border: 1px solid #eee; |
| 157 |
border-radius: 3px; |
| 158 |
padding: 1em 1em 0; |
| 159 |
margin-bottom: 1.5em; |
| 160 |
} |
| 161 |
.alignCenter.art-text pre { |
| 162 |
padding: 0; |
| 163 |
} |
| 164 |
.alignCenter { |
| 165 |
margin: 1em 0; |
| 166 |
} |
| 167 |
.alignCenter > *:first-child { |
| 168 |
border: none; |
| 169 |
/* this isn't optimal, but it's an existence proof. PrinceXML doesn't |
| 170 |
support flexbox yet. |
| 171 |
*/ |
| 172 |
display: table; |
| 173 |
margin: 0 auto; |
| 174 |
} |
| 175 |
|
| 176 |
/* lists */ |
| 177 |
ol, ul { |
| 178 |
padding: 0; |
| 179 |
margin: 0 0 1em 2em; |
| 180 |
} |
| 181 |
ol ol, ul ul, ol ul, ul ol { |
| 182 |
margin-left: 1em; |
| 183 |
} |
| 184 |
li { |
| 185 |
margin: 0 0 0.25em 0; |
| 186 |
} |
| 187 |
.ulCompact li { |
| 188 |
margin: 0; |
| 189 |
} |
| 190 |
ul.empty, .ulEmpty { |
| 191 |
list-style-type: none; |
| 192 |
} |
| 193 |
ul.empty li, .ulEmpty li { |
| 194 |
margin-top: 0.5em; |
| 195 |
} |
| 196 |
ul.compact, .ulCompact, |
| 197 |
ol.compact, .olCompact { |
| 198 |
line-height: 100%; |
| 199 |
margin: 0 0 0 2em; |
| 200 |
} |
| 201 |
|
| 202 |
/* definition lists */ |
| 203 |
dl { |
| 204 |
} |
| 205 |
dl > dt { |
| 206 |
float: left; |
| 207 |
margin-right: 1em; |
| 208 |
} |
| 209 |
/* |
| 210 |
dl.nohang > dt { |
| 211 |
float: none; |
| 212 |
} |
| 213 |
*/ |
| 214 |
dl > dd { |
| 215 |
margin-bottom: .8em; |
| 216 |
min-height: 1.3em; |
| 217 |
} |
| 218 |
dl.compact > dd, .dlCompact > dd { |
| 219 |
margin-bottom: 0em; |
| 220 |
} |
| 221 |
dl > dd > dl { |
| 222 |
margin-top: 0.5em; |
| 223 |
margin-bottom: 0em; |
| 224 |
} |
| 225 |
|
| 226 |
/* links */ |
| 227 |
a { |
| 228 |
text-decoration: none; |
| 229 |
} |
| 230 |
a[href] { |
| 231 |
color: #22e; /* Arlen: WCAG 2019 */ |
| 232 |
} |
| 233 |
a[href]:hover { |
| 234 |
background-color: #f2f2f2; |
| 235 |
} |
| 236 |
figcaption a[href], |
| 237 |
a[href].selfRef { |
| 238 |
color: #222; |
| 239 |
} |
| 240 |
/* XXX probably not this: |
| 241 |
a.selfRef:hover { |
| 242 |
background-color: transparent; |
| 243 |
cursor: default; |
| 244 |
} */ |
| 245 |
|
| 246 |
/* Figures */ |
| 247 |
tt, code, pre, code { |
| 248 |
background-color: #f9f9f9; |
| 249 |
font-family: 'Roboto Mono', monospace; |
| 250 |
} |
| 251 |
pre { |
| 252 |
border: 1px solid #eee; |
| 253 |
margin: 0; |
| 254 |
padding: 1em; |
| 255 |
} |
| 256 |
img { |
| 257 |
max-width: 100%; |
| 258 |
} |
| 259 |
figure { |
| 260 |
margin: 0; |
| 261 |
} |
| 262 |
figure blockquote { |
| 263 |
margin: 0.8em 0.4em 0.4em; |
| 264 |
} |
| 265 |
figcaption { |
| 266 |
font-style: italic; |
| 267 |
margin: 0 0 1em 0; |
| 268 |
} |
| 269 |
@media screen { |
| 270 |
pre { |
| 271 |
overflow-x: auto; |
| 272 |
max-width: 100%; |
| 273 |
max-width: calc(100% - 22px); |
| 274 |
} |
| 275 |
} |
| 276 |
|
| 277 |
/* aside, blockquote */ |
| 278 |
aside, blockquote { |
| 279 |
margin-left: 0; |
| 280 |
padding: 1.2em 2em; |
| 281 |
} |
| 282 |
blockquote { |
| 283 |
background-color: #f9f9f9; |
| 284 |
color: #111; /* Arlen: WCAG 2019 */ |
| 285 |
border: 1px solid #ddd; |
| 286 |
border-radius: 3px; |
| 287 |
margin: 1em 0; |
| 288 |
} |
| 289 |
cite { |
| 290 |
display: block; |
| 291 |
text-align: right; |
| 292 |
font-style: italic; |
| 293 |
} |
| 294 |
|
| 295 |
/* tables */ |
| 296 |
table { |
| 297 |
width: 100%; |
| 298 |
margin: 0 0 1em; |
| 299 |
border-collapse: collapse; |
| 300 |
border: 1px solid #eee; |
| 301 |
} |
| 302 |
th, td { |
| 303 |
text-align: left; |
| 304 |
vertical-align: top; |
| 305 |
padding: 0.5em 0.75em; |
| 306 |
} |
| 307 |
th { |
| 308 |
text-align: left; |
| 309 |
background-color: #e9e9e9; |
| 310 |
} |
| 311 |
tr:nth-child(2n+1) > td { |
| 312 |
background-color: #f5f5f5; |
| 313 |
} |
| 314 |
table caption { |
| 315 |
font-style: italic; |
| 316 |
margin: 0; |
| 317 |
padding: 0; |
| 318 |
text-align: left; |
| 319 |
} |
| 320 |
table p { |
| 321 |
/* XXX to avoid bottom margin on table row signifiers. If paragraphs should |
| 322 |
be allowed within tables more generally, it would be far better to select on a class. */ |
| 323 |
margin: 0; |
| 324 |
} |
| 325 |
|
| 326 |
/* pilcrow */ |
| 327 |
a.pilcrow { |
| 328 |
color: #666; /* Arlen: AHDJ 2019 */ |
| 329 |
text-decoration: none; |
| 330 |
visibility: hidden; |
| 331 |
user-select: none; |
| 332 |
-ms-user-select: none; |
| 333 |
-o-user-select:none; |
| 334 |
-moz-user-select: none; |
| 335 |
-khtml-user-select: none; |
| 336 |
-webkit-user-select: none; |
| 337 |
-webkit-touch-callout: none; |
| 338 |
} |
| 339 |
@media screen { |
| 340 |
aside:hover > a.pilcrow, |
| 341 |
p:hover > a.pilcrow, |
| 342 |
blockquote:hover > a.pilcrow, |
| 343 |
div:hover > a.pilcrow, |
| 344 |
li:hover > a.pilcrow, |
| 345 |
pre:hover > a.pilcrow { |
| 346 |
visibility: visible; |
| 347 |
} |
| 348 |
a.pilcrow:hover { |
| 349 |
background-color: transparent; |
| 350 |
} |
| 351 |
} |
| 352 |
|
| 353 |
/* misc */ |
| 354 |
hr { |
| 355 |
border: 0; |
| 356 |
border-top: 1px solid #eee; |
| 357 |
} |
| 358 |
.bcp14 { |
| 359 |
font-variant: small-caps; |
| 360 |
} |
| 361 |
|
| 362 |
.role { |
| 363 |
font-variant: all-small-caps; |
| 364 |
} |
| 365 |
|
| 366 |
/* info block */ |
| 367 |
#identifiers { |
| 368 |
margin: 0; |
| 369 |
font-size: 0.9em; |
| 370 |
} |
| 371 |
#identifiers dt { |
| 372 |
width: 3em; |
| 373 |
clear: left; |
| 374 |
} |
| 375 |
#identifiers dd { |
| 376 |
float: left; |
| 377 |
margin-bottom: 0; |
| 378 |
} |
| 379 |
#identifiers .authors .author { |
| 380 |
display: inline-block; |
| 381 |
margin-right: 1.5em; |
| 382 |
} |
| 383 |
#identifiers .authors .org { |
| 384 |
font-style: italic; |
| 385 |
} |
| 386 |
|
| 387 |
/* The prepared/rendered info at the very bottom of the page */ |
| 388 |
.docInfo { |
| 389 |
color: #666; /* Arlen: WCAG 2019 */ |
| 390 |
font-size: 0.9em; |
| 391 |
font-style: italic; |
| 392 |
margin-top: 2em; |
| 393 |
} |
| 394 |
.docInfo .prepared { |
| 395 |
float: left; |
| 396 |
} |
| 397 |
.docInfo .prepared { |
| 398 |
float: right; |
| 399 |
} |
| 400 |
|
| 401 |
/* table of contents */ |
| 402 |
#toc { |
| 403 |
padding: 0.75em 0 2em 0; |
| 404 |
margin-bottom: 1em; |
| 405 |
} |
| 406 |
nav.toc ul { |
| 407 |
margin: 0 0.5em 0 0; |
| 408 |
padding: 0; |
| 409 |
list-style: none; |
| 410 |
} |
| 411 |
nav.toc li { |
| 412 |
line-height: 1.3em; |
| 413 |
margin: 0.75em 0; |
| 414 |
padding-left: 1.2em; |
| 415 |
text-indent: -1.2em; |
| 416 |
} |
| 417 |
/* references */ |
| 418 |
.references dt { |
| 419 |
text-align: right; |
| 420 |
font-weight: bold; |
| 421 |
min-width: 7em; |
| 422 |
} |
| 423 |
.references dd { |
| 424 |
margin-left: 8em; |
| 425 |
overflow: auto; |
| 426 |
} |
| 427 |
|
| 428 |
.refInstance { |
| 429 |
margin-bottom: 1.25em; |
| 430 |
} |
| 431 |
|
| 432 |
.references .ascii { |
| 433 |
margin-bottom: 0.25em; |
| 434 |
} |
| 435 |
|
| 436 |
/* index */ |
| 437 |
.index ul { |
| 438 |
margin: 0 0 0 1em; |
| 439 |
padding: 0; |
| 440 |
list-style: none; |
| 441 |
} |
| 442 |
.index ul ul { |
| 443 |
margin: 0; |
| 444 |
} |
| 445 |
.index li { |
| 446 |
margin: 0; |
| 447 |
text-indent: -2em; |
| 448 |
padding-left: 2em; |
| 449 |
padding-bottom: 5px; |
| 450 |
} |
| 451 |
.indexIndex { |
| 452 |
margin: 0.5em 0 1em; |
| 453 |
} |
| 454 |
.index a { |
| 455 |
font-weight: 700; |
| 456 |
} |
| 457 |
/* make the index two-column on all but the smallest screens */ |
| 458 |
@media (min-width: 600px) { |
| 459 |
.index ul { |
| 460 |
-moz-column-count: 2; |
| 461 |
-moz-column-gap: 20px; |
| 462 |
} |
| 463 |
.index ul ul { |
| 464 |
-moz-column-count: 1; |
| 465 |
-moz-column-gap: 0; |
| 466 |
} |
| 467 |
} |
| 468 |
|
| 469 |
/* authors */ |
| 470 |
address.vcard { |
| 471 |
font-style: normal; |
| 472 |
margin: 1em 0; |
| 473 |
} |
| 474 |
|
| 475 |
address.vcard .nameRole { |
| 476 |
font-weight: 700; |
| 477 |
margin-left: 0; |
| 478 |
} |
| 479 |
address.vcard .label { |
| 480 |
font-family: "Noto Sans",Arial,Helvetica,sans-serif; |
| 481 |
margin: 0.5em 0; |
| 482 |
} |
| 483 |
address.vcard .type { |
| 484 |
display: none; |
| 485 |
} |
| 486 |
.alternative-contact { |
| 487 |
margin: 1.5em 0 1em; |
| 488 |
} |
| 489 |
hr.addr { |
| 490 |
border-top: 1px dashed; |
| 491 |
margin: 0; |
| 492 |
color: #ddd; |
| 493 |
max-width: calc(100% - 16px); |
| 494 |
} |
| 495 |
|
| 496 |
/* temporary notes */ |
| 497 |
.rfcEditorRemove::before { |
| 498 |
position: absolute; |
| 499 |
top: 0.2em; |
| 500 |
right: 0.2em; |
| 501 |
padding: 0.2em; |
| 502 |
content: "The RFC Editor will remove this note"; |
| 503 |
color: #9e2a00; /* Arlen: WCAG 2019 */ |
| 504 |
background-color: #ffd; /* Arlen: WCAG 2019 */ |
| 505 |
} |
| 506 |
.rfcEditorRemove { |
| 507 |
position: relative; |
| 508 |
padding-top: 1.8em; |
| 509 |
background-color: #ffd; /* Arlen: WCAG 2019 */ |
| 510 |
border-radius: 3px; |
| 511 |
} |
| 512 |
.cref { |
| 513 |
background-color: #ffd; /* Arlen: WCAG 2019 */ |
| 514 |
padding: 2px 4px; |
| 515 |
} |
| 516 |
.crefSource { |
| 517 |
font-style: italic; |
| 518 |
} |
| 519 |
/* alternative layout for smaller screens */ |
| 520 |
@media screen and (max-width: 1023px) { |
| 521 |
body { |
| 522 |
padding-top: 2em; |
| 523 |
} |
| 524 |
#title { |
| 525 |
padding: 1em 0; |
| 526 |
} |
| 527 |
h1 { |
| 528 |
font-size: 24px; |
| 529 |
} |
| 530 |
h2 { |
| 531 |
font-size: 20px; |
| 532 |
margin-top: -18px; /* provide offset for in-page anchors */ |
| 533 |
padding-top: 38px; |
| 534 |
} |
| 535 |
#identifiers dd { |
| 536 |
max-width: 60%; |
| 537 |
} |
| 538 |
#toc { |
| 539 |
position: fixed; |
| 540 |
z-index: 2; |
| 541 |
top: 0; |
| 542 |
right: 0; |
| 543 |
padding: 0; |
| 544 |
margin: 0; |
| 545 |
background-color: inherit; |
| 546 |
border-bottom: 1px solid #ccc; |
| 547 |
} |
| 548 |
#toc h2 { |
| 549 |
margin: -1px 0 0 0; |
| 550 |
padding: 4px 0 4px 6px; |
| 551 |
padding-right: 1em; |
| 552 |
min-width: 190px; |
| 553 |
font-size: 1.1em; |
| 554 |
text-align: right; |
| 555 |
background-color: #444; |
| 556 |
color: white; |
| 557 |
cursor: pointer; |
| 558 |
} |
| 559 |
#toc h2::before { /* css hamburger */ |
| 560 |
float: right; |
| 561 |
position: relative; |
| 562 |
width: 1em; |
| 563 |
height: 1px; |
| 564 |
left: -164px; |
| 565 |
margin: 6px 0 0 0; |
| 566 |
background: white none repeat scroll 0 0; |
| 567 |
box-shadow: 0 4px 0 0 white, 0 8px 0 0 white; |
| 568 |
content: ""; |
| 569 |
} |
| 570 |
#toc nav { |
| 571 |
display: none; |
| 572 |
padding: 0.5em 1em 1em; |
| 573 |
overflow: auto; |
| 574 |
height: calc(100vh - 48px); |
| 575 |
border-left: 1px solid #ddd; |
| 576 |
} |
| 577 |
} |
| 578 |
|
| 579 |
/* alternative layout for wide screens */ |
| 580 |
@media screen and (min-width: 1024px) { |
| 581 |
body { |
| 582 |
max-width: 724px; |
| 583 |
margin: 42px auto; |
| 584 |
padding-left: 1.5em; |
| 585 |
padding-right: 29em; |
| 586 |
} |
| 587 |
#toc { |
| 588 |
position: fixed; |
| 589 |
top: 42px; |
| 590 |
right: 42px; |
| 591 |
width: 25%; |
| 592 |
margin: 0; |
| 593 |
padding: 0 1em; |
| 594 |
z-index: 1; |
| 595 |
} |
| 596 |
#toc h2 { |
| 597 |
border-top: none; |
| 598 |
border-bottom: 1px solid #ddd; |
| 599 |
font-size: 1em; |
| 600 |
font-weight: normal; |
| 601 |
margin: 0; |
| 602 |
padding: 0.25em 1em 1em 0; |
| 603 |
} |
| 604 |
#toc nav { |
| 605 |
display: block; |
| 606 |
height: calc(90vh - 84px); |
| 607 |
bottom: 0; |
| 608 |
padding: 0.5em 0 0; |
| 609 |
overflow: auto; |
| 610 |
} |
| 611 |
img { /* future proofing */ |
| 612 |
max-width: 100%; |
| 613 |
height: auto; |
| 614 |
} |
| 615 |
} |
| 616 |
|
| 617 |
/* pagination */ |
| 618 |
@media print { |
| 619 |
body { |
| 620 |
|
| 621 |
width: 100%; |
| 622 |
} |
| 623 |
p { |
| 624 |
orphans: 3; |
| 625 |
widows: 3; |
| 626 |
} |
| 627 |
#n-copyright-notice { |
| 628 |
border-bottom: none; |
| 629 |
} |
| 630 |
#toc, #n-introduction { |
| 631 |
page-break-before: always; |
| 632 |
} |
| 633 |
#toc { |
| 634 |
border-top: none; |
| 635 |
padding-top: 0; |
| 636 |
} |
| 637 |
figure, pre { |
| 638 |
page-break-inside: avoid; |
| 639 |
} |
| 640 |
figure { |
| 641 |
overflow: scroll; |
| 642 |
} |
| 643 |
h1, h2, h3, h4, h5, h6 { |
| 644 |
page-break-after: avoid; |
| 645 |
} |
| 646 |
h2+*, h3+*, h4+*, h5+*, h6+* { |
| 647 |
page-break-before: avoid; |
| 648 |
} |
| 649 |
pre { |
| 650 |
white-space: pre-wrap; |
| 651 |
word-wrap: break-word; |
| 652 |
font-size: 10pt; |
| 653 |
} |
| 654 |
table { |
| 655 |
border: 1px solid #ddd; |
| 656 |
} |
| 657 |
td { |
| 658 |
border-top: 1px solid #ddd; |
| 659 |
} |
| 660 |
} |
| 661 |
|
| 662 |
/* This is commented out here, as the string-set: doesn't |
| 663 |
pass W3C validation currently */ |
| 664 |
/* |
| 665 |
.ears thead .left { |
| 666 |
string-set: ears-top-left content(); |
| 667 |
} |
| 668 |
|
| 669 |
.ears thead .center { |
| 670 |
string-set: ears-top-center content(); |
| 671 |
} |
| 672 |
|
| 673 |
.ears thead .right { |
| 674 |
string-set: ears-top-right content(); |
| 675 |
} |
| 676 |
|
| 677 |
.ears tfoot .left { |
| 678 |
string-set: ears-bottom-left content(); |
| 679 |
} |
| 680 |
|
| 681 |
.ears tfoot .center { |
| 682 |
string-set: ears-bottom-center content(); |
| 683 |
} |
| 684 |
|
| 685 |
.ears tfoot .right { |
| 686 |
string-set: ears-bottom-right content(); |
| 687 |
} |
| 688 |
*/ |
| 689 |
|
| 690 |
@page :first { |
| 691 |
padding-top: 0; |
| 692 |
@top-left { |
| 693 |
content: normal; |
| 694 |
border: none; |
| 695 |
} |
| 696 |
@top-center { |
| 697 |
content: normal; |
| 698 |
border: none; |
| 699 |
} |
| 700 |
@top-right { |
| 701 |
content: normal; |
| 702 |
border: none; |
| 703 |
} |
| 704 |
} |
| 705 |
|
| 706 |
@page { |
| 707 |
size: A4; |
| 708 |
margin-bottom: 45mm; |
| 709 |
padding-top: 20px; |
| 710 |
/* The follwing is commented out here, but set appropriately by in code, as |
| 711 |
the content depends on the document */ |
| 712 |
/* |
| 713 |
@top-left { |
| 714 |
content: 'Internet-Draft'; |
| 715 |
vertical-align: bottom; |
| 716 |
border-bottom: solid 1px #ccc; |
| 717 |
} |
| 718 |
@top-left { |
| 719 |
content: string(ears-top-left); |
| 720 |
vertical-align: bottom; |
| 721 |
border-bottom: solid 1px #ccc; |
| 722 |
} |
| 723 |
@top-center { |
| 724 |
content: string(ears-top-center); |
| 725 |
vertical-align: bottom; |
| 726 |
border-bottom: solid 1px #ccc; |
| 727 |
} |
| 728 |
@top-right { |
| 729 |
content: string(ears-top-right); |
| 730 |
vertical-align: bottom; |
| 731 |
border-bottom: solid 1px #ccc; |
| 732 |
} |
| 733 |
@bottom-left { |
| 734 |
content: string(ears-bottom-left); |
| 735 |
vertical-align: top; |
| 736 |
border-top: solid 1px #ccc; |
| 737 |
} |
| 738 |
@bottom-center { |
| 739 |
content: string(ears-bottom-center); |
| 740 |
vertical-align: top; |
| 741 |
border-top: solid 1px #ccc; |
| 742 |
} |
| 743 |
@bottom-right { |
| 744 |
content: '[Page ' counter(page) ']'; |
| 745 |
vertical-align: top; |
| 746 |
border-top: solid 1px #ccc; |
| 747 |
} |
| 748 |
*/ |
| 749 |
|
| 750 |
} |
| 751 |
|
| 752 |
/* Changes introduced to fix issues found during implementation */ |
| 753 |
/* Make sure links are clickable even if overlapped by following H* */ |
| 754 |
a { |
| 755 |
z-index: 2; |
| 756 |
} |
| 757 |
/* Separate body from document info even without intervening H1 */ |
| 758 |
section { |
| 759 |
clear: both; |
| 760 |
} |
| 761 |
|
| 762 |
|
| 763 |
/* Top align author divs, to avoid names without organization dropping level with org names */ |
| 764 |
.author { |
| 765 |
vertical-align: top; |
| 766 |
} |
| 767 |
|
| 768 |
/* Leave room in document info to show Internet-Draft on one line */ |
| 769 |
#identifiers dt { |
| 770 |
width: 8em; |
| 771 |
} |
| 772 |
|
| 773 |
/* Don't waste quite as much whitespace between label and value in doc info */ |
| 774 |
#identifiers dd { |
| 775 |
margin-left: 1em; |
| 776 |
} |
| 777 |
|
| 778 |
/* Give floating toc a background color (needed when it's a div inside section */ |
| 779 |
#toc { |
| 780 |
background-color: white; |
| 781 |
} |
| 782 |
|
| 783 |
/* Make the collapsed ToC header render white on gray also when it's a link */ |
| 784 |
@media screen and (max-width: 1023px) { |
| 785 |
#toc h2 a, |
| 786 |
#toc h2 a:link, |
| 787 |
#toc h2 a:focus, |
| 788 |
#toc h2 a:hover, |
| 789 |
#toc a.toplink, |
| 790 |
#toc a.toplink:hover { |
| 791 |
color: white; |
| 792 |
background-color: #444; |
| 793 |
text-decoration: none; |
| 794 |
} |
| 795 |
} |
| 796 |
|
| 797 |
/* Give the bottom of the ToC some whitespace */ |
| 798 |
@media screen and (min-width: 1024px) { |
| 799 |
#toc { |
| 800 |
padding: 0 0 1em 1em; |
| 801 |
} |
| 802 |
} |
| 803 |
|
| 804 |
/* Style section numbers with more space between number and title */ |
| 805 |
.section-number { |
| 806 |
padding-right: 0.5em; |
| 807 |
} |
| 808 |
|
| 809 |
/* prevent monospace from becoming overly large */ |
| 810 |
tt, code, pre, code { |
| 811 |
font-size: 95%; |
| 812 |
} |
| 813 |
|
| 814 |
/* Fix the height/width aspect for ascii art*/ |
| 815 |
pre.sourcecode, |
| 816 |
.art-text pre { |
| 817 |
line-height: 1.12; |
| 818 |
} |
| 819 |
|
| 820 |
|
| 821 |
/* Add styling for a link in the ToC that points to the top of the document */ |
| 822 |
a.toplink { |
| 823 |
float: right; |
| 824 |
margin-right: 0.5em; |
| 825 |
} |
| 826 |
|
| 827 |
/* Fix the dl styling to match the RFC 7992 attributes */ |
| 828 |
dl > dt, |
| 829 |
dl.dlParallel > dt { |
| 830 |
float: left; |
| 831 |
margin-right: 1em; |
| 832 |
} |
| 833 |
dl.dlNewline > dt { |
| 834 |
float: none; |
| 835 |
} |
| 836 |
|
| 837 |
/* Provide styling for table cell text alignment */ |
| 838 |
table td.text-left, |
| 839 |
table th.text-left { |
| 840 |
text-align: left; |
| 841 |
} |
| 842 |
table td.text-center, |
| 843 |
table th.text-center { |
| 844 |
text-align: center; |
| 845 |
} |
| 846 |
table td.text-right, |
| 847 |
table th.text-right { |
| 848 |
text-align: right; |
| 849 |
} |
| 850 |
|
| 851 |
/* Make the alternative author contact informatio look less like just another |
| 852 |
author, and group it closer with the primary author contact information */ |
| 853 |
.alternative-contact { |
| 854 |
margin: 0.5em 0 0.25em 0; |
| 855 |
} |
| 856 |
address .non-ascii { |
| 857 |
margin: 0 0 0 2em; |
| 858 |
} |
| 859 |
|
| 860 |
/* With it being possible to set tables with alignment |
| 861 |
left, center, and right, { width: 100%; } does not make sense */ |
| 862 |
table { |
| 863 |
width: auto; |
| 864 |
} |
| 865 |
|
| 866 |
/* Avoid reference text that sits in a block with very wide left margin, |
| 867 |
because of a long floating dt label.*/ |
| 868 |
.references dd { |
| 869 |
overflow: visible; |
| 870 |
} |
| 871 |
|
| 872 |
/* Control caption placement */ |
| 873 |
caption { |
| 874 |
caption-side: bottom; |
| 875 |
} |
| 876 |
|
| 877 |
/* Limit the width of the author address vcard, so names in right-to-left |
| 878 |
script don't end up on the other side of the page. */ |
| 879 |
|
| 880 |
address.vcard { |
| 881 |
max-width: 30em; |
| 882 |
margin-right: auto; |
| 883 |
} |
| 884 |
|
| 885 |
/* For address alignment dependent on LTR or RTL scripts */ |
| 886 |
address div.left { |
| 887 |
text-align: left; |
| 888 |
} |
| 889 |
address div.right { |
| 890 |
text-align: right; |
| 891 |
} |
| 892 |
|
| 893 |
/* Provide table alignment support. We can't use the alignX classes above |
| 894 |
since they do unwanted things with caption and other styling. */ |
| 895 |
table.right { |
| 896 |
margin-left: auto; |
| 897 |
margin-right: 0; |
| 898 |
} |
| 899 |
table.center { |
| 900 |
margin-left: auto; |
| 901 |
margin-right: auto; |
| 902 |
} |
| 903 |
table.left { |
| 904 |
margin-left: 0; |
| 905 |
margin-right: auto; |
| 906 |
} |
| 907 |
|
| 908 |
/* Give the table caption label the same styling as the figcaption */ |
| 909 |
caption a[href] { |
| 910 |
color: #222; |
| 911 |
} |
| 912 |
|
| 913 |
@media print { |
| 914 |
.toplink { |
| 915 |
display: none; |
| 916 |
} |
| 917 |
|
| 918 |
/* avoid overwriting the top border line with the ToC header */ |
| 919 |
#toc { |
| 920 |
padding-top: 1px; |
| 921 |
} |
| 922 |
|
| 923 |
/* Avoid page breaks inside dl and author address entries */ |
| 924 |
.vcard { |
| 925 |
page-break-inside: avoid; |
| 926 |
} |
| 927 |
|
| 928 |
} |
| 929 |
/* Avoid wrapping of URLs in references */ |
| 930 |
@media screen { |
| 931 |
.references a { |
| 932 |
white-space: nowrap; |
| 933 |
} |
| 934 |
} |
| 935 |
/* Tweak the bcp14 keyword presentation */ |
| 936 |
.bcp14 { |
| 937 |
font-variant: small-caps; |
| 938 |
font-weight: bold; |
| 939 |
font-size: 0.9em; |
| 940 |
} |
| 941 |
/* Tweak the invisible space above H* in order not to overlay links in text above */ |
| 942 |
h2 { |
| 943 |
margin-top: -18px; /* provide offset for in-page anchors */ |
| 944 |
padding-top: 31px; |
| 945 |
} |
| 946 |
h3 { |
| 947 |
margin-top: -18px; /* provide offset for in-page anchors */ |
| 948 |
padding-top: 24px; |
| 949 |
} |
| 950 |
h4 { |
| 951 |
margin-top: -18px; /* provide offset for in-page anchors */ |
| 952 |
padding-top: 24px; |
| 953 |
} |
| 954 |
/* Float artwork pilcrow to the right */ |
| 955 |
@media screen { |
| 956 |
.artwork a.pilcrow { |
| 957 |
display: block; |
| 958 |
line-height: 0.7; |
| 959 |
margin-top: 0.15em; |
| 960 |
} |
| 961 |
} |
| 962 |
/* Make pilcrows on dd visible */ |
| 963 |
@media screen { |
| 964 |
dd:hover > a.pilcrow { |
| 965 |
visibility: visible; |
| 966 |
} |
| 967 |
} |
| 968 |
/* Make the placement of figcaption match that of a table's caption |
| 969 |
by removing the figure's added bottom margin */ |
| 970 |
.alignLeft.art-text, |
| 971 |
.alignCenter.art-text, |
| 972 |
.alignRight.art-text { |
| 973 |
margin-bottom: 0; |
| 974 |
} |
| 975 |
.alignLeft, |
| 976 |
.alignCenter, |
| 977 |
.alignRight { |
| 978 |
margin: 1em 0 0 0; |
| 979 |
} |
| 980 |
/* In print, the pilcrow won't show on hover, so prevent it from taking up space, |
| 981 |
possibly even requiring a new line */ |
| 982 |
@media print { |
| 983 |
a.pilcrow { |
| 984 |
display: none; |
| 985 |
} |
| 986 |
} |
| 987 |
/* Styling for the external metadata */ |
| 988 |
div#external-metadata { |
| 989 |
background-color: #eee; |
| 990 |
padding: 0.5em; |
| 991 |
margin-bottom: 0.5em; |
| 992 |
display: none; |
| 993 |
} |
| 994 |
div#internal-metadata { |
| 995 |
padding: 0.5em; /* to match the external-metadata padding */ |
| 996 |
} |
| 997 |
/* Styling for title RFC Number */ |
| 998 |
h1#rfcnum { |
| 999 |
clear: both; |
| 1000 |
margin: 0 0 -1em; |
| 1001 |
padding: 1em 0 0 0; |
| 1002 |
} |
| 1003 |
/* Make .olPercent look the same as <ol><li> */ |
| 1004 |
dl.olPercent > dd { |
| 1005 |
margin: 0 0 0.25em 0; |
| 1006 |
min-height: initial; |
| 1007 |
} |
| 1008 |
/* Give aside some styling to set it apart */ |
| 1009 |
aside { |
| 1010 |
border-left: 1px solid #ddd; |
| 1011 |
margin: 1em 0 1em 2em; |
| 1012 |
padding: 0.2em 2em; |
| 1013 |
} |
| 1014 |
aside > dl, |
| 1015 |
aside > ol, |
| 1016 |
aside > ul, |
| 1017 |
aside > table, |
| 1018 |
aside > p { |
| 1019 |
margin-bottom: 0.5em; |
| 1020 |
} |
| 1021 |
/* Additional page break settings */ |
| 1022 |
@media print { |
| 1023 |
figcaption, table caption { |
| 1024 |
page-break-before: avoid; |
| 1025 |
} |
| 1026 |
} |
| 1027 |
/* Font size adjustments for print */ |
| 1028 |
@media print { |
| 1029 |
body { font-size: 10pt; line-height: normal; max-width: 96%; } |
| 1030 |
h1 { font-size: 1.72em; padding-top: 1.5em; } /* 1*1.2*1.2*1.2 */ |
| 1031 |
h2 { font-size: 1.44em; padding-top: 1.5em; } /* 1*1.2*1.2 */ |
| 1032 |
h3 { font-size: 1.2em; padding-top: 1.5em; } /* 1*1.2 */ |
| 1033 |
h4 { font-size: 1em; padding-top: 1.5em; } |
| 1034 |
h5, h6 { font-size: 1em; margin: initial; padding: 0.5em 0 0.3em; } |
| 1035 |
} |
| 1036 |
/* Sourcecode margin in print, when there's no pilcrow */ |
| 1037 |
@media print { |
| 1038 |
.artwork, |
| 1039 |
.sourcecode { |
| 1040 |
margin-bottom: 1em; |
| 1041 |
} |
| 1042 |
} |
| 1043 |
/* |
| 1044 |
The margin-left: 0 on <dd> removes all distinction |
| 1045 |
between levels from nested <dl>s. Undo that. |
| 1046 |
*/ |
| 1047 |
dl.olPercent > dd, |
| 1048 |
dd { |
| 1049 |
margin-left: revert; |
| 1050 |
}</style> |
| 1051 |
<link href="rfc-local.css" type="text/css" rel="stylesheet"> |
| 1052 |
<link href="https://dx.doi.org/10.17487/rfc8691" rel="alternate"> |
| 1053 |
<link href="urn:issn:2070-1721" rel="alternate"> |
| 1054 |
<link href="https://datatracker.ietf.org/doc/draft-ietf-ipwave-ipv6-over-80211ocb-52" rel="prev"> |
| 1055 |
</head> |
| 1056 |
<body> |
| 1057 |
<script src="https://www.rfc-editor.org/js/metadata.min.js"></script> |
| 1058 |
<table class="ears"> |
| 1059 |
<thead><tr> |
| 1060 |
<td class="left">RFC 8691</td> |
| 1061 |
<td class="center">IPv6 over 802.11-OCB</td> |
| 1062 |
<td class="right">December 2019</td> |
| 1063 |
</tr></thead> |
| 1064 |
<tfoot><tr> |
| 1065 |
<td class="left">Benamar, et al.</td> |
| 1066 |
<td class="center">Standards Track</td> |
| 1067 |
<td class="right">[Page]</td> |
| 1068 |
</tr></tfoot> |
| 1069 |
</table> |
| 1070 |
<div id="external-metadata" class="document-information"></div> |
| 1071 |
<div id="internal-metadata" class="document-information"> |
| 1072 |
<dl id="identifiers"> |
| 1073 |
<dt class="label-stream">Stream:</dt> |
| 1074 |
<dd class="stream">Internet Engineering Task Force (IETF)</dd> |
| 1075 |
<dt class="label-rfc">RFC:</dt> |
| 1076 |
<dd class="rfc"><a href="https://www.rfc-editor.org/rfc/rfc8691" class="eref">8691</a></dd> |
| 1077 |
<dt class="label-category">Category:</dt> |
| 1078 |
<dd class="category">Standards Track</dd> |
| 1079 |
<dt class="label-published">Published:</dt> |
| 1080 |
<dd class="published"> |
| 1081 |
<time datetime="2019-12" class="published">December 2019</time> |
| 1082 |
</dd> |
| 1083 |
<dt class="label-issn">ISSN:</dt> |
| 1084 |
<dd class="issn">2070-1721</dd> |
| 1085 |
<dt class="label-authors">Authors:</dt> |
| 1086 |
<dd class="authors"> |
| 1087 |
<div class="author"> |
| 1088 |
<div class="author-name">N. Benamar</div> |
| 1089 |
<div class="org">Moulay Ismail University of Meknes</div> |
| 1090 |
</div> |
| 1091 |
<div class="author"> |
| 1092 |
<div class="author-name">J. Härri</div> |
| 1093 |
<div class="org">EURECOM</div> |
| 1094 |
</div> |
| 1095 |
<div class="author"> |
| 1096 |
<div class="author-name">J. Lee</div> |
| 1097 |
<div class="org">Sangmyung University</div> |
| 1098 |
</div> |
| 1099 |
<div class="author"> |
| 1100 |
<div class="author-name">T. Ernst</div> |
| 1101 |
<div class="org">YoGoKo</div> |
| 1102 |
</div> |
| 1103 |
</dd> |
| 1104 |
</dl> |
| 1105 |
</div> |
| 1106 |
<h1 id="rfcnum">RFC 8691</h1> |
| 1107 |
<h1 id="title">Basic Support for IPv6 Networks Operating Outside the Context of a Basic Service Set over IEEE Std 802.11</h1> |
| 1108 |
<section id="section-abstract"> |
| 1109 |
<h2 id="abstract"><a href="#abstract" class="selfRef">Abstract</a></h2> |
| 1110 |
<p id="section-abstract-1"> |
| 1111 |
This document provides methods and settings |
| 1112 |
for using IPv6 to communicate among nodes within range of one another |
| 1113 |
over a single IEEE 802.11-OCB link. Support for these methods and |
| 1114 |
settings require minimal changes to existing stacks. This document |
| 1115 |
also describes limitations associated with using these methods. |
| 1116 |
Optimizations and usage of IPv6 over more complex scenarios |
| 1117 |
are not covered in this specification and are a subject for future work.<a href="#section-abstract-1" class="pilcrow">¶</a></p> |
| 1118 |
</section> |
| 1119 |
<div id="status-of-memo"> |
| 1120 |
<section id="section-boilerplate.1"> |
| 1121 |
<h2 id="name-status-of-this-memo"> |
| 1122 |
<a href="#name-status-of-this-memo" class="section-name selfRef">Status of This Memo</a> |
| 1123 |
</h2> |
| 1124 |
<p id="section-boilerplate.1-1"> |
| 1125 |
This is an Internet Standards Track document.<a href="#section-boilerplate.1-1" class="pilcrow">¶</a></p> |
| 1126 |
<p id="section-boilerplate.1-2"> |
| 1127 |
This document is a product of the Internet Engineering Task Force |
| 1128 |
(IETF). It represents the consensus of the IETF community. It has |
| 1129 |
received public review and has been approved for publication by |
| 1130 |
the Internet Engineering Steering Group (IESG). Further |
| 1131 |
information on Internet Standards is available in Section 2 of |
| 1132 |
RFC 7841.<a href="#section-boilerplate.1-2" class="pilcrow">¶</a></p> |
| 1133 |
<p id="section-boilerplate.1-3"> |
| 1134 |
Information about the current status of this document, any |
| 1135 |
errata, and how to provide feedback on it may be obtained at |
| 1136 |
<span><a href="https://www.rfc-editor.org/info/rfc8691">https://www.rfc-editor.org/info/rfc8691</a></span>.<a href="#section-boilerplate.1-3" class="pilcrow">¶</a></p> |
| 1137 |
</section> |
| 1138 |
</div> |
| 1139 |
<div id="copyright"> |
| 1140 |
<section id="section-boilerplate.2"> |
| 1141 |
<h2 id="name-copyright-notice"> |
| 1142 |
<a href="#name-copyright-notice" class="section-name selfRef">Copyright Notice</a> |
| 1143 |
</h2> |
| 1144 |
<p id="section-boilerplate.2-1"> |
| 1145 |
Copyright (c) 2019 IETF Trust and the persons identified as the |
| 1146 |
document authors. All rights reserved.<a href="#section-boilerplate.2-1" class="pilcrow">¶</a></p> |
| 1147 |
<p id="section-boilerplate.2-2"> |
| 1148 |
This document is subject to BCP 78 and the IETF Trust's Legal |
| 1149 |
Provisions Relating to IETF Documents |
| 1150 |
(<span><a href="https://trustee.ietf.org/license-info">https://trustee.ietf.org/license-info</a></span>) in effect on the date of |
| 1151 |
publication of this document. Please review these documents |
| 1152 |
carefully, as they describe your rights and restrictions with |
| 1153 |
respect to this document. Code Components extracted from this |
| 1154 |
document must include Simplified BSD License text as described in |
| 1155 |
Section 4.e of the Trust Legal Provisions and are provided without |
| 1156 |
warranty as described in the Simplified BSD License.<a href="#section-boilerplate.2-2" class="pilcrow">¶</a></p> |
| 1157 |
</section> |
| 1158 |
</div> |
| 1159 |
<div id="toc"> |
| 1160 |
<section id="section-toc.1"> |
| 1161 |
<a href="#" onclick="scroll(0,0)" class="toplink">▲</a><h2 id="name-table-of-contents"> |
| 1162 |
<a href="#name-table-of-contents" class="section-name selfRef">Table of Contents</a> |
| 1163 |
</h2> |
| 1164 |
<nav class="toc"><ul class="toc ulEmpty"> |
| 1165 |
<li class="toc ulEmpty" id="section-toc.1-1.1"> |
| 1166 |
<p id="section-toc.1-1.1.1"><a href="#section-1" class="xref">1</a>. <a href="#name-introduction" class="xref">Introduction</a><a href="#section-toc.1-1.1.1" class="pilcrow">¶</a></p> |
| 1167 |
</li> |
| 1168 |
<li class="toc ulEmpty" id="section-toc.1-1.2"> |
| 1169 |
<p id="section-toc.1-1.2.1"><a href="#section-2" class="xref">2</a>. <a href="#name-terminology" class="xref">Terminology</a><a href="#section-toc.1-1.2.1" class="pilcrow">¶</a></p> |
| 1170 |
</li> |
| 1171 |
<li class="toc ulEmpty" id="section-toc.1-1.3"> |
| 1172 |
<p id="section-toc.1-1.3.1"><a href="#section-3" class="xref">3</a>. <a href="#name-communication-scenarios-whe" class="xref">Communication Scenarios Where IEEE 802.11-OCB Links Are Used</a><a href="#section-toc.1-1.3.1" class="pilcrow">¶</a></p> |
| 1173 |
</li> |
| 1174 |
<li class="toc ulEmpty" id="section-toc.1-1.4"> |
| 1175 |
<p id="section-toc.1-1.4.1"><a href="#section-4" class="xref">4</a>. <a href="#name-ipv6-over-80211-ocb" class="xref">IPv6 over 802.11-OCB</a><a href="#section-toc.1-1.4.1" class="pilcrow">¶</a></p> |
| 1176 |
<ul class="toc ulEmpty"> |
| 1177 |
<li class="toc ulEmpty" id="section-toc.1-1.4.2.1"> |
| 1178 |
<p id="section-toc.1-1.4.2.1.1"><a href="#section-4.1" class="xref">4.1</a>. <a href="#name-maximum-transmission-unit-m" class="xref">Maximum Transmission Unit (MTU)</a><a href="#section-toc.1-1.4.2.1.1" class="pilcrow">¶</a></p> |
| 1179 |
</li> |
| 1180 |
<li class="toc ulEmpty" id="section-toc.1-1.4.2.2"> |
| 1181 |
<p id="section-toc.1-1.4.2.2.1"><a href="#section-4.2" class="xref">4.2</a>. <a href="#name-frame-format" class="xref">Frame Format</a><a href="#section-toc.1-1.4.2.2.1" class="pilcrow">¶</a></p> |
| 1182 |
</li> |
| 1183 |
<li class="toc ulEmpty" id="section-toc.1-1.4.2.3"> |
| 1184 |
<p id="section-toc.1-1.4.2.3.1"><a href="#section-4.3" class="xref">4.3</a>. <a href="#name-link-local-addresses" class="xref">Link-Local Addresses</a><a href="#section-toc.1-1.4.2.3.1" class="pilcrow">¶</a></p> |
| 1185 |
</li> |
| 1186 |
<li class="toc ulEmpty" id="section-toc.1-1.4.2.4"> |
| 1187 |
<p id="section-toc.1-1.4.2.4.1"><a href="#section-4.4" class="xref">4.4</a>. <a href="#name-stateless-autoconfiguration" class="xref">Stateless Autoconfiguration</a><a href="#section-toc.1-1.4.2.4.1" class="pilcrow">¶</a></p> |
| 1188 |
</li> |
| 1189 |
<li class="toc ulEmpty" id="section-toc.1-1.4.2.5"> |
| 1190 |
<p id="section-toc.1-1.4.2.5.1"><a href="#section-4.5" class="xref">4.5</a>. <a href="#name-address-mapping" class="xref">Address Mapping</a><a href="#section-toc.1-1.4.2.5.1" class="pilcrow">¶</a></p> |
| 1191 |
<ul class="toc ulEmpty"> |
| 1192 |
<li class="toc ulEmpty" id="section-toc.1-1.4.2.5.2.1"> |
| 1193 |
<p id="section-toc.1-1.4.2.5.2.1.1"><a href="#section-4.5.1" class="xref">4.5.1</a>. <a href="#name-address-mapping-unicast" class="xref">Address Mapping -- Unicast</a><a href="#section-toc.1-1.4.2.5.2.1.1" class="pilcrow">¶</a></p> |
| 1194 |
</li> |
| 1195 |
<li class="toc ulEmpty" id="section-toc.1-1.4.2.5.2.2"> |
| 1196 |
<p id="section-toc.1-1.4.2.5.2.2.1"><a href="#section-4.5.2" class="xref">4.5.2</a>. <a href="#name-address-mapping-multicast" class="xref">Address Mapping -- Multicast</a><a href="#section-toc.1-1.4.2.5.2.2.1" class="pilcrow">¶</a></p> |
| 1197 |
</li> |
| 1198 |
</ul> |
| 1199 |
</li> |
| 1200 |
<li class="toc ulEmpty" id="section-toc.1-1.4.2.6"> |
| 1201 |
<p id="section-toc.1-1.4.2.6.1"><a href="#section-4.6" class="xref">4.6</a>. <a href="#name-subnet-structure" class="xref">Subnet Structure</a><a href="#section-toc.1-1.4.2.6.1" class="pilcrow">¶</a></p> |
| 1202 |
</li> |
| 1203 |
</ul> |
| 1204 |
</li> |
| 1205 |
<li class="toc ulEmpty" id="section-toc.1-1.5"> |
| 1206 |
<p id="section-toc.1-1.5.1"><a href="#section-5" class="xref">5</a>. <a href="#name-security-considerations" class="xref">Security Considerations</a><a href="#section-toc.1-1.5.1" class="pilcrow">¶</a></p> |
| 1207 |
<ul class="toc ulEmpty"> |
| 1208 |
<li class="toc ulEmpty" id="section-toc.1-1.5.2.1"> |
| 1209 |
<p id="section-toc.1-1.5.2.1.1"><a href="#section-5.1" class="xref">5.1</a>. <a href="#name-privacy-considerations" class="xref">Privacy Considerations</a><a href="#section-toc.1-1.5.2.1.1" class="pilcrow">¶</a></p> |
| 1210 |
<ul class="toc ulEmpty"> |
| 1211 |
<li class="toc ulEmpty" id="section-toc.1-1.5.2.1.2.1"> |
| 1212 |
<p id="section-toc.1-1.5.2.1.2.1.1"><a href="#section-5.1.1" class="xref">5.1.1</a>. <a href="#name-privacy-risks-of-meaningful" class="xref">Privacy Risks of Meaningful Information in Interface IDs</a><a href="#section-toc.1-1.5.2.1.2.1.1" class="pilcrow">¶</a></p> |
| 1213 |
</li> |
| 1214 |
</ul> |
| 1215 |
</li> |
| 1216 |
<li class="toc ulEmpty" id="section-toc.1-1.5.2.2"> |
| 1217 |
<p id="section-toc.1-1.5.2.2.1"><a href="#section-5.2" class="xref">5.2</a>. <a href="#name-mac-address-and-interface-i" class="xref">MAC Address and Interface ID Generation</a><a href="#section-toc.1-1.5.2.2.1" class="pilcrow">¶</a></p> |
| 1218 |
</li> |
| 1219 |
<li class="toc ulEmpty" id="section-toc.1-1.5.2.3"> |
| 1220 |
<p id="section-toc.1-1.5.2.3.1"><a href="#section-5.3" class="xref">5.3</a>. <a href="#name-pseudonymization-impact-on-" class="xref">Pseudonymization Impact on Confidentiality and Trust</a><a href="#section-toc.1-1.5.2.3.1" class="pilcrow">¶</a></p> |
| 1221 |
</li> |
| 1222 |
</ul> |
| 1223 |
</li> |
| 1224 |
<li class="toc ulEmpty" id="section-toc.1-1.6"> |
| 1225 |
<p id="section-toc.1-1.6.1"><a href="#section-6" class="xref">6</a>. <a href="#name-iana-considerations" class="xref">IANA Considerations</a><a href="#section-toc.1-1.6.1" class="pilcrow">¶</a></p> |
| 1226 |
</li> |
| 1227 |
<li class="toc ulEmpty" id="section-toc.1-1.7"> |
| 1228 |
<p id="section-toc.1-1.7.1"><a href="#section-7" class="xref">7</a>. <a href="#name-references" class="xref">References</a><a href="#section-toc.1-1.7.1" class="pilcrow">¶</a></p> |
| 1229 |
<ul class="toc ulEmpty"> |
| 1230 |
<li class="toc ulEmpty" id="section-toc.1-1.7.2.1"> |
| 1231 |
<p id="section-toc.1-1.7.2.1.1"><a href="#section-7.1" class="xref">7.1</a>. <a href="#name-normative-references" class="xref">Normative References</a><a href="#section-toc.1-1.7.2.1.1" class="pilcrow">¶</a></p> |
| 1232 |
</li> |
| 1233 |
<li class="toc ulEmpty" id="section-toc.1-1.7.2.2"> |
| 1234 |
<p id="section-toc.1-1.7.2.2.1"><a href="#section-7.2" class="xref">7.2</a>. <a href="#name-informative-references" class="xref">Informative References</a><a href="#section-toc.1-1.7.2.2.1" class="pilcrow">¶</a></p> |
| 1235 |
</li> |
| 1236 |
</ul> |
| 1237 |
</li> |
| 1238 |
<li class="toc ulEmpty" id="section-toc.1-1.8"> |
| 1239 |
<p id="section-toc.1-1.8.1"><a href="#section-appendix.a" class="xref">Appendix A</a>. <a href="#name-80211p" class="xref">802.11p</a><a href="#section-toc.1-1.8.1" class="pilcrow">¶</a></p> |
| 1240 |
</li> |
| 1241 |
<li class="toc ulEmpty" id="section-toc.1-1.9"> |
| 1242 |
<p id="section-toc.1-1.9.1"><a href="#section-appendix.b" class="xref">Appendix B</a>. <a href="#name-aspects-introduced-by-ocb-m" class="xref">Aspects Introduced by OCB Mode to 802.11</a><a href="#section-toc.1-1.9.1" class="pilcrow">¶</a></p> |
| 1243 |
</li> |
| 1244 |
<li class="toc ulEmpty" id="section-toc.1-1.10"> |
| 1245 |
<p id="section-toc.1-1.10.1"><a href="#section-appendix.c" class="xref">Appendix C</a>. <a href="#name-changes-needed-on-an-80211a" class="xref">Changes Needed on an 802.11a Software Driver to Become an 802.11-OCB Driver</a><a href="#section-toc.1-1.10.1" class="pilcrow">¶</a></p> |
| 1246 |
</li> |
| 1247 |
<li class="toc ulEmpty" id="section-toc.1-1.11"> |
| 1248 |
<p id="section-toc.1-1.11.1"><a href="#section-appendix.d" class="xref">Appendix D</a>. <a href="#name-protocol-layering" class="xref">Protocol Layering</a><a href="#section-toc.1-1.11.1" class="pilcrow">¶</a></p> |
| 1249 |
</li> |
| 1250 |
<li class="toc ulEmpty" id="section-toc.1-1.12"> |
| 1251 |
<p id="section-toc.1-1.12.1"><a href="#section-appendix.e" class="xref">Appendix E</a>. <a href="#name-design-considerations" class="xref">Design Considerations</a><a href="#section-toc.1-1.12.1" class="pilcrow">¶</a></p> |
| 1252 |
</li> |
| 1253 |
<li class="toc ulEmpty" id="section-toc.1-1.13"> |
| 1254 |
<p id="section-toc.1-1.13.1"><a href="#section-appendix.f" class="xref">Appendix F</a>. <a href="#name-ieee-80211-messages-transmi" class="xref">IEEE 802.11 Messages Transmitted in OCB Mode</a><a href="#section-toc.1-1.13.1" class="pilcrow">¶</a></p> |
| 1255 |
</li> |
| 1256 |
<li class="toc ulEmpty" id="section-toc.1-1.14"> |
| 1257 |
<p id="section-toc.1-1.14.1"><a href="#section-appendix.g" class="xref">Appendix G</a>. <a href="#name-examples-of-packet-formats" class="xref">Examples of Packet Formats</a><a href="#section-toc.1-1.14.1" class="pilcrow">¶</a></p> |
| 1258 |
<ul class="toc ulEmpty"> |
| 1259 |
<li class="toc ulEmpty" id="section-toc.1-1.14.2.1"> |
| 1260 |
<p id="section-toc.1-1.14.2.1.1"><a href="#section-g.1" class="xref">G.1</a>. <a href="#name-capture-in-monitor-mode" class="xref">Capture in Monitor Mode</a><a href="#section-toc.1-1.14.2.1.1" class="pilcrow">¶</a></p> |
| 1261 |
</li> |
| 1262 |
<li class="toc ulEmpty" id="section-toc.1-1.14.2.2"> |
| 1263 |
<p id="section-toc.1-1.14.2.2.1"><a href="#section-g.2" class="xref">G.2</a>. <a href="#name-capture-in-normal-mode" class="xref">Capture in Normal Mode</a><a href="#section-toc.1-1.14.2.2.1" class="pilcrow">¶</a></p> |
| 1264 |
</li> |
| 1265 |
</ul> |
| 1266 |
</li> |
| 1267 |
<li class="toc ulEmpty" id="section-toc.1-1.15"> |
| 1268 |
<p id="section-toc.1-1.15.1"><a href="#section-appendix.h" class="xref">Appendix H</a>. <a href="#name-extra-terminology" class="xref">Extra Terminology</a><a href="#section-toc.1-1.15.1" class="pilcrow">¶</a></p> |
| 1269 |
</li> |
| 1270 |
<li class="toc ulEmpty" id="section-toc.1-1.16"> |
| 1271 |
<p id="section-toc.1-1.16.1"><a href="#section-appendix.i" class="xref">Appendix I</a>. <a href="#name-neighbor-discovery-nd-poten" class="xref">Neighbor Discovery (ND) Potential Issues in Wireless Links</a><a href="#section-toc.1-1.16.1" class="pilcrow">¶</a></p> |
| 1272 |
</li> |
| 1273 |
<li class="toc ulEmpty" id="section-toc.1-1.17"> |
| 1274 |
<p id="section-toc.1-1.17.1"><a href="#section-appendix.j" class="xref"></a><a href="#name-acknowledgements" class="xref">Acknowledgements</a><a href="#section-toc.1-1.17.1" class="pilcrow">¶</a></p> |
| 1275 |
</li> |
| 1276 |
<li class="toc ulEmpty" id="section-toc.1-1.18"> |
| 1277 |
<p id="section-toc.1-1.18.1"><a href="#section-appendix.k" class="xref"></a><a href="#name-contributors" class="xref">Contributors</a><a href="#section-toc.1-1.18.1" class="pilcrow">¶</a></p> |
| 1278 |
</li> |
| 1279 |
<li class="toc ulEmpty" id="section-toc.1-1.19"> |
| 1280 |
<p id="section-toc.1-1.19.1"><a href="#section-appendix.l" class="xref"></a><a href="#name-authors-addresses" class="xref">Authors' Addresses</a><a href="#section-toc.1-1.19.1" class="pilcrow">¶</a></p> |
| 1281 |
</li> |
| 1282 |
</ul> |
| 1283 |
</nav> |
| 1284 |
</section> |
| 1285 |
</div> |
| 1286 |
<section id="section-1"> |
| 1287 |
<h2 id="name-introduction"> |
| 1288 |
<a href="#section-1" class="section-number selfRef">1. </a><a href="#name-introduction" class="section-name selfRef">Introduction</a> |
| 1289 |
</h2> |
| 1290 |
<p id="section-1-1"> |
| 1291 |
This document provides a baseline for using IPv6 to |
| 1292 |
communicate among nodes in range of one another over a single IEEE 802.11-OCB link |
| 1293 |
<span>[<a href="#IEEE-802.11-2016" class="xref">IEEE-802.11-2016</a>]</span> (a.k.a., 802.11p; |
| 1294 |
see Appendices <a href="#i802.11p" class="xref">A</a>, |
| 1295 |
<a href="#introduced-by-OCB" class="xref">B</a>, and <a href="#software-changes" class="xref">C</a>) |
| 1296 |
with minimal changes to existing stacks. Moreover, the document |
| 1297 |
identifies the limitations |
| 1298 |
of such usage. Concretely, the document describes the layering |
| 1299 |
of IPv6 networking on top of the IEEE Std 802.11 MAC layer or an IEEE Std 802.3 |
| 1300 |
MAC layer with a frame translation underneath. The resulting stack is derived from IPv6 |
| 1301 |
over Ethernet <span>[<a href="#RFC2464" class="xref">RFC2464</a>]</span> but operates over 802.11-OCB to provide at least P2P (point-to-point) connectivity |
| 1302 |
using IPv6 Neighbor Discovery (ND) and link-local addresses.<a href="#section-1-1" class="pilcrow">¶</a></p> |
| 1303 |
<p id="section-1-2"> |
| 1304 |
The IPv6 network layer operates on 802.11-OCB in the same |
| 1305 |
manner as operating on the Ethernet with the following |
| 1306 |
exceptions:<a href="#section-1-2" class="pilcrow">¶</a></p> |
| 1307 |
<ul> |
| 1308 |
<li id="section-1-3.1"> |
| 1309 |
Exceptions due to the different operation of the IPv6 network |
| 1310 |
layer on 802.11 compared to the Ethernet. The operation of IP |
| 1311 |
on Ethernet is described in <span>[<a href="#RFC1042" class="xref">RFC1042</a>]</span> and <span>[<a href="#RFC2464" class="xref">RFC2464</a>]</span>.<a href="#section-1-3.1" class="pilcrow">¶</a> |
| 1312 |
</li> |
| 1313 |
<li id="section-1-3.2"> |
| 1314 |
Exceptions due to the OCB nature of 802.11-OCB compared to |
| 1315 |
802.11. This has impacts on security, privacy, subnet |
| 1316 |
structure, and movement detection. Security and |
| 1317 |
privacy recommendations are discussed in Sections <a href="#slaac" class="xref">4.4</a> and <a href="#Security" class="xref">5</a>. The subnet structure is described |
| 1318 |
in <a href="#subnet-structure" class="xref">Section 4.6</a>. The movement |
| 1319 |
detection on OCB links is not described in this document. |
| 1320 |
Likewise, ND extensions and IP Wireless Access in Vehicular |
| 1321 |
Environments (IPWAVE) optimizations for vehicular communications are |
| 1322 |
not in scope of this document. The expectation is that further specifications will be edited to cover |
| 1323 |
more complex vehicular networking scenarios.<a href="#section-1-3.2" class="pilcrow">¶</a> |
| 1324 |
</li> |
| 1325 |
</ul> |
| 1326 |
<p id="section-1-4"> |
| 1327 |
The reader may refer to <span>[<a href="#I-D.ietf-ipwave-vehicular-networking" class="xref">IPWAVE</a>]</span> for an overview of |
| 1328 |
problems related to running IPv6 over 802.11-OCB. It is out of scope |
| 1329 |
of this document to reiterate those problems.<a href="#section-1-4" class="pilcrow">¶</a></p> |
| 1330 |
</section> |
| 1331 |
<div id="terminology"> |
| 1332 |
<section id="section-2"> |
| 1333 |
<h2 id="name-terminology"> |
| 1334 |
<a href="#section-2" class="section-number selfRef">2. </a><a href="#name-terminology" class="section-name selfRef">Terminology</a> |
| 1335 |
</h2> |
| 1336 |
<p id="section-2-1"> |
| 1337 |
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>", |
| 1338 |
"<span class="bcp14">MAY</span>", and "<span class="bcp14">OPTIONAL</span>" in this document are to be interpreted as |
| 1339 |
described in BCP 14 <span>[<a href="#RFC2119" class="xref">RFC2119</a>]</span> <span>[<a href="#RFC8174" class="xref">RFC8174</a>]</span> |
| 1340 |
when, and only when, they appear in all capitals, as shown here.<a href="#section-2-1" class="pilcrow">¶</a></p> |
| 1341 |
<p id="section-2-2"> |
| 1342 |
The document makes uses of the following terms:<a href="#section-2-2" class="pilcrow">¶</a></p> |
| 1343 |
<dl class="dlNewline" id="section-2-3"> |
| 1344 |
<dt id="section-2-3.1">IP-OBU (Internet Protocol On-Board Unit):</dt> |
| 1345 |
<dd id="section-2-3.2">An IP-OBU denotes a |
| 1346 |
computer situated in a vehicle such as a car, bicycle, |
| 1347 |
or similar. It has at least one IP interface that runs in |
| 1348 |
mode OCB of 802.11 and has an "OBU" transceiver. See |
| 1349 |
the definition of the term "OBU" in <a href="#extra-terminology" class="xref">Appendix H</a>.<a href="#section-2-3.2" class="pilcrow">¶</a> |
| 1350 |
</dd> |
| 1351 |
<dt id="section-2-3.3">IP-RSU (IP Roadside Unit):</dt> |
| 1352 |
<dd id="section-2-3.4">An IP-RSU is situated along the |
| 1353 |
road. It has at least two distinct IP-enabled interfaces. The |
| 1354 |
wireless PHY/MAC layer of at least one of its IP-enabled |
| 1355 |
interfaces is configured to operate in 802.11-OCB mode. An |
| 1356 |
IP-RSU communicates with the IP-OBU over an 802.11 |
| 1357 |
wireless link operating in OCB mode. An IP-RSU is similar to |
| 1358 |
an Access Network Router (ANR), defined in <span>[<a href="#RFC3753" class="xref">RFC3753</a>]</span>, and a Wireless Termination Point (WTP), |
| 1359 |
defined in <span>[<a href="#RFC5415" class="xref">RFC5415</a>]</span>.<a href="#section-2-3.4" class="pilcrow">¶</a> |
| 1360 |
</dd> |
| 1361 |
<dt id="section-2-3.5">OCB (outside the context of a Basic Service Set - BSS):</dt> |
| 1362 |
<dd id="section-2-3.6">This is a mode |
| 1363 |
of operation in which a station (STA) is not a member of a BSS and does |
| 1364 |
not utilize IEEE Std 802.11 authentication, association, or |
| 1365 |
data confidentiality.<a href="#section-2-3.6" class="pilcrow">¶</a> |
| 1366 |
</dd> |
| 1367 |
<dt id="section-2-3.7">802.11-OCB:</dt> |
| 1368 |
<dd id="section-2-3.8"> This refers to the mode specified in IEEE Std 802.11-2016 when the |
| 1369 |
MIB attribute dot11OCBActivited is 'true'.<a href="#section-2-3.8" class="pilcrow">¶</a> |
| 1370 |
</dd> |
| 1371 |
</dl> |
| 1372 |
</section> |
| 1373 |
</div> |
| 1374 |
<section id="section-3"> |
| 1375 |
<h2 id="name-communication-scenarios-whe"> |
| 1376 |
<a href="#section-3" class="section-number selfRef">3. </a><a href="#name-communication-scenarios-whe" class="section-name selfRef">Communication Scenarios Where IEEE 802.11-OCB Links Are Used</a> |
| 1377 |
</h2> |
| 1378 |
<p id="section-3-1"> |
| 1379 |
IEEE 802.11-OCB networks are used for vehicular |
| 1380 |
communications as 'Wireless Access in Vehicular |
| 1381 |
Environments'. In particular, we refer the reader to <span>[<a href="#I-D.ietf-ipwave-vehicular-networking" class="xref">IPWAVE</a>]</span>, which lists |
| 1382 |
some scenarios and requirements for IP in Intelligent |
| 1383 |
Transportation Systems (ITS).<a href="#section-3-1" class="pilcrow">¶</a></p> |
| 1384 |
<p id="section-3-2"> |
| 1385 |
The link model is the following: STA --- 802.11-OCB --- STA. |
| 1386 |
In vehicular networks, STAs can be IP-RSUs and/or IP-OBUs. |
| 1387 |
All links are assumed to be P2P, and multiple links can be on one radio |
| 1388 |
interface. While 802.11-OCB is clearly specified and a legacy IPv6 |
| 1389 |
stack can operate on such links, the use of the operating environment |
| 1390 |
(vehicular networks) brings in new perspectives.<a href="#section-3-2" class="pilcrow">¶</a></p> |
| 1391 |
</section> |
| 1392 |
<section id="section-4"> |
| 1393 |
<h2 id="name-ipv6-over-80211-ocb"> |
| 1394 |
<a href="#section-4" class="section-number selfRef">4. </a><a href="#name-ipv6-over-80211-ocb" class="section-name selfRef">IPv6 over 802.11-OCB</a> |
| 1395 |
</h2> |
| 1396 |
<div id="MTU"> |
| 1397 |
<section id="section-4.1"> |
| 1398 |
<h3 id="name-maximum-transmission-unit-m"> |
| 1399 |
<a href="#section-4.1" class="section-number selfRef">4.1. </a><a href="#name-maximum-transmission-unit-m" class="section-name selfRef">Maximum Transmission Unit (MTU)</a> |
| 1400 |
</h3> |
| 1401 |
<p id="section-4.1-1"> |
| 1402 |
The default MTU for IP packets on 802.11-OCB is inherited |
| 1403 |
from <span>[<a href="#RFC2464" class="xref">RFC2464</a>]</span> and, as such, is 1500 octets. |
| 1404 |
As noted in <span>[<a href="#RFC8200" class="xref">RFC8200</a>]</span>, every link on the Internet must have a |
| 1405 |
minimum MTU of 1280 octets and must follow the other |
| 1406 |
recommendations, especially with regard to fragmentation.<a href="#section-4.1-1" class="pilcrow">¶</a></p> |
| 1407 |
</section> |
| 1408 |
</div> |
| 1409 |
<section id="section-4.2"> |
| 1410 |
<h3 id="name-frame-format"> |
| 1411 |
<a href="#section-4.2" class="section-number selfRef">4.2. </a><a href="#name-frame-format" class="section-name selfRef">Frame Format</a> |
| 1412 |
</h3> |
| 1413 |
<p id="section-4.2-1"> |
| 1414 |
IP packets <span class="bcp14">MUST</span> be transmitted over 802.11-OCB media as QoS |
| 1415 |
data frames whose format is specified in an IEEE 802.11 spec |
| 1416 |
<span>[<a href="#IEEE-802.11-2016" class="xref">IEEE-802.11-2016</a>]</span>.<a href="#section-4.2-1" class="pilcrow">¶</a></p> |
| 1417 |
<p id="section-4.2-2"> |
| 1418 |
The IPv6 packet transmitted on 802.11-OCB is |
| 1419 |
immediately preceded by a Logical Link Control (LLC) header |
| 1420 |
and an 802.11 header. In the LLC header and in accordance |
| 1421 |
with EtherType Protocol Discrimination (EPD; see <a href="#epd" class="xref">Appendix D</a>), the value of the Type field <span class="bcp14">MUST</span> be set to |
| 1422 |
0x86DD (IPv6). The mapping to the 802.11 data service <span class="bcp14">SHOULD</span> |
| 1423 |
use a 'priority' value of 1 (QoS with a 'Background' user priority), |
| 1424 |
reserving higher priority values for safety-critical and time-sensitive |
| 1425 |
traffic, including the ones listed in <span>[<a href="#ETSI-sec-archi" class="xref">ETSI-sec-archi</a>]</span>.<a href="#section-4.2-2" class="pilcrow">¶</a></p> |
| 1426 |
<p id="section-4.2-3"> |
| 1427 |
To simplify the Application Programming Interface (API) |
| 1428 |
between the operating system and the 802.11-OCB media, |
| 1429 |
device drivers <span class="bcp14">MAY</span> implement IPv6 over Ethernet as per <span>[<a href="#RFC2464" class="xref">RFC2464</a>]</span> |
| 1430 |
and then a frame translation from 802.3 to 802.11 in order |
| 1431 |
to minimize the code changes.<a href="#section-4.2-3" class="pilcrow">¶</a></p> |
| 1432 |
</section> |
| 1433 |
<div id="ll"> |
| 1434 |
<section id="section-4.3"> |
| 1435 |
<h3 id="name-link-local-addresses"> |
| 1436 |
<a href="#section-4.3" class="section-number selfRef">4.3. </a><a href="#name-link-local-addresses" class="section-name selfRef">Link-Local Addresses</a> |
| 1437 |
</h3> |
| 1438 |
<p id="section-4.3-1"> |
| 1439 |
There are several types of IPv6 addresses <span>[<a href="#RFC4291" class="xref">RFC4291</a>]</span> <span>[<a href="#RFC4193" class="xref">RFC4193</a>]</span> that may be |
| 1440 |
assigned to an 802.11-OCB interface. Among these types of |
| 1441 |
addresses, only the IPv6 link-local addresses can be formed |
| 1442 |
using an EUI-64 identifier, particularly during transition |
| 1443 |
time (the period of time before an interface starts using an address |
| 1444 |
different from the LL one).<a href="#section-4.3-1" class="pilcrow">¶</a></p> |
| 1445 |
<p id="section-4.3-2"> |
| 1446 |
If the IPv6 link-local address is formed using an EUI-64 |
| 1447 |
identifier, then the mechanism for forming that address is |
| 1448 |
the same mechanism as that used to form an IPv6 link-local |
| 1449 |
address on Ethernet links. Moreover, regardless of whether the interface |
| 1450 |
identifier is derived from the EUI-64 identifier, its length is 64 bits, |
| 1451 |
as is the case for the Ethernet <span>[<a href="#RFC2464" class="xref">RFC2464</a>]</span>.<a href="#section-4.3-2" class="pilcrow">¶</a></p> |
| 1452 |
</section> |
| 1453 |
</div> |
| 1454 |
<div id="slaac"> |
| 1455 |
<section id="section-4.4"> |
| 1456 |
<h3 id="name-stateless-autoconfiguration"> |
| 1457 |
<a href="#section-4.4" class="section-number selfRef">4.4. </a><a href="#name-stateless-autoconfiguration" class="section-name selfRef">Stateless Autoconfiguration</a> |
| 1458 |
</h3> |
| 1459 |
<p id="section-4.4-1"> |
| 1460 |
The steps a host takes in deciding how to |
| 1461 |
autoconfigure its interfaces in IPv6 are described |
| 1462 |
in <span>[<a href="#RFC4862" class="xref">RFC4862</a>]</span>. This section describes |
| 1463 |
the formation of Interface Identifiers for 'Global' or 'Unique Local' IPv6 addresses. Interface Identifiers |
| 1464 |
for 'link-local' IPv6 addresses are discussed in <a href="#ll" class="xref">Section 4.3</a>.<a href="#section-4.4-1" class="pilcrow">¶</a></p> |
| 1465 |
<p id="section-4.4-2"> |
| 1466 |
The <span class="bcp14">RECOMMENDED</span> method for forming |
| 1467 |
stable Interface Identifiers (IIDs) is described in <span>[<a href="#RFC8064" class="xref">RFC8064</a>]</span>. The method of forming IIDs described in |
| 1468 |
<span><a href="https://www.rfc-editor.org/rfc/rfc2464#section-4" class="relref">Section 4</a> of [<a href="#RFC2464" class="xref">RFC2464</a>]</span> <span class="bcp14">MAY</span> be used during |
| 1469 |
transition time, particularly for IPv6 link-local |
| 1470 |
addresses. Regardless of the method used to form the IID, |
| 1471 |
its length is 64 bits, similarly to IPv6 over Ethernet <span>[<a href="#RFC2464" class="xref">RFC2464</a>]</span>.<a href="#section-4.4-2" class="pilcrow">¶</a></p> |
| 1472 |
<p id="section-4.4-3"> |
| 1473 |
The bits in the IID have no specific meaning, |
| 1474 |
and the identifier should be treated as an opaque value. |
| 1475 |
The bits 'Universal' and 'Group' in the identifier of an |
| 1476 |
802.11-OCB interface, which is an IEEE link-layer address, are |
| 1477 |
significant. The details of this significance are |
| 1478 |
described in <span>[<a href="#RFC7136" class="xref">RFC7136</a>]</span>.<a href="#section-4.4-3" class="pilcrow">¶</a></p> |
| 1479 |
<p id="section-4.4-4"> |
| 1480 |
Semantically opaque IIDs, instead of |
| 1481 |
meaningful IIDs derived from a valid and |
| 1482 |
meaningful MAC address (<span>[<a href="#RFC2464" class="xref">RFC2464</a>], <a href="https://www.rfc-editor.org/rfc/rfc2464#section-4" class="relref">Section 4</a></span>), help avoid certain privacy risks (see the risks |
| 1483 |
mentioned in <a href="#privacy-opaque-iid" class="xref">Section 5.1.1</a>). If |
| 1484 |
semantically opaque IIDs are needed, they |
| 1485 |
may be generated using the method for generating |
| 1486 |
semantically opaque IIDs with IPv6 |
| 1487 |
Stateless Address Autoconfiguration given in <span>[<a href="#RFC7217" class="xref">RFC7217</a>]</span>. Typically, an opaque IID is formed starting from identifiers different |
| 1488 |
from the MAC addresses and from cryptographically strong |
| 1489 |
material. Thus, privacy-sensitive information is absent |
| 1490 |
from Interface IDs because it is impossible to calculate |
| 1491 |
back the initial value from which the Interface ID was first |
| 1492 |
generated.<a href="#section-4.4-4" class="pilcrow">¶</a></p> |
| 1493 |
<p id="section-4.4-5"> |
| 1494 |
Some applications that use IPv6 packets on 802.11-OCB links |
| 1495 |
(among other link types) may benefit from IPv6 addresses |
| 1496 |
whose IIDs don't change too often. It is |
| 1497 |
<span class="bcp14">RECOMMENDED</span> to use the mechanisms described in <span>[<a href="#RFC7217" class="xref">RFC7217</a>]</span> to |
| 1498 |
permit the use of stable IIDs that do not |
| 1499 |
change within one subnet prefix. A possible source for the |
| 1500 |
Net_Iface parameter is a virtual interface name or logical |
| 1501 |
interface name that is decided by a local administrator.<a href="#section-4.4-5" class="pilcrow">¶</a></p> |
| 1502 |
</section> |
| 1503 |
</div> |
| 1504 |
<section id="section-4.5"> |
| 1505 |
<h3 id="name-address-mapping"> |
| 1506 |
<a href="#section-4.5" class="section-number selfRef">4.5. </a><a href="#name-address-mapping" class="section-name selfRef">Address Mapping</a> |
| 1507 |
</h3> |
| 1508 |
<p id="section-4.5-1"> |
| 1509 |
Unicast and multicast address mapping <span class="bcp14">MUST</span> follow the |
| 1510 |
procedures specified for Ethernet interfaces described in Sections <a href="https://www.rfc-editor.org/rfc/rfc2464#section-6" class="relref">6</a> and <a href="https://www.rfc-editor.org/rfc/rfc2464#section-7" class="relref">7</a> of <span>[<a href="#RFC2464" class="xref">RFC2464</a>]</span>.<a href="#section-4.5-1" class="pilcrow">¶</a></p> |
| 1511 |
<section id="section-4.5.1"> |
| 1512 |
<h4 id="name-address-mapping-unicast"> |
| 1513 |
<a href="#section-4.5.1" class="section-number selfRef">4.5.1. </a><a href="#name-address-mapping-unicast" class="section-name selfRef">Address Mapping -- Unicast</a> |
| 1514 |
</h4> |
| 1515 |
<p id="section-4.5.1-1"> |
| 1516 |
This document is scoped for Address Resolution (AR) and Duplicate Address Detection (DAD) per <span>[<a href="#RFC4862" class="xref">RFC4862</a>]</span>.<a href="#section-4.5.1-1" class="pilcrow">¶</a></p> |
| 1517 |
</section> |
| 1518 |
<div id="address-mapping-multicast"> |
| 1519 |
<section id="section-4.5.2"> |
| 1520 |
<h4 id="name-address-mapping-multicast"> |
| 1521 |
<a href="#section-4.5.2" class="section-number selfRef">4.5.2. </a><a href="#name-address-mapping-multicast" class="section-name selfRef">Address Mapping -- Multicast</a> |
| 1522 |
</h4> |
| 1523 |
<p id="section-4.5.2-1"> |
| 1524 |
The multicast address mapping is performed according to |
| 1525 |
the method specified in <span><a href="https://www.rfc-editor.org/rfc/rfc2464#section-7" class="relref">Section 7</a> of [<a href="#RFC2464" class="xref">RFC2464</a>]</span>. The meaning of the value "33-33" |
| 1526 |
mentioned there is |
| 1527 |
defined in <span><a href="https://www.rfc-editor.org/rfc/rfc7042#section-2.3.1" class="relref">Section 2.3.1</a> of [<a href="#RFC7042" class="xref">RFC7042</a>]</span>.<a href="#section-4.5.2-1" class="pilcrow">¶</a></p> |
| 1528 |
<p id="section-4.5.2-2"> |
| 1529 |
Transmitting IPv6 packets to multicast destinations over |
| 1530 |
802.11 links proved to have some performance issues <span>[<a href="#I-D.ietf-mboned-ieee802-mcast-problems" class="xref">IEEE802-MCAST</a>]</span>. These |
| 1531 |
issues may be exacerbated in OCB mode. |
| 1532 |
Future improvement to this specification should consider solutions for these problems.<a href="#section-4.5.2-2" class="pilcrow">¶</a></p> |
| 1533 |
</section> |
| 1534 |
</div> |
| 1535 |
</section> |
| 1536 |
<div id="subnet-structure"> |
| 1537 |
<section id="section-4.6"> |
| 1538 |
<h3 id="name-subnet-structure"> |
| 1539 |
<a href="#section-4.6" class="section-number selfRef">4.6. </a><a href="#name-subnet-structure" class="section-name selfRef">Subnet Structure</a> |
| 1540 |
</h3> |
| 1541 |
<p id="section-4.6-1"> |
| 1542 |
When vehicles are in close range, a subnet may be formed over |
| 1543 |
802.11-OCB interfaces (not by their in-vehicle interfaces). |
| 1544 |
A Prefix List conceptual data structure (<span>[<a href="#RFC4861" class="xref">RFC4861</a>], <a href="https://www.rfc-editor.org/rfc/rfc4861#section-5.1" class="relref">Section 5.1</a></span>) is maintained for each |
| 1545 |
802.11-OCB interface.<a href="#section-4.6-1" class="pilcrow">¶</a></p> |
| 1546 |
<p id="section-4.6-2"> |
| 1547 |
The IPv6 Neighbor Discovery protocol (ND) requires reflexive properties |
| 1548 |
(bidirectional connectivity), which is generally, though not always, the case for P2P OCB links. |
| 1549 |
IPv6 ND also requires transitive properties for DAD and AR, so an IPv6 subnet can be mapped |
| 1550 |
on an OCB network only if all nodes in the network share a single |
| 1551 |
physical broadcast domain. The extension to IPv6 ND operating on a |
| 1552 |
subnet that covers multiple OCB links and does not fully overlap |
| 1553 |
(i.e., non-broadcast multi-access (NBMA)) is not in scope of this document. |
| 1554 |
Finally, IPv6 ND requires permanent connectivity of all nodes in the subnet |
| 1555 |
to defend their addresses -- in other words, very stable network conditions.<a href="#section-4.6-2" class="pilcrow">¶</a></p> |
| 1556 |
<p id="section-4.6-3"> |
| 1557 |
The structure of this subnet is ephemeral in that it is |
| 1558 |
strongly influenced by the mobility of vehicles: the hidden |
| 1559 |
terminal effects appear, and the 802.11 networks in OCB mode may |
| 1560 |
be considered ad hoc networks with an addressing model, |
| 1561 |
as described in <span>[<a href="#RFC5889" class="xref">RFC5889</a>]</span>. On the other hand, |
| 1562 |
the structure of the internal subnets in each vehicle is |
| 1563 |
relatively stable.<a href="#section-4.6-3" class="pilcrow">¶</a></p> |
| 1564 |
<p id="section-4.6-4"> |
| 1565 |
As recommended in <span>[<a href="#RFC5889" class="xref">RFC5889</a>]</span>, when the timing |
| 1566 |
requirements are very strict (e.g., fast-drive-through IP-RSU |
| 1567 |
coverage), no on-link subnet prefix should be configured on |
| 1568 |
an 802.11-OCB interface. In such cases, the exclusive use |
| 1569 |
of IPv6 link-local addresses is <span class="bcp14">RECOMMENDED</span>.<a href="#section-4.6-4" class="pilcrow">¶</a></p> |
| 1570 |
<p id="section-4.6-5"> |
| 1571 |
Additionally, even if the timing requirements are not very |
| 1572 |
strict (e.g., the moving subnet formed by two following |
| 1573 |
vehicles is stable, a fixed IP-RSU is absent), the subnet is |
| 1574 |
disconnected from the Internet (i.e., a default route is absent), |
| 1575 |
and the addressing peers are equally qualified (that is, it is impossible |
| 1576 |
to determine whether some vehicle owns and distributes |
| 1577 |
addresses to others), the use of link-local addresses is |
| 1578 |
<span class="bcp14">RECOMMENDED</span>.<a href="#section-4.6-5" class="pilcrow">¶</a></p> |
| 1579 |
<p id="section-4.6-6"> |
| 1580 |
The baseline ND protocol <span>[<a href="#RFC4861" class="xref">RFC4861</a>]</span> <span class="bcp14">MUST</span> be supported over 802.11-OCB links. |
| 1581 |
Transmitting ND packets may prove to have some performance |
| 1582 |
issues, as mentioned in <a href="#address-mapping-multicast" class="xref">Section 4.5.2</a> and |
| 1583 |
<a href="#nd-wireless" class="xref">Appendix I</a>. |
| 1584 |
These issues may be exacerbated in OCB mode. |
| 1585 |
Solutions for these problems should consider the OCB mode |
| 1586 |
of operation. Future solutions to OCB should consider solutions |
| 1587 |
for avoiding broadcast. The best of current knowledge |
| 1588 |
indicates the kinds of issues that may arise with ND in |
| 1589 |
OCB mode; they are described in <a href="#nd-wireless" class="xref">Appendix I</a>.<a href="#section-4.6-6" class="pilcrow">¶</a></p> |
| 1590 |
<p id="section-4.6-7"> |
| 1591 |
Protocols like Mobile IPv6 <span>[<a href="#RFC6275" class="xref">RFC6275</a>]</span> |
| 1592 |
<span>[<a href="#RFC3963" class="xref">RFC3963</a>]</span> and |
| 1593 |
DNAv6 <span>[<a href="#RFC6059" class="xref">RFC6059</a>]</span>, which depend on timely |
| 1594 |
movement detection, might need additional tuning work to |
| 1595 |
handle the lack of link-layer notifications during handover. |
| 1596 |
This topic is left for further study.<a href="#section-4.6-7" class="pilcrow">¶</a></p> |
| 1597 |
</section> |
| 1598 |
</div> |
| 1599 |
</section> |
| 1600 |
<div id="Security"> |
| 1601 |
<section id="section-5"> |
| 1602 |
<h2 id="name-security-considerations"> |
| 1603 |
<a href="#section-5" class="section-number selfRef">5. </a><a href="#name-security-considerations" class="section-name selfRef">Security Considerations</a> |
| 1604 |
</h2> |
| 1605 |
<p id="section-5-1"> |
| 1606 |
Any security mechanism at the IP layer or above that may be |
| 1607 |
implemented for the general case of IPv6 may also be implemented |
| 1608 |
for IPv6 operating over 802.11-OCB.<a href="#section-5-1" class="pilcrow">¶</a></p> |
| 1609 |
<p id="section-5-2"> |
| 1610 |
The OCB operation does not use existing 802.11 |
| 1611 |
link-layer security mechanisms. There is no encryption |
| 1612 |
applied below the network layer running on 802.11-OCB. At |
| 1613 |
the application layer, the IEEE 1609.2 document <span>[<a href="#IEEE-1609.2" class="xref">IEEE-1609.2</a>]</span> provides security services for |
| 1614 |
certain applications to use; application-layer mechanisms are |
| 1615 |
out of scope of this document. On the other hand, a security |
| 1616 |
mechanism provided at the networking layer, such as IPsec <span>[<a href="#RFC4301" class="xref">RFC4301</a>]</span>, may provide data security protection to a |
| 1617 |
wider range of applications.<a href="#section-5-2" class="pilcrow">¶</a></p> |
| 1618 |
<p id="section-5-3"> |
| 1619 |
802.11-OCB does not provide any cryptographic protection because it operates outside the context of a BSS (no |
| 1620 |
Association Request/Response or Challenge messages). |
| 1621 |
Therefore, an attacker can sniff or inject traffic while within |
| 1622 |
range of a vehicle or IP-RSU (by setting an interface card's frequency to the proper range). |
| 1623 |
Also, an attacker may not adhere to the legal limits |
| 1624 |
for radio power and can use a very sensitive directional antenna; |
| 1625 |
if attackers wish to attack a given exchange, they do not necessarily |
| 1626 |
need to be in close physical proximity. Hence, such a link is less protected than |
| 1627 |
commonly used links (a wired link or the aforementioned 802.11 links with link-layer security).<a href="#section-5-3" class="pilcrow">¶</a></p> |
| 1628 |
<p id="section-5-4">Therefore, any node can join a subnet and directly communicate with any |
| 1629 |
nodes on the subset, including potentially impersonating another node. This |
| 1630 |
design allows for a number of threats outlined in <span><a href="https://www.rfc-editor.org/rfc/rfc6959#section-3" class="relref">Section 3</a> of [<a href="#RFC6959" class="xref">RFC6959</a>]</span>. |
| 1631 |
While not widely deployed, SEND <span>[<a href="#RFC3971" class="xref">RFC3971</a>]</span> <span>[<a href="#RFC3972" class="xref">RFC3972</a>]</span> is a solution |
| 1632 |
that can address spoof-based attack vectors.<a href="#section-5-4" class="pilcrow">¶</a></p> |
| 1633 |
<div id="Privacy"> |
| 1634 |
<section id="section-5.1"> |
| 1635 |
<h3 id="name-privacy-considerations"> |
| 1636 |
<a href="#section-5.1" class="section-number selfRef">5.1. </a><a href="#name-privacy-considerations" class="section-name selfRef">Privacy Considerations</a> |
| 1637 |
</h3> |
| 1638 |
<p id="section-5.1-1"> |
| 1639 |
As with all Ethernet and 802.11 interface identifiers <span>[<a href="#RFC7721" class="xref">RFC7721</a>]</span>, the identifier of an 802.11-OCB |
| 1640 |
interface may involve privacy, MAC address spoofing, and IP |
| 1641 |
hijacking risks. A vehicle embarking an IP-OBU |
| 1642 |
whose egress interface is 802.11-OCB may expose itself to |
| 1643 |
eavesdropping and subsequent correlation of data. This may |
| 1644 |
reveal data considered private by the vehicle owner; there |
| 1645 |
is a risk of being tracked. In outdoor public |
| 1646 |
environments, where vehicles typically circulate, the |
| 1647 |
privacy risks are greater than in indoor settings. |
| 1648 |
It is highly likely that attacker sniffers are deployed |
| 1649 |
along routes that listen for IEEE frames, including IP |
| 1650 |
packets, of vehicles passing by. For this reason, in 802.11-OCB deployments, there is a strong necessity to use |
| 1651 |
protection tools such as dynamically changing MAC addresses |
| 1652 |
(<a href="#mac-change" class="xref">Section 5.2</a>), semantically opaque Interface |
| 1653 |
Identifiers, and stable Interface Identifiers (<a href="#slaac" class="xref">Section 4.4</a>). An example of a change policy is to change the MAC |
| 1654 |
address of the OCB interface each time the system boots up. |
| 1655 |
This may help mitigate privacy risks to a |
| 1656 |
certain level. Furthermore, for privacy concerns, <span>[<a href="#RFC8065" class="xref">RFC8065</a>]</span> recommends using an address-generation scheme |
| 1657 |
rather than generating addresses from a fixed link-layer address. |
| 1658 |
However, there are some specificities related to vehicles. Since roaming is an important |
| 1659 |
characteristic of moving vehicles, the use of the same Link-Local Address over time |
| 1660 |
can indicate the presence of the same vehicle in different places and thus lead to location tracking. |
| 1661 |
Hence, a vehicle should get hints about a change of environment (e.g., engine running, GPS, etc.) |
| 1662 |
and renew the IID in its LLAs.<a href="#section-5.1-1" class="pilcrow">¶</a></p> |
| 1663 |
<div id="privacy-opaque-iid"> |
| 1664 |
<section id="section-5.1.1"> |
| 1665 |
<h4 id="name-privacy-risks-of-meaningful"> |
| 1666 |
<a href="#section-5.1.1" class="section-number selfRef">5.1.1. </a><a href="#name-privacy-risks-of-meaningful" class="section-name selfRef">Privacy Risks of Meaningful Information in Interface IDs</a> |
| 1667 |
</h4> |
| 1668 |
<p id="section-5.1.1-1"> |
| 1669 |
The privacy risks of using MAC addresses displayed in |
| 1670 |
Interface Identifiers are important. IPv6 packets can |
| 1671 |
be captured easily on the Internet and on-link on public |
| 1672 |
roads. For this reason, an attacker may realize many |
| 1673 |
attacks on privacy. One such attack on 802.11-OCB is to |
| 1674 |
capture, store, and correlate company ID information |
| 1675 |
present in the MAC addresses of a large number of cars (e.g., listening for |
| 1676 |
Router Advertisements or other IPv6 application data |
| 1677 |
packets, and recording the value of the source address in |
| 1678 |
these packets). Further correlation of this information |
| 1679 |
with other data captured by other means or other visual |
| 1680 |
information (e.g., car color) may constitute privacy |
| 1681 |
risks.<a href="#section-5.1.1-1" class="pilcrow">¶</a></p> |
| 1682 |
</section> |
| 1683 |
</div> |
| 1684 |
</section> |
| 1685 |
</div> |
| 1686 |
<div id="mac-change"> |
| 1687 |
<section id="section-5.2"> |
| 1688 |
<h3 id="name-mac-address-and-interface-i"> |
| 1689 |
<a href="#section-5.2" class="section-number selfRef">5.2. </a><a href="#name-mac-address-and-interface-i" class="section-name selfRef">MAC Address and Interface ID Generation</a> |
| 1690 |
</h3> |
| 1691 |
<p id="section-5.2-1"> |
| 1692 |
In 802.11-OCB networks, the MAC addresses may change during |
| 1693 |
well-defined renumbering events. At the moment the MAC |
| 1694 |
address is changed on an 802.11-OCB interface, all the |
| 1695 |
Interface Identifiers of IPv6 addresses assigned to that |
| 1696 |
interface <span class="bcp14">MUST</span> change.<a href="#section-5.2-1" class="pilcrow">¶</a></p> |
| 1697 |
<p id="section-5.2-2"> |
| 1698 |
Implementations should use a policy dictating when the MAC address is changed on the 802.11-OCB interface. |
| 1699 |
For more information on the motivation of this policy, please refer to |
| 1700 |
the privacy discussion in <a href="#introduced-by-OCB" class="xref">Appendix B</a>.<a href="#section-5.2-2" class="pilcrow">¶</a></p> |
| 1701 |
<p id="section-5.2-3"> |
| 1702 |
A 'randomized' MAC address has the following |
| 1703 |
characteristics:<a href="#section-5.2-3" class="pilcrow">¶</a></p> |
| 1704 |
<ul> |
| 1705 |
<li id="section-5.2-4.1"> |
| 1706 |
The "Local/Global" bit is set to "locally administered".<a href="#section-5.2-4.1" class="pilcrow">¶</a> |
| 1707 |
</li> |
| 1708 |
<li id="section-5.2-4.2"> |
| 1709 |
The "Unicast/Multicast" bit is set to "Unicast".<a href="#section-5.2-4.2" class="pilcrow">¶</a> |
| 1710 |
</li> |
| 1711 |
<li id="section-5.2-4.3"> |
| 1712 |
The 46 remaining bits are set to a random value using a |
| 1713 |
random number generator that meets the requirements of |
| 1714 |
<span>[<a href="#RFC4086" class="xref">RFC4086</a>]</span>.<a href="#section-5.2-4.3" class="pilcrow">¶</a> |
| 1715 |
</li> |
| 1716 |
</ul> |
| 1717 |
<p id="section-5.2-5"> |
| 1718 |
To meet the randomization requirements for the 46 remaining |
| 1719 |
bits, a hash function may be used. For example, the hash function |
| 1720 |
defined in <span>[<a href="#SHA256" class="xref">SHA256</a>]</span> |
| 1721 |
may be used with the input of a 256-bit local secret, the 'nominal' |
| 1722 |
MAC address of the interface, and a representation of the date and |
| 1723 |
time of the renumbering event.<a href="#section-5.2-5" class="pilcrow">¶</a></p> |
| 1724 |
<p id="section-5.2-6"> |
| 1725 |
A randomized Interface ID has the same characteristics of a |
| 1726 |
randomized MAC address except for the length in bits.<a href="#section-5.2-6" class="pilcrow">¶</a></p> |
| 1727 |
</section> |
| 1728 |
</div> |
| 1729 |
<div id="pseudonym"> |
| 1730 |
<section id="section-5.3"> |
| 1731 |
<h3 id="name-pseudonymization-impact-on-"> |
| 1732 |
<a href="#section-5.3" class="section-number selfRef">5.3. </a><a href="#name-pseudonymization-impact-on-" class="section-name selfRef">Pseudonymization Impact on Confidentiality and Trust</a> |
| 1733 |
</h3> |
| 1734 |
<p id="section-5.3-1"> |
| 1735 |
Vehicle and drivers privacy relies on pseudonymization mechanisms |
| 1736 |
such as the ones described in <a href="#mac-change" class="xref">Section 5.2</a>. |
| 1737 |
This pseudonymization means that upper-layer protocols and applications |
| 1738 |
<span class="bcp14">SHOULD NOT</span> rely on layer-2 or layer-3 addresses to assume that the other participant can be trusted.<a href="#section-5.3-1" class="pilcrow">¶</a></p> |
| 1739 |
</section> |
| 1740 |
</div> |
| 1741 |
</section> |
| 1742 |
</div> |
| 1743 |
<div id="IANA"> |
| 1744 |
<section id="section-6"> |
| 1745 |
<h2 id="name-iana-considerations"> |
| 1746 |
<a href="#section-6" class="section-number selfRef">6. </a><a href="#name-iana-considerations" class="section-name selfRef">IANA Considerations</a> |
| 1747 |
</h2> |
| 1748 |
<p id="section-6-1"> |
| 1749 |
This document has no IANA actions.<a href="#section-6-1" class="pilcrow">¶</a></p> |
| 1750 |
</section> |
| 1751 |
</div> |
| 1752 |
<section id="section-7"> |
| 1753 |
<h2 id="name-references"> |
| 1754 |
<a href="#section-7" class="section-number selfRef">7. </a><a href="#name-references" class="section-name selfRef">References</a> |
| 1755 |
</h2> |
| 1756 |
<section id="section-7.1"> |
| 1757 |
<h3 id="name-normative-references"> |
| 1758 |
<a href="#section-7.1" class="section-number selfRef">7.1. </a><a href="#name-normative-references" class="section-name selfRef">Normative References</a> |
| 1759 |
</h3> |
| 1760 |
<dl class="references"> |
| 1761 |
<dt id="IEEE-802.11-2016">[IEEE-802.11-2016]</dt> |
| 1762 |
<dd> |
| 1763 |
<span class="refAuthor">IEEE</span>, <span class="refTitle">"IEEE Standard for Information technology - Telecommunications and information exchange between systems Local and metropolitan area networks--Specific requirements - Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications"</span>, <span class="seriesInfo">IEEE Standard 802.11-2016</span>, <time datetime="2016-12">December 2016</time>, <span><<a href="https://standards.ieee.org/findstds/standard/802.11-2016.html">https://standards.ieee.org/findstds/standard/802.11-2016.html</a>></span>. </dd> |
| 1764 |
<dt id="RFC1042">[RFC1042]</dt> |
| 1765 |
<dd> |
| 1766 |
<span class="refAuthor">Postel, J.</span><span class="refAuthor"> and J. Reynolds</span>, <span class="refTitle">"Standard for the transmission of IP datagrams over IEEE 802 networks"</span>, <span class="seriesInfo">STD 43</span>, <span class="seriesInfo">RFC 1042</span>, <span class="seriesInfo">DOI 10.17487/RFC1042</span>, <time datetime="1988-02">February 1988</time>, <span><<a href="https://www.rfc-editor.org/info/rfc1042">https://www.rfc-editor.org/info/rfc1042</a>></span>. </dd> |
| 1767 |
<dt id="RFC2119">[RFC2119]</dt> |
| 1768 |
<dd> |
| 1769 |
<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">March 1997</time>, <span><<a href="https://www.rfc-editor.org/info/rfc2119">https://www.rfc-editor.org/info/rfc2119</a>></span>. </dd> |
| 1770 |
<dt id="RFC2464">[RFC2464]</dt> |
| 1771 |
<dd> |
| 1772 |
<span class="refAuthor">Crawford, M.</span>, <span class="refTitle">"Transmission of IPv6 Packets over Ethernet Networks"</span>, <span class="seriesInfo">RFC 2464</span>, <span class="seriesInfo">DOI 10.17487/RFC2464</span>, <time datetime="1998-12">December 1998</time>, <span><<a href="https://www.rfc-editor.org/info/rfc2464">https://www.rfc-editor.org/info/rfc2464</a>></span>. </dd> |
| 1773 |
<dt id="RFC4086">[RFC4086]</dt> |
| 1774 |
<dd> |
| 1775 |
<span class="refAuthor">Eastlake 3rd, D.</span><span class="refAuthor">, Schiller, J.</span><span class="refAuthor">, and S. Crocker</span>, <span class="refTitle">"Randomness Requirements for Security"</span>, <span class="seriesInfo">BCP 106</span>, <span class="seriesInfo">RFC 4086</span>, <span class="seriesInfo">DOI 10.17487/RFC4086</span>, <time datetime="2005-06">June 2005</time>, <span><<a href="https://www.rfc-editor.org/info/rfc4086">https://www.rfc-editor.org/info/rfc4086</a>></span>. </dd> |
| 1776 |
<dt id="RFC4191">[RFC4191]</dt> |
| 1777 |
<dd> |
| 1778 |
<span class="refAuthor">Draves, R.</span><span class="refAuthor"> and D. Thaler</span>, <span class="refTitle">"Default Router Preferences and More-Specific Routes"</span>, <span class="seriesInfo">RFC 4191</span>, <span class="seriesInfo">DOI 10.17487/RFC4191</span>, <time datetime="2005-11">November 2005</time>, <span><<a href="https://www.rfc-editor.org/info/rfc4191">https://www.rfc-editor.org/info/rfc4191</a>></span>. </dd> |
| 1779 |
<dt id="RFC4193">[RFC4193]</dt> |
| 1780 |
<dd> |
| 1781 |
<span class="refAuthor">Hinden, R.</span><span class="refAuthor"> and B. Haberman</span>, <span class="refTitle">"Unique Local IPv6 Unicast Addresses"</span>, <span class="seriesInfo">RFC 4193</span>, <span class="seriesInfo">DOI 10.17487/RFC4193</span>, <time datetime="2005-10">October 2005</time>, <span><<a href="https://www.rfc-editor.org/info/rfc4193">https://www.rfc-editor.org/info/rfc4193</a>></span>. </dd> |
| 1782 |
<dt id="RFC4291">[RFC4291]</dt> |
| 1783 |
<dd> |
| 1784 |
<span class="refAuthor">Hinden, R.</span><span class="refAuthor"> and S. Deering</span>, <span class="refTitle">"IP Version 6 Addressing Architecture"</span>, <span class="seriesInfo">RFC 4291</span>, <span class="seriesInfo">DOI 10.17487/RFC4291</span>, <time datetime="2006-02">February 2006</time>, <span><<a href="https://www.rfc-editor.org/info/rfc4291">https://www.rfc-editor.org/info/rfc4291</a>></span>. </dd> |
| 1785 |
<dt id="RFC4301">[RFC4301]</dt> |
| 1786 |
<dd> |
| 1787 |
<span class="refAuthor">Kent, S.</span><span class="refAuthor"> and K. Seo</span>, <span class="refTitle">"Security Architecture for the Internet Protocol"</span>, <span class="seriesInfo">RFC 4301</span>, <span class="seriesInfo">DOI 10.17487/RFC4301</span>, <time datetime="2005-12">December 2005</time>, <span><<a href="https://www.rfc-editor.org/info/rfc4301">https://www.rfc-editor.org/info/rfc4301</a>></span>. </dd> |
| 1788 |
<dt id="RFC4861">[RFC4861]</dt> |
| 1789 |
<dd> |
| 1790 |
<span class="refAuthor">Narten, T.</span><span class="refAuthor">, Nordmark, E.</span><span class="refAuthor">, Simpson, W.</span><span class="refAuthor">, and H. Soliman</span>, <span class="refTitle">"Neighbor Discovery for IP version 6 (IPv6)"</span>, <span class="seriesInfo">RFC 4861</span>, <span class="seriesInfo">DOI 10.17487/RFC4861</span>, <time datetime="2007-09">September 2007</time>, <span><<a href="https://www.rfc-editor.org/info/rfc4861">https://www.rfc-editor.org/info/rfc4861</a>></span>. </dd> |
| 1791 |
<dt id="RFC4862">[RFC4862]</dt> |
| 1792 |
<dd> |
| 1793 |
<span class="refAuthor">Thomson, S.</span><span class="refAuthor">, Narten, T.</span><span class="refAuthor">, and T. Jinmei</span>, <span class="refTitle">"IPv6 Stateless Address Autoconfiguration"</span>, <span class="seriesInfo">RFC 4862</span>, <span class="seriesInfo">DOI 10.17487/RFC4862</span>, <time datetime="2007-09">September 2007</time>, <span><<a href="https://www.rfc-editor.org/info/rfc4862">https://www.rfc-editor.org/info/rfc4862</a>></span>. </dd> |
| 1794 |
<dt id="RFC5415">[RFC5415]</dt> |
| 1795 |
<dd> |
| 1796 |
<span class="refAuthor">Calhoun, P., Ed.</span><span class="refAuthor">, Montemurro, M., Ed.</span><span class="refAuthor">, and D. Stanley, Ed.</span>, <span class="refTitle">"Control And Provisioning of Wireless Access Points (CAPWAP) Protocol Specification"</span>, <span class="seriesInfo">RFC 5415</span>, <span class="seriesInfo">DOI 10.17487/RFC5415</span>, <time datetime="2009-03">March 2009</time>, <span><<a href="https://www.rfc-editor.org/info/rfc5415">https://www.rfc-editor.org/info/rfc5415</a>></span>. </dd> |
| 1797 |
<dt id="RFC6059">[RFC6059]</dt> |
| 1798 |
<dd> |
| 1799 |
<span class="refAuthor">Krishnan, S.</span><span class="refAuthor"> and G. Daley</span>, <span class="refTitle">"Simple Procedures for Detecting Network Attachment in IPv6"</span>, <span class="seriesInfo">RFC 6059</span>, <span class="seriesInfo">DOI 10.17487/RFC6059</span>, <time datetime="2010-11">November 2010</time>, <span><<a href="https://www.rfc-editor.org/info/rfc6059">https://www.rfc-editor.org/info/rfc6059</a>></span>. </dd> |
| 1800 |
<dt id="RFC6275">[RFC6275]</dt> |
| 1801 |
<dd> |
| 1802 |
<span class="refAuthor">Perkins, C., Ed.</span><span class="refAuthor">, Johnson, D.</span><span class="refAuthor">, and J. Arkko</span>, <span class="refTitle">"Mobility Support in IPv6"</span>, <span class="seriesInfo">RFC 6275</span>, <span class="seriesInfo">DOI 10.17487/RFC6275</span>, <time datetime="2011-07">July 2011</time>, <span><<a href="https://www.rfc-editor.org/info/rfc6275">https://www.rfc-editor.org/info/rfc6275</a>></span>. </dd> |
| 1803 |
<dt id="RFC7042">[RFC7042]</dt> |
| 1804 |
<dd> |
| 1805 |
<span class="refAuthor">Eastlake 3rd, D.</span><span class="refAuthor"> and J. Abley</span>, <span class="refTitle">"IANA Considerations and IETF Protocol and Documentation Usage for IEEE 802 Parameters"</span>, <span class="seriesInfo">BCP 141</span>, <span class="seriesInfo">RFC 7042</span>, <span class="seriesInfo">DOI 10.17487/RFC7042</span>, <time datetime="2013-10">October 2013</time>, <span><<a href="https://www.rfc-editor.org/info/rfc7042">https://www.rfc-editor.org/info/rfc7042</a>></span>. </dd> |
| 1806 |
<dt id="RFC7136">[RFC7136]</dt> |
| 1807 |
<dd> |
| 1808 |
<span class="refAuthor">Carpenter, B.</span><span class="refAuthor"> and S. Jiang</span>, <span class="refTitle">"Significance of IPv6 Interface Identifiers"</span>, <span class="seriesInfo">RFC 7136</span>, <span class="seriesInfo">DOI 10.17487/RFC7136</span>, <time datetime="2014-02">February 2014</time>, <span><<a href="https://www.rfc-editor.org/info/rfc7136">https://www.rfc-editor.org/info/rfc7136</a>></span>. </dd> |
| 1809 |
<dt id="RFC7217">[RFC7217]</dt> |
| 1810 |
<dd> |
| 1811 |
<span class="refAuthor">Gont, F.</span>, <span class="refTitle">"A Method for Generating Semantically Opaque Interface Identifiers with IPv6 Stateless Address Autoconfiguration (SLAAC)"</span>, <span class="seriesInfo">RFC 7217</span>, <span class="seriesInfo">DOI 10.17487/RFC7217</span>, <time datetime="2014-04">April 2014</time>, <span><<a href="https://www.rfc-editor.org/info/rfc7217">https://www.rfc-editor.org/info/rfc7217</a>></span>. </dd> |
| 1812 |
<dt id="RFC8064">[RFC8064]</dt> |
| 1813 |
<dd> |
| 1814 |
<span class="refAuthor">Gont, F.</span><span class="refAuthor">, Cooper, A.</span><span class="refAuthor">, Thaler, D.</span><span class="refAuthor">, and W. Liu</span>, <span class="refTitle">"Recommendation on Stable IPv6 Interface Identifiers"</span>, <span class="seriesInfo">RFC 8064</span>, <span class="seriesInfo">DOI 10.17487/RFC8064</span>, <time datetime="2017-02">February 2017</time>, <span><<a href="https://www.rfc-editor.org/info/rfc8064">https://www.rfc-editor.org/info/rfc8064</a>></span>. </dd> |
| 1815 |
<dt id="RFC8174">[RFC8174]</dt> |
| 1816 |
<dd> |
| 1817 |
<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">May 2017</time>, <span><<a href="https://www.rfc-editor.org/info/rfc8174">https://www.rfc-editor.org/info/rfc8174</a>></span>. </dd> |
| 1818 |
<dt id="RFC8200">[RFC8200]</dt> |
| 1819 |
<dd> |
| 1820 |
<span class="refAuthor">Deering, S.</span><span class="refAuthor"> and R. Hinden</span>, <span class="refTitle">"Internet Protocol, Version 6 (IPv6) Specification"</span>, <span class="seriesInfo">STD 86</span>, <span class="seriesInfo">RFC 8200</span>, <span class="seriesInfo">DOI 10.17487/RFC8200</span>, <time datetime="2017-07">July 2017</time>, <span><<a href="https://www.rfc-editor.org/info/rfc8200">https://www.rfc-editor.org/info/rfc8200</a>></span>. </dd> |
| 1821 |
</dl> |
| 1822 |
</section> |
| 1823 |
<section id="section-7.2"> |
| 1824 |
<h3 id="name-informative-references"> |
| 1825 |
<a href="#section-7.2" class="section-number selfRef">7.2. </a><a href="#name-informative-references" class="section-name selfRef">Informative References</a> |
| 1826 |
</h3> |
| 1827 |
<dl class="references"> |
| 1828 |
<dt id="CFR-90">[CFR-90]</dt> |
| 1829 |
<dd> |
| 1830 |
<span class="refAuthor">e-CFR</span>, <span class="refTitle">"Electronic Code of Federal Regulations"</span>, <span class="refContent">Title 47, Part 90 - PRIVATE LAND MOBILE RADIO SERVICES</span>, <span><<a href="https://www.ecfr.gov/cgi-bin/text-idx?node=pt47.5.90&rgn=div5">https://www.ecfr.gov/cgi-bin/text-idx?node=pt47.5.90&rgn=div5</a>></span>. </dd> |
| 1831 |
<dt id="CFR-90.7">[CFR-90.7]</dt> |
| 1832 |
<dd> |
| 1833 |
<span class="refAuthor">e-CFR</span>, <span class="refTitle">"Electronic Code of Federal Regulations"</span>, <span class="refContent">Title 47, CFR 90.7 - Definitions</span>, <span><<a href="https://www.ecfr.gov/cgi-bin/text-idx?node=pt47.5.90&rgn=div5#se47.5.90_17">https://www.ecfr.gov/cgi-bin/text-idx?node=pt47.5.90&rgn=div5#se47.5.90_17</a>></span>. </dd> |
| 1834 |
<dt id="CFR-95">[CFR-95]</dt> |
| 1835 |
<dd> |
| 1836 |
<span class="refAuthor">e-CFR</span>, <span class="refTitle">"Electronic Code of Federal Regulations"</span>, <span class="refContent">Title 47, CFR 95 - PERSONAL RADIO SERVICES</span>, <span><<a href="https://www.ecfr.gov/cgi-bin/text-idx?node=pt47.5.95&rgn=div5">https://www.ecfr.gov/cgi-bin/text-idx?node=pt47.5.95&rgn=div5</a>></span>. </dd> |
| 1837 |
<dt id="ETSI-sec-archi">[ETSI-sec-archi]</dt> |
| 1838 |
<dd> |
| 1839 |
<span class="refTitle">"Intelligent Transport Systems (ITS); Security; ITS communications security architecture and security management"</span>, <span class="seriesInfo">ETSI TS 102 940 V1.2.1</span>, <time datetime="2016-11">November 2016</time>, <span><<a href="http://www.etsi.org/deliver/etsi_ts/102900_102999/102940/01.02.01_60/ts_102940v010201p.pdf">http://www.etsi.org/deliver/etsi_ts/102900_102999/102940/01.02.01_60/ts_102940v010201p.pdf</a>></span>. </dd> |
| 1840 |
<dt id="IEEE-1609.2">[IEEE-1609.2]</dt> |
| 1841 |
<dd> |
| 1842 |
<span class="refAuthor">IEEE</span>, <span class="refTitle">"IEEE Standard for Wireless Access in Vehicular Environments--Security Services for Applications and Management Messages"</span>, <span class="seriesInfo">DOI 10.1109/IEEESTD.2016.7426684</span>, <span class="seriesInfo">IEEE Standard 1609.2-2016</span>, <time datetime="2016-03">March 2016</time>, <span><<a href="http://ieeexplore.ieee.org/document/7426684">http://ieeexplore.ieee.org/document/7426684</a>></span>. </dd> |
| 1843 |
<dt id="IEEE-1609.3">[IEEE-1609.3]</dt> |
| 1844 |
<dd> |
| 1845 |
<span class="refAuthor">IEEE</span>, <span class="refTitle">"IEEE Standard for Wireless Access in Vehicular Environments (WAVE) -- Networking Services"</span>, <span class="seriesInfo">DOI 10.1109/IEEESTD.2016.7458115</span>, <span class="seriesInfo">IEEE Standard 1609.3-2016</span>, <time datetime="2016-04">April 2016</time>, <span><<a href="http://ieeexplore.ieee.org/document/7458115">http://ieeexplore.ieee.org/document/7458115</a>></span>. </dd> |
| 1846 |
<dt id="IEEE-1609.4">[IEEE-1609.4]</dt> |
| 1847 |
<dd> |
| 1848 |
<span class="refAuthor">IEEE</span>, <span class="refTitle">"IEEE Standard for Wireless Access in Vehicular Environments (WAVE) -- Multi-Channel Operation"</span>, <span class="seriesInfo">DOI 10.1109/IEEESTD.2016.7435228</span>, <span class="seriesInfo">IEEE Standard 1609.4-2016</span>, <time datetime="2016-03">March 2016</time>, <span><<a href="http://ieeexplore.ieee.org/document/7435228">http://ieeexplore.ieee.org/document/7435228</a>></span>. </dd> |
| 1849 |
<dt id="IEEE-802.11-2007">[IEEE-802.11-2007]</dt> |
| 1850 |
<dd> |
| 1851 |
<span class="refAuthor">IEEE</span>, <span class="refTitle">"IEEE Standard for Information Technology - Telecommunications and Information Exchange Between Systems - Local and Metropolitan Area Networks - Specific Requirements - Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications"</span>, <span class="seriesInfo">DOI 10.1109/IEEESTD.2007.373646</span>, <span class="seriesInfo">IEEE Standard 802.11-2007</span>, <time datetime="2007-06">June 2007</time>, <span><<a href="https://ieeexplore.ieee.org/document/4248378">https://ieeexplore.ieee.org/document/4248378</a>></span>. </dd> |
| 1852 |
<dt id="IEEE-802.11-2012">[IEEE-802.11-2012]</dt> |
| 1853 |
<dd> |
| 1854 |
<span class="refAuthor">IEEE</span>, <span class="refTitle">"IEEE Standard for Information technology--Telecommunications and information exchange between systems Local and metropolitan area networks--Specific requirements Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications"</span>, <span class="seriesInfo">DOI 10.1109/IEEESTD.2012.6178212</span>, <span class="seriesInfo">IEEE Standard 802.11-2012</span>, <time datetime="2012-03">March 2012</time>, <span><<a href="https://ieeexplore.ieee.org/document/6419735">https://ieeexplore.ieee.org/document/6419735</a>></span>. </dd> |
| 1855 |
<dt id="IEEE-802.11p-2010">[IEEE-802.11p-2010]</dt> |
| 1856 |
<dd> |
| 1857 |
<span class="refAuthor">IEEE</span>, <span class="refTitle">"IEEE Standard for Information technology - Telecommunications and information exchange between systems - Local and metropolitan area networks - Specific requirements, Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications, Amendment 6: Wireless Access in Vehicular Environments"</span>, <span class="seriesInfo">DOI 10.1109/IEEESTD.2010.5514475</span>, <span class="seriesInfo">IEEE Standard 802.11p-2010</span>, <time datetime="2010-07">July 2010</time>, <span><<a href="https://standards.ieee.org/standard/802_11p-2010.html">https://standards.ieee.org/standard/802_11p-2010.html</a>></span>. </dd> |
| 1858 |
<dt id="IEEE-802.3-2012">[IEEE-802.3-2012]</dt> |
| 1859 |
<dd> |
| 1860 |
<span class="refAuthor">IEEE</span>, <span class="refTitle">"IEEE Standard for Ethernet"</span>, <span class="seriesInfo">DOI 10.1109/IEEESTD.2012.6419735</span>, <span class="seriesInfo">IEEE Standard 802.3-2012</span>, <time datetime="2012-12">December 2012</time>, <span><<a href="https://ieeexplore.ieee.org/document/6419735">https://ieeexplore.ieee.org/document/6419735</a>></span>. </dd> |
| 1861 |
<dt id="I-D.ietf-mboned-ieee802-mcast-problems">[IEEE802-MCAST]</dt> |
| 1862 |
<dd> |
| 1863 |
<span class="refAuthor">Perkins, C.</span><span class="refAuthor">, McBride, M.</span><span class="refAuthor">, Stanley, D.</span><span class="refAuthor">, Kumari, W.</span><span class="refAuthor">, and J. Zuniga</span>, <span class="refTitle">"Multicast Considerations over IEEE 802 Wireless Media"</span>, <span class="refContent">Work in Progress</span>, <span class="seriesInfo">Internet-Draft, draft-ietf-mboned-ieee802-mcast-problems-11</span>, <time datetime="2019-12-11">11 December 2019</time>, <span><<a href="https://tools.ietf.org/html/draft-ietf-mboned-ieee802-mcast-problems-11">https://tools.ietf.org/html/draft-ietf-mboned-ieee802-mcast-problems-11</a>></span>. </dd> |
| 1864 |
<dt id="I-D.ietf-ipwave-vehicular-networking">[IPWAVE]</dt> |
| 1865 |
<dd> |
| 1866 |
<span class="refAuthor">Jeong, J.</span>, <span class="refTitle">"IP Wireless Access in Vehicular Environments (IPWAVE): Problem Statement and Use Cases"</span>, <span class="refContent">Work in Progress</span>, <span class="seriesInfo">Internet-Draft, draft-ietf-ipwave-vehicular-networking-12</span>, <time datetime="2019-10-03">3 October 2019</time>, <span><<a href="https://tools.ietf.org/html/draft-ietf-ipwave-vehicular-networking-12">https://tools.ietf.org/html/draft-ietf-ipwave-vehicular-networking-12</a>></span>. </dd> |
| 1867 |
<dt id="RFC3753">[RFC3753]</dt> |
| 1868 |
<dd> |
| 1869 |
<span class="refAuthor">Manner, J., Ed.</span><span class="refAuthor"> and M. Kojo, Ed.</span>, <span class="refTitle">"Mobility Related Terminology"</span>, <span class="seriesInfo">RFC 3753</span>, <span class="seriesInfo">DOI 10.17487/RFC3753</span>, <time datetime="2004-06">June 2004</time>, <span><<a href="https://www.rfc-editor.org/info/rfc3753">https://www.rfc-editor.org/info/rfc3753</a>></span>. </dd> |
| 1870 |
<dt id="RFC3963">[RFC3963]</dt> |
| 1871 |
<dd> |
| 1872 |
<span class="refAuthor">Devarapalli, V.</span><span class="refAuthor">, Wakikawa, R.</span><span class="refAuthor">, Petrescu, A.</span><span class="refAuthor">, and P. Thubert</span>, <span class="refTitle">"Network Mobility (NEMO) Basic Support Protocol"</span>, <span class="seriesInfo">RFC 3963</span>, <span class="seriesInfo">DOI 10.17487/RFC3963</span>, <time datetime="2005-01">January 2005</time>, <span><<a href="https://www.rfc-editor.org/info/rfc3963">https://www.rfc-editor.org/info/rfc3963</a>></span>. </dd> |
| 1873 |
<dt id="RFC3971">[RFC3971]</dt> |
| 1874 |
<dd> |
| 1875 |
<span class="refAuthor">Arkko, J., Ed.</span><span class="refAuthor">, Kempf, J.</span><span class="refAuthor">, Zill, B.</span><span class="refAuthor">, and P. Nikander</span>, <span class="refTitle">"SEcure Neighbor Discovery (SEND)"</span>, <span class="seriesInfo">RFC 3971</span>, <span class="seriesInfo">DOI 10.17487/RFC3971</span>, <time datetime="2005-03">March 2005</time>, <span><<a href="https://www.rfc-editor.org/info/rfc3971">https://www.rfc-editor.org/info/rfc3971</a>></span>. </dd> |
| 1876 |
<dt id="RFC3972">[RFC3972]</dt> |
| 1877 |
<dd> |
| 1878 |
<span class="refAuthor">Aura, T.</span>, <span class="refTitle">"Cryptographically Generated Addresses (CGA)"</span>, <span class="seriesInfo">RFC 3972</span>, <span class="seriesInfo">DOI 10.17487/RFC3972</span>, <time datetime="2005-03">March 2005</time>, <span><<a href="https://www.rfc-editor.org/info/rfc3972">https://www.rfc-editor.org/info/rfc3972</a>></span>. </dd> |
| 1879 |
<dt id="RFC5889">[RFC5889]</dt> |
| 1880 |
<dd> |
| 1881 |
<span class="refAuthor">Baccelli, E., Ed.</span><span class="refAuthor"> and M. Townsley, Ed.</span>, <span class="refTitle">"IP Addressing Model in Ad Hoc Networks"</span>, <span class="seriesInfo">RFC 5889</span>, <span class="seriesInfo">DOI 10.17487/RFC5889</span>, <time datetime="2010-09">September 2010</time>, <span><<a href="https://www.rfc-editor.org/info/rfc5889">https://www.rfc-editor.org/info/rfc5889</a>></span>. </dd> |
| 1882 |
<dt id="RFC6959">[RFC6959]</dt> |
| 1883 |
<dd> |
| 1884 |
<span class="refAuthor">McPherson, D.</span><span class="refAuthor">, Baker, F.</span><span class="refAuthor">, and J. Halpern</span>, <span class="refTitle">"Source Address Validation Improvement (SAVI) Threat Scope"</span>, <span class="seriesInfo">RFC 6959</span>, <span class="seriesInfo">DOI 10.17487/RFC6959</span>, <time datetime="2013-05">May 2013</time>, <span><<a href="https://www.rfc-editor.org/info/rfc6959">https://www.rfc-editor.org/info/rfc6959</a>></span>. </dd> |
| 1885 |
<dt id="RFC7721">[RFC7721]</dt> |
| 1886 |
<dd> |
| 1887 |
<span class="refAuthor">Cooper, A.</span><span class="refAuthor">, Gont, F.</span><span class="refAuthor">, and D. Thaler</span>, <span class="refTitle">"Security and Privacy Considerations for IPv6 Address Generation Mechanisms"</span>, <span class="seriesInfo">RFC 7721</span>, <span class="seriesInfo">DOI 10.17487/RFC7721</span>, <time datetime="2016-03">March 2016</time>, <span><<a href="https://www.rfc-editor.org/info/rfc7721">https://www.rfc-editor.org/info/rfc7721</a>></span>. </dd> |
| 1888 |
<dt id="RFC8065">[RFC8065]</dt> |
| 1889 |
<dd> |
| 1890 |
<span class="refAuthor">Thaler, D.</span>, <span class="refTitle">"Privacy Considerations for IPv6 Adaptation-Layer Mechanisms"</span>, <span class="seriesInfo">RFC 8065</span>, <span class="seriesInfo">DOI 10.17487/RFC8065</span>, <time datetime="2017-02">February 2017</time>, <span><<a href="https://www.rfc-editor.org/info/rfc8065">https://www.rfc-editor.org/info/rfc8065</a>></span>. </dd> |
| 1891 |
<dt id="RFC8505">[RFC8505]</dt> |
| 1892 |
<dd> |
| 1893 |
<span class="refAuthor">Thubert, P., Ed.</span><span class="refAuthor">, Nordmark, E.</span><span class="refAuthor">, Chakrabarti, S.</span><span class="refAuthor">, and C. Perkins</span>, <span class="refTitle">"Registration Extensions for IPv6 over Low-Power Wireless Personal Area Network (6LoWPAN) Neighbor Discovery"</span>, <span class="seriesInfo">RFC 8505</span>, <span class="seriesInfo">DOI 10.17487/RFC8505</span>, <time datetime="2018-11">November 2018</time>, <span><<a href="https://www.rfc-editor.org/info/rfc8505">https://www.rfc-editor.org/info/rfc8505</a>></span>. </dd> |
| 1894 |
<dt id="SHA256">[SHA256]</dt> |
| 1895 |
<dd> |
| 1896 |
<span class="refAuthor">National Institute of Standards and Technology</span>, <span class="refTitle">"Secure Hash Standard (SHS)"</span>, <span class="seriesInfo">DOI 10.6028/NIST.FIPS.180-4</span>, <span class="seriesInfo">FIPS 180-4</span>, <time datetime="2015-08">August 2015</time>, <span><<a href="https://csrc.nist.gov/publications/detail/fips/180/4/final">https://csrc.nist.gov/publications/detail/fips/180/4/final</a>></span>. </dd> |
| 1897 |
</dl> |
| 1898 |
</section> |
| 1899 |
</section> |
| 1900 |
<div id="i802.11p"> |
| 1901 |
<section id="section-appendix.a"> |
| 1902 |
<h2 id="name-80211p"> |
| 1903 |
<a href="#section-appendix.a" class="section-number selfRef">Appendix A. </a><a href="#name-80211p" class="section-name selfRef">802.11p</a> |
| 1904 |
</h2> |
| 1905 |
<p id="section-appendix.a-1"> |
| 1906 |
The term "802.11p" is an earlier definition. The behavior of |
| 1907 |
"802.11p" networks is rolled in <span>[<a href="#IEEE-802.11-2016" class="xref">IEEE-802.11-2016</a>]</span>. In that document, the term "802.11p" disappears. |
| 1908 |
Instead, each 802.11p feature is conditioned by the IEEE |
| 1909 |
Management Information Base (MIB) attribute "OCBActivated" |
| 1910 |
<span>[<a href="#IEEE-802.11-2016" class="xref">IEEE-802.11-2016</a>]</span>. Whenever OCBActivated is |
| 1911 |
set to "true", the IEEE Std 802.11-OCB state is activated. For |
| 1912 |
example, an 802.11 STAtion operating outside the context of a |
| 1913 |
BSS has the OCBActivated flag set. Such a |
| 1914 |
station, when it has the flag set, uses a BSS identifier equal |
| 1915 |
to ff:ff:ff:ff:ff:ff.<a href="#section-appendix.a-1" class="pilcrow">¶</a></p> |
| 1916 |
</section> |
| 1917 |
</div> |
| 1918 |
<div id="introduced-by-OCB"> |
| 1919 |
<section id="section-appendix.b"> |
| 1920 |
<h2 id="name-aspects-introduced-by-ocb-m"> |
| 1921 |
<a href="#section-appendix.b" class="section-number selfRef">Appendix B. </a><a href="#name-aspects-introduced-by-ocb-m" class="section-name selfRef">Aspects Introduced by OCB Mode to 802.11</a> |
| 1922 |
</h2> |
| 1923 |
<p id="section-appendix.b-1"> |
| 1924 |
In IEEE 802.11-OCB mode, all nodes in the wireless range |
| 1925 |
can directly communicate with each other without involving |
| 1926 |
authentication or association procedures. In OCB mode, the |
| 1927 |
manner in which channels are selected and used is simplified |
| 1928 |
compared to when in BSS mode. Contrary to BSS mode, at the link |
| 1929 |
layer, it is necessary to statically set the same channel |
| 1930 |
number (or frequency) on two stations that need to communicate |
| 1931 |
with each other (in BSS mode, this channel set operation is |
| 1932 |
performed automatically during 'scanning'). The manner in |
| 1933 |
which stations set their channel number in OCB mode is not |
| 1934 |
specified in this document. Stations STA1 and STA2 can |
| 1935 |
exchange IP packets only if they are set to the same channel. |
| 1936 |
At the IP layer, they then discover each other by using the IPv6 |
| 1937 |
Neighbor Discovery protocol. The allocation of a particular |
| 1938 |
channel for a particular use is defined statically in |
| 1939 |
standards authored by ETSI in Europe, the FCC in the United States of America, and |
| 1940 |
similar organizations in South Korea, Japan, and other parts of |
| 1941 |
the world.<a href="#section-appendix.b-1" class="pilcrow">¶</a></p> |
| 1942 |
<p id="section-appendix.b-2"> |
| 1943 |
Briefly, the IEEE 802.11-OCB mode has the following |
| 1944 |
properties:<a href="#section-appendix.b-2" class="pilcrow">¶</a></p> |
| 1945 |
<ul> |
| 1946 |
<li id="section-appendix.b-3.1"> |
| 1947 |
The use by each node of a 'wildcard' BSS identifier (BSSID) (i.e., each bit |
| 1948 |
of the BSSID is set to 1).<a href="#section-appendix.b-3.1" class="pilcrow">¶</a> |
| 1949 |
</li> |
| 1950 |
<li id="section-appendix.b-3.2"> No IEEE 802.11 beacon frames are transmitted.<a href="#section-appendix.b-3.2" class="pilcrow">¶</a> |
| 1951 |
</li> |
| 1952 |
<li id="section-appendix.b-3.3"> No authentication is required in order to be able to communicate.<a href="#section-appendix.b-3.3" class="pilcrow">¶</a> |
| 1953 |
</li> |
| 1954 |
<li id="section-appendix.b-3.4"> No association is needed in order to be able to communicate.<a href="#section-appendix.b-3.4" class="pilcrow">¶</a> |
| 1955 |
</li> |
| 1956 |
<li id="section-appendix.b-3.5"> No encryption is provided in order to be able to communicate.<a href="#section-appendix.b-3.5" class="pilcrow">¶</a> |
| 1957 |
</li> |
| 1958 |
<li id="section-appendix.b-3.6"> Flag dot11OCBActivated is set to "true".<a href="#section-appendix.b-3.6" class="pilcrow">¶</a> |
| 1959 |
</li> |
| 1960 |
</ul> |
| 1961 |
<p id="section-appendix.b-4"> |
| 1962 |
|
| 1963 |
All the nodes in the radio communication range (IP-OBU and IP-RSU) |
| 1964 |
receive all the messages transmitted (IP-OBU and IP-RSU) within the |
| 1965 |
radio communication range. The MAC CDMA function resolves any |
| 1966 |
eventual conflict(s).<a href="#section-appendix.b-4" class="pilcrow">¶</a></p> |
| 1967 |
<p id="section-appendix.b-5"> |
| 1968 |
The message exchange diagram in <a href="#fig_mess-exch" class="xref">Figure 1</a> |
| 1969 |
illustrates a comparison between traditional 802.11 and 802.11 |
| 1970 |
in OCB mode. The 'Data' messages can be IP packets such as |
| 1971 |
HTTP or others. Other 802.11 management and control frames |
| 1972 |
(non-IP) may be transmitted, as specified in the 802.11 |
| 1973 |
standard. The names of these messages as |
| 1974 |
currently specified by the 802.11 standard are listed in <a href="#OCB-messages" class="xref">Appendix F</a>.<a href="#section-appendix.b-5" class="pilcrow">¶</a></p> |
| 1975 |
<span id="name-difference-between-messages"></span><div id="fig_mess-exch"> |
| 1976 |
<figure id="figure-1"> |
| 1977 |
<div class="artwork art-text alignCenter" id="section-appendix.b-6.1"> |
| 1978 |
<pre> |
| 1979 |
STA AP STA1 STA2 |
| 1980 |
| | | | |
| 1981 |
|<------ Beacon -------| |<------ Data -------->| |
| 1982 |
| | | | |
| 1983 |
|---- Probe Req. ----->| |<------ Data -------->| |
| 1984 |
|<--- Probe Res. ------| | | |
| 1985 |
| | |<------ Data -------->| |
| 1986 |
|---- Auth Req. ------>| | | |
| 1987 |
|<--- Auth Res. -------| |<------ Data -------->| |
| 1988 |
| | | | |
| 1989 |
|---- Asso Req. ------>| |<------ Data -------->| |
| 1990 |
|<--- Asso Res. -------| | | |
| 1991 |
| | |<------ Data -------->| |
| 1992 |
|<------ Data -------->| | | |
| 1993 |
|<------ Data -------->| |<------ Data -------->| |
| 1994 |
|
| 1995 |
(i) 802.11 Infrastructure mode (ii) 802.11-OCB mode </pre> |
| 1996 |
</div> |
| 1997 |
<figcaption><a href="#figure-1" class="selfRef">Figure 1</a>: |
| 1998 |
<a href="#name-difference-between-messages" class="selfRef">Difference between Messages Exchanged on 802.11 (Left) and 802.11-OCB (Right)</a> |
| 1999 |
</figcaption></figure> |
| 2000 |
</div> |
| 2001 |
<p id="section-appendix.b-7"> |
| 2002 |
The 802.11-OCB interface was specified in <span>[<a href="#IEEE-802.11p-2010" class="xref">IEEE-802.11p-2010</a>]</span>, Amendment 6: Wireless |
| 2003 |
Access in Vehicular Environments, as an amendment |
| 2004 |
to <span>[<a href="#IEEE-802.11-2007" class="xref">IEEE-802.11-2007</a>]</span>. Since then, this amendment |
| 2005 |
has been integrated into <span>[<a href="#IEEE-802.11-2012" class="xref">IEEE-802.11-2012</a>]</span> and <span>[<a href="#IEEE-802.11-2016" class="xref">IEEE-802.11-2016</a>]</span>.<a href="#section-appendix.b-7" class="pilcrow">¶</a></p> |
| 2006 |
<p id="section-appendix.b-8"> |
| 2007 |
In <span>[<a href="#IEEE-802.11p-2010" class="xref">IEEE-802.11p-2010</a>]</span>, anything qualified specifically as |
| 2008 |
"OCBActivated" or "outside the context of a basic service" |
| 2009 |
that is set to be "true" actually refers to OCB aspects |
| 2010 |
introduced to 802.11.<a href="#section-appendix.b-8" class="pilcrow">¶</a></p> |
| 2011 |
<p id="section-appendix.b-9"> |
| 2012 |
In order to delineate the aspects introduced by 802.11-OCB to |
| 2013 |
802.11, we refer to the earlier <span>[<a href="#IEEE-802.11p-2010" class="xref">IEEE-802.11p-2010</a>]</span>. The amendment is concerned with |
| 2014 |
vehicular communications, where the wireless link is similar |
| 2015 |
to that of Wireless LAN (using a PHY layer specified by |
| 2016 |
802.11a/b/g/n) but needs to cope with the high mobility |
| 2017 |
factor inherent in scenarios of communications between moving |
| 2018 |
vehicles and between vehicles and fixed infrastructure |
| 2019 |
deployed along roads. While 'p' is a letter identifying the |
| 2020 |
Amendment, just like 'a', 'b', 'g', and 'n' are, 'p' is concerned |
| 2021 |
more with MAC modifications and is slightly concerned with PHY |
| 2022 |
modifications; the others are mainly about PHY modifications. |
| 2023 |
It is possible in practice to combine a 'p' MAC with an 'a' |
| 2024 |
PHY by operating outside the context of a BSS with Orthogonal |
| 2025 |
Frequency Division |
| 2026 |
Multiplexing (OFDM) at |
| 2027 |
5.4 GHz and 5.9 GHz.<a href="#section-appendix.b-9" class="pilcrow">¶</a></p> |
| 2028 |
<p id="section-appendix.b-10"> |
| 2029 |
The 802.11-OCB links are specified to be as compatible as |
| 2030 |
possible with the behavior of 802.11a/b/g/n and future |
| 2031 |
generation IEEE WLAN links. From the IP perspective, an |
| 2032 |
802.11-OCB MAC layer offers practically the same interface to |
| 2033 |
IP as 802.11a/b/g/n and 802.3. A packet sent by an IP-OBU |
| 2034 |
may be received by one or multiple IP-RSUs. The link-layer |
| 2035 |
resolution is performed by using the IPv6 Neighbor Discovery |
| 2036 |
protocol.<a href="#section-appendix.b-10" class="pilcrow">¶</a></p> |
| 2037 |
<p id="section-appendix.b-11"> |
| 2038 |
To support this similarity statement (IPv6 is layered on top |
| 2039 |
of LLC on top of 802.11-OCB in the same way that IPv6 is |
| 2040 |
layered on top of LLC on top of 802.11a/b/g/n (for WLAN) or |
| 2041 |
on top of LLC on top of 802.3 (for Ethernet)), it is |
| 2042 |
useful to analyze the differences between the 802.11-OCB and |
| 2043 |
802.11 specifications. During this analysis, we note that |
| 2044 |
whereas 802.11-OCB lists relatively complex and numerous |
| 2045 |
changes to the MAC layer (and very few to the PHY layer), |
| 2046 |
there are only a few characteristics that may be important |
| 2047 |
for an implementation transmitting IPv6 packets on 802.11-OCB |
| 2048 |
links.<a href="#section-appendix.b-11" class="pilcrow">¶</a></p> |
| 2049 |
<p id="section-appendix.b-12"> |
| 2050 |
The most important 802.11-OCB aspect that influences the IPv6 |
| 2051 |
functioning is the OCB characteristic; an additional, less |
| 2052 |
direct influence is the maximum bandwidth afforded by the PHY |
| 2053 |
modulation/demodulation methods and channel access specified |
| 2054 |
by 802.11-OCB. The maximum bandwidth theoretically possible |
| 2055 |
in 802.11-OCB is 54 Mbit/s (when using, for example, the |
| 2056 |
following parameters: a 20 MHz channel; modulation of 64-QAM; |
| 2057 |
a coding rate R of 3/4). With regard to IP over 802.11-OCB, in |
| 2058 |
practice, a commonly observed figure is 12 Mbit/s; this bandwidth allows |
| 2059 |
the operation of a wide range of protocols relying on IPv6.<a href="#section-appendix.b-12" class="pilcrow">¶</a></p> |
| 2060 |
<ul> |
| 2061 |
<li id="section-appendix.b-13.1"> |
| 2062 |
Operation outside the context of a BSS (OCB): The 802.11-OCB links |
| 2063 |
(previously 802.11p) are operated without a BSS. This means that IEEE 802.11 |
| 2064 |
beacon, Association Request/Response, Authentication |
| 2065 |
Request/Response, and similar frames are not used. The used |
| 2066 |
identifier of BSS (BSSID) always has a hexadecimal value of |
| 2067 |
0xffffffffffff (48 '1' bits, represented as MAC address |
| 2068 |
ff:ff:ff:ff:ff:ff; otherwise, the 'wildcard' BSSID), as |
| 2069 |
opposed to an arbitrary BSSID value set by an administrator |
| 2070 |
(e.g., 'My-Home-AccessPoint'). The OCB operation -- namely, |
| 2071 |
the lack of beacon-based scanning and lack of |
| 2072 |
authentication -- should be taken into account when the |
| 2073 |
Mobile IPv6 protocol <span>[<a href="#RFC6275" class="xref">RFC6275</a>]</span> and the |
| 2074 |
protocols for IP layer security <span>[<a href="#RFC4301" class="xref">RFC4301</a>]</span> |
| 2075 |
are used. The way these protocols adapt to OCB is not |
| 2076 |
described in this document.<a href="#section-appendix.b-13.1" class="pilcrow">¶</a> |
| 2077 |
</li> |
| 2078 |
<li id="section-appendix.b-13.2"> |
| 2079 |
Timing Advertisement: This is a new message defined in |
| 2080 |
802.11-OCB that does not exist in 802.11a/b/g/n. This |
| 2081 |
message is used by stations to inform other stations about |
| 2082 |
the value of time. It is similar to the time delivered |
| 2083 |
by a Global Navigation Satellite System (GNSS) (e.g., Galileo, GPS, etc.) or by a cellular |
| 2084 |
system. This message is optional for implementation.<a href="#section-appendix.b-13.2" class="pilcrow">¶</a> |
| 2085 |
</li> |
| 2086 |
<li id="section-appendix.b-13.3"> |
| 2087 |
Frequency range: This is a characteristic of the PHY layer; it has |
| 2088 |
almost no impact on the interface between MAC and IP. However, it is worth considering that the |
| 2089 |
frequency range is regulated by a regional authority |
| 2090 |
(ARCEP, ECC/CEPT based on ENs from ETSI, FCC, etc.); as |
| 2091 |
part of the regulation process, specific applications are |
| 2092 |
associated with specific frequency ranges. |
| 2093 |
In the case of 802.11-OCB, the regulator associates a set of frequency |
| 2094 |
ranges or slots within a band to the use of applications of vehicular |
| 2095 |
communications in a band known as "5.9 GHz". |
| 2096 |
The 5.9 GHz band is different from the 2.4 GHz and 5 GHz |
| 2097 |
bands used by Wireless LAN. However, as with Wireless LAN, the |
| 2098 |
operation of 802.11-OCB in 5.9 GHz bands does not require a |
| 2099 |
license in the EU (in the US, the 5.9 GHz is a licensed band of |
| 2100 |
spectrum; for the fixed infrastructure, explicit FCC authorization |
| 2101 |
is required; for an on-board device, a 'licensed-by-rule' concept |
| 2102 |
applies, where rule certification conformity is required). Technical |
| 2103 |
conditions are different from those of the "2.4 GHz" |
| 2104 |
or "5 GHz" bands. The allowed power levels and, implicitly, the |
| 2105 |
maximum allowed distance between vehicles is 33 dBm for |
| 2106 |
802.11-OCB (in Europe) compared to 20 dBm for Wireless |
| 2107 |
LAN 802.11a/b/g/n; this leads to a maximum distance of |
| 2108 |
approximately 1 km compared to approximately 50 m. |
| 2109 |
Additionally, specific conditions related to congestion |
| 2110 |
avoidance, jamming avoidance, and radar detection are |
| 2111 |
imposed on the use of DSRC (in the US) and on the use of |
| 2112 |
frequencies for Intelligent Transportation Systems (in |
| 2113 |
the EU) compared to Wireless LAN (802.11a/b/g/n).<a href="#section-appendix.b-13.3" class="pilcrow">¶</a> |
| 2114 |
</li> |
| 2115 |
<li id="section-appendix.b-13.4"> |
| 2116 |
'Half-rate' encoding: As the frequency range, this |
| 2117 |
parameter is related to PHY and thus does not have much |
| 2118 |
impact on the interface between the IP layer and the |
| 2119 |
MAC layer.<a href="#section-appendix.b-13.4" class="pilcrow">¶</a> |
| 2120 |
</li> |
| 2121 |
<li id="section-appendix.b-13.5"> |
| 2122 |
In vehicular communications using 802.11-OCB links, there |
| 2123 |
are strong privacy requirements with respect to |
| 2124 |
addressing. While the 802.11-OCB standard does not |
| 2125 |
specify anything in particular with respect to MAC |
| 2126 |
addresses, in these settings, there is a strong need |
| 2127 |
for a dynamic change of these addresses (as opposed to the |
| 2128 |
non-vehicular settings -- real wall protection -- where |
| 2129 |
fixed MAC addresses do not currently pose privacy |
| 2130 |
risks). This is further described in <a href="#Security" class="xref">Section 5</a>. A relevant function is described in |
| 2131 |
<span>[<a href="#IEEE-1609.3" class="xref">IEEE-1609.3</a>]</span> |
| 2132 |
and <span>[<a href="#IEEE-1609.4" class="xref">IEEE-1609.4</a>]</span>.<a href="#section-appendix.b-13.5" class="pilcrow">¶</a> |
| 2133 |
</li> |
| 2134 |
</ul> |
| 2135 |
</section> |
| 2136 |
</div> |
| 2137 |
<div id="software-changes"> |
| 2138 |
<section id="section-appendix.c"> |
| 2139 |
<h2 id="name-changes-needed-on-an-80211a"> |
| 2140 |
<a href="#section-appendix.c" class="section-number selfRef">Appendix C. </a><a href="#name-changes-needed-on-an-80211a" class="section-name selfRef">Changes Needed on an 802.11a Software Driver to Become an 802.11-OCB Driver</a> |
| 2141 |
</h2> |
| 2142 |
<p id="section-appendix.c-1"> |
| 2143 |
The 802.11p amendment modifies both the 802.11 stack's |
| 2144 |
physical and MAC layers, but all the induced modifications |
| 2145 |
can be quite easily obtained by modifying an existing |
| 2146 |
802.11a ad hoc stack.<a href="#section-appendix.c-1" class="pilcrow">¶</a></p> |
| 2147 |
<p id="section-appendix.c-2"> |
| 2148 |
The conditions for 802.11a hardware to be compliant with 802.11-OCB are as |
| 2149 |
follows:<a href="#section-appendix.c-2" class="pilcrow">¶</a></p> |
| 2150 |
<ul> |
| 2151 |
<li id="section-appendix.c-3.1"> |
| 2152 |
The PHY entity shall be an OFDM system. It must support the frequency |
| 2153 |
bands on which the regulator recommends the use of ITS |
| 2154 |
communications -- for example, using an IEEE 802.11-OCB layer of |
| 2155 |
5875 MHz to 5925 MHz in France.<a href="#section-appendix.c-3.1" class="pilcrow">¶</a> |
| 2156 |
</li> |
| 2157 |
<li id="section-appendix.c-3.2"> |
| 2158 |
The OFDM system must provide a "half-clocked" operation |
| 2159 |
using 10 MHz channel spacings.<a href="#section-appendix.c-3.2" class="pilcrow">¶</a> |
| 2160 |
</li> |
| 2161 |
<li id="section-appendix.c-3.3"> |
| 2162 |
The chip transmit spectrum mask must be compliant with the |
| 2163 |
"Transmit spectrum mask" from the IEEE 802.11p amendment |
| 2164 |
(but experimental environments do not require compliance).<a href="#section-appendix.c-3.3" class="pilcrow">¶</a> |
| 2165 |
</li> |
| 2166 |
<li id="section-appendix.c-3.4"> |
| 2167 |
The chip should be able to transmit up to 44.8 dBm when |
| 2168 |
used in the United States and up to |
| 2169 |
33 dBm in Europe; other regional conditions apply.<a href="#section-appendix.c-3.4" class="pilcrow">¶</a> |
| 2170 |
</li> |
| 2171 |
</ul> |
| 2172 |
<p id="section-appendix.c-4"> |
| 2173 |
Changes needed on the network stack in OCB mode are as follows:<a href="#section-appendix.c-4" class="pilcrow">¶</a></p> |
| 2174 |
<ul> |
| 2175 |
<li id="section-appendix.c-5.1"> |
| 2176 |
<p id="section-appendix.c-5.1.1"> |
| 2177 |
Physical layer:<a href="#section-appendix.c-5.1.1" class="pilcrow">¶</a></p> |
| 2178 |
<ul> |
| 2179 |
<li id="section-appendix.c-5.1.2.1"> |
| 2180 |
Orthogonal frequency-division multiple access |
| 2181 |
The chip must use the Orthogonal Frequency Division Multiple |
| 2182 |
Access (OFDMA) encoding mode.<a href="#section-appendix.c-5.1.2.1" class="pilcrow">¶</a> |
| 2183 |
</li> |
| 2184 |
<li id="section-appendix.c-5.1.2.2"> |
| 2185 |
The chip must be set to half-mode rate mode (the |
| 2186 |
internal clock frequency is divided by two).<a href="#section-appendix.c-5.1.2.2" class="pilcrow">¶</a> |
| 2187 |
</li> |
| 2188 |
<li id="section-appendix.c-5.1.2.3"> |
| 2189 |
The chip must use dedicated channels and should allow |
| 2190 |
the use of higher emission powers. This may require |
| 2191 |
modifications to the local computer file that |
| 2192 |
describes regulatory domains rules if used by the |
| 2193 |
kernel to enforce local specific restrictions. Such |
| 2194 |
modifications to the local computer file must respect |
| 2195 |
the location-specific regulatory rules.<a href="#section-appendix.c-5.1.2.3" class="pilcrow">¶</a> |
| 2196 |
</li> |
| 2197 |
</ul> |
| 2198 |
</li> |
| 2199 |
<li id="section-appendix.c-5.2"> |
| 2200 |
<p id="section-appendix.c-5.2.1"> |
| 2201 |
MAC layer:<a href="#section-appendix.c-5.2.1" class="pilcrow">¶</a></p> |
| 2202 |
<ul> |
| 2203 |
<li id="section-appendix.c-5.2.2.1"> |
| 2204 |
All management frames (beacons, join, leave, and |
| 2205 |
others) emission and reception must be disabled, |
| 2206 |
except for frames of subtype Action and Timing |
| 2207 |
Advertisement (defined below).<a href="#section-appendix.c-5.2.2.1" class="pilcrow">¶</a> |
| 2208 |
</li> |
| 2209 |
<li id="section-appendix.c-5.2.2.2"> |
| 2210 |
No encryption key or method must be used.<a href="#section-appendix.c-5.2.2.2" class="pilcrow">¶</a> |
| 2211 |
</li> |
| 2212 |
<li id="section-appendix.c-5.2.2.3"> |
| 2213 |
Packet emission and reception must be performed as in |
| 2214 |
ad hoc mode using the wildcard BSSID |
| 2215 |
(ff:ff:ff:ff:ff:ff).<a href="#section-appendix.c-5.2.2.3" class="pilcrow">¶</a> |
| 2216 |
</li> |
| 2217 |
<li id="section-appendix.c-5.2.2.4"> |
| 2218 |
The functions related to joining a BSS (Association |
| 2219 |
Request/Response) and authentication |
| 2220 |
(Authentication Request/Reply, Challenge) are not |
| 2221 |
called.<a href="#section-appendix.c-5.2.2.4" class="pilcrow">¶</a> |
| 2222 |
</li> |
| 2223 |
<li id="section-appendix.c-5.2.2.5"> |
| 2224 |
The beacon interval is always set to 0 (zero).<a href="#section-appendix.c-5.2.2.5" class="pilcrow">¶</a> |
| 2225 |
</li> |
| 2226 |
<li id="section-appendix.c-5.2.2.6"> |
| 2227 |
Timing Advertisement frames, defined in the |
| 2228 |
amendment, should be supported. The upper layer |
| 2229 |
should be able to trigger such frames emission and retrieve |
| 2230 |
information contained in the received Timing |
| 2231 |
Advertisements.<a href="#section-appendix.c-5.2.2.6" class="pilcrow">¶</a> |
| 2232 |
</li> |
| 2233 |
</ul> |
| 2234 |
</li> |
| 2235 |
</ul> |
| 2236 |
</section> |
| 2237 |
</div> |
| 2238 |
<div id="epd"> |
| 2239 |
<section id="section-appendix.d"> |
| 2240 |
<h2 id="name-protocol-layering"> |
| 2241 |
<a href="#section-appendix.d" class="section-number selfRef">Appendix D. </a><a href="#name-protocol-layering" class="section-name selfRef">Protocol Layering</a> |
| 2242 |
</h2> |
| 2243 |
<p id="section-appendix.d-1"> |
| 2244 |
A more theoretical and detailed view of layer stacking and |
| 2245 |
interfaces between the IP layer and 802.11-OCB layers is |
| 2246 |
illustrated in <a href="#fig_epd" class="xref">Figure 2</a>. The IP layer |
| 2247 |
operates on top of EtherType Protocol Discrimination |
| 2248 |
(EPD). This discrimination layer is described in <span>[<a href="#IEEE-802.3-2012" class="xref">IEEE-802.3-2012</a>]</span>. The interface between IPv6 and EPD is the LLC_SAP |
| 2249 |
(Link Layer Control Service Access Point).<a href="#section-appendix.d-1" class="pilcrow">¶</a></p> |
| 2250 |
<span id="name-ethertype-protocol-discrimi"></span><div id="fig_epd"> |
| 2251 |
<figure id="figure-2"> |
| 2252 |
<div class="artwork art-text alignCenter" id="section-appendix.d-2.1"> |
| 2253 |
<pre> |
| 2254 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2255 |
| IPv6 | |
| 2256 |
+-+-+-+-+-+-{ }+-+-+-+-+-+-+-+ |
| 2257 |
{ LLC_SAP } 802.11-OCB |
| 2258 |
+-+-+-+-+-+-{ }+-+-+-+-+-+-+-+ Boundary |
| 2259 |
| EPD | | | |
| 2260 |
| | MLME | | |
| 2261 |
+-+-+-{ MAC_SAP }+-+-+-| MLME_SAP | |
| 2262 |
| MAC Sublayer | | | 802.11-OCB |
| 2263 |
| and ch. coord. | | SME | Services |
| 2264 |
+-+-+-{ PHY_SAP }+-+-+-+-+-+-+-| | |
| 2265 |
| | PLME | | |
| 2266 |
| PHY Layer | PLME_SAP | |
| 2267 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ </pre> |
| 2268 |
</div> |
| 2269 |
<figcaption><a href="#figure-2" class="selfRef">Figure 2</a>: |
| 2270 |
<a href="#name-ethertype-protocol-discrimi" class="selfRef">EtherType Protocol Discrimination</a> |
| 2271 |
</figcaption></figure> |
| 2272 |
</div> |
| 2273 |
</section> |
| 2274 |
</div> |
| 2275 |
<div id="design-considerations"> |
| 2276 |
<section id="section-appendix.e"> |
| 2277 |
<h2 id="name-design-considerations"> |
| 2278 |
<a href="#section-appendix.e" class="section-number selfRef">Appendix E. </a><a href="#name-design-considerations" class="section-name selfRef">Design Considerations</a> |
| 2279 |
</h2> |
| 2280 |
<p id="section-appendix.e-1"> |
| 2281 |
The networks defined by 802.11-OCB are in many ways similar to |
| 2282 |
other networks of the 802.11 family. In theory, the |
| 2283 |
transportation of IPv6 over 802.11-OCB could be very similar to |
| 2284 |
the operation of IPv6 over other networks of the 802.11 |
| 2285 |
family. However, the high mobility, strong link asymmetry, and |
| 2286 |
very short connection makes the 802.11-OCB link significantly |
| 2287 |
different from other 802.11 networks. Also, automotive |
| 2288 |
applications have specific requirements for reliability, |
| 2289 |
security, and privacy, which further add to the particularity |
| 2290 |
of the 802.11-OCB link.<a href="#section-appendix.e-1" class="pilcrow">¶</a></p> |
| 2291 |
</section> |
| 2292 |
</div> |
| 2293 |
<div id="OCB-messages"> |
| 2294 |
<section id="section-appendix.f"> |
| 2295 |
<h2 id="name-ieee-80211-messages-transmi"> |
| 2296 |
<a href="#section-appendix.f" class="section-number selfRef">Appendix F. </a><a href="#name-ieee-80211-messages-transmi" class="section-name selfRef">IEEE 802.11 Messages Transmitted in OCB Mode</a> |
| 2297 |
</h2> |
| 2298 |
<p id="section-appendix.f-1"> |
| 2299 |
At the time of writing, this is the list of |
| 2300 |
IEEE 802.11 messages that may be transmitted in OCB mode, |
| 2301 |
i.e., when dot11OCBActivated is true in a STA:<a href="#section-appendix.f-1" class="pilcrow">¶</a></p> |
| 2302 |
<ul> |
| 2303 |
<li id="section-appendix.f-2.1"> |
| 2304 |
The STA may send management frames of subtype Action and, |
| 2305 |
if the STA maintains a TSF Timer, subtype Timing |
| 2306 |
Advertisement.<a href="#section-appendix.f-2.1" class="pilcrow">¶</a> |
| 2307 |
</li> |
| 2308 |
<li id="section-appendix.f-2.2"> |
| 2309 |
The STA may send control frames except those of subtype |
| 2310 |
PS-Poll, CF-End, and CF-End plus CFAck.<a href="#section-appendix.f-2.2" class="pilcrow">¶</a> |
| 2311 |
</li> |
| 2312 |
<li id="section-appendix.f-2.3"> |
| 2313 |
The STA <span class="bcp14">MUST</span> send data frames of subtype QoS |
| 2314 |
Data.<a href="#section-appendix.f-2.3" class="pilcrow">¶</a> |
| 2315 |
</li> |
| 2316 |
</ul> |
| 2317 |
</section> |
| 2318 |
</div> |
| 2319 |
<div id="example-packets"> |
| 2320 |
<section id="section-appendix.g"> |
| 2321 |
<h2 id="name-examples-of-packet-formats"> |
| 2322 |
<a href="#section-appendix.g" class="section-number selfRef">Appendix G. </a><a href="#name-examples-of-packet-formats" class="section-name selfRef">Examples of Packet Formats</a> |
| 2323 |
</h2> |
| 2324 |
<p id="section-appendix.g-1"> |
| 2325 |
This section describes an example of an IPv6 packet captured |
| 2326 |
over an IEEE 802.11-OCB link.<a href="#section-appendix.g-1" class="pilcrow">¶</a></p> |
| 2327 |
<p id="section-appendix.g-2"> |
| 2328 |
By way of example, we show that there is no modification in the |
| 2329 |
headers when transmitted over 802.11-OCB networks -- they are |
| 2330 |
transmitted like any other 802.11 and Ethernet packets.<a href="#section-appendix.g-2" class="pilcrow">¶</a></p> |
| 2331 |
<p id="section-appendix.g-3"> |
| 2332 |
We describe an experiment for capturing an IPv6 packet on an |
| 2333 |
802.11-OCB link. In the topology depicted in <a href="#topo" class="xref">Figure 3</a>, the packet is an IPv6 Router Advertisement. |
| 2334 |
This packet is emitted by a router on its 802.11-OCB |
| 2335 |
interface. The packet is captured on the host using a |
| 2336 |
network protocol analyzer (e.g., Wireshark). The capture is |
| 2337 |
performed in two different modes: direct mode and monitor |
| 2338 |
mode. The topology used during the capture is depicted below.<a href="#section-appendix.g-3" class="pilcrow">¶</a></p> |
| 2339 |
<p id="section-appendix.g-4"> |
| 2340 |
The packet is captured on the host. The host is an IP-OBU |
| 2341 |
containing an 802.11 interface in Peripheral Component Interconnect |
| 2342 |
(PCI) Express format (an Industrial Technology Research Institute |
| 2343 |
(ITRI) product). The kernel runs the ath5k software driver with |
| 2344 |
modifications for OCB mode. The capture tool is Wireshark. |
| 2345 |
The file format for saving and analyzing is .pcap. The packet is |
| 2346 |
generated by the router, which is an IP-RSU (an ITRI |
| 2347 |
product).<a href="#section-appendix.g-4" class="pilcrow">¶</a></p> |
| 2348 |
<span id="name-topology-for-capturing-ip-p"></span><div id="topo"> |
| 2349 |
<figure id="figure-3"> |
| 2350 |
<div class="artwork art-text alignCenter" id="section-appendix.g-5.1"> |
| 2351 |
<pre> |
| 2352 |
+--------+ +-------+ |
| 2353 |
| | 802.11-OCB Link | | |
| 2354 |
---| Router |--------------------------------| Host | |
| 2355 |
| | | | |
| 2356 |
+--------+ +-------+ </pre> |
| 2357 |
</div> |
| 2358 |
<figcaption><a href="#figure-3" class="selfRef">Figure 3</a>: |
| 2359 |
<a href="#name-topology-for-capturing-ip-p" class="selfRef">Topology for Capturing IP Packets on 802.11-OCB</a> |
| 2360 |
</figcaption></figure> |
| 2361 |
</div> |
| 2362 |
<p id="section-appendix.g-6"> |
| 2363 |
During several capture operations running from a few moments |
| 2364 |
to several hours, no messages relevant to the BSSID contexts |
| 2365 |
were captured (Association Request/Response, Authentication |
| 2366 |
Req/Resp, or beacon). This shows that the operation of |
| 2367 |
802.11-OCB is outside the context of a BSSID.<a href="#section-appendix.g-6" class="pilcrow">¶</a></p> |
| 2368 |
<p id="section-appendix.g-7"> |
| 2369 |
Overall, the captured message is identical to a capture of |
| 2370 |
an IPv6 packet emitted on an 802.11b interface. The contents |
| 2371 |
are exactly the same.<a href="#section-appendix.g-7" class="pilcrow">¶</a></p> |
| 2372 |
<section id="section-g.1"> |
| 2373 |
<h2 id="name-capture-in-monitor-mode"> |
| 2374 |
<a href="#section-g.1" class="section-number selfRef">G.1. </a><a href="#name-capture-in-monitor-mode" class="section-name selfRef">Capture in Monitor Mode</a> |
| 2375 |
</h2> |
| 2376 |
<p id="section-g.1-1"> |
| 2377 |
The IPv6 RA packet captured in monitor mode is illustrated |
| 2378 |
below. The Radiotap header provides more flexibility for |
| 2379 |
reporting the characteristics of frames. The Radiotap header |
| 2380 |
is prepended by this particular stack and operating system on |
| 2381 |
the host machine to the RA packet received from the network |
| 2382 |
(the Radiotap header is not present on the air). The |
| 2383 |
implementation-dependent Radiotap header is useful for |
| 2384 |
piggybacking PHY information from the chip's registers as data |
| 2385 |
in a packet that is understandable by userland applications using |
| 2386 |
socket interfaces (the PHY interface can be, for example, |
| 2387 |
power levels, data rate, or the ratio of signal to noise).<a href="#section-g.1-1" class="pilcrow">¶</a></p> |
| 2388 |
<p id="section-g.1-2"> |
| 2389 |
The packet present on the air is formed by the IEEE 802.11 Data |
| 2390 |
header, Logical Link Control header, IPv6 Base header, and |
| 2391 |
ICMPv6 header.<a href="#section-g.1-2" class="pilcrow">¶</a></p> |
| 2392 |
<span id="name-radiotap-header-v0"></span><div id="figA"> |
| 2393 |
<figure id="figure-4"> |
| 2394 |
<div class="artwork art-text alignCenter" id="section-g.1-3.1"> |
| 2395 |
<pre> |
| 2396 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2397 |
|Header Revision| Header Pad | Header Length | |
| 2398 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2399 |
| Present Flags | |
| 2400 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2401 |
| Data Rate | Pad | |
| 2402 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2403 |
</pre> |
| 2404 |
</div> |
| 2405 |
<figcaption><a href="#figure-4" class="selfRef">Figure 4</a>: |
| 2406 |
<a href="#name-radiotap-header-v0" class="selfRef">Radiotap Header v0</a> |
| 2407 |
</figcaption></figure> |
| 2408 |
</div> |
| 2409 |
<span id="name-ieee-80211-data-header"></span><div id="figB"> |
| 2410 |
<figure id="figure-5"> |
| 2411 |
<div class="artwork art-text alignCenter" id="section-g.1-4.1"> |
| 2412 |
<pre> |
| 2413 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2414 |
| Type/Subtype and Frame Ctrl | Duration | |
| 2415 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2416 |
| Receiver Address... |
| 2417 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2418 |
... Receiver Address | Transmitter Address... |
| 2419 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2420 |
... Transmitter Address | |
| 2421 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2422 |
| BSS ID... |
| 2423 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2424 |
... BSS ID | Frag Number and Seq Number | |
| 2425 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2426 |
</pre> |
| 2427 |
</div> |
| 2428 |
<figcaption><a href="#figure-5" class="selfRef">Figure 5</a>: |
| 2429 |
<a href="#name-ieee-80211-data-header" class="selfRef">IEEE 802.11 Data Header</a> |
| 2430 |
</figcaption></figure> |
| 2431 |
</div> |
| 2432 |
<span id="name-logical-link-control-header"></span><div id="figC"> |
| 2433 |
<figure id="figure-6"> |
| 2434 |
<div class="artwork art-text alignCenter" id="section-g.1-5.1"> |
| 2435 |
<pre> |
| 2436 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2437 |
| DSAP |I| SSAP |C| Control Field | Org. Code... |
| 2438 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2439 |
... Organizational Code | Type | |
| 2440 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2441 |
</pre> |
| 2442 |
</div> |
| 2443 |
<figcaption><a href="#figure-6" class="selfRef">Figure 6</a>: |
| 2444 |
<a href="#name-logical-link-control-header" class="selfRef">Logical Link Control Header</a> |
| 2445 |
</figcaption></figure> |
| 2446 |
</div> |
| 2447 |
<span id="name-ipv6-base-header"></span><div id="figD"> |
| 2448 |
<figure id="figure-7"> |
| 2449 |
<div class="artwork art-text alignCenter" id="section-g.1-6.1"> |
| 2450 |
<pre> |
| 2451 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2452 |
|Version| Traffic Class | Flow Label | |
| 2453 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2454 |
| Payload Length | Next Header | Hop Limit | |
| 2455 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2456 |
| | |
| 2457 |
+ + |
| 2458 |
| | |
| 2459 |
+ Source Address + |
| 2460 |
| | |
| 2461 |
+ + |
| 2462 |
| | |
| 2463 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2464 |
| | |
| 2465 |
+ + |
| 2466 |
| | |
| 2467 |
+ Destination Address + |
| 2468 |
| | |
| 2469 |
+ + |
| 2470 |
| | |
| 2471 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2472 |
</pre> |
| 2473 |
</div> |
| 2474 |
<figcaption><a href="#figure-7" class="selfRef">Figure 7</a>: |
| 2475 |
<a href="#name-ipv6-base-header" class="selfRef">IPv6 Base Header</a> |
| 2476 |
</figcaption></figure> |
| 2477 |
</div> |
| 2478 |
<span id="name-router-advertisement"></span><div id="figE"> |
| 2479 |
<figure id="figure-8"> |
| 2480 |
<div class="artwork art-text alignCenter" id="section-g.1-7.1"> |
| 2481 |
<pre> |
| 2482 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2483 |
| Type | Code | Checksum | |
| 2484 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2485 |
| Cur Hop Limit |M|O| Reserved | Router Lifetime | |
| 2486 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2487 |
| Reachable Time | |
| 2488 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2489 |
| Retrans Timer | |
| 2490 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2491 |
| Options ... |
| 2492 |
+-+-+-+-+-+-+-+-+-+-+-+- </pre> |
| 2493 |
</div> |
| 2494 |
<figcaption><a href="#figure-8" class="selfRef">Figure 8</a>: |
| 2495 |
<a href="#name-router-advertisement" class="selfRef">Router Advertisement</a> |
| 2496 |
</figcaption></figure> |
| 2497 |
</div> |
| 2498 |
<p id="section-g.1-8"> |
| 2499 |
The value of the Data Rate field in the Radiotap header is set |
| 2500 |
to 6 Mb/s. This indicates the rate at which this RA was |
| 2501 |
received.<a href="#section-g.1-8" class="pilcrow">¶</a></p> |
| 2502 |
<p id="section-g.1-9"> |
| 2503 |
The value of the Transmitter Address in the IEEE 802.11 Data |
| 2504 |
header is set to a 48-bit value. The value of the destination |
| 2505 |
address is 33:33:00:00:00:1 (all-nodes multicast address). |
| 2506 |
The value of the BSS ID field is ff:ff:ff:ff:ff:ff, which is |
| 2507 |
recognized by the network protocol analyzer as being |
| 2508 |
"broadcast". The Fragment number and Sequence number fields |
| 2509 |
together are set to 0x90C6.<a href="#section-g.1-9" class="pilcrow">¶</a></p> |
| 2510 |
<p id="section-g.1-10"> |
| 2511 |
The value of the Organization Code field in the |
| 2512 |
Logical Link Control header is set to 0x0, recognized as |
| 2513 |
"Encapsulated Ethernet". The value of the Type field is |
| 2514 |
0x86DD (hexadecimal 86DD; otherwise, #86DD), recognized |
| 2515 |
as "IPv6".<a href="#section-g.1-10" class="pilcrow">¶</a></p> |
| 2516 |
<p id="section-g.1-11"> |
| 2517 |
A Router Advertisement is periodically sent by the router to |
| 2518 |
multicast group address ff02::1. It is ICMP packet type |
| 2519 |
134. The IPv6 Neighbor Discovery's Router Advertisement |
| 2520 |
message contains an 8-bit field reserved for single-bit flags, |
| 2521 |
as described in <span>[<a href="#RFC4861" class="xref">RFC4861</a>]</span>.<a href="#section-g.1-11" class="pilcrow">¶</a></p> |
| 2522 |
<p id="section-g.1-12"> |
| 2523 |
The IPv6 header contains the link-local address of the router |
| 2524 |
(source) configured via the EUI-64 algorithm, and the destination |
| 2525 |
address is set to ff02::1.<a href="#section-g.1-12" class="pilcrow">¶</a></p> |
| 2526 |
<p id="section-g.1-13"> |
| 2527 |
The Ethernet Type field in the Logical Link Control header |
| 2528 |
is set to 0x86dd, which indicates that the frame transports |
| 2529 |
an IPv6 packet. In the IEEE 802.11 data, the destination |
| 2530 |
address is 33:33:00:00:00:01, which is the corresponding |
| 2531 |
multicast MAC address. The BSS ID is a broadcast address of |
| 2532 |
ff:ff:ff:ff:ff:ff. Due to the short link duration between |
| 2533 |
vehicles and the roadside infrastructure, there is no need in IEEE 802.11-OCB |
| 2534 |
to wait for the completion of association |
| 2535 |
and authentication procedures before exchanging data. IEEE |
| 2536 |
802.11-OCB enabled nodes use the wildcard BSSID (a value of |
| 2537 |
all 1s) and may start communicating as soon as they arrive |
| 2538 |
on the communication channel.<a href="#section-g.1-13" class="pilcrow">¶</a></p> |
| 2539 |
</section> |
| 2540 |
<section id="section-g.2"> |
| 2541 |
<h2 id="name-capture-in-normal-mode"> |
| 2542 |
<a href="#section-g.2" class="section-number selfRef">G.2. </a><a href="#name-capture-in-normal-mode" class="section-name selfRef">Capture in Normal Mode</a> |
| 2543 |
</h2> |
| 2544 |
<p id="section-g.2-1"> |
| 2545 |
The same IPv6 Router Advertisement packet described above |
| 2546 |
(monitor mode) is captured on the host in normal mode and is |
| 2547 |
depicted below.<a href="#section-g.2-1" class="pilcrow">¶</a></p> |
| 2548 |
<span id="name-ethernet-ii-header"></span><div id="figF"> |
| 2549 |
<figure id="figure-9"> |
| 2550 |
<div class="artwork art-text alignCenter" id="section-g.2-2.1"> |
| 2551 |
<pre> |
| 2552 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2553 |
| Destination... |
| 2554 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2555 |
...Destination | Source... |
| 2556 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2557 |
...Source | |
| 2558 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2559 |
| Type | |
| 2560 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2561 |
</pre> |
| 2562 |
</div> |
| 2563 |
<figcaption><a href="#figure-9" class="selfRef">Figure 9</a>: |
| 2564 |
<a href="#name-ethernet-ii-header" class="selfRef">Ethernet II Header</a> |
| 2565 |
</figcaption></figure> |
| 2566 |
</div> |
| 2567 |
<span id="name-ipv6-base-header-2"></span><div id="figG"> |
| 2568 |
<figure id="figure-10"> |
| 2569 |
<div class="artwork art-text alignCenter" id="section-g.2-3.1"> |
| 2570 |
<pre> |
| 2571 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2572 |
|Version| Traffic Class | Flow Label | |
| 2573 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2574 |
| Payload Length | Next Header | Hop Limit | |
| 2575 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2576 |
| | |
| 2577 |
+ + |
| 2578 |
| | |
| 2579 |
+ Source Address + |
| 2580 |
| | |
| 2581 |
+ + |
| 2582 |
| | |
| 2583 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2584 |
| | |
| 2585 |
+ + |
| 2586 |
| | |
| 2587 |
+ Destination Address + |
| 2588 |
| | |
| 2589 |
+ + |
| 2590 |
| | |
| 2591 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2592 |
</pre> |
| 2593 |
</div> |
| 2594 |
<figcaption><a href="#figure-10" class="selfRef">Figure 10</a>: |
| 2595 |
<a href="#name-ipv6-base-header-2" class="selfRef">IPv6 Base Header</a> |
| 2596 |
</figcaption></figure> |
| 2597 |
</div> |
| 2598 |
<span id="name-router-advertisement-2"></span><div id="figH"> |
| 2599 |
<figure id="figure-11"> |
| 2600 |
<div class="artwork art-text alignCenter" id="section-g.2-4.1"> |
| 2601 |
<pre> |
| 2602 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2603 |
| Type | Code | Checksum | |
| 2604 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2605 |
| Cur Hop Limit |M|O| Reserved | Router Lifetime | |
| 2606 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2607 |
| Reachable Time | |
| 2608 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2609 |
| Retrans Timer | |
| 2610 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 2611 |
| Options ... |
| 2612 |
+-+-+-+-+-+-+-+-+-+-+-+- </pre> |
| 2613 |
</div> |
| 2614 |
<figcaption><a href="#figure-11" class="selfRef">Figure 11</a>: |
| 2615 |
<a href="#name-router-advertisement-2" class="selfRef">Router Advertisement</a> |
| 2616 |
</figcaption></figure> |
| 2617 |
</div> |
| 2618 |
<p id="section-g.2-5"> |
| 2619 |
One notices that the Radiotap header, the IEEE 802.11 Data |
| 2620 |
header, and the Logical Link Control headers are not present. |
| 2621 |
On the other hand, a new header named the Ethernet II header is |
| 2622 |
present.<a href="#section-g.2-5" class="pilcrow">¶</a></p> |
| 2623 |
<p id="section-g.2-6"> |
| 2624 |
The Destination and Source addresses in the Ethernet II header |
| 2625 |
contain the same values as the Receiver Address and |
| 2626 |
Transmitter Address fields present in the IEEE 802.11 Data header in |
| 2627 |
the monitor mode capture.<a href="#section-g.2-6" class="pilcrow">¶</a></p> |
| 2628 |
<p id="section-g.2-7"> |
| 2629 |
The value of the Type field in the Ethernet II header is |
| 2630 |
0x86DD (recognized as "IPv6"); this value is the same as |
| 2631 |
the value of the Type field in the Logical Link Control header |
| 2632 |
in the monitor mode capture.<a href="#section-g.2-7" class="pilcrow">¶</a></p> |
| 2633 |
<p id="section-g.2-8"> |
| 2634 |
The knowledgeable experimenter will no doubt notice the |
| 2635 |
similarity of this Ethernet II header with a capture in normal |
| 2636 |
mode on a pure Ethernet cable interface.<a href="#section-g.2-8" class="pilcrow">¶</a></p> |
| 2637 |
<p id="section-g.2-9"> |
| 2638 |
A frame translation is inserted on top of a pure IEEE 802.11 |
| 2639 |
MAC layer in order to adapt packets before delivering the |
| 2640 |
payload data to the applications. It adapts 802.11 LLC/MAC |
| 2641 |
headers to Ethernet II headers. Specifically, this |
| 2642 |
adaptation consists of the elimination of the Radiotap, |
| 2643 |
802.11, and LLC headers and the insertion of the Ethernet |
| 2644 |
II header. In this way, IPv6 runs straight over LLC over |
| 2645 |
the 802.11-OCB MAC layer; this is further confirmed by the |
| 2646 |
use of the unique Type 0x86DD.<a href="#section-g.2-9" class="pilcrow">¶</a></p> |
| 2647 |
</section> |
| 2648 |
</section> |
| 2649 |
</div> |
| 2650 |
<div id="extra-terminology"> |
| 2651 |
<section id="section-appendix.h"> |
| 2652 |
<h2 id="name-extra-terminology"> |
| 2653 |
<a href="#section-appendix.h" class="section-number selfRef">Appendix H. </a><a href="#name-extra-terminology" class="section-name selfRef">Extra Terminology</a> |
| 2654 |
</h2> |
| 2655 |
<p id="section-appendix.h-1"> |
| 2656 |
The following terms are defined outside the IETF. They are |
| 2657 |
used to define the main terms in the terminology section (<a href="#terminology" class="xref">Section 2</a>).<a href="#section-appendix.h-1" class="pilcrow">¶</a></p> |
| 2658 |
<dl class="dlNewline" id="section-appendix.h-2"> |
| 2659 |
<dt id="section-appendix.h-2.1">DSRC (Dedicated Short Range Communication):</dt> |
| 2660 |
<dd id="section-appendix.h-2.2">The US Federal Communications Commission |
| 2661 |
(FCC) Dedicated Short Range Communication (DSRC) is defined in |
| 2662 |
the Code of Federal Regulations (CFR) 47, Parts 90 <span>[<a href="#CFR-90" class="xref">CFR-90</a>]</span> and 95 <span>[<a href="#CFR-95" class="xref">CFR-95</a>]</span>. |
| 2663 |
This Code is referenced in the definitions below. At the time |
| 2664 |
of the writing of this document, the last update of this |
| 2665 |
Code was dated December 6, 2019.<a href="#section-appendix.h-2.2" class="pilcrow">¶</a> |
| 2666 |
</dd> |
| 2667 |
<dt id="section-appendix.h-2.3">DSRCS (Dedicated Short-Range Communications Services):</dt> |
| 2668 |
<dd id="section-appendix.h-2.4"> |
| 2669 |
Radio techniques are used to transfer data over short distances between |
| 2670 |
roadside and mobile units, between mobile units, and between portable and |
| 2671 |
mobile units to perform operations related to the improvement of traffic |
| 2672 |
flow, traffic safety, and other intelligent transportation service |
| 2673 |
applications in a variety of environments. DSRCS systems may also transmit status and |
| 2674 |
instructional messages related to the units involved. <span>[<a href="#CFR-90.7" class="xref">CFR-90.7</a>]</span><a href="#section-appendix.h-2.4" class="pilcrow">¶</a> |
| 2675 |
</dd> |
| 2676 |
<dt id="section-appendix.h-2.5">OBU (On-Board Unit):</dt> |
| 2677 |
<dd id="section-appendix.h-2.6">An |
| 2678 |
On-Board Unit is a DSRCS transceiver that is normally mounted |
| 2679 |
in or on a vehicle or may be a portable unit in some instances. An OBU can be operational while a vehicle or |
| 2680 |
person is either mobile or stationary. The OBUs receive and |
| 2681 |
contend for time to transmit on one or more radio frequency |
| 2682 |
(RF) channels. Except where specifically excluded, OBU |
| 2683 |
operation is permitted wherever vehicle operation or human |
| 2684 |
passage is permitted. The OBUs mounted in vehicles are |
| 2685 |
licensed by rule under part 95 of <span>[<a href="#CFR-95" class="xref">CFR-95</a>]</span> and |
| 2686 |
communicate with Roadside Units (RSUs) and other OBUs. |
| 2687 |
Portable OBUs are also licensed by rule under part 95 of <span>[<a href="#CFR-95" class="xref">CFR-95</a>]</span>. OBU operations in the Unlicensed National |
| 2688 |
Information Infrastructure (U-NII) Bands follow the rules in |
| 2689 |
those bands. <span>[<a href="#CFR-90.7" class="xref">CFR-90.7</a>]</span><a href="#section-appendix.h-2.6" class="pilcrow">¶</a> |
| 2690 |
</dd> |
| 2691 |
<dt id="section-appendix.h-2.7">RSU (Roadside Unit):</dt> |
| 2692 |
<dd id="section-appendix.h-2.8">A |
| 2693 |
Roadside Unit is a DSRC transceiver that is mounted along a |
| 2694 |
road or pedestrian passageway. An RSU may also be mounted on |
| 2695 |
a vehicle or may be hand carried, but it may only operate when the |
| 2696 |
vehicle or hand-carried unit is stationary. Perhaps |
| 2697 |
Furthermore, an RSU is restricted to the location where it is licensed |
| 2698 |
to operate. However, portable |
| 2699 |
or handheld RSUs are permitted to operate where they do not |
| 2700 |
interfere with a site-licensed operation. An RSU broadcasts |
| 2701 |
data to OBUs or exchanges data with OBUs in its communications |
| 2702 |
zone. An RSU also provides channel assignments and operating |
| 2703 |
instructions to OBUs in its communications zone when |
| 2704 |
required. <span>[<a href="#CFR-90.7" class="xref">CFR-90.7</a>]</span><a href="#section-appendix.h-2.8" class="pilcrow">¶</a> |
| 2705 |
</dd> |
| 2706 |
</dl> |
| 2707 |
</section> |
| 2708 |
</div> |
| 2709 |
<div id="nd-wireless"> |
| 2710 |
<section id="section-appendix.i"> |
| 2711 |
<h2 id="name-neighbor-discovery-nd-poten"> |
| 2712 |
<a href="#section-appendix.i" class="section-number selfRef">Appendix I. </a><a href="#name-neighbor-discovery-nd-poten" class="section-name selfRef">Neighbor Discovery (ND) Potential Issues in Wireless Links</a> |
| 2713 |
</h2> |
| 2714 |
<p id="section-appendix.i-1"> |
| 2715 |
IPv6 Neighbor Discovery (IPv6 ND) <span>[<a href="#RFC4861" class="xref">RFC4861</a>]</span> <span>[<a href="#RFC4862" class="xref">RFC4862</a>]</span> was |
| 2716 |
designed for point-to-point and transit links, such as |
| 2717 |
Ethernet, with the expectation of cheap and reliable support |
| 2718 |
for multicast from the lower layer. <span><a href="https://www.rfc-editor.org/rfc/rfc4861#section-3.2" class="relref">Section 3.2</a> of [<a href="#RFC4861" class="xref">RFC4861</a>]</span> indicates that the operation on shared media and on |
| 2719 |
NBMA networks require additional |
| 2720 |
support, e.g., for AR and DAD, which depend on multicast. An |
| 2721 |
infrastructureless radio network such as OCB shares properties |
| 2722 |
with both shared media and NBMA networks and then adds its |
| 2723 |
own complexity, e.g., from movement and interference that |
| 2724 |
allow only transient and non-transitive reachability between |
| 2725 |
any set of peers.<a href="#section-appendix.i-1" class="pilcrow">¶</a></p> |
| 2726 |
<p id="section-appendix.i-2"> |
| 2727 |
The uniqueness of an address within a scoped domain is a key |
| 2728 |
pillar of IPv6 and is the basis for unicast IP communication. <span>[<a href="#RFC4861" class="xref">RFC4861</a>]</span> details the DAD method to prevent an address from |
| 2729 |
being duplicated. For a link-local address, the scope is the link, |
| 2730 |
whereas for a globally reachable address, the scope is much |
| 2731 |
larger. The underlying assumption for DAD to operate |
| 2732 |
correctly is that the node that owns an IPv6 address can reach |
| 2733 |
any other node within the scope at the time it claims its |
| 2734 |
address, which is done by sending a Neighbor Solicitation (NS) multicast message, and |
| 2735 |
can hear any future claim for that address by another party |
| 2736 |
within the scope for the duration of the address ownership.<a href="#section-appendix.i-2" class="pilcrow">¶</a></p> |
| 2737 |
<p id="section-appendix.i-3"> |
| 2738 |
In the case of OCB, there is a potentially a need to define a scope that is |
| 2739 |
compatible with DAD. The scope cannot be the set of nodes that a transmitter |
| 2740 |
can reach at a particular time because that set varies all the time and |
| 2741 |
does not meet the DAD requirements for a link-local address that can be |
| 2742 |
used anytime and anywhere. The generic expectation of a reliable |
| 2743 |
multicast is not ensured, and the operation of DAD and AR |
| 2744 |
as specified by <span>[<a href="#RFC4861" class="xref">RFC4861</a>]</span> cannot be |
| 2745 |
guaranteed. Moreover, multicast transmissions that rely on |
| 2746 |
broadcast are not only unreliable but are also often |
| 2747 |
detrimental to unicast traffic (see <span>[<a href="#I-D.ietf-mboned-ieee802-mcast-problems" class="xref">IEEE802-MCAST</a>]</span>).<a href="#section-appendix.i-3" class="pilcrow">¶</a></p> |
| 2748 |
<p id="section-appendix.i-4"> |
| 2749 |
Early experience indicates that it should be possible to |
| 2750 |
exchange IPv6 packets over OCB while relying on IPv6 ND alone |
| 2751 |
for DAD and AR (Address Resolution) in good conditions. In the absence |
| 2752 |
of a correct DAD operation, a node that relies only on IPv6 ND |
| 2753 |
for AR and DAD over OCB should ensure that the addresses that |
| 2754 |
it uses are unique by means other than DAD. It must be noted |
| 2755 |
that deriving an IPv6 address from a globally unique MAC |
| 2756 |
address has this property but may yield privacy issues.<a href="#section-appendix.i-4" class="pilcrow">¶</a></p> |
| 2757 |
<p id="section-appendix.i-5"><span>[<a href="#RFC8505" class="xref">RFC8505</a>]</span> provides a more recent approach to IPv6 ND, in |
| 2758 |
particular DAD. <span>[<a href="#RFC8505" class="xref">RFC8505</a>]</span> is designed to fit wireless and |
| 2759 |
otherwise constrained networks whereby multicast and/or |
| 2760 |
continuous access to the medium may not be guaranteed. <span>[<a href="#RFC8505" class="xref">RFC8505</a>], <a href="https://www.rfc-editor.org/rfc/rfc8505#section-5.6" class="relref">Section 5.6</a></span> ("Link-Local Addresses and Registration") |
| 2761 |
indicates that the scope of uniqueness for a link-local |
| 2762 |
address is restricted to a pair of nodes that uses it to |
| 2763 |
communicate and provides a method to assert the uniqueness |
| 2764 |
and resolve the link-layer address using a unicast exchange.<a href="#section-appendix.i-5" class="pilcrow">¶</a></p> |
| 2765 |
<p id="section-appendix.i-6"><span>[<a href="#RFC8505" class="xref">RFC8505</a>]</span> also enables a router (acting as a 6LR) to own a |
| 2766 |
prefix and act as a registrar (acting as a 6LBR) for addresses |
| 2767 |
within the associated subnet. A peer host (acting as a 6LN) |
| 2768 |
registers an address derived from that prefix and can use it |
| 2769 |
for the lifetime of the registration. The prefix is advertised |
| 2770 |
as not on-link, which means that the 6LN uses the 6LR to relay |
| 2771 |
its packets within the subnet, and participation to the subnet |
| 2772 |
is constrained to the time of reachability to the 6LR. Note |
| 2773 |
that an RSU that provides internet connectivity <span class="bcp14">MAY</span> announce a |
| 2774 |
default router preference <span>[<a href="#RFC4191" class="xref">RFC4191</a>]</span>, whereas a car that does |
| 2775 |
not provide that connectivity <span class="bcp14">MUST NOT</span> do so. This operation |
| 2776 |
presents similarities to that of an access point, but at |
| 2777 |
Layer 3. This is why <span>[<a href="#RFC8505" class="xref">RFC8505</a>]</span> is well suited for wireless in |
| 2778 |
general.<a href="#section-appendix.i-6" class="pilcrow">¶</a></p> |
| 2779 |
<p id="section-appendix.i-7"> |
| 2780 |
Support of <span>[<a href="#RFC8505" class="xref">RFC8505</a>]</span> may be implemented on OCB. OCB nodes |
| 2781 |
that support <span>[<a href="#RFC8505" class="xref">RFC8505</a>]</span> <span class="bcp14">SHOULD</span> support the 6LN operation in order |
| 2782 |
to act as a host and may support the 6LR and 6LBR operations |
| 2783 |
in order to act as a router and in particular to own a prefix |
| 2784 |
that can be used by hosts that are compliant with <span>[<a href="#RFC8505" class="xref">RFC8505</a>]</span> for address |
| 2785 |
autoconfiguration and registration.<a href="#section-appendix.i-7" class="pilcrow">¶</a></p> |
| 2786 |
</section> |
| 2787 |
</div> |
| 2788 |
<div id="Acknowledgements"> |
| 2789 |
<section id="section-appendix.j"> |
| 2790 |
<h2 id="name-acknowledgements"> |
| 2791 |
<a href="#name-acknowledgements" class="section-name selfRef">Acknowledgements</a> |
| 2792 |
</h2> |
| 2793 |
<p id="section-appendix.j-1"> |
| 2794 |
The authors would like to thank <span class="contact-name">Alexandre Petrescu</span> for |
| 2795 |
initiating this work and for being the lead author up to draft version 43 of |
| 2796 |
this document.<a href="#section-appendix.j-1" class="pilcrow">¶</a></p> |
| 2797 |
<p id="section-appendix.j-2"> |
| 2798 |
|
| 2799 |
The authors would like to thank <span class="contact-name">Pascal Thubert</span> for reviewing, |
| 2800 |
proofreading, and suggesting modifications for this document.<a href="#section-appendix.j-2" class="pilcrow">¶</a></p> |
| 2801 |
<p id="section-appendix.j-3"> |
| 2802 |
|
| 2803 |
The authors would like to thank <span class="contact-name">Mohamed Boucadair</span> for |
| 2804 |
proofreading and suggesting modifications for this document.<a href="#section-appendix.j-3" class="pilcrow">¶</a></p> |
| 2805 |
<p id="section-appendix.j-4"> |
| 2806 |
|
| 2807 |
The authors would like to thank <span class="contact-name">Eric Vyncke</span> for |
| 2808 |
reviewing the suggesting modifications of this document.<a href="#section-appendix.j-4" class="pilcrow">¶</a></p> |
| 2809 |
<p id="section-appendix.j-5"> |
| 2810 |
The authors would like to thank <span class="contact-name">Witold Klaudel</span>, <span class="contact-name">Ryuji Wakikawa</span>, <span class="contact-name">Emmanuel Baccelli</span>, <span class="contact-name">John Kenney</span>, <span class="contact-name">John Moring</span>, |
| 2811 |
<span class="contact-name">Francois Simon</span>, <span class="contact-name">Dan Romascanu</span>, <span class="contact-name">Konstantin Khait</span>, <span class="contact-name">Ralph Droms</span>, |
| 2812 |
<span class="contact-name">Richard 'Dick' Roy</span>, <span class="contact-name">Ray Hunter</span>, <span class="contact-name">Tom Kurihara</span>, <span class="contact-name">Michal Sojka</span>, |
| 2813 |
<span class="contact-name">Jan de Jongh</span>, <span class="contact-name">Suresh Krishnan</span>, <span class="contact-name">Dino Farinacci</span>, <span class="contact-name">Vincent Park</span>, |
| 2814 |
<span class="contact-name">Jaehoon Paul Jeong</span>, <span class="contact-name">Gloria Gwynne</span>, <span class="contact-name">Hans-Joachim Fischer</span>, <span class="contact-name">Russ Housley</span>, <span class="contact-name">Rex Buddenberg</span>, <span class="contact-name">Erik Nordmark</span>, <span class="contact-name">Bob Moskowitz</span>, <span class="contact-name">Andrew Dryden</span>, <span class="contact-name">Georg Mayer</span>, <span class="contact-name">Dorothy Stanley</span>, <span class="contact-name">Sandra Cespedes</span>, <span class="contact-name">Mariano Falcitelli</span>, <span class="contact-name">Sri Gundavelli</span>, <span class="contact-name">Abdussalam Baryun</span>, <span class="contact-name">Margaret Cullen</span>, <span class="contact-name">Erik Kline</span>, <span class="contact-name">Carlos Jesus Bernardos Cano</span>, |
| 2815 |
<span class="contact-name">Ronald in 't Velt</span>, <span class="contact-name">Katrin Sjoberg</span>, <span class="contact-name">Roland Bless</span>, <span class="contact-name">Tijink Jasja</span>, <span class="contact-name">Kevin Smith</span>, |
| 2816 |
<span class="contact-name">Brian Carpenter</span>, <span class="contact-name">Julian Reschke</span>, <span class="contact-name">Mikael Abrahamsson</span>, <span class="contact-name">Dirk von Hugo</span>, <span class="contact-name">Lorenzo Colitti</span>, <span class="contact-name">Pascal Thubert</span>, <span class="contact-name">Ole Troan</span>, <span class="contact-name">Jinmei Tatuya</span>, <span class="contact-name">Joel Halpern</span>, <span class="contact-name">Eric Gray</span>, and <span class="contact-name">William Whyte</span>. Their |
| 2817 |
valuable comments clarified particular issues and generally |
| 2818 |
helped to improve the document.<a href="#section-appendix.j-5" class="pilcrow">¶</a></p> |
| 2819 |
<p id="section-appendix.j-6"><span class="contact-name">Pierre Pfister</span>, <span class="contact-name">Rostislav Lisovy</span>, and others wrote 802.11-OCB |
| 2820 |
drivers for Linux.<a href="#section-appendix.j-6" class="pilcrow">¶</a></p> |
| 2821 |
<p id="section-appendix.j-7"> |
| 2822 |
For the multicast discussion, the authors would like to thank |
| 2823 |
<span class="contact-name">Owen DeLong</span>, <span class="contact-name">Joe Touch</span>, |
| 2824 |
<span class="contact-name">Jen Linkova</span>, <span class="contact-name">Erik Kline</span>, <span class="contact-name">Brian Haberman</span>, and participants to discussions in network working |
| 2825 |
groups.<a href="#section-appendix.j-7" class="pilcrow">¶</a></p> |
| 2826 |
<p id="section-appendix.j-8"> |
| 2827 |
The authors would like to thank the participants of the |
| 2828 |
Birds-of-a-Feather "Intelligent Transportation Systems" |
| 2829 |
meetings held at IETF in 2016.<a href="#section-appendix.j-8" class="pilcrow">¶</a></p> |
| 2830 |
<p id="section-appendix.j-9"> |
| 2831 |
The human rights protocol considerations review was done by <span class="contact-name">Amelia Andersdotter</span>.<a href="#section-appendix.j-9" class="pilcrow">¶</a></p> |
| 2832 |
<p id="section-appendix.j-10">The work of <span class="contact-name">Jong-Hyouk Lee</span> was supported by the National Research Foundation |
| 2833 |
of Korea (NRF) grant funded by the Korea government (MSIT) (NRF-2018R1A4A1025632).<a href="#section-appendix.j-10" class="pilcrow">¶</a></p> |
| 2834 |
<p id="section-appendix.j-11">The work of <span class="contact-name">Jérôme Härri</span> was supported by EURECOM industrial members, |
| 2835 |
namely BMW Group, IABG, Monaco Telecom, Orange, SAP and Symantec. This RFC |
| 2836 |
reflects the view of the IPWAVE WG and does not necessarily reflect the |
| 2837 |
official policy or position of EURECOM industrial members.<a href="#section-appendix.j-11" class="pilcrow">¶</a></p> |
| 2838 |
</section> |
| 2839 |
</div> |
| 2840 |
<div id="Contributors"> |
| 2841 |
<section id="section-appendix.k"> |
| 2842 |
<h2 id="name-contributors"> |
| 2843 |
<a href="#name-contributors" class="section-name selfRef">Contributors</a> |
| 2844 |
</h2> |
| 2845 |
<p id="section-appendix.k-1"><span class="contact-name">Christian Huitema</span> and <span class="contact-name">Tony Li</span> contributed to this document.<a href="#section-appendix.k-1" class="pilcrow">¶</a></p> |
| 2846 |
<p id="section-appendix.k-2"><span class="contact-name">Romain Kuntz</span> contributed extensively regarding IPv6 handovers |
| 2847 |
between links running outside the context of a BSS (802.11-OCB |
| 2848 |
links).<a href="#section-appendix.k-2" class="pilcrow">¶</a></p> |
| 2849 |
<p id="section-appendix.k-3"><span class="contact-name">Tim Leinmueller</span> contributed the idea of the use of IPv6 over |
| 2850 |
802.11-OCB for the distribution of certificates.<a href="#section-appendix.k-3" class="pilcrow">¶</a></p> |
| 2851 |
<p id="section-appendix.k-4"><span class="contact-name">Marios Makassikis</span>, <span class="contact-name">Jose Santa Lozano</span>, <span class="contact-name">Albin Severinson</span>, and |
| 2852 |
<span class="contact-name">Alexey Voronov</span> provided significant feedback on the experience |
| 2853 |
of using IP messages over 802.11-OCB in initial trials.<a href="#section-appendix.k-4" class="pilcrow">¶</a></p> |
| 2854 |
<p id="section-appendix.k-5"><span class="contact-name">Michelle Wetterwald</span> contributed extensively to the MTU |
| 2855 |
discussion, offered the ETSI ITS perspective, and reviewed |
| 2856 |
other parts of the document.<a href="#section-appendix.k-5" class="pilcrow">¶</a></p> |
| 2857 |
</section> |
| 2858 |
</div> |
| 2859 |
<div id="authors-addresses"> |
| 2860 |
<section id="section-appendix.l"> |
| 2861 |
<h2 id="name-authors-addresses"> |
| 2862 |
<a href="#name-authors-addresses" class="section-name selfRef">Authors' Addresses</a> |
| 2863 |
</h2> |
| 2864 |
<address class="vcard"> |
| 2865 |
<div dir="auto" class="left"><span class="fn nameRole">Nabil Benamar</span></div> |
| 2866 |
<div dir="auto" class="left"><span class="org">Moulay Ismail University of Meknes</span></div> |
| 2867 |
<div dir="auto" class="left"><span class="country-name">Morocco</span></div> |
| 2868 |
<div class="tel"> |
| 2869 |
<span>Phone:</span> |
| 2870 |
<a href="tel:+212670832236" class="tel">+212670832236</a> |
| 2871 |
</div> |
| 2872 |
<div class="email"> |
| 2873 |
<span>Email:</span> |
| 2874 |
<a href="mailto:[email protected]" class="email">[email protected]</a> |
| 2875 |
</div> |
| 2876 |
</address> |
| 2877 |
<address class="vcard"> |
| 2878 |
<div dir="auto" class="left"><span class="fn nameRole">Jérôme Härri</span></div> |
| 2879 |
<div dir="auto" class="left"><span class="org">EURECOM</span></div> |
| 2880 |
<div dir="auto" class="left"> |
| 2881 |
<span class="postal-code">06904</span> <span class="locality">Sophia-Antipolis</span> |
| 2882 |
</div> |
| 2883 |
<div dir="auto" class="left"><span class="country-name">France</span></div> |
| 2884 |
<div class="tel"> |
| 2885 |
<span>Phone:</span> |
| 2886 |
<a href="tel:+33493008134" class="tel">+33493008134</a> |
| 2887 |
</div> |
| 2888 |
<div class="email"> |
| 2889 |
<span>Email:</span> |
| 2890 |
<a href="mailto:[email protected]" class="email">[email protected]</a> |
| 2891 |
</div> |
| 2892 |
</address> |
| 2893 |
<address class="vcard"> |
| 2894 |
<div dir="auto" class="left"><span class="fn nameRole">Jong-Hyouk Lee</span></div> |
| 2895 |
<div dir="auto" class="left"><span class="org">Sangmyung University</span></div> |
| 2896 |
<div dir="auto" class="left"><span class="street-address">31, Sangmyeongdae-gil, Dongnam-gu</span></div> |
| 2897 |
<div dir="auto" class="left"><span class="locality"> |
| 2898 |
Cheonan |
| 2899 |
</span></div> |
| 2900 |
<div dir="auto" class="left"><span class="postal-code">31066</span></div> |
| 2901 |
<div dir="auto" class="left"><span class="country-name">Republic of Korea</span></div> |
| 2902 |
<div class="email"> |
| 2903 |
<span>Email:</span> |
| 2904 |
<a href="mailto:[email protected]" class="email">[email protected]</a> |
| 2905 |
</div> |
| 2906 |
</address> |
| 2907 |
<address class="vcard"> |
| 2908 |
<div dir="auto" class="left"><span class="fn nameRole">Thierry ERNST</span></div> |
| 2909 |
<div dir="auto" class="left"><span class="org">YoGoKo</span></div> |
| 2910 |
<div dir="auto" class="left"><span class="street-address">1137A Avenue des Champs-Blancs</span></div> |
| 2911 |
<div dir="auto" class="left"> |
| 2912 |
<span class="postal-code">35510</span> <span class="locality">CESON-SEVIGNE</span> |
| 2913 |
</div> |
| 2914 |
<div dir="auto" class="left"><span class="country-name">France</span></div> |
| 2915 |
<div class="email"> |
| 2916 |
<span>Email:</span> |
| 2917 |
<a href="mailto:[email protected]" class="email">[email protected]</a> |
| 2918 |
</div> |
| 2919 |
</address> |
| 2920 |
</section> |
| 2921 |
</div> |
| 2922 |
<script>var toc = document.getElementById("toc"); |
| 2923 |
var tocToggle = toc.querySelector("h2"); |
| 2924 |
var tocNav = toc.querySelector("nav"); |
| 2925 |
|
| 2926 |
// mobile menu toggle |
| 2927 |
tocToggle.onclick = function(event) { |
| 2928 |
if (window.innerWidth < 1024) { |
| 2929 |
var tocNavDisplay = tocNav.currentStyle ? tocNav.currentStyle.display : getComputedStyle(tocNav, null).display; |
| 2930 |
if (tocNavDisplay == "none") { |
| 2931 |
tocNav.style.display = "block"; |
| 2932 |
} else { |
| 2933 |
tocNav.style.display = "none"; |
| 2934 |
} |
| 2935 |
} |
| 2936 |
} |
| 2937 |
|
| 2938 |
// toc anchor scroll to anchor |
| 2939 |
tocNav.addEventListener("click", function (event) { |
| 2940 |
event.preventDefault(); |
| 2941 |
if (event.target.nodeName == 'A') { |
| 2942 |
if (window.innerWidth < 1024) { |
| 2943 |
tocNav.style.display = "none"; |
| 2944 |
} |
| 2945 |
var href = event.target.getAttribute("href"); |
| 2946 |
var anchorId = href.substr(1); |
| 2947 |
var anchor = document.getElementById(anchorId); |
| 2948 |
anchor.scrollIntoView(true); |
| 2949 |
window.history.pushState("","",href); |
| 2950 |
} |
| 2951 |
}); |
| 2952 |
|
| 2953 |
// switch toc mode when window resized |
| 2954 |
window.onresize = function () { |
| 2955 |
if (window.innerWidth < 1024) { |
| 2956 |
tocNav.style.display = "none"; |
| 2957 |
} else { |
| 2958 |
tocNav.style.display = "block"; |
| 2959 |
} |
| 2960 |
} |
| 2961 |
</script> |
| 2962 |
</body> |
| 2963 |
</html> |