| 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 9305: Locator/ID Separation Protocol (LISP) Generic Protocol Extension</title> |
| 8 |
<meta content="Fabio Maino" name="author"> |
| 9 |
<meta content="Jennifer Lemon" name="author"> |
| 10 |
<meta content="Puneet Agarwal" name="author"> |
| 11 |
<meta content="Darrel Lewis" name="author"> |
| 12 |
<meta content="Michael Smith" name="author"> |
| 13 |
<meta content=" |
| 14 |
This document describes extensions to the Locator/ID Separation |
| 15 |
Protocol (LISP) data plane, via changes to the LISP header, to support |
| 16 |
multiprotocol encapsulation and allow the introduction of new protocol |
| 17 |
capabilities. |
| 18 |
" name="description"> |
| 19 |
<meta content="xml2rfc 3.15.1" name="generator"> |
| 20 |
<meta content="security" name="keyword"> |
| 21 |
<meta content="policy" name="keyword"> |
| 22 |
<meta content="9305" name="rfc.number"> |
| 23 |
<!-- Generator version information: |
| 24 |
xml2rfc 3.15.1 |
| 25 |
Python 3.9.13 |
| 26 |
appdirs 1.4.4 |
| 27 |
ConfigArgParse 1.5.3 |
| 28 |
google-i18n-address 2.5.1 |
| 29 |
html5lib 1.1 |
| 30 |
intervaltree 3.1.0 |
| 31 |
Jinja2 3.1.2 |
| 32 |
kitchen 1.2.6 |
| 33 |
lxml 4.9.0 |
| 34 |
MarkupSafe 2.1.1 |
| 35 |
pycountry 22.3.5 |
| 36 |
PyYAML 6.0 |
| 37 |
requests 2.28.0 |
| 38 |
setuptools 44.1.1 |
| 39 |
six 1.16.0 |
| 40 |
weasyprint 56.1 |
| 41 |
--> |
| 42 |
<link href="rfc9305.xml" rel="alternate" type="application/rfc+xml"> |
| 43 |
<link href="#copyright" rel="license"> |
| 44 |
<style type="text/css">/* |
| 45 |
|
| 46 |
NOTE: Changes at the bottom of this file overrides some earlier settings. |
| 47 |
|
| 48 |
Once the style has stabilized and has been adopted as an official RFC style, |
| 49 |
this can be consolidated so that style settings occur only in one place, but |
| 50 |
for now the contents of this file consists first of the initial CSS work as |
| 51 |
provided to the RFC Formatter (xml2rfc) work, followed by itemized and |
| 52 |
commented changes found necssary during the development of the v3 |
| 53 |
formatters. |
| 54 |
|
| 55 |
*/ |
| 56 |
|
| 57 |
/* fonts */ |
| 58 |
@import url('https://fonts.googleapis.com/css?family=Noto+Sans'); /* Sans-serif */ |
| 59 |
@import url('https://fonts.googleapis.com/css?family=Noto+Serif'); /* Serif (print) */ |
| 60 |
@import url('https://fonts.googleapis.com/css?family=Roboto+Mono'); /* Monospace */ |
| 61 |
|
| 62 |
@viewport { |
| 63 |
zoom: 1.0; |
| 64 |
width: extend-to-zoom; |
| 65 |
} |
| 66 |
@-ms-viewport { |
| 67 |
width: extend-to-zoom; |
| 68 |
zoom: 1.0; |
| 69 |
} |
| 70 |
/* general and mobile first */ |
| 71 |
html { |
| 72 |
} |
| 73 |
body { |
| 74 |
max-width: 90%; |
| 75 |
margin: 1.5em auto; |
| 76 |
color: #222; |
| 77 |
background-color: #fff; |
| 78 |
font-size: 14px; |
| 79 |
font-family: 'Noto Sans', Arial, Helvetica, sans-serif; |
| 80 |
line-height: 1.6; |
| 81 |
scroll-behavior: smooth; |
| 82 |
} |
| 83 |
.ears { |
| 84 |
display: none; |
| 85 |
} |
| 86 |
|
| 87 |
/* headings */ |
| 88 |
#title, h1, h2, h3, h4, h5, h6 { |
| 89 |
margin: 1em 0 0.5em; |
| 90 |
font-weight: bold; |
| 91 |
line-height: 1.3; |
| 92 |
} |
| 93 |
#title { |
| 94 |
clear: both; |
| 95 |
border-bottom: 1px solid #ddd; |
| 96 |
margin: 0 0 0.5em 0; |
| 97 |
padding: 1em 0 0.5em; |
| 98 |
} |
| 99 |
.author { |
| 100 |
padding-bottom: 4px; |
| 101 |
} |
| 102 |
h1 { |
| 103 |
font-size: 26px; |
| 104 |
margin: 1em 0; |
| 105 |
} |
| 106 |
h2 { |
| 107 |
font-size: 22px; |
| 108 |
margin-top: -20px; /* provide offset for in-page anchors */ |
| 109 |
padding-top: 33px; |
| 110 |
} |
| 111 |
h3 { |
| 112 |
font-size: 18px; |
| 113 |
margin-top: -36px; /* provide offset for in-page anchors */ |
| 114 |
padding-top: 42px; |
| 115 |
} |
| 116 |
h4 { |
| 117 |
font-size: 16px; |
| 118 |
margin-top: -36px; /* provide offset for in-page anchors */ |
| 119 |
padding-top: 42px; |
| 120 |
} |
| 121 |
h5, h6 { |
| 122 |
font-size: 14px; |
| 123 |
} |
| 124 |
#n-copyright-notice { |
| 125 |
border-bottom: 1px solid #ddd; |
| 126 |
padding-bottom: 1em; |
| 127 |
margin-bottom: 1em; |
| 128 |
} |
| 129 |
/* general structure */ |
| 130 |
p { |
| 131 |
padding: 0; |
| 132 |
margin: 0 0 1em 0; |
| 133 |
text-align: left; |
| 134 |
} |
| 135 |
div, span { |
| 136 |
position: relative; |
| 137 |
} |
| 138 |
div { |
| 139 |
margin: 0; |
| 140 |
} |
| 141 |
.alignRight.art-text { |
| 142 |
background-color: #f9f9f9; |
| 143 |
border: 1px solid #eee; |
| 144 |
border-radius: 3px; |
| 145 |
padding: 1em 1em 0; |
| 146 |
margin-bottom: 1.5em; |
| 147 |
} |
| 148 |
.alignRight.art-text pre { |
| 149 |
padding: 0; |
| 150 |
} |
| 151 |
.alignRight { |
| 152 |
margin: 1em 0; |
| 153 |
} |
| 154 |
.alignRight > *:first-child { |
| 155 |
border: none; |
| 156 |
margin: 0; |
| 157 |
float: right; |
| 158 |
clear: both; |
| 159 |
} |
| 160 |
.alignRight > *:nth-child(2) { |
| 161 |
clear: both; |
| 162 |
display: block; |
| 163 |
border: none; |
| 164 |
} |
| 165 |
svg { |
| 166 |
display: block; |
| 167 |
} |
| 168 |
.alignCenter.art-text { |
| 169 |
background-color: #f9f9f9; |
| 170 |
border: 1px solid #eee; |
| 171 |
border-radius: 3px; |
| 172 |
padding: 1em 1em 0; |
| 173 |
margin-bottom: 1.5em; |
| 174 |
} |
| 175 |
.alignCenter.art-text pre { |
| 176 |
padding: 0; |
| 177 |
} |
| 178 |
.alignCenter { |
| 179 |
margin: 1em 0; |
| 180 |
} |
| 181 |
.alignCenter > *:first-child { |
| 182 |
display: table; |
| 183 |
border: none; |
| 184 |
margin: 0 auto; |
| 185 |
} |
| 186 |
|
| 187 |
/* lists */ |
| 188 |
ol, ul { |
| 189 |
padding: 0; |
| 190 |
margin: 0 0 1em 2em; |
| 191 |
} |
| 192 |
ol ol, ul ul, ol ul, ul ol { |
| 193 |
margin-left: 1em; |
| 194 |
} |
| 195 |
li { |
| 196 |
margin: 0 0 0.25em 0; |
| 197 |
} |
| 198 |
.ulCompact li { |
| 199 |
margin: 0; |
| 200 |
} |
| 201 |
ul.empty, .ulEmpty { |
| 202 |
list-style-type: none; |
| 203 |
} |
| 204 |
ul.empty li, .ulEmpty li { |
| 205 |
margin-top: 0.5em; |
| 206 |
} |
| 207 |
ul.ulBare, li.ulBare { |
| 208 |
margin-left: 0em !important; |
| 209 |
} |
| 210 |
ul.compact, .ulCompact, |
| 211 |
ol.compact, .olCompact { |
| 212 |
line-height: 100%; |
| 213 |
margin: 0 0 0 2em; |
| 214 |
} |
| 215 |
|
| 216 |
/* definition lists */ |
| 217 |
dl { |
| 218 |
} |
| 219 |
dl > dt { |
| 220 |
float: left; |
| 221 |
margin-right: 1em; |
| 222 |
} |
| 223 |
/* |
| 224 |
dl.nohang > dt { |
| 225 |
float: none; |
| 226 |
} |
| 227 |
*/ |
| 228 |
dl > dd { |
| 229 |
margin-bottom: .8em; |
| 230 |
min-height: 1.3em; |
| 231 |
} |
| 232 |
dl.compact > dd, .dlCompact > dd { |
| 233 |
margin-bottom: 0em; |
| 234 |
} |
| 235 |
dl > dd > dl { |
| 236 |
margin-top: 0.5em; |
| 237 |
margin-bottom: 0em; |
| 238 |
} |
| 239 |
|
| 240 |
/* links */ |
| 241 |
a { |
| 242 |
text-decoration: none; |
| 243 |
} |
| 244 |
a[href] { |
| 245 |
color: #22e; /* Arlen: WCAG 2019 */ |
| 246 |
} |
| 247 |
a[href]:hover { |
| 248 |
background-color: #f2f2f2; |
| 249 |
} |
| 250 |
figcaption a[href], |
| 251 |
a[href].selfRef { |
| 252 |
color: #222; |
| 253 |
} |
| 254 |
/* XXX probably not this: |
| 255 |
a.selfRef:hover { |
| 256 |
background-color: transparent; |
| 257 |
cursor: default; |
| 258 |
} */ |
| 259 |
|
| 260 |
/* Figures */ |
| 261 |
tt, code, pre { |
| 262 |
background-color: #f9f9f9; |
| 263 |
font-family: 'Roboto Mono', monospace; |
| 264 |
} |
| 265 |
pre { |
| 266 |
border: 1px solid #eee; |
| 267 |
margin: 0; |
| 268 |
padding: 1em; |
| 269 |
} |
| 270 |
img { |
| 271 |
max-width: 100%; |
| 272 |
} |
| 273 |
figure { |
| 274 |
margin: 0; |
| 275 |
} |
| 276 |
figure blockquote { |
| 277 |
margin: 0.8em 0.4em 0.4em; |
| 278 |
} |
| 279 |
figcaption { |
| 280 |
font-style: italic; |
| 281 |
margin: 0 0 1em 0; |
| 282 |
} |
| 283 |
@media screen { |
| 284 |
pre { |
| 285 |
overflow-x: auto; |
| 286 |
max-width: 100%; |
| 287 |
max-width: calc(100% - 22px); |
| 288 |
} |
| 289 |
} |
| 290 |
|
| 291 |
/* aside, blockquote */ |
| 292 |
aside, blockquote { |
| 293 |
margin-left: 0; |
| 294 |
padding: 1.2em 2em; |
| 295 |
} |
| 296 |
blockquote { |
| 297 |
background-color: #f9f9f9; |
| 298 |
color: #111; /* Arlen: WCAG 2019 */ |
| 299 |
border: 1px solid #ddd; |
| 300 |
border-radius: 3px; |
| 301 |
margin: 1em 0; |
| 302 |
} |
| 303 |
cite { |
| 304 |
display: block; |
| 305 |
text-align: right; |
| 306 |
font-style: italic; |
| 307 |
} |
| 308 |
|
| 309 |
/* tables */ |
| 310 |
table { |
| 311 |
width: 100%; |
| 312 |
margin: 0 0 1em; |
| 313 |
border-collapse: collapse; |
| 314 |
border: 1px solid #eee; |
| 315 |
} |
| 316 |
th, td { |
| 317 |
text-align: left; |
| 318 |
vertical-align: top; |
| 319 |
padding: 0.5em 0.75em; |
| 320 |
} |
| 321 |
th { |
| 322 |
text-align: left; |
| 323 |
background-color: #e9e9e9; |
| 324 |
} |
| 325 |
tr:nth-child(2n+1) > td { |
| 326 |
background-color: #f5f5f5; |
| 327 |
} |
| 328 |
table caption { |
| 329 |
font-style: italic; |
| 330 |
margin: 0; |
| 331 |
padding: 0; |
| 332 |
text-align: left; |
| 333 |
} |
| 334 |
table p { |
| 335 |
/* XXX to avoid bottom margin on table row signifiers. If paragraphs should |
| 336 |
be allowed within tables more generally, it would be far better to select on a class. */ |
| 337 |
margin: 0; |
| 338 |
} |
| 339 |
|
| 340 |
/* pilcrow */ |
| 341 |
a.pilcrow { |
| 342 |
color: #666; /* Arlen: AHDJ 2019 */ |
| 343 |
text-decoration: none; |
| 344 |
visibility: hidden; |
| 345 |
user-select: none; |
| 346 |
-ms-user-select: none; |
| 347 |
-o-user-select:none; |
| 348 |
-moz-user-select: none; |
| 349 |
-khtml-user-select: none; |
| 350 |
-webkit-user-select: none; |
| 351 |
-webkit-touch-callout: none; |
| 352 |
} |
| 353 |
@media screen { |
| 354 |
aside:hover > a.pilcrow, |
| 355 |
p:hover > a.pilcrow, |
| 356 |
blockquote:hover > a.pilcrow, |
| 357 |
div:hover > a.pilcrow, |
| 358 |
li:hover > a.pilcrow, |
| 359 |
pre:hover > a.pilcrow { |
| 360 |
visibility: visible; |
| 361 |
} |
| 362 |
a.pilcrow:hover { |
| 363 |
background-color: transparent; |
| 364 |
} |
| 365 |
} |
| 366 |
|
| 367 |
/* misc */ |
| 368 |
hr { |
| 369 |
border: 0; |
| 370 |
border-top: 1px solid #eee; |
| 371 |
} |
| 372 |
.bcp14 { |
| 373 |
font-variant: small-caps; |
| 374 |
} |
| 375 |
|
| 376 |
.role { |
| 377 |
font-variant: all-small-caps; |
| 378 |
} |
| 379 |
|
| 380 |
/* info block */ |
| 381 |
#identifiers { |
| 382 |
margin: 0; |
| 383 |
font-size: 0.9em; |
| 384 |
} |
| 385 |
#identifiers dt { |
| 386 |
width: 3em; |
| 387 |
clear: left; |
| 388 |
} |
| 389 |
#identifiers dd { |
| 390 |
float: left; |
| 391 |
margin-bottom: 0; |
| 392 |
} |
| 393 |
/* Fix PDF info block run off issue */ |
| 394 |
@media print { |
| 395 |
#identifiers dd { |
| 396 |
float: none; |
| 397 |
} |
| 398 |
} |
| 399 |
#identifiers .authors .author { |
| 400 |
display: inline-block; |
| 401 |
margin-right: 1.5em; |
| 402 |
} |
| 403 |
#identifiers .authors .org { |
| 404 |
font-style: italic; |
| 405 |
} |
| 406 |
|
| 407 |
/* The prepared/rendered info at the very bottom of the page */ |
| 408 |
.docInfo { |
| 409 |
color: #666; /* Arlen: WCAG 2019 */ |
| 410 |
font-size: 0.9em; |
| 411 |
font-style: italic; |
| 412 |
margin-top: 2em; |
| 413 |
} |
| 414 |
.docInfo .prepared { |
| 415 |
float: left; |
| 416 |
} |
| 417 |
.docInfo .prepared { |
| 418 |
float: right; |
| 419 |
} |
| 420 |
|
| 421 |
/* table of contents */ |
| 422 |
#toc { |
| 423 |
padding: 0.75em 0 2em 0; |
| 424 |
margin-bottom: 1em; |
| 425 |
} |
| 426 |
nav.toc ul { |
| 427 |
margin: 0 0.5em 0 0; |
| 428 |
padding: 0; |
| 429 |
list-style: none; |
| 430 |
} |
| 431 |
nav.toc li { |
| 432 |
line-height: 1.3em; |
| 433 |
margin: 0.75em 0; |
| 434 |
padding-left: 1.2em; |
| 435 |
text-indent: -1.2em; |
| 436 |
} |
| 437 |
/* references */ |
| 438 |
.references dt { |
| 439 |
text-align: right; |
| 440 |
font-weight: bold; |
| 441 |
min-width: 7em; |
| 442 |
} |
| 443 |
.references dd { |
| 444 |
margin-left: 8em; |
| 445 |
overflow: auto; |
| 446 |
} |
| 447 |
|
| 448 |
.refInstance { |
| 449 |
margin-bottom: 1.25em; |
| 450 |
} |
| 451 |
|
| 452 |
.references .ascii { |
| 453 |
margin-bottom: 0.25em; |
| 454 |
} |
| 455 |
|
| 456 |
/* index */ |
| 457 |
.index ul { |
| 458 |
margin: 0 0 0 1em; |
| 459 |
padding: 0; |
| 460 |
list-style: none; |
| 461 |
} |
| 462 |
.index ul ul { |
| 463 |
margin: 0; |
| 464 |
} |
| 465 |
.index li { |
| 466 |
margin: 0; |
| 467 |
text-indent: -2em; |
| 468 |
padding-left: 2em; |
| 469 |
padding-bottom: 5px; |
| 470 |
} |
| 471 |
.indexIndex { |
| 472 |
margin: 0.5em 0 1em; |
| 473 |
} |
| 474 |
.index a { |
| 475 |
font-weight: 700; |
| 476 |
} |
| 477 |
/* make the index two-column on all but the smallest screens */ |
| 478 |
@media (min-width: 600px) { |
| 479 |
.index ul { |
| 480 |
-moz-column-count: 2; |
| 481 |
-moz-column-gap: 20px; |
| 482 |
} |
| 483 |
.index ul ul { |
| 484 |
-moz-column-count: 1; |
| 485 |
-moz-column-gap: 0; |
| 486 |
} |
| 487 |
} |
| 488 |
|
| 489 |
/* authors */ |
| 490 |
address.vcard { |
| 491 |
font-style: normal; |
| 492 |
margin: 1em 0; |
| 493 |
} |
| 494 |
|
| 495 |
address.vcard .nameRole { |
| 496 |
font-weight: 700; |
| 497 |
margin-left: 0; |
| 498 |
} |
| 499 |
address.vcard .label { |
| 500 |
font-family: "Noto Sans",Arial,Helvetica,sans-serif; |
| 501 |
margin: 0.5em 0; |
| 502 |
} |
| 503 |
address.vcard .type { |
| 504 |
display: none; |
| 505 |
} |
| 506 |
.alternative-contact { |
| 507 |
margin: 1.5em 0 1em; |
| 508 |
} |
| 509 |
hr.addr { |
| 510 |
border-top: 1px dashed; |
| 511 |
margin: 0; |
| 512 |
color: #ddd; |
| 513 |
max-width: calc(100% - 16px); |
| 514 |
} |
| 515 |
|
| 516 |
/* temporary notes */ |
| 517 |
.rfcEditorRemove::before { |
| 518 |
position: absolute; |
| 519 |
top: 0.2em; |
| 520 |
right: 0.2em; |
| 521 |
padding: 0.2em; |
| 522 |
content: "The RFC Editor will remove this note"; |
| 523 |
color: #9e2a00; /* Arlen: WCAG 2019 */ |
| 524 |
background-color: #ffd; /* Arlen: WCAG 2019 */ |
| 525 |
} |
| 526 |
.rfcEditorRemove { |
| 527 |
position: relative; |
| 528 |
padding-top: 1.8em; |
| 529 |
background-color: #ffd; /* Arlen: WCAG 2019 */ |
| 530 |
border-radius: 3px; |
| 531 |
} |
| 532 |
.cref { |
| 533 |
background-color: #ffd; /* Arlen: WCAG 2019 */ |
| 534 |
padding: 2px 4px; |
| 535 |
} |
| 536 |
.crefSource { |
| 537 |
font-style: italic; |
| 538 |
} |
| 539 |
/* alternative layout for smaller screens */ |
| 540 |
@media screen and (max-width: 1023px) { |
| 541 |
body { |
| 542 |
padding-top: 2em; |
| 543 |
} |
| 544 |
#title { |
| 545 |
padding: 1em 0; |
| 546 |
} |
| 547 |
h1 { |
| 548 |
font-size: 24px; |
| 549 |
} |
| 550 |
h2 { |
| 551 |
font-size: 20px; |
| 552 |
margin-top: -18px; /* provide offset for in-page anchors */ |
| 553 |
padding-top: 38px; |
| 554 |
} |
| 555 |
#identifiers dd { |
| 556 |
max-width: 60%; |
| 557 |
} |
| 558 |
#toc { |
| 559 |
position: fixed; |
| 560 |
z-index: 2; |
| 561 |
top: 0; |
| 562 |
right: 0; |
| 563 |
padding: 0; |
| 564 |
margin: 0; |
| 565 |
background-color: inherit; |
| 566 |
border-bottom: 1px solid #ccc; |
| 567 |
} |
| 568 |
#toc h2 { |
| 569 |
margin: -1px 0 0 0; |
| 570 |
padding: 4px 0 4px 6px; |
| 571 |
padding-right: 1em; |
| 572 |
min-width: 190px; |
| 573 |
font-size: 1.1em; |
| 574 |
text-align: right; |
| 575 |
background-color: #444; |
| 576 |
color: white; |
| 577 |
cursor: pointer; |
| 578 |
} |
| 579 |
#toc h2::before { /* css hamburger */ |
| 580 |
float: right; |
| 581 |
position: relative; |
| 582 |
width: 1em; |
| 583 |
height: 1px; |
| 584 |
left: -164px; |
| 585 |
margin: 6px 0 0 0; |
| 586 |
background: white none repeat scroll 0 0; |
| 587 |
box-shadow: 0 4px 0 0 white, 0 8px 0 0 white; |
| 588 |
content: ""; |
| 589 |
} |
| 590 |
#toc nav { |
| 591 |
display: none; |
| 592 |
padding: 0.5em 1em 1em; |
| 593 |
overflow: auto; |
| 594 |
height: calc(100vh - 48px); |
| 595 |
border-left: 1px solid #ddd; |
| 596 |
} |
| 597 |
} |
| 598 |
|
| 599 |
/* alternative layout for wide screens */ |
| 600 |
@media screen and (min-width: 1024px) { |
| 601 |
body { |
| 602 |
max-width: 724px; |
| 603 |
margin: 42px auto; |
| 604 |
padding-left: 1.5em; |
| 605 |
padding-right: 29em; |
| 606 |
} |
| 607 |
#toc { |
| 608 |
position: fixed; |
| 609 |
top: 42px; |
| 610 |
right: 42px; |
| 611 |
width: 25%; |
| 612 |
margin: 0; |
| 613 |
padding: 0 1em; |
| 614 |
z-index: 1; |
| 615 |
} |
| 616 |
#toc h2 { |
| 617 |
border-top: none; |
| 618 |
border-bottom: 1px solid #ddd; |
| 619 |
font-size: 1em; |
| 620 |
font-weight: normal; |
| 621 |
margin: 0; |
| 622 |
padding: 0.25em 1em 1em 0; |
| 623 |
} |
| 624 |
#toc nav { |
| 625 |
display: block; |
| 626 |
height: calc(90vh - 84px); |
| 627 |
bottom: 0; |
| 628 |
padding: 0.5em 0 0; |
| 629 |
overflow: auto; |
| 630 |
} |
| 631 |
img { /* future proofing */ |
| 632 |
max-width: 100%; |
| 633 |
height: auto; |
| 634 |
} |
| 635 |
} |
| 636 |
|
| 637 |
/* pagination */ |
| 638 |
@media print { |
| 639 |
body { |
| 640 |
|
| 641 |
width: 100%; |
| 642 |
} |
| 643 |
p { |
| 644 |
orphans: 3; |
| 645 |
widows: 3; |
| 646 |
} |
| 647 |
#n-copyright-notice { |
| 648 |
border-bottom: none; |
| 649 |
} |
| 650 |
#toc, #n-introduction { |
| 651 |
page-break-before: always; |
| 652 |
} |
| 653 |
#toc { |
| 654 |
border-top: none; |
| 655 |
padding-top: 0; |
| 656 |
} |
| 657 |
figure, pre { |
| 658 |
page-break-inside: avoid; |
| 659 |
} |
| 660 |
figure { |
| 661 |
overflow: scroll; |
| 662 |
} |
| 663 |
pre.breakable { |
| 664 |
break-inside: auto; |
| 665 |
} |
| 666 |
h1, h2, h3, h4, h5, h6 { |
| 667 |
page-break-after: avoid; |
| 668 |
} |
| 669 |
h2+*, h3+*, h4+*, h5+*, h6+* { |
| 670 |
page-break-before: avoid; |
| 671 |
} |
| 672 |
pre { |
| 673 |
white-space: pre-wrap; |
| 674 |
word-wrap: break-word; |
| 675 |
font-size: 10pt; |
| 676 |
} |
| 677 |
table { |
| 678 |
border: 1px solid #ddd; |
| 679 |
} |
| 680 |
td { |
| 681 |
border-top: 1px solid #ddd; |
| 682 |
} |
| 683 |
} |
| 684 |
|
| 685 |
/* This is commented out here, as the string-set: doesn't |
| 686 |
pass W3C validation currently */ |
| 687 |
/* |
| 688 |
.ears thead .left { |
| 689 |
string-set: ears-top-left content(); |
| 690 |
} |
| 691 |
|
| 692 |
.ears thead .center { |
| 693 |
string-set: ears-top-center content(); |
| 694 |
} |
| 695 |
|
| 696 |
.ears thead .right { |
| 697 |
string-set: ears-top-right content(); |
| 698 |
} |
| 699 |
|
| 700 |
.ears tfoot .left { |
| 701 |
string-set: ears-bottom-left content(); |
| 702 |
} |
| 703 |
|
| 704 |
.ears tfoot .center { |
| 705 |
string-set: ears-bottom-center content(); |
| 706 |
} |
| 707 |
|
| 708 |
.ears tfoot .right { |
| 709 |
string-set: ears-bottom-right content(); |
| 710 |
} |
| 711 |
*/ |
| 712 |
|
| 713 |
@page :first { |
| 714 |
padding-top: 0; |
| 715 |
@top-left { |
| 716 |
content: normal; |
| 717 |
border: none; |
| 718 |
} |
| 719 |
@top-center { |
| 720 |
content: normal; |
| 721 |
border: none; |
| 722 |
} |
| 723 |
@top-right { |
| 724 |
content: normal; |
| 725 |
border: none; |
| 726 |
} |
| 727 |
} |
| 728 |
|
| 729 |
@page { |
| 730 |
size: A4; |
| 731 |
margin-bottom: 45mm; |
| 732 |
padding-top: 20px; |
| 733 |
/* The follwing is commented out here, but set appropriately by in code, as |
| 734 |
the content depends on the document */ |
| 735 |
/* |
| 736 |
@top-left { |
| 737 |
content: 'Internet-Draft'; |
| 738 |
vertical-align: bottom; |
| 739 |
border-bottom: solid 1px #ccc; |
| 740 |
} |
| 741 |
@top-left { |
| 742 |
content: string(ears-top-left); |
| 743 |
vertical-align: bottom; |
| 744 |
border-bottom: solid 1px #ccc; |
| 745 |
} |
| 746 |
@top-center { |
| 747 |
content: string(ears-top-center); |
| 748 |
vertical-align: bottom; |
| 749 |
border-bottom: solid 1px #ccc; |
| 750 |
} |
| 751 |
@top-right { |
| 752 |
content: string(ears-top-right); |
| 753 |
vertical-align: bottom; |
| 754 |
border-bottom: solid 1px #ccc; |
| 755 |
} |
| 756 |
@bottom-left { |
| 757 |
content: string(ears-bottom-left); |
| 758 |
vertical-align: top; |
| 759 |
border-top: solid 1px #ccc; |
| 760 |
} |
| 761 |
@bottom-center { |
| 762 |
content: string(ears-bottom-center); |
| 763 |
vertical-align: top; |
| 764 |
border-top: solid 1px #ccc; |
| 765 |
} |
| 766 |
@bottom-right { |
| 767 |
content: '[Page ' counter(page) ']'; |
| 768 |
vertical-align: top; |
| 769 |
border-top: solid 1px #ccc; |
| 770 |
} |
| 771 |
*/ |
| 772 |
|
| 773 |
} |
| 774 |
|
| 775 |
/* Changes introduced to fix issues found during implementation */ |
| 776 |
/* Make sure links are clickable even if overlapped by following H* */ |
| 777 |
a { |
| 778 |
z-index: 2; |
| 779 |
} |
| 780 |
/* Separate body from document info even without intervening H1 */ |
| 781 |
section { |
| 782 |
clear: both; |
| 783 |
} |
| 784 |
|
| 785 |
|
| 786 |
/* Top align author divs, to avoid names without organization dropping level with org names */ |
| 787 |
.author { |
| 788 |
vertical-align: top; |
| 789 |
} |
| 790 |
|
| 791 |
/* Leave room in document info to show Internet-Draft on one line */ |
| 792 |
#identifiers dt { |
| 793 |
width: 8em; |
| 794 |
} |
| 795 |
|
| 796 |
/* Don't waste quite as much whitespace between label and value in doc info */ |
| 797 |
#identifiers dd { |
| 798 |
margin-left: 1em; |
| 799 |
} |
| 800 |
|
| 801 |
/* Give floating toc a background color (needed when it's a div inside section */ |
| 802 |
#toc { |
| 803 |
background-color: white; |
| 804 |
} |
| 805 |
|
| 806 |
/* Make the collapsed ToC header render white on gray also when it's a link */ |
| 807 |
@media screen and (max-width: 1023px) { |
| 808 |
#toc h2 a, |
| 809 |
#toc h2 a:link, |
| 810 |
#toc h2 a:focus, |
| 811 |
#toc h2 a:hover, |
| 812 |
#toc a.toplink, |
| 813 |
#toc a.toplink:hover { |
| 814 |
color: white; |
| 815 |
background-color: #444; |
| 816 |
text-decoration: none; |
| 817 |
} |
| 818 |
} |
| 819 |
|
| 820 |
/* Give the bottom of the ToC some whitespace */ |
| 821 |
@media screen and (min-width: 1024px) { |
| 822 |
#toc { |
| 823 |
padding: 0 0 1em 1em; |
| 824 |
} |
| 825 |
} |
| 826 |
|
| 827 |
/* Style section numbers with more space between number and title */ |
| 828 |
.section-number { |
| 829 |
padding-right: 0.5em; |
| 830 |
} |
| 831 |
|
| 832 |
/* prevent monospace from becoming overly large */ |
| 833 |
tt, code, pre { |
| 834 |
font-size: 95%; |
| 835 |
} |
| 836 |
|
| 837 |
/* Fix the height/width aspect for ascii art*/ |
| 838 |
pre.sourcecode, |
| 839 |
.art-text pre { |
| 840 |
line-height: 1.12; |
| 841 |
} |
| 842 |
|
| 843 |
|
| 844 |
/* Add styling for a link in the ToC that points to the top of the document */ |
| 845 |
a.toplink { |
| 846 |
float: right; |
| 847 |
margin-right: 0.5em; |
| 848 |
} |
| 849 |
|
| 850 |
/* Fix the dl styling to match the RFC 7992 attributes */ |
| 851 |
dl > dt, |
| 852 |
dl.dlParallel > dt { |
| 853 |
float: left; |
| 854 |
margin-right: 1em; |
| 855 |
} |
| 856 |
dl.dlNewline > dt { |
| 857 |
float: none; |
| 858 |
} |
| 859 |
|
| 860 |
/* Provide styling for table cell text alignment */ |
| 861 |
table td.text-left, |
| 862 |
table th.text-left { |
| 863 |
text-align: left; |
| 864 |
} |
| 865 |
table td.text-center, |
| 866 |
table th.text-center { |
| 867 |
text-align: center; |
| 868 |
} |
| 869 |
table td.text-right, |
| 870 |
table th.text-right { |
| 871 |
text-align: right; |
| 872 |
} |
| 873 |
|
| 874 |
/* Make the alternative author contact informatio look less like just another |
| 875 |
author, and group it closer with the primary author contact information */ |
| 876 |
.alternative-contact { |
| 877 |
margin: 0.5em 0 0.25em 0; |
| 878 |
} |
| 879 |
address .non-ascii { |
| 880 |
margin: 0 0 0 2em; |
| 881 |
} |
| 882 |
|
| 883 |
/* With it being possible to set tables with alignment |
| 884 |
left, center, and right, { width: 100%; } does not make sense */ |
| 885 |
table { |
| 886 |
width: auto; |
| 887 |
} |
| 888 |
|
| 889 |
/* Avoid reference text that sits in a block with very wide left margin, |
| 890 |
because of a long floating dt label.*/ |
| 891 |
.references dd { |
| 892 |
overflow: visible; |
| 893 |
} |
| 894 |
|
| 895 |
/* Control caption placement */ |
| 896 |
caption { |
| 897 |
caption-side: bottom; |
| 898 |
} |
| 899 |
|
| 900 |
/* Limit the width of the author address vcard, so names in right-to-left |
| 901 |
script don't end up on the other side of the page. */ |
| 902 |
|
| 903 |
address.vcard { |
| 904 |
max-width: 30em; |
| 905 |
margin-right: auto; |
| 906 |
} |
| 907 |
|
| 908 |
/* For address alignment dependent on LTR or RTL scripts */ |
| 909 |
address div.left { |
| 910 |
text-align: left; |
| 911 |
} |
| 912 |
address div.right { |
| 913 |
text-align: right; |
| 914 |
} |
| 915 |
|
| 916 |
/* Provide table alignment support. We can't use the alignX classes above |
| 917 |
since they do unwanted things with caption and other styling. */ |
| 918 |
table.right { |
| 919 |
margin-left: auto; |
| 920 |
margin-right: 0; |
| 921 |
} |
| 922 |
table.center { |
| 923 |
margin-left: auto; |
| 924 |
margin-right: auto; |
| 925 |
} |
| 926 |
table.left { |
| 927 |
margin-left: 0; |
| 928 |
margin-right: auto; |
| 929 |
} |
| 930 |
|
| 931 |
/* Give the table caption label the same styling as the figcaption */ |
| 932 |
caption a[href] { |
| 933 |
color: #222; |
| 934 |
} |
| 935 |
|
| 936 |
@media print { |
| 937 |
.toplink { |
| 938 |
display: none; |
| 939 |
} |
| 940 |
|
| 941 |
/* avoid overwriting the top border line with the ToC header */ |
| 942 |
#toc { |
| 943 |
padding-top: 1px; |
| 944 |
} |
| 945 |
|
| 946 |
/* Avoid page breaks inside dl and author address entries */ |
| 947 |
.vcard { |
| 948 |
page-break-inside: avoid; |
| 949 |
} |
| 950 |
|
| 951 |
} |
| 952 |
/* Tweak the bcp14 keyword presentation */ |
| 953 |
.bcp14 { |
| 954 |
font-variant: small-caps; |
| 955 |
font-weight: bold; |
| 956 |
font-size: 0.9em; |
| 957 |
} |
| 958 |
/* Tweak the invisible space above H* in order not to overlay links in text above */ |
| 959 |
h2 { |
| 960 |
margin-top: -18px; /* provide offset for in-page anchors */ |
| 961 |
padding-top: 31px; |
| 962 |
} |
| 963 |
h3 { |
| 964 |
margin-top: -18px; /* provide offset for in-page anchors */ |
| 965 |
padding-top: 24px; |
| 966 |
} |
| 967 |
h4 { |
| 968 |
margin-top: -18px; /* provide offset for in-page anchors */ |
| 969 |
padding-top: 24px; |
| 970 |
} |
| 971 |
/* Float artwork pilcrow to the right */ |
| 972 |
@media screen { |
| 973 |
.artwork a.pilcrow { |
| 974 |
display: block; |
| 975 |
line-height: 0.7; |
| 976 |
margin-top: 0.15em; |
| 977 |
} |
| 978 |
} |
| 979 |
/* Make pilcrows on dd visible */ |
| 980 |
@media screen { |
| 981 |
dd:hover > a.pilcrow { |
| 982 |
visibility: visible; |
| 983 |
} |
| 984 |
} |
| 985 |
/* Make the placement of figcaption match that of a table's caption |
| 986 |
by removing the figure's added bottom margin */ |
| 987 |
.alignLeft.art-text, |
| 988 |
.alignCenter.art-text, |
| 989 |
.alignRight.art-text { |
| 990 |
margin-bottom: 0; |
| 991 |
} |
| 992 |
.alignLeft, |
| 993 |
.alignCenter, |
| 994 |
.alignRight { |
| 995 |
margin: 1em 0 0 0; |
| 996 |
} |
| 997 |
/* In print, the pilcrow won't show on hover, so prevent it from taking up space, |
| 998 |
possibly even requiring a new line */ |
| 999 |
@media print { |
| 1000 |
a.pilcrow { |
| 1001 |
display: none; |
| 1002 |
} |
| 1003 |
} |
| 1004 |
/* Styling for the external metadata */ |
| 1005 |
div#external-metadata { |
| 1006 |
background-color: #eee; |
| 1007 |
padding: 0.5em; |
| 1008 |
margin-bottom: 0.5em; |
| 1009 |
display: none; |
| 1010 |
} |
| 1011 |
div#internal-metadata { |
| 1012 |
padding: 0.5em; /* to match the external-metadata padding */ |
| 1013 |
} |
| 1014 |
/* Styling for title RFC Number */ |
| 1015 |
h1#rfcnum { |
| 1016 |
clear: both; |
| 1017 |
margin: 0 0 -1em; |
| 1018 |
padding: 1em 0 0 0; |
| 1019 |
} |
| 1020 |
/* Make .olPercent look the same as <ol><li> */ |
| 1021 |
dl.olPercent > dd { |
| 1022 |
margin-bottom: 0.25em; |
| 1023 |
min-height: initial; |
| 1024 |
} |
| 1025 |
/* Give aside some styling to set it apart */ |
| 1026 |
aside { |
| 1027 |
border-left: 1px solid #ddd; |
| 1028 |
margin: 1em 0 1em 2em; |
| 1029 |
padding: 0.2em 2em; |
| 1030 |
} |
| 1031 |
aside > dl, |
| 1032 |
aside > ol, |
| 1033 |
aside > ul, |
| 1034 |
aside > table, |
| 1035 |
aside > p { |
| 1036 |
margin-bottom: 0.5em; |
| 1037 |
} |
| 1038 |
/* Additional page break settings */ |
| 1039 |
@media print { |
| 1040 |
figcaption, table caption { |
| 1041 |
page-break-before: avoid; |
| 1042 |
} |
| 1043 |
} |
| 1044 |
/* Font size adjustments for print */ |
| 1045 |
@media print { |
| 1046 |
body { font-size: 10pt; line-height: normal; max-width: 96%; } |
| 1047 |
h1 { font-size: 1.72em; padding-top: 1.5em; } /* 1*1.2*1.2*1.2 */ |
| 1048 |
h2 { font-size: 1.44em; padding-top: 1.5em; } /* 1*1.2*1.2 */ |
| 1049 |
h3 { font-size: 1.2em; padding-top: 1.5em; } /* 1*1.2 */ |
| 1050 |
h4 { font-size: 1em; padding-top: 1.5em; } |
| 1051 |
h5, h6 { font-size: 1em; margin: initial; padding: 0.5em 0 0.3em; } |
| 1052 |
} |
| 1053 |
/* Sourcecode margin in print, when there's no pilcrow */ |
| 1054 |
@media print { |
| 1055 |
.artwork, |
| 1056 |
.artwork > pre, |
| 1057 |
.sourcecode { |
| 1058 |
margin-bottom: 1em; |
| 1059 |
} |
| 1060 |
} |
| 1061 |
/* Avoid narrow tables forcing too narrow table captions, which may render badly */ |
| 1062 |
table { |
| 1063 |
min-width: 20em; |
| 1064 |
} |
| 1065 |
/* ol type a */ |
| 1066 |
ol.type-a { list-style-type: lower-alpha; } |
| 1067 |
ol.type-A { list-style-type: upper-alpha; } |
| 1068 |
ol.type-i { list-style-type: lower-roman; } |
| 1069 |
ol.type-I { list-style-type: lower-roman; } |
| 1070 |
/* Apply the print table and row borders in general, on request from the RPC, |
| 1071 |
and increase the contrast between border and odd row background sligthtly */ |
| 1072 |
table { |
| 1073 |
border: 1px solid #ddd; |
| 1074 |
} |
| 1075 |
td { |
| 1076 |
border-top: 1px solid #ddd; |
| 1077 |
} |
| 1078 |
tr { |
| 1079 |
break-inside: avoid; |
| 1080 |
} |
| 1081 |
tr:nth-child(2n+1) > td { |
| 1082 |
background-color: #f8f8f8; |
| 1083 |
} |
| 1084 |
/* Use style rules to govern display of the TOC. */ |
| 1085 |
@media screen and (max-width: 1023px) { |
| 1086 |
#toc nav { display: none; } |
| 1087 |
#toc.active nav { display: block; } |
| 1088 |
} |
| 1089 |
/* Add support for keepWithNext */ |
| 1090 |
.keepWithNext { |
| 1091 |
break-after: avoid-page; |
| 1092 |
break-after: avoid-page; |
| 1093 |
} |
| 1094 |
/* Add support for keepWithPrevious */ |
| 1095 |
.keepWithPrevious { |
| 1096 |
break-before: avoid-page; |
| 1097 |
} |
| 1098 |
/* Change the approach to avoiding breaks inside artwork etc. */ |
| 1099 |
figure, pre, table, .artwork, .sourcecode { |
| 1100 |
break-before: auto; |
| 1101 |
break-after: auto; |
| 1102 |
} |
| 1103 |
/* Avoid breaks between <dt> and <dd> */ |
| 1104 |
dl { |
| 1105 |
break-before: auto; |
| 1106 |
break-inside: auto; |
| 1107 |
} |
| 1108 |
dt { |
| 1109 |
break-before: auto; |
| 1110 |
break-after: avoid-page; |
| 1111 |
} |
| 1112 |
dd { |
| 1113 |
break-before: avoid-page; |
| 1114 |
break-after: auto; |
| 1115 |
orphans: 3; |
| 1116 |
widows: 3 |
| 1117 |
} |
| 1118 |
span.break, dd.break { |
| 1119 |
margin-bottom: 0; |
| 1120 |
min-height: 0; |
| 1121 |
break-before: auto; |
| 1122 |
break-inside: auto; |
| 1123 |
break-after: auto; |
| 1124 |
} |
| 1125 |
/* Undo break-before ToC */ |
| 1126 |
@media print { |
| 1127 |
#toc { |
| 1128 |
break-before: auto; |
| 1129 |
} |
| 1130 |
} |
| 1131 |
/* Text in compact lists should not get extra bottim margin space, |
| 1132 |
since that would makes the list not compact */ |
| 1133 |
ul.compact p, .ulCompact p, |
| 1134 |
ol.compact p, .olCompact p { |
| 1135 |
margin: 0; |
| 1136 |
} |
| 1137 |
/* But the list as a whole needs the extra space at the end */ |
| 1138 |
section ul.compact, |
| 1139 |
section .ulCompact, |
| 1140 |
section ol.compact, |
| 1141 |
section .olCompact { |
| 1142 |
margin-bottom: 1em; /* same as p not within ul.compact etc. */ |
| 1143 |
} |
| 1144 |
/* The tt and code background above interferes with for instance table cell |
| 1145 |
backgrounds. Changed to something a bit more selective. */ |
| 1146 |
tt, code { |
| 1147 |
background-color: transparent; |
| 1148 |
} |
| 1149 |
p tt, p code, li tt, li code { |
| 1150 |
background-color: #f8f8f8; |
| 1151 |
} |
| 1152 |
/* Tweak the pre margin -- 0px doesn't come out well */ |
| 1153 |
pre { |
| 1154 |
margin-top: 0.5px; |
| 1155 |
} |
| 1156 |
/* Tweak the comact list text */ |
| 1157 |
ul.compact, .ulCompact, |
| 1158 |
ol.compact, .olCompact, |
| 1159 |
dl.compact, .dlCompact { |
| 1160 |
line-height: normal; |
| 1161 |
} |
| 1162 |
/* Don't add top margin for nested lists */ |
| 1163 |
li > ul, li > ol, li > dl, |
| 1164 |
dd > ul, dd > ol, dd > dl, |
| 1165 |
dl > dd > dl { |
| 1166 |
margin-top: initial; |
| 1167 |
} |
| 1168 |
/* Elements that should not be rendered on the same line as a <dt> */ |
| 1169 |
/* This should match the element list in writer.text.TextWriter.render_dl() */ |
| 1170 |
dd > div.artwork:first-child, |
| 1171 |
dd > aside:first-child, |
| 1172 |
dd > figure:first-child, |
| 1173 |
dd > ol:first-child, |
| 1174 |
dd > div:first-child > pre.sourcecode, |
| 1175 |
dd > table:first-child, |
| 1176 |
dd > ul:first-child { |
| 1177 |
clear: left; |
| 1178 |
} |
| 1179 |
/* fix for weird browser behaviour when <dd/> is empty */ |
| 1180 |
dt+dd:empty::before{ |
| 1181 |
content: "\00a0"; |
| 1182 |
} |
| 1183 |
/* Make paragraph spacing inside <li> smaller than in body text, to fit better within the list */ |
| 1184 |
li > p { |
| 1185 |
margin-bottom: 0.5em |
| 1186 |
} |
| 1187 |
/* Don't let p margin spill out from inside list items */ |
| 1188 |
li > p:last-of-type { |
| 1189 |
margin-bottom: 0; |
| 1190 |
} |
| 1191 |
</style> |
| 1192 |
<link href="rfc-local.css" rel="stylesheet" type="text/css"> |
| 1193 |
<link href="https://dx.doi.org/10.17487/rfc9305" rel="alternate"> |
| 1194 |
<link href="urn:issn:2070-1721" rel="alternate"> |
| 1195 |
<link href="https://datatracker.ietf.org/doc/draft-ietf-lisp-gpe-19" rel="prev"> |
| 1196 |
</head> |
| 1197 |
<body class="xml2rfc"> |
| 1198 |
<script src="https://www.rfc-editor.org/js/metadata.min.js"></script> |
| 1199 |
<table class="ears"> |
| 1200 |
<thead><tr> |
| 1201 |
<td class="left">RFC 9305</td> |
| 1202 |
<td class="center">LISP-GPE</td> |
| 1203 |
<td class="right">October 2022</td> |
| 1204 |
</tr></thead> |
| 1205 |
<tfoot><tr> |
| 1206 |
<td class="left">Maino, et al.</td> |
| 1207 |
<td class="center">Standards Track</td> |
| 1208 |
<td class="right">[Page]</td> |
| 1209 |
</tr></tfoot> |
| 1210 |
</table> |
| 1211 |
<div id="external-metadata" class="document-information"></div> |
| 1212 |
<div id="internal-metadata" class="document-information"> |
| 1213 |
<dl id="identifiers"> |
| 1214 |
<dt class="label-stream">Stream:</dt> |
| 1215 |
<dd class="stream">Internet Engineering Task Force (IETF)</dd> |
| 1216 |
<dt class="label-rfc">RFC:</dt> |
| 1217 |
<dd class="rfc"><a href="https://www.rfc-editor.org/rfc/rfc9305" class="eref">9305</a></dd> |
| 1218 |
<dt class="label-category">Category:</dt> |
| 1219 |
<dd class="category">Standards Track</dd> |
| 1220 |
<dt class="label-published">Published:</dt> |
| 1221 |
<dd class="published"> |
| 1222 |
<time datetime="2022-10" class="published">October 2022</time> |
| 1223 |
</dd> |
| 1224 |
<dt class="label-issn">ISSN:</dt> |
| 1225 |
<dd class="issn">2070-1721</dd> |
| 1226 |
<dt class="label-authors">Authors:</dt> |
| 1227 |
<dd class="authors"> |
| 1228 |
<div class="author"> |
| 1229 |
<div class="author-name">F. Maino, <span class="editor">Ed.</span> |
| 1230 |
</div> |
| 1231 |
<div class="org">Cisco</div> |
| 1232 |
</div> |
| 1233 |
<div class="author"> |
| 1234 |
<div class="author-name">J. Lemon</div> |
| 1235 |
</div> |
| 1236 |
<div class="author"> |
| 1237 |
<div class="author-name">P. Agarwal</div> |
| 1238 |
<div class="org">Innovium</div> |
| 1239 |
</div> |
| 1240 |
<div class="author"> |
| 1241 |
<div class="author-name">D. Lewis</div> |
| 1242 |
<div class="org">Cisco</div> |
| 1243 |
</div> |
| 1244 |
<div class="author"> |
| 1245 |
<div class="author-name">M. Smith</div> |
| 1246 |
<div class="org">Cisco</div> |
| 1247 |
</div> |
| 1248 |
</dd> |
| 1249 |
</dl> |
| 1250 |
</div> |
| 1251 |
<h1 id="rfcnum">RFC 9305</h1> |
| 1252 |
<h1 id="title">Locator/ID Separation Protocol (LISP) Generic Protocol Extension</h1> |
| 1253 |
<section id="section-abstract"> |
| 1254 |
<h2 id="abstract"><a href="#abstract" class="selfRef">Abstract</a></h2> |
| 1255 |
<p id="section-abstract-1">This document describes extensions to the Locator/ID Separation |
| 1256 |
Protocol (LISP) data plane, via changes to the LISP header, to support |
| 1257 |
multiprotocol encapsulation and allow the introduction of new protocol |
| 1258 |
capabilities.<a href="#section-abstract-1" class="pilcrow">¶</a></p> |
| 1259 |
</section> |
| 1260 |
<div id="status-of-memo"> |
| 1261 |
<section id="section-boilerplate.1"> |
| 1262 |
<h2 id="name-status-of-this-memo"> |
| 1263 |
<a href="#name-status-of-this-memo" class="section-name selfRef">Status of This Memo</a> |
| 1264 |
</h2> |
| 1265 |
<p id="section-boilerplate.1-1"> |
| 1266 |
This is an Internet Standards Track document.<a href="#section-boilerplate.1-1" class="pilcrow">¶</a></p> |
| 1267 |
<p id="section-boilerplate.1-2"> |
| 1268 |
This document is a product of the Internet Engineering Task Force |
| 1269 |
(IETF). It represents the consensus of the IETF community. It has |
| 1270 |
received public review and has been approved for publication by |
| 1271 |
the Internet Engineering Steering Group (IESG). Further |
| 1272 |
information on Internet Standards is available in Section 2 of |
| 1273 |
RFC 7841.<a href="#section-boilerplate.1-2" class="pilcrow">¶</a></p> |
| 1274 |
<p id="section-boilerplate.1-3"> |
| 1275 |
Information about the current status of this document, any |
| 1276 |
errata, and how to provide feedback on it may be obtained at |
| 1277 |
<span><a href="https://www.rfc-editor.org/info/rfc9305">https://www.rfc-editor.org/info/rfc9305</a></span>.<a href="#section-boilerplate.1-3" class="pilcrow">¶</a></p> |
| 1278 |
</section> |
| 1279 |
</div> |
| 1280 |
<div id="copyright"> |
| 1281 |
<section id="section-boilerplate.2"> |
| 1282 |
<h2 id="name-copyright-notice"> |
| 1283 |
<a href="#name-copyright-notice" class="section-name selfRef">Copyright Notice</a> |
| 1284 |
</h2> |
| 1285 |
<p id="section-boilerplate.2-1"> |
| 1286 |
Copyright (c) 2022 IETF Trust and the persons identified as the |
| 1287 |
document authors. All rights reserved.<a href="#section-boilerplate.2-1" class="pilcrow">¶</a></p> |
| 1288 |
<p id="section-boilerplate.2-2"> |
| 1289 |
This document is subject to BCP 78 and the IETF Trust's Legal |
| 1290 |
Provisions Relating to IETF Documents |
| 1291 |
(<span><a href="https://trustee.ietf.org/license-info">https://trustee.ietf.org/license-info</a></span>) in effect on the date of |
| 1292 |
publication of this document. Please review these documents |
| 1293 |
carefully, as they describe your rights and restrictions with |
| 1294 |
respect to this document. Code Components extracted from this |
| 1295 |
document must include Revised BSD License text as described in |
| 1296 |
Section 4.e of the Trust Legal Provisions and are provided without |
| 1297 |
warranty as described in the Revised BSD License.<a href="#section-boilerplate.2-2" class="pilcrow">¶</a></p> |
| 1298 |
</section> |
| 1299 |
</div> |
| 1300 |
<div id="toc"> |
| 1301 |
<section id="section-toc.1"> |
| 1302 |
<a href="#" onclick="scroll(0,0)" class="toplink">▲</a><h2 id="name-table-of-contents"> |
| 1303 |
<a href="#name-table-of-contents" class="section-name selfRef">Table of Contents</a> |
| 1304 |
</h2> |
| 1305 |
<nav class="toc"><ul class="compact toc ulBare ulEmpty"> |
| 1306 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.1"> |
| 1307 |
<p id="section-toc.1-1.1.1" class="keepWithNext"><a href="#section-1" class="auto internal xref">1</a>. <a href="#name-introduction" class="internal xref">Introduction</a></p> |
| 1308 |
<ul class="compact toc ulBare ulEmpty"> |
| 1309 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.1.2.1"> |
| 1310 |
<p id="section-toc.1-1.1.2.1.1" class="keepWithNext"><a href="#section-1.1" class="auto internal xref">1.1</a>. <a href="#name-conventions" class="internal xref">Conventions</a></p> |
| 1311 |
</li> |
| 1312 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.1.2.2"> |
| 1313 |
<p id="section-toc.1-1.1.2.2.1" class="keepWithNext"><a href="#section-1.2" class="auto internal xref">1.2</a>. <a href="#name-definitions-of-terms" class="internal xref">Definitions of Terms</a></p> |
| 1314 |
</li> |
| 1315 |
</ul> |
| 1316 |
</li> |
| 1317 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.2"> |
| 1318 |
<p id="section-toc.1-1.2.1"><a href="#section-2" class="auto internal xref">2</a>. <a href="#name-lisp-header-without-protoco" class="internal xref">LISP Header without Protocol Extensions</a></p> |
| 1319 |
</li> |
| 1320 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.3"> |
| 1321 |
<p id="section-toc.1-1.3.1"><a href="#section-3" class="auto internal xref">3</a>. <a href="#name-lisp-generic-protocol-exten" class="internal xref">LISP Generic Protocol Extension (LISP-GPE)</a></p> |
| 1322 |
</li> |
| 1323 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.4"> |
| 1324 |
<p id="section-toc.1-1.4.1"><a href="#section-4" class="auto internal xref">4</a>. <a href="#name-implementation-and-deployme" class="internal xref">Implementation and Deployment Considerations</a></p> |
| 1325 |
<ul class="compact toc ulBare ulEmpty"> |
| 1326 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.4.2.1"> |
| 1327 |
<p id="section-toc.1-1.4.2.1.1"><a href="#section-4.1" class="auto internal xref">4.1</a>. <a href="#name-applicability-statement" class="internal xref">Applicability Statement</a></p> |
| 1328 |
</li> |
| 1329 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.4.2.2"> |
| 1330 |
<p id="section-toc.1-1.4.2.2.1"><a href="#section-4.2" class="auto internal xref">4.2</a>. <a href="#name-congestion-control-function" class="internal xref">Congestion-Control Functionality</a></p> |
| 1331 |
</li> |
| 1332 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.4.2.3"> |
| 1333 |
<p id="section-toc.1-1.4.2.3.1"><a href="#section-4.3" class="auto internal xref">4.3</a>. <a href="#name-udp-checksum" class="internal xref">UDP Checksum</a></p> |
| 1334 |
<ul class="compact toc ulBare ulEmpty"> |
| 1335 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.4.2.3.2.1"> |
| 1336 |
<p id="section-toc.1-1.4.2.3.2.1.1"><a href="#section-4.3.1" class="auto internal xref">4.3.1</a>. <a href="#name-udp-zero-checksum-handling-" class="internal xref">UDP Zero Checksum Handling with IPv6</a></p> |
| 1337 |
</li> |
| 1338 |
</ul> |
| 1339 |
</li> |
| 1340 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.4.2.4"> |
| 1341 |
<p id="section-toc.1-1.4.2.4.1"><a href="#section-4.4" class="auto internal xref">4.4</a>. <a href="#name-dscp-ecn-ttl-and-8021q" class="internal xref">DSCP, ECN, TTL, and 802.1Q</a></p> |
| 1342 |
</li> |
| 1343 |
</ul> |
| 1344 |
</li> |
| 1345 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.5"> |
| 1346 |
<p id="section-toc.1-1.5.1"><a href="#section-5" class="auto internal xref">5</a>. <a href="#name-backward-compatibility" class="internal xref">Backward Compatibility</a></p> |
| 1347 |
<ul class="compact toc ulBare ulEmpty"> |
| 1348 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.5.2.1"> |
| 1349 |
<p id="section-toc.1-1.5.2.1.1"><a href="#section-5.1" class="auto internal xref">5.1</a>. <a href="#name-detection-of-etr-capabiliti" class="internal xref">Detection of ETR Capabilities</a></p> |
| 1350 |
</li> |
| 1351 |
</ul> |
| 1352 |
</li> |
| 1353 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.6"> |
| 1354 |
<p id="section-toc.1-1.6.1"><a href="#section-6" class="auto internal xref">6</a>. <a href="#name-iana-considerations" class="internal xref">IANA Considerations</a></p> |
| 1355 |
<ul class="compact toc ulBare ulEmpty"> |
| 1356 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.6.2.1"> |
| 1357 |
<p id="section-toc.1-1.6.2.1.1"><a href="#section-6.1" class="auto internal xref">6.1</a>. <a href="#name-lisp-gpe-next-protocol-regi" class="internal xref">LISP-GPE Next Protocol Registry</a></p> |
| 1358 |
</li> |
| 1359 |
</ul> |
| 1360 |
</li> |
| 1361 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.7"> |
| 1362 |
<p id="section-toc.1-1.7.1"><a href="#section-7" class="auto internal xref">7</a>. <a href="#name-security-considerations" class="internal xref">Security Considerations</a></p> |
| 1363 |
</li> |
| 1364 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.8"> |
| 1365 |
<p id="section-toc.1-1.8.1"><a href="#section-8" class="auto internal xref">8</a>. <a href="#name-references" class="internal xref">References</a></p> |
| 1366 |
<ul class="compact toc ulBare ulEmpty"> |
| 1367 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.8.2.1"> |
| 1368 |
<p id="section-toc.1-1.8.2.1.1"><a href="#section-8.1" class="auto internal xref">8.1</a>. <a href="#name-normative-references" class="internal xref">Normative References</a></p> |
| 1369 |
</li> |
| 1370 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.8.2.2"> |
| 1371 |
<p id="section-toc.1-1.8.2.2.1"><a href="#section-8.2" class="auto internal xref">8.2</a>. <a href="#name-informative-references" class="internal xref">Informative References</a></p> |
| 1372 |
</li> |
| 1373 |
</ul> |
| 1374 |
</li> |
| 1375 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.9"> |
| 1376 |
<p id="section-toc.1-1.9.1"><a href="#appendix-A" class="auto internal xref"></a><a href="#name-acknowledgments" class="internal xref">Acknowledgments</a></p> |
| 1377 |
</li> |
| 1378 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.10"> |
| 1379 |
<p id="section-toc.1-1.10.1"><a href="#appendix-B" class="auto internal xref"></a><a href="#name-contributors" class="internal xref">Contributors</a></p> |
| 1380 |
</li> |
| 1381 |
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.11"> |
| 1382 |
<p id="section-toc.1-1.11.1"><a href="#appendix-C" class="auto internal xref"></a><a href="#name-authors-addresses" class="internal xref">Authors' Addresses</a></p> |
| 1383 |
</li> |
| 1384 |
</ul> |
| 1385 |
</nav> |
| 1386 |
</section> |
| 1387 |
</div> |
| 1388 |
<div id="Introduction"> |
| 1389 |
<section id="section-1"> |
| 1390 |
<h2 id="name-introduction"> |
| 1391 |
<a href="#section-1" class="section-number selfRef">1. </a><a href="#name-introduction" class="section-name selfRef">Introduction</a> |
| 1392 |
</h2> |
| 1393 |
<p id="section-1-1">The LISP data plane is defined in <span>[<a href="#RFC9300" class="cite xref">RFC9300</a>]</span>. |
| 1394 |
It specifies an encapsulation |
| 1395 |
format that carries IPv4 or IPv6 packets (henceforth jointly referred to |
| 1396 |
as IP) in a LISP header and outer UDP/IP transport.<a href="#section-1-1" class="pilcrow">¶</a></p> |
| 1397 |
<p id="section-1-2">The LISP data plane header does not specify the protocol being |
| 1398 |
encapsulated and, therefore, is currently limited to encapsulating only IP |
| 1399 |
packet payloads. Other protocols, most notably the Virtual eXtensible Local |
| 1400 |
Area Network (VXLAN) protocol <span>[<a href="#RFC7348" class="cite xref">RFC7348</a>]</span> (which defines a header format similar to LISP), are used to encapsulate Layer 2 (L2) protocols, |
| 1401 |
such as Ethernet.<a href="#section-1-2" class="pilcrow">¶</a></p> |
| 1402 |
<p id="section-1-3">This document defines an extension for the LISP header, as defined in |
| 1403 |
<span>[<a href="#RFC9300" class="cite xref">RFC9300</a>]</span>, to indicate the inner |
| 1404 |
protocol, enabling the encapsulation of Ethernet, IP, or any other |
| 1405 |
desired protocol, all the while ensuring compatibility with existing LISP |
| 1406 |
deployments.<a href="#section-1-3" class="pilcrow">¶</a></p> |
| 1407 |
<p id="section-1-4">A flag in the LISP header -- the P-bit -- is used to signal the |
| 1408 |
presence of the 8-bit 'Next Protocol' field. The 'Next Protocol' field, when |
| 1409 |
present, uses 8 bits of the field that was allocated to the Echo-Noncing |
| 1410 |
and Map-Versioning features in <span>[<a href="#RFC9300" class="cite xref">RFC9300</a>]</span>. Those two features are no longer |
| 1411 |
available when the P-bit is used. However, appropriate LISP |
| 1412 |
Generic Protocol Extension (LISP-GPE) shim headers can be defined to specify |
| 1413 |
capabilities that are equivalent to Echo-Noncing and/or |
| 1414 |
Map-Versioning.<a href="#section-1-4" class="pilcrow">¶</a></p> |
| 1415 |
<p id="section-1-5">Since all of the reserved bits of the LISP data plane header have |
| 1416 |
been allocated, LISP-GPE can also be used to extend the LISP data plane |
| 1417 |
header by defining Next Protocol shim headers that implement new |
| 1418 |
data plane functions not supported in the LISP header. For example, the use |
| 1419 |
of the Group-Based Policy (GBP) header <span>[<a href="#VXLAN-LISP" class="cite xref">VXLAN-LISP</a>]</span> or of the In situ Operations, |
| 1420 |
Administration, and Maintenance (IOAM) header <span>[<a href="#VXLAN-GPE" class="cite xref">VXLAN-GPE</a>]</span> with LISP-GPE can be |
| 1421 |
considered an extension to add support in the data plane for GBP functionalities or IOAM metadata.<a href="#section-1-5" class="pilcrow">¶</a></p> |
| 1422 |
<div id="Conventions"> |
| 1423 |
<section id="section-1.1"> |
| 1424 |
<h3 id="name-conventions"> |
| 1425 |
<a href="#section-1.1" class="section-number selfRef">1.1. </a><a href="#name-conventions" class="section-name selfRef">Conventions</a> |
| 1426 |
</h3> |
| 1427 |
<p id="section-1.1-1">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>", |
| 1428 |
"<span class="bcp14">SHOULD</span>", "<span class="bcp14">SHOULD NOT</span>", "<span class="bcp14">RECOMMENDED</span>", "<span class="bcp14">NOT RECOMMENDED</span>", "<span class="bcp14">MAY</span>", and |
| 1429 |
"<span class="bcp14">OPTIONAL</span>" in this document are to be interpreted as described in BCP |
| 1430 |
14 <span>[<a href="#RFC2119" class="cite xref">RFC2119</a>]</span> <span>[<a href="#RFC8174" class="cite xref">RFC8174</a>]</span> when, and only |
| 1431 |
when, they appear in all capitals, as shown here.<a href="#section-1.1-1" class="pilcrow">¶</a></p> |
| 1432 |
</section> |
| 1433 |
</div> |
| 1434 |
<div id="Abbreviations"> |
| 1435 |
<section id="section-1.2"> |
| 1436 |
<h3 id="name-definitions-of-terms"> |
| 1437 |
<a href="#section-1.2" class="section-number selfRef">1.2. </a><a href="#name-definitions-of-terms" class="section-name selfRef">Definitions of Terms</a> |
| 1438 |
</h3> |
| 1439 |
<p id="section-1.2-1">This document uses terms already defined in <span>[<a href="#RFC9300" class="cite xref">RFC9300</a>]</span>.<a href="#section-1.2-1" class="pilcrow">¶</a></p> |
| 1440 |
</section> |
| 1441 |
</div> |
| 1442 |
</section> |
| 1443 |
</div> |
| 1444 |
<div id="LISP_header"> |
| 1445 |
<section id="section-2"> |
| 1446 |
<h2 id="name-lisp-header-without-protoco"> |
| 1447 |
<a href="#section-2" class="section-number selfRef">2. </a><a href="#name-lisp-header-without-protoco" class="section-name selfRef">LISP Header without Protocol Extensions</a> |
| 1448 |
</h2> |
| 1449 |
<p id="section-2-1">As described in <a href="#Introduction" class="auto internal xref">Section 1</a>, the LISP header has no |
| 1450 |
protocol identifier that indicates the type of payload being carried. |
| 1451 |
Because of this, LISP is limited to carrying IP payloads.<a href="#section-2-1" class="pilcrow">¶</a></p> |
| 1452 |
<p id="section-2-2">The LISP header <span>[<a href="#RFC9300" class="cite xref">RFC9300</a>]</span> contains a |
| 1453 |
series of flags (some defined, some reserved), a 'Nonce/Map-Version' field, |
| 1454 |
and an 'Instance ID/Locator-Status-Bits' field. The flags provide |
| 1455 |
flexibility to define how the various fields are encoded. Notably, Flag |
| 1456 |
bit 5 is the last reserved bit in the LISP header.<a href="#section-2-2" class="pilcrow">¶</a></p> |
| 1457 |
<span id="name-lisp-header"></span><div id="LISP_Header"> |
| 1458 |
<figure id="figure-1"> |
| 1459 |
<div class="alignLeft art-text artwork" id="section-2-3.1"> |
| 1460 |
<pre> |
| 1461 |
0 1 2 3 |
| 1462 |
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 |
| 1463 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 1464 |
|N|L|E|V|I|R|K|K| Nonce/Map-Version | |
| 1465 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 1466 |
| Instance ID/Locator-Status-Bits | |
| 1467 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 1468 |
</pre> |
| 1469 |
</div> |
| 1470 |
<figcaption><a href="#figure-1" class="selfRef">Figure 1</a>: |
| 1471 |
<a href="#name-lisp-header" class="selfRef">LISP Header</a> |
| 1472 |
</figcaption></figure> |
| 1473 |
</div> |
| 1474 |
</section> |
| 1475 |
</div> |
| 1476 |
<div id="LISP_GPE"> |
| 1477 |
<section id="section-3"> |
| 1478 |
<h2 id="name-lisp-generic-protocol-exten"> |
| 1479 |
<a href="#section-3" class="section-number selfRef">3. </a><a href="#name-lisp-generic-protocol-exten" class="section-name selfRef">LISP Generic Protocol Extension (LISP-GPE)</a> |
| 1480 |
</h2> |
| 1481 |
<p id="section-3-1">This document defines two changes to the LISP header in order to |
| 1482 |
support multiprotocol encapsulation: the introduction of the P-bit and |
| 1483 |
the definition of a 'Next Protocol' field. This document specifies the |
| 1484 |
protocol behavior when the P-bit is set to 1; no changes are introduced |
| 1485 |
when the P-bit is set to 0. The LISP-GPE header is shown in <a href="#GPE_Header" class="auto internal xref">Figure 2</a> and described below.<a href="#section-3-1" class="pilcrow">¶</a></p> |
| 1486 |
<span id="name-lisp-gpe-header"></span><div id="GPE_Header"> |
| 1487 |
<figure id="figure-2"> |
| 1488 |
<div class="alignLeft art-text artwork" id="section-3-2.1"> |
| 1489 |
<pre> |
| 1490 |
0 1 2 3 |
| 1491 |
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 |
| 1492 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 1493 |
|N|L|E|V|I|P|K|K| Nonce/Map-Version/Next Protocol | |
| 1494 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 1495 |
| Instance ID/Locator-Status-Bits | |
| 1496 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 1497 |
</pre> |
| 1498 |
</div> |
| 1499 |
<figcaption><a href="#figure-2" class="selfRef">Figure 2</a>: |
| 1500 |
<a href="#name-lisp-gpe-header" class="selfRef">LISP-GPE Header</a> |
| 1501 |
</figcaption></figure> |
| 1502 |
</div> |
| 1503 |
<span class="break"></span><dl class="dlParallel" id="section-3-3"> |
| 1504 |
<dt id="section-3-3.1">P-Bit:</dt> |
| 1505 |
<dd style="margin-left: 1.5em" id="section-3-3.2">Flag bit 5 is defined as the Next Protocol bit. |
| 1506 |
The P-bit is set to 1 to indicate the presence of the 8-bit 'Next |
| 1507 |
Protocol' field.<a href="#section-3-3.2" class="pilcrow">¶</a> |
| 1508 |
</dd> |
| 1509 |
<dd class="break"></dd> |
| 1510 |
</dl> |
| 1511 |
<p id="section-3-4">If the P-bit is clear (0), the LISP header is |
| 1512 |
bit-by-bit equivalent to the definition in <span>[<a href="#RFC9300" class="cite xref">RFC9300</a>]</span>.<a href="#section-3-4" class="pilcrow">¶</a></p> |
| 1513 |
<p id="section-3-5">When the P-bit is set to 1, bits N, E, and V, and bits 8-23 of the |
| 1514 |
'Nonce/Map-Version/Next Protocol' field <span class="bcp14">MUST</span> be set to zero on |
| 1515 |
transmission and <span class="bcp14">MUST</span> be ignored on receipt. Features equivalent to |
| 1516 |
those that were implemented with bits N, E, and V in <span>[<a href="#RFC9300" class="cite xref">RFC9300</a>]</span>, such as Echo-Noncing and |
| 1517 |
Map-Versioning, can be implemented by defining appropriate LISP-GPE |
| 1518 |
shim headers.<a href="#section-3-5" class="pilcrow">¶</a></p> |
| 1519 |
<p id="section-3-6">When the P-bit is set to 1, the LISP-GPE header is encoded |
| 1520 |
as:<a href="#section-3-6" class="pilcrow">¶</a></p> |
| 1521 |
<span id="name-lisp-gpe-with-p-bit-set-to-"></span><div id="GPE_Header_Next_Protocol"> |
| 1522 |
<figure id="figure-3"> |
| 1523 |
<div class="alignLeft art-text artwork" id="section-3-7.1"> |
| 1524 |
<pre> |
| 1525 |
0 x 0 0 x 1 x x |
| 1526 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 1527 |
|N|L|E|V|I|P|K|K| 0x0000 | Next Protocol | |
| 1528 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 1529 |
| Instance ID/Locator-Status-Bits | |
| 1530 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 1531 |
</pre> |
| 1532 |
</div> |
| 1533 |
<figcaption><a href="#figure-3" class="selfRef">Figure 3</a>: |
| 1534 |
<a href="#name-lisp-gpe-with-p-bit-set-to-" class="selfRef">LISP-GPE with P-bit Set to 1</a> |
| 1535 |
</figcaption></figure> |
| 1536 |
</div> |
| 1537 |
<span class="break"></span><dl class="dlParallel" id="section-3-8"> |
| 1538 |
<dt id="section-3-8.1">Next Protocol:</dt> |
| 1539 |
<dd style="margin-left: 1.5em" id="section-3-8.2">When the P-bit is set to 1, the lower 8 |
| 1540 |
bits of the first 32-bit word are used to carry a Next Protocol. |
| 1541 |
This 'Next Protocol' field contains the protocol of the encapsulated |
| 1542 |
payload packet.<a href="#section-3-8.2" class="pilcrow">¶</a> |
| 1543 |
</dd> |
| 1544 |
<dd class="break"></dd> |
| 1545 |
</dl> |
| 1546 |
<p id="section-3-9">This document defines the following Next Protocol values:<a href="#section-3-9" class="pilcrow">¶</a></p> |
| 1547 |
<span class="break"></span><dl class="dlParallel" id="section-3-10"> |
| 1548 |
<dt id="section-3-10.1">0x00:</dt> |
| 1549 |
<dd style="margin-left: 1.5em" id="section-3-10.2">Reserved<a href="#section-3-10.2" class="pilcrow">¶</a> |
| 1550 |
</dd> |
| 1551 |
<dd class="break"></dd> |
| 1552 |
<dt id="section-3-10.3">0x01:</dt> |
| 1553 |
<dd style="margin-left: 1.5em" id="section-3-10.4">IPv4<a href="#section-3-10.4" class="pilcrow">¶</a> |
| 1554 |
</dd> |
| 1555 |
<dd class="break"></dd> |
| 1556 |
<dt id="section-3-10.5">0x02:</dt> |
| 1557 |
<dd style="margin-left: 1.5em" id="section-3-10.6">IPv6<a href="#section-3-10.6" class="pilcrow">¶</a> |
| 1558 |
</dd> |
| 1559 |
<dd class="break"></dd> |
| 1560 |
<dt id="section-3-10.7">0x03:</dt> |
| 1561 |
<dd style="margin-left: 1.5em" id="section-3-10.8">Ethernet<a href="#section-3-10.8" class="pilcrow">¶</a> |
| 1562 |
</dd> |
| 1563 |
<dd class="break"></dd> |
| 1564 |
<dt id="section-3-10.9">0x04:</dt> |
| 1565 |
<dd style="margin-left: 1.5em" id="section-3-10.10">Network Service Header (NSH) <span>[<a href="#RFC8300" class="cite xref">RFC8300</a>]</span><a href="#section-3-10.10" class="pilcrow">¶</a> |
| 1566 |
</dd> |
| 1567 |
<dd class="break"></dd> |
| 1568 |
<dt id="section-3-10.11">0x05 to 0x7D:</dt> |
| 1569 |
<dd style="margin-left: 1.5em" id="section-3-10.12">Unassigned<a href="#section-3-10.12" class="pilcrow">¶</a> |
| 1570 |
</dd> |
| 1571 |
<dd class="break"></dd> |
| 1572 |
<dt id="section-3-10.13">0x7E and 0x7F:</dt> |
| 1573 |
<dd style="margin-left: 1.5em" id="section-3-10.14">Experimentation and testing<a href="#section-3-10.14" class="pilcrow">¶</a> |
| 1574 |
</dd> |
| 1575 |
<dd class="break"></dd> |
| 1576 |
<dt id="section-3-10.15">0x80 to 0xFD:</dt> |
| 1577 |
<dd style="margin-left: 1.5em" id="section-3-10.16">Unassigned (shim headers)<a href="#section-3-10.16" class="pilcrow">¶</a> |
| 1578 |
</dd> |
| 1579 |
<dd class="break"></dd> |
| 1580 |
<dt id="section-3-10.17">0xFE, 0xFF:</dt> |
| 1581 |
<dd style="margin-left: 1.5em" id="section-3-10.18">Experimentation and testing (shim |
| 1582 |
headers)<a href="#section-3-10.18" class="pilcrow">¶</a> |
| 1583 |
</dd> |
| 1584 |
<dd class="break"></dd> |
| 1585 |
</dl> |
| 1586 |
<p id="section-3-11">The values are tracked in the IANA "LISP-GPE Next |
| 1587 |
Protocol" registry, as described in <a href="#Next_protocol" class="auto internal xref">Section 6.1</a>.<a href="#section-3-11" class="pilcrow">¶</a></p> |
| 1588 |
<p id="section-3-12">Next Protocol values 0x7E, 0x7F, 0xFE, and 0xFF are assigned for |
| 1589 |
experimentation and testing, as per <span>[<a href="#RFC3692" class="cite xref">RFC3692</a>]</span>.<a href="#section-3-12" class="pilcrow">¶</a></p> |
| 1590 |
<p id="section-3-13">Next Protocol values from 0x80 to 0xFD are assigned to protocols |
| 1591 |
encoded as generic shim headers. All shim protocols <span class="bcp14">MUST</span> use the |
| 1592 |
header structure in <a href="#shim" class="auto internal xref">Figure 4</a>, which includes a 'Next |
| 1593 |
Protocol' field. When shim headers are used with other protocols |
| 1594 |
identified by Next Protocol values from 0x00 to 0x7F, all the shim |
| 1595 |
headers <span class="bcp14">MUST</span> come first.<a href="#section-3-13" class="pilcrow">¶</a></p> |
| 1596 |
<p id="section-3-14">Shim headers can be used to incrementally deploy new GPE features, |
| 1597 |
keeping the processing of shim headers known to a given Tunnel Router (xTR) |
| 1598 |
implementation in the 'fast' path (typically an Application-Specific Integrated |
| 1599 |
Circuit (ASIC)) while punting the |
| 1600 |
processing of the remaining new GPE features to the 'slow' path.<a href="#section-3-14" class="pilcrow">¶</a></p> |
| 1601 |
<p id="section-3-15">Shim protocols <span class="bcp14">MUST</span> have the first 32 bits defined as:<a href="#section-3-15" class="pilcrow">¶</a></p> |
| 1602 |
<p id="section-3-16" class="keepWithNext"></p> |
| 1603 |
<span id="name-shim-header"></span><div id="shim"> |
| 1604 |
<figure id="figure-4"> |
| 1605 |
<div class="alignLeft art-text artwork" id="section-3-17.1"> |
| 1606 |
<pre> |
| 1607 |
0 1 2 3 |
| 1608 |
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 |
| 1609 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 1610 |
| Type | Length | Reserved | Next Protocol | |
| 1611 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 1612 |
| | |
| 1613 |
~ Protocol-Specific Fields ~ |
| 1614 |
| | |
| 1615 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 1616 |
</pre> |
| 1617 |
</div> |
| 1618 |
<figcaption><a href="#figure-4" class="selfRef">Figure 4</a>: |
| 1619 |
<a href="#name-shim-header" class="selfRef">Shim Header</a> |
| 1620 |
</figcaption></figure> |
| 1621 |
</div> |
| 1622 |
<p id="section-3-18" class="keepWithPrevious"></p> |
| 1623 |
<p id="section-3-19">Where:<a href="#section-3-19" class="pilcrow">¶</a></p> |
| 1624 |
<span class="break"></span><dl class="dlParallel" id="section-3-20"> |
| 1625 |
<dt id="section-3-20.1">Type:</dt> |
| 1626 |
<dd style="margin-left: 1.5em" id="section-3-20.2">This field identifies the different messages of |
| 1627 |
this protocol.<a href="#section-3-20.2" class="pilcrow">¶</a> |
| 1628 |
</dd> |
| 1629 |
<dd class="break"></dd> |
| 1630 |
<dt id="section-3-20.3">Length:</dt> |
| 1631 |
<dd style="margin-left: 1.5em" id="section-3-20.4">This field indicates the length, in 4-octet units, of this protocol |
| 1632 |
message, not including the first 4 octets.<a href="#section-3-20.4" class="pilcrow">¶</a> |
| 1633 |
</dd> |
| 1634 |
<dd class="break"></dd> |
| 1635 |
<dt id="section-3-20.5">Reserved:</dt> |
| 1636 |
<dd style="margin-left: 1.5em" id="section-3-20.6">The use of this field is reserved to the |
| 1637 |
protocol defined in this message.<a href="#section-3-20.6" class="pilcrow">¶</a> |
| 1638 |
</dd> |
| 1639 |
<dd class="break"></dd> |
| 1640 |
<dt id="section-3-20.7">Next Protocol:</dt> |
| 1641 |
<dd style="margin-left: 1.5em" id="section-3-20.8">This field contains |
| 1642 |
the protocol of the encapsulated payload. The values are tracked in |
| 1643 |
the IANA "LISP-GPE Next Protocol" registry, as described in <a href="#Next_protocol" class="auto internal xref">Section 6.1</a>.<a href="#section-3-20.8" class="pilcrow">¶</a> |
| 1644 |
</dd> |
| 1645 |
<dd class="break"></dd> |
| 1646 |
</dl> |
| 1647 |
</section> |
| 1648 |
</div> |
| 1649 |
<div id="Deployments"> |
| 1650 |
<section id="section-4"> |
| 1651 |
<h2 id="name-implementation-and-deployme"> |
| 1652 |
<a href="#section-4" class="section-number selfRef">4. </a><a href="#name-implementation-and-deployme" class="section-name selfRef">Implementation and Deployment Considerations</a> |
| 1653 |
</h2> |
| 1654 |
<div id="Applicability"> |
| 1655 |
<section id="section-4.1"> |
| 1656 |
<h3 id="name-applicability-statement"> |
| 1657 |
<a href="#section-4.1" class="section-number selfRef">4.1. </a><a href="#name-applicability-statement" class="section-name selfRef">Applicability Statement</a> |
| 1658 |
</h3> |
| 1659 |
<p id="section-4.1-1">LISP-GPE conforms, as a UDP-based encapsulation protocol, to the |
| 1660 |
UDP usage guidelines specified in <span>[<a href="#RFC8085" class="cite xref">RFC8085</a>]</span>. The |
| 1661 |
applicability of these guidelines is dependent on the underlay IP |
| 1662 |
network and the nature of the encapsulated payload.<a href="#section-4.1-1" class="pilcrow">¶</a></p> |
| 1663 |
<p id="section-4.1-2"><span>[<a href="#RFC8085" class="cite xref">RFC8085</a>]</span> outlines two applicability scenarios for |
| 1664 |
UDP applications: 1) the general Internet and 2) a controlled environment. |
| 1665 |
A controlled environment means a single administrative domain or |
| 1666 |
adjacent set of cooperating domains. A network in a controlled |
| 1667 |
environment can be managed to operate under certain conditions, whereas, |
| 1668 |
in the general Internet, this cannot be done. Hence, requirements for a |
| 1669 |
tunnel protocol operating under a controlled environment can be less |
| 1670 |
restrictive than the requirements of the general Internet.<a href="#section-4.1-2" class="pilcrow">¶</a></p> |
| 1671 |
<p id="section-4.1-3">The LISP-GPE scope of applicability is the same set of use cases |
| 1672 |
covered by <span>[<a href="#RFC9300" class="cite xref">RFC9300</a>]</span> for the LISP |
| 1673 |
data plane protocol. The common property of these use cases is a large |
| 1674 |
set of cooperating entities seeking to communicate over the public |
| 1675 |
Internet or other large underlay IP infrastructures while keeping the |
| 1676 |
addressing and topology of the cooperating entities separate from the |
| 1677 |
underlay and Internet topology, routing, and addressing.<a href="#section-4.1-3" class="pilcrow">¶</a></p> |
| 1678 |
<p id="section-4.1-4">LISP-GPE is meant to be deployed in network environments operated |
| 1679 |
by a single operator or adjacent set of cooperating network operators |
| 1680 |
that fit with the definition of controlled environments in <span>[<a href="#RFC8085" class="cite xref">RFC8085</a>]</span>.<a href="#section-4.1-4" class="pilcrow">¶</a></p> |
| 1681 |
<p id="section-4.1-5">For the purpose of this document, a Traffic-Managed Controlled |
| 1682 |
Environment (TMCE), outlined in <span>[<a href="#RFC8086" class="cite xref">RFC8086</a>]</span>, is defined |
| 1683 |
as an IP network that is traffic-engineered and/or otherwise managed |
| 1684 |
(e.g., via the use of traffic rate limiters) to avoid congestion. |
| 1685 |
Significant portions of the text in this section are based on <span>[<a href="#RFC8086" class="cite xref">RFC8086</a>]</span>.<a href="#section-4.1-5" class="pilcrow">¶</a></p> |
| 1686 |
<p id="section-4.1-6">It is the responsibility of the network operators to ensure that |
| 1687 |
the guidelines/requirements in this section are followed as applicable |
| 1688 |
to their LISP-GPE deployments.<a href="#section-4.1-6" class="pilcrow">¶</a></p> |
| 1689 |
</section> |
| 1690 |
</div> |
| 1691 |
<div id="CongestionControl"> |
| 1692 |
<section id="section-4.2"> |
| 1693 |
<h3 id="name-congestion-control-function"> |
| 1694 |
<a href="#section-4.2" class="section-number selfRef">4.2. </a><a href="#name-congestion-control-function" class="section-name selfRef">Congestion-Control Functionality</a> |
| 1695 |
</h3> |
| 1696 |
<p id="section-4.2-1">LISP-GPE does not provide congestion-control functionality |
| 1697 |
and relies on the payload protocol traffic for congestion control. As |
| 1698 |
such, LISP-GPE <span class="bcp14">MUST</span> be used with congestion-controlled traffic or |
| 1699 |
within a network that is traffic managed to avoid congestion (TMCE). |
| 1700 |
An operator of a traffic-managed network (TMCE) may avoid congestion |
| 1701 |
by careful provisioning of their networks, rate limiting of user data |
| 1702 |
traffic, and traffic engineering according to path capacity.<a href="#section-4.2-1" class="pilcrow">¶</a></p> |
| 1703 |
<p id="section-4.2-2">Keeping in mind the recommendation above, new encapsulated |
| 1704 |
payloads, when registered with LISP-GPE, <span class="bcp14">MUST</span> be accompanied by a set |
| 1705 |
of guidelines derived from <span><a href="https://www.rfc-editor.org/rfc/rfc9300#section-5" class="relref">Section 5</a> of [<a href="#RFC9300" class="cite xref">RFC9300</a>]</span>. |
| 1706 |
Such new protocols should be designed for explicit congestion signals |
| 1707 |
to propagate consistently from lower-layer protocols into IP. Then, the |
| 1708 |
IP internetwork layer can act as a portability layer to carry |
| 1709 |
congestion notifications from non-IP-aware congested nodes up to the |
| 1710 |
transport layer (L4). By following the guidelines in <span>[<a href="#I-D.ietf-tsvwg-ecn-encap-guidelines" class="cite xref">ENCAP-GUIDE</a>]</span>, subnetwork designers |
| 1711 |
can enable a Layer 2 protocol to participate in congestion control |
| 1712 |
without dropping packets, via propagation of Explicit Congestion |
| 1713 |
Notification (ECN) data <span>[<a href="#RFC3168" class="cite xref">RFC3168</a>]</span> to receivers.<a href="#section-4.2-2" class="pilcrow">¶</a></p> |
| 1714 |
</section> |
| 1715 |
</div> |
| 1716 |
<div id="UDPChecksum"> |
| 1717 |
<section id="section-4.3"> |
| 1718 |
<h3 id="name-udp-checksum"> |
| 1719 |
<a href="#section-4.3" class="section-number selfRef">4.3. </a><a href="#name-udp-checksum" class="section-name selfRef">UDP Checksum</a> |
| 1720 |
</h3> |
| 1721 |
<p id="section-4.3-1">For IP payloads, <span><a href="https://www.rfc-editor.org/rfc/rfc9300#section-5.3" class="relref">Section 5.3</a> of [<a href="#RFC9300" class="cite xref">RFC9300</a>]</span> |
| 1722 |
specifies how to handle UDP |
| 1723 |
checksums, encouraging implementors to consider UDP checksum usage |
| 1724 |
guidelines in <span><a href="https://www.rfc-editor.org/rfc/rfc8085#section-3.4" class="relref">Section 3.4</a> of [<a href="#RFC8085" class="cite xref">RFC8085</a>]</span> when it is |
| 1725 |
desirable to protect UDP and LISP headers against corruption.<a href="#section-4.3-1" class="pilcrow">¶</a></p> |
| 1726 |
<p id="section-4.3-2">In order to protect the integrity of LISP-GPE headers, options, and |
| 1727 |
payloads (for example, to avoid misdelivery of payloads to different |
| 1728 |
tenant systems in the case of data corruption), the outer UDP checksum <span class="bcp14">SHOULD</span> |
| 1729 |
be used with LISP-GPE when transported over IPv4. The UDP checksum |
| 1730 |
provides a statistical guarantee that a payload was not corrupted in |
| 1731 |
transit. These integrity checks are not strong from a coding or |
| 1732 |
cryptographic perspective and are not designed to detect |
| 1733 |
physical-layer errors or malicious modifications of the datagram (see |
| 1734 |
<span><a href="https://www.rfc-editor.org/rfc/rfc8085#section-3.4" class="relref">Section 3.4</a> of [<a href="#RFC8085" class="cite xref">RFC8085</a>]</span>). In deployments where such a |
| 1735 |
risk exists, an operator <span class="bcp14">SHOULD</span> use additional data integrity |
| 1736 |
mechanisms, such as those offered by IPsec.<a href="#section-4.3-2" class="pilcrow">¶</a></p> |
| 1737 |
<p id="section-4.3-3">An operator <span class="bcp14">MAY</span> choose to disable a UDP checksum and use a zero |
| 1738 |
checksum if LISP-GPE packet integrity is provided by other data |
| 1739 |
integrity mechanisms, such as IPsec or additional checksums, or if one |
| 1740 |
of the conditions in <a href="#IPv6Checksum" class="auto internal xref">Section 4.3.1</a> (a, b, or c) is |
| 1741 |
met.<a href="#section-4.3-3" class="pilcrow">¶</a></p> |
| 1742 |
<div id="IPv6Checksum"> |
| 1743 |
<section id="section-4.3.1"> |
| 1744 |
<h4 id="name-udp-zero-checksum-handling-"> |
| 1745 |
<a href="#section-4.3.1" class="section-number selfRef">4.3.1. </a><a href="#name-udp-zero-checksum-handling-" class="section-name selfRef">UDP Zero Checksum Handling with IPv6</a> |
| 1746 |
</h4> |
| 1747 |
<p id="section-4.3.1-1">By default, a UDP checksum <span class="bcp14">MUST</span> be used when LISP-GPE is |
| 1748 |
transported over IPv6. A tunnel endpoint <span class="bcp14">MAY</span> be configured for use |
| 1749 |
with a zero UDP checksum if additional requirements described in this |
| 1750 |
section are met.<a href="#section-4.3.1-1" class="pilcrow">¶</a></p> |
| 1751 |
<p id="section-4.3.1-2">When LISP-GPE is used over IPv6, a UDP checksum is used to protect |
| 1752 |
IPv6 headers, UDP headers, and LISP-GPE headers and payloads from |
| 1753 |
potential data corruption. As such, by default, LISP-GPE <span class="bcp14">MUST</span> use a UDP |
| 1754 |
checksum when transported over IPv6. An operator <span class="bcp14">MAY</span> choose to |
| 1755 |
configure to operate with a zero UDP checksum if operating in a |
| 1756 |
traffic-managed controlled environment, as stated in <a href="#Applicability" class="auto internal xref">Section 4.1</a>, if one of the following conditions is met:<a href="#section-4.3.1-2" class="pilcrow">¶</a></p> |
| 1757 |
<ol start="1" type="a" class="normal type-a" id="section-4.3.1-3"> |
| 1758 |
<li id="section-4.3.1-3.1">It is known that packet corruption is exceptionally |
| 1759 |
unlikely (perhaps based on an operator's knowledge of equipment types in their |
| 1760 |
underlay network), and the operator is willing to take the risk of |
| 1761 |
undetected packet corruption.<a href="#section-4.3.1-3.1" class="pilcrow">¶</a> |
| 1762 |
</li> |
| 1763 |
<li id="section-4.3.1-3.2">It is determined through observational measurements |
| 1764 |
(perhaps |
| 1765 |
through historic or current traffic flows that use a non-zero |
| 1766 |
checksum) that the level of packet corruption is tolerably low, |
| 1767 |
and the operator is willing to take the risk of undetected |
| 1768 |
corruption.<a href="#section-4.3.1-3.2" class="pilcrow">¶</a> |
| 1769 |
</li> |
| 1770 |
<li id="section-4.3.1-3.3">LISP-GPE payloads are carrying applications that are tolerant |
| 1771 |
of misdelivered or corrupted packets (perhaps through higher-layer |
| 1772 |
checksum validation and/or reliability through retransmission).<a href="#section-4.3.1-3.3" class="pilcrow">¶</a> |
| 1773 |
</li> |
| 1774 |
</ol> |
| 1775 |
<p id="section-4.3.1-4">In addition, LISP-GPE tunnel implementations using a zero UDP |
| 1776 |
checksum <span class="bcp14">MUST</span> meet the following requirements:<a href="#section-4.3.1-4" class="pilcrow">¶</a></p> |
| 1777 |
<ol start="1" type="1" class="normal type-1" id="section-4.3.1-5"> |
| 1778 |
<li id="section-4.3.1-5.1">Use of a UDP checksum over IPv6 <span class="bcp14">MUST</span> be the default |
| 1779 |
configuration for all LISP-GPE tunnels.<a href="#section-4.3.1-5.1" class="pilcrow">¶</a> |
| 1780 |
</li> |
| 1781 |
<li id="section-4.3.1-5.2">If LISP-GPE is used with a zero UDP checksum over IPv6, then |
| 1782 |
such xTR implementations <span class="bcp14">MUST</span> meet all the requirements specified |
| 1783 |
in <span><a href="https://www.rfc-editor.org/rfc/rfc6936#section-4" class="relref">Section 4</a> of [<a href="#RFC6936" class="cite xref">RFC6936</a>]</span> and requirement 1 |
| 1784 |
specified in <span><a href="https://www.rfc-editor.org/rfc/rfc6936#section-5" class="relref">Section 5</a> of [<a href="#RFC6936" class="cite xref">RFC6936</a>]</span>.<a href="#section-4.3.1-5.2" class="pilcrow">¶</a> |
| 1785 |
</li> |
| 1786 |
<li id="section-4.3.1-5.3">The Egress Tunnel Router (ETR) that decapsulates the packet <span class="bcp14">SHOULD</span> |
| 1787 |
check that the source |
| 1788 |
and destination IPv6 addresses are valid for the LISP-GPE tunnel |
| 1789 |
that is configured to receive a zero UDP checksum and discard |
| 1790 |
other packets that fail such checks.<a href="#section-4.3.1-5.3" class="pilcrow">¶</a> |
| 1791 |
</li> |
| 1792 |
<li id="section-4.3.1-5.4">The Ingress Tunnel Router (ITR) that encapsulates the packet <span class="bcp14">MAY</span> |
| 1793 |
use different IPv6 |
| 1794 |
source addresses for each LISP-GPE tunnel that uses zero UDP |
| 1795 |
checksum mode in order to strengthen the decapsulator's check of |
| 1796 |
the IPv6 source address (i.e., the same IPv6 source address is not |
| 1797 |
to be used with more than one IPv6 destination address, |
| 1798 |
irrespective of whether that destination address is a unicast or |
| 1799 |
multicast address). When this is not possible, it is <span class="bcp14">RECOMMENDED</span> |
| 1800 |
to use each source address for as few LISP-GPE tunnels that use a |
| 1801 |
zero UDP checksum as is feasible.<a href="#section-4.3.1-5.4" class="pilcrow">¶</a> |
| 1802 |
</li> |
| 1803 |
<li id="section-4.3.1-5.5">Measures <span class="bcp14">SHOULD</span> be taken to prevent LISP-GPE traffic over |
| 1804 |
IPv6 with a zero UDP checksum from escaping into the general |
| 1805 |
Internet. Examples of such measures include employing packet |
| 1806 |
filters at the Proxy Egress Tunnel Router (PETR) and/or keeping logical or physical |
| 1807 |
separation of the LISP network from networks in the general |
| 1808 |
Internet.<a href="#section-4.3.1-5.5" class="pilcrow">¶</a> |
| 1809 |
</li> |
| 1810 |
</ol> |
| 1811 |
<p id="section-4.3.1-6">The above requirements do not change the |
| 1812 |
requirements specified in <span>[<a href="#RFC6935" class="cite xref">RFC6935</a>]</span>, |
| 1813 |
<span>[<a href="#RFC6936" class="cite xref">RFC6936</a>]</span>, or <span>[<a href="#RFC8200" class="cite xref">RFC8200</a>]</span>.<a href="#section-4.3.1-6" class="pilcrow">¶</a></p> |
| 1814 |
<p id="section-4.3.1-7">The requirement to check the source IPv6 address in addition to |
| 1815 |
the destination IPv6 address, plus the recommendation against the reuse |
| 1816 |
of source IPv6 addresses among LISP-GPE tunnels, collectively provide |
| 1817 |
some mitigation for the absence of UDP checksum coverage of the IPv6 |
| 1818 |
header. A traffic-managed controlled environment that satisfies at |
| 1819 |
least one of the three conditions listed at the beginning of this |
| 1820 |
section provides additional assurance.<a href="#section-4.3.1-7" class="pilcrow">¶</a></p> |
| 1821 |
</section> |
| 1822 |
</div> |
| 1823 |
</section> |
| 1824 |
</div> |
| 1825 |
<div id="DSCP"> |
| 1826 |
<section id="section-4.4"> |
| 1827 |
<h3 id="name-dscp-ecn-ttl-and-8021q"> |
| 1828 |
<a href="#section-4.4" class="section-number selfRef">4.4. </a><a href="#name-dscp-ecn-ttl-and-8021q" class="section-name selfRef">DSCP, ECN, TTL, and 802.1Q</a> |
| 1829 |
</h3> |
| 1830 |
<p id="section-4.4-1">When encapsulating IP (including over Ethernet) packets, <span>[<a href="#RFC2983" class="cite xref">RFC2983</a>]</span> provides guidance for mapping packets that contain Differentiated Services Code Point |
| 1831 |
(DSCP) information between inner |
| 1832 |
and outer IP headers. The Pipe model typically fits better with network |
| 1833 |
virtualization. The DSCP value on the tunnel header is set based on a |
| 1834 |
policy (which may be a fixed value, one based on the inner traffic |
| 1835 |
class, or some other mechanism for grouping traffic). Some aspects of |
| 1836 |
the Uniform model (which treats the inner and outer DSCP value as a |
| 1837 |
single field by copying on ingress and egress) may also apply, such as |
| 1838 |
the ability to remark the inner header on tunnel egress based on |
| 1839 |
transit marking. However, the Uniform model is not conceptually |
| 1840 |
consistent with network virtualization, which seeks to provide strong |
| 1841 |
isolation between encapsulated traffic and the physical network.<a href="#section-4.4-1" class="pilcrow">¶</a></p> |
| 1842 |
<p id="section-4.4-2"><span>[<a href="#RFC6040" class="cite xref">RFC6040</a>]</span> describes the mechanism for exposing ECN |
| 1843 |
capabilities on IP tunnels and propagating congestion markers to the |
| 1844 |
inner packets. This behavior <span class="bcp14">MUST</span> be followed for IP packets |
| 1845 |
encapsulated in LISP-GPE.<a href="#section-4.4-2" class="pilcrow">¶</a></p> |
| 1846 |
<p id="section-4.4-3">Though the Uniform model or the Pipe model could be used for TTL (or Hop Limit |
| 1847 |
in the case of IPv6) handling when tunneling IP packets, the Pipe model is |
| 1848 |
more aligned with network virtualization. <span>[<a href="#RFC2003" class="cite xref">RFC2003</a>]</span> |
| 1849 |
provides guidance on handling TTL between inner IP headers and outer IP |
| 1850 |
tunnels; this model is more aligned with the Pipe model and is |
| 1851 |
recommended for use with LISP-GPE for network-virtualization |
| 1852 |
applications.<a href="#section-4.4-3" class="pilcrow">¶</a></p> |
| 1853 |
<p id="section-4.4-4">When a LISP-GPE router performs Ethernet encapsulation, the inner |
| 1854 |
802.1Q 3-bit Priority Code Point |
| 1855 |
('PCP') field <span>[<a href="#IEEE.802.1Q_2014" class="cite xref">IEEE.802.1Q_2014</a>]</span> <span class="bcp14">MAY</span> be mapped from the encapsulated frame to the DSCP |
| 1856 |
codepoint of the Differentiated Services ('DS') field defined in <span>[<a href="#RFC2474" class="cite xref">RFC2474</a>]</span>.<a href="#section-4.4-4" class="pilcrow">¶</a></p> |
| 1857 |
<p id="section-4.4-5">When a LISP-GPE router performs Ethernet encapsulation, the |
| 1858 |
inner-header 802.1Q VLAN Identifier (VID) <span>[<a href="#IEEE.802.1Q_2014" class="cite xref">IEEE.802.1Q_2014</a>]</span> |
| 1859 |
<span class="bcp14">MAY</span> be mapped to, or used to determine, the LISP 'Instance ID' |
| 1860 |
(IID) field.<a href="#section-4.4-5" class="pilcrow">¶</a></p> |
| 1861 |
<p id="section-4.4-6">Refer to <a href="#Security" class="auto internal xref">Section 7</a> for considerations about the use |
| 1862 |
of integrity protection for deployments, such as the public Internet, |
| 1863 |
concerned with on-path attackers.<a href="#section-4.4-6" class="pilcrow">¶</a></p> |
| 1864 |
</section> |
| 1865 |
</div> |
| 1866 |
</section> |
| 1867 |
</div> |
| 1868 |
<div id="Compatibility"> |
| 1869 |
<section id="section-5"> |
| 1870 |
<h2 id="name-backward-compatibility"> |
| 1871 |
<a href="#section-5" class="section-number selfRef">5. </a><a href="#name-backward-compatibility" class="section-name selfRef">Backward Compatibility</a> |
| 1872 |
</h2> |
| 1873 |
<p id="section-5-1">LISP-GPE uses the same UDP destination port (4341) allocated to |
| 1874 |
LISP.<a href="#section-5-1" class="pilcrow">¶</a></p> |
| 1875 |
<p id="section-5-2">When encapsulating IP packets to a non-LISP-GPE-capable router, the |
| 1876 |
P-bit <span class="bcp14">MUST</span> be set to 0. That is, the encapsulation format defined in |
| 1877 |
this document <span class="bcp14">MUST NOT</span> be sent to a router that has not indicated that |
| 1878 |
it supports this specification, because such a router would ignore the |
| 1879 |
P-bit (as described in <span>[<a href="#RFC9300" class="cite xref">RFC9300</a>]</span>) and so |
| 1880 |
would misinterpret the other LISP header fields, possibly causing |
| 1881 |
significant errors.<a href="#section-5-2" class="pilcrow">¶</a></p> |
| 1882 |
<div id="ETR_CAPABILITIES"> |
| 1883 |
<section id="section-5.1"> |
| 1884 |
<h3 id="name-detection-of-etr-capabiliti"> |
| 1885 |
<a href="#section-5.1" class="section-number selfRef">5.1. </a><a href="#name-detection-of-etr-capabiliti" class="section-name selfRef">Detection of ETR Capabilities</a> |
| 1886 |
</h3> |
| 1887 |
<p id="section-5.1-1">The discovery of xTR capabilities to support LISP-GPE is out of the |
| 1888 |
scope of this document. Given that the applicability domain of |
| 1889 |
LISP-GPE is a traffic-managed controlled environment, ITR/ETR (xTR) |
| 1890 |
configuration mechanisms may be used for this purpose.<a href="#section-5.1-1" class="pilcrow">¶</a></p> |
| 1891 |
</section> |
| 1892 |
</div> |
| 1893 |
</section> |
| 1894 |
</div> |
| 1895 |
<div id="IANA"> |
| 1896 |
<section id="section-6"> |
| 1897 |
<h2 id="name-iana-considerations"> |
| 1898 |
<a href="#section-6" class="section-number selfRef">6. </a><a href="#name-iana-considerations" class="section-name selfRef">IANA Considerations</a> |
| 1899 |
</h2> |
| 1900 |
<p id="section-6-1"></p> |
| 1901 |
<div id="Next_protocol"> |
| 1902 |
<section id="section-6.1"> |
| 1903 |
<h3 id="name-lisp-gpe-next-protocol-regi"> |
| 1904 |
<a href="#section-6.1" class="section-number selfRef">6.1. </a><a href="#name-lisp-gpe-next-protocol-regi" class="section-name selfRef">LISP-GPE Next Protocol Registry</a> |
| 1905 |
</h3> |
| 1906 |
<p id="section-6.1-1">IANA has created a registry called "LISP-GPE Next Protocol". |
| 1907 |
These are 8-bit values. Next Protocol values in the table below are |
| 1908 |
defined in this document. New values are assigned under the |
| 1909 |
Specification Required policy <span>[<a href="#RFC8126" class="cite xref">RFC8126</a>]</span>. The protocols |
| 1910 |
that are being assigned values do not themselves need to be IETF |
| 1911 |
Standards Track protocols.<a href="#section-6.1-1" class="pilcrow">¶</a></p> |
| 1912 |
<table class="center" id="table-1"> |
| 1913 |
<caption><a href="#table-1" class="selfRef">Table 1</a></caption> |
| 1914 |
<thead> |
| 1915 |
<tr> |
| 1916 |
<th class="text-left" rowspan="1" colspan="1">Next Protocol</th> |
| 1917 |
<th class="text-left" rowspan="1" colspan="1">Description</th> |
| 1918 |
<th class="text-left" rowspan="1" colspan="1">Reference</th> |
| 1919 |
</tr> |
| 1920 |
</thead> |
| 1921 |
<tbody> |
| 1922 |
<tr> |
| 1923 |
<td class="text-left" rowspan="1" colspan="1">0x00</td> |
| 1924 |
<td class="text-left" rowspan="1" colspan="1">Reserved</td> |
| 1925 |
<td class="text-left" rowspan="1" colspan="1">RFC 9305</td> |
| 1926 |
</tr> |
| 1927 |
<tr> |
| 1928 |
<td class="text-left" rowspan="1" colspan="1">0x01</td> |
| 1929 |
<td class="text-left" rowspan="1" colspan="1">IPv4</td> |
| 1930 |
<td class="text-left" rowspan="1" colspan="1">RFC 9305</td> |
| 1931 |
</tr> |
| 1932 |
<tr> |
| 1933 |
<td class="text-left" rowspan="1" colspan="1">0x02</td> |
| 1934 |
<td class="text-left" rowspan="1" colspan="1">IPv6</td> |
| 1935 |
<td class="text-left" rowspan="1" colspan="1">RFC 9305</td> |
| 1936 |
</tr> |
| 1937 |
<tr> |
| 1938 |
<td class="text-left" rowspan="1" colspan="1">0x03</td> |
| 1939 |
<td class="text-left" rowspan="1" colspan="1">Ethernet</td> |
| 1940 |
<td class="text-left" rowspan="1" colspan="1">RFC 9305</td> |
| 1941 |
</tr> |
| 1942 |
<tr> |
| 1943 |
<td class="text-left" rowspan="1" colspan="1">0x04</td> |
| 1944 |
<td class="text-left" rowspan="1" colspan="1">NSH</td> |
| 1945 |
<td class="text-left" rowspan="1" colspan="1">RFC 9305</td> |
| 1946 |
</tr> |
| 1947 |
<tr> |
| 1948 |
<td class="text-left" rowspan="1" colspan="1">0x05-0x7D</td> |
| 1949 |
<td class="text-left" rowspan="1" colspan="1">Unassigned</td> |
| 1950 |
<td class="text-left" rowspan="1" colspan="1"></td> |
| 1951 |
</tr> |
| 1952 |
<tr> |
| 1953 |
<td class="text-left" rowspan="1" colspan="1">0x7E-0x7F</td> |
| 1954 |
<td class="text-left" rowspan="1" colspan="1">Experimentation and testing</td> |
| 1955 |
<td class="text-left" rowspan="1" colspan="1">RFC 9305</td> |
| 1956 |
</tr> |
| 1957 |
<tr> |
| 1958 |
<td class="text-left" rowspan="1" colspan="1">0x80-0xFD</td> |
| 1959 |
<td class="text-left" rowspan="1" colspan="1">Unassigned (shim headers)</td> |
| 1960 |
<td class="text-left" rowspan="1" colspan="1"></td> |
| 1961 |
</tr> |
| 1962 |
<tr> |
| 1963 |
<td class="text-left" rowspan="1" colspan="1">0xFE-0xFF</td> |
| 1964 |
<td class="text-left" rowspan="1" colspan="1">Experimentation and testing (shim headers)</td> |
| 1965 |
<td class="text-left" rowspan="1" colspan="1">RFC 9305</td> |
| 1966 |
</tr> |
| 1967 |
</tbody> |
| 1968 |
</table> |
| 1969 |
</section> |
| 1970 |
</div> |
| 1971 |
</section> |
| 1972 |
</div> |
| 1973 |
<div id="Security"> |
| 1974 |
<section id="section-7"> |
| 1975 |
<h2 id="name-security-considerations"> |
| 1976 |
<a href="#section-7" class="section-number selfRef">7. </a><a href="#name-security-considerations" class="section-name selfRef">Security Considerations</a> |
| 1977 |
</h2> |
| 1978 |
<p id="section-7-1">LISP-GPE security considerations are similar to the LISP security |
| 1979 |
considerations and mitigation techniques documented in <span>[<a href="#RFC7835" class="cite xref">RFC7835</a>]</span>.<a href="#section-7-1" class="pilcrow">¶</a></p> |
| 1980 |
<p id="section-7-2">As is the case for many encapsulations that use optional extensions, LISP-GPE is |
| 1981 |
subject to on-path adversaries that can make arbitrary modifications to |
| 1982 |
the packet (including the P-bit) to change or remove any part of the |
| 1983 |
payload, or claim to encapsulate any protocol payload type. Typical |
| 1984 |
integrity protection mechanisms (such as IPsec) <span class="bcp14">SHOULD</span> be used in |
| 1985 |
combination with LISP-GPE by those protocol extensions that want to |
| 1986 |
protect against on-path attackers.<a href="#section-7-2" class="pilcrow">¶</a></p> |
| 1987 |
<p id="section-7-3">With LISP-GPE, issues such as data plane spoofing, flooding, and |
| 1988 |
traffic redirection may depend on the particular protocol payload |
| 1989 |
encapsulated.<a href="#section-7-3" class="pilcrow">¶</a></p> |
| 1990 |
</section> |
| 1991 |
</div> |
| 1992 |
<section id="section-8"> |
| 1993 |
<h2 id="name-references"> |
| 1994 |
<a href="#section-8" class="section-number selfRef">8. </a><a href="#name-references" class="section-name selfRef">References</a> |
| 1995 |
</h2> |
| 1996 |
<section id="section-8.1"> |
| 1997 |
<h3 id="name-normative-references"> |
| 1998 |
<a href="#section-8.1" class="section-number selfRef">8.1. </a><a href="#name-normative-references" class="section-name selfRef">Normative References</a> |
| 1999 |
</h3> |
| 2000 |
<dl class="references"> |
| 2001 |
<dt id="IEEE.802.1Q_2014">[IEEE.802.1Q_2014]</dt> |
| 2002 |
<dd> |
| 2003 |
<span class="refAuthor">IEEE</span>, <span class="refTitle">"IEEE Standard for Local and metropolitan area networks--Bridges and Bridged Networks"</span>, <span class="refContent">IEEE Std 802.1Q-2014</span>, <time datetime="2014-12" class="refDate">December 2014</time>, <span><<a href="https://ieeexplore.ieee.org/document/6991462">https://ieeexplore.ieee.org/document/6991462</a>></span>. </dd> |
| 2004 |
<dd class="break"></dd> |
| 2005 |
<dt id="RFC2119">[RFC2119]</dt> |
| 2006 |
<dd> |
| 2007 |
<span class="refAuthor">Bradner, S.</span>, <span class="refTitle">"Key words for use in RFCs to Indicate Requirement Levels"</span>, <span class="seriesInfo">BCP 14</span>, <span class="seriesInfo">RFC 2119</span>, <span class="seriesInfo">DOI 10.17487/RFC2119</span>, <time datetime="1997-03" class="refDate">March 1997</time>, <span><<a href="https://www.rfc-editor.org/info/rfc2119">https://www.rfc-editor.org/info/rfc2119</a>></span>. </dd> |
| 2008 |
<dd class="break"></dd> |
| 2009 |
<dt id="RFC6040">[RFC6040]</dt> |
| 2010 |
<dd> |
| 2011 |
<span class="refAuthor">Briscoe, B.</span>, <span class="refTitle">"Tunnelling of Explicit Congestion Notification"</span>, <span class="seriesInfo">RFC 6040</span>, <span class="seriesInfo">DOI 10.17487/RFC6040</span>, <time datetime="2010-11" class="refDate">November 2010</time>, <span><<a href="https://www.rfc-editor.org/info/rfc6040">https://www.rfc-editor.org/info/rfc6040</a>></span>. </dd> |
| 2012 |
<dd class="break"></dd> |
| 2013 |
<dt id="RFC8174">[RFC8174]</dt> |
| 2014 |
<dd> |
| 2015 |
<span class="refAuthor">Leiba, B.</span>, <span class="refTitle">"Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words"</span>, <span class="seriesInfo">BCP 14</span>, <span class="seriesInfo">RFC 8174</span>, <span class="seriesInfo">DOI 10.17487/RFC8174</span>, <time datetime="2017-05" class="refDate">May 2017</time>, <span><<a href="https://www.rfc-editor.org/info/rfc8174">https://www.rfc-editor.org/info/rfc8174</a>></span>. </dd> |
| 2016 |
<dd class="break"></dd> |
| 2017 |
<dt id="RFC9300">[RFC9300]</dt> |
| 2018 |
<dd> |
| 2019 |
<span class="refAuthor">Farinacci, D.</span>, <span class="refAuthor">Fuller, V.</span>, <span class="refAuthor">Meyer, D.</span>, <span class="refAuthor">Lewis, D.</span>, and <span class="refAuthor">A. Cabellos, Ed.</span>, <span class="refTitle">"The Locator/ID Separation Protocol (LISP)"</span>, <span class="seriesInfo">RFC 9300</span>, <span class="seriesInfo">DOI 10.17487/RFC9300</span>, <time datetime="2022-10" class="refDate">October 2022</time>, <span><<a href="https://www.rfc-editor.org/info/rfc9300">https://www.rfc-editor.org/info/rfc9300</a>></span>. </dd> |
| 2020 |
<dd class="break"></dd> |
| 2021 |
</dl> |
| 2022 |
</section> |
| 2023 |
<section id="section-8.2"> |
| 2024 |
<h3 id="name-informative-references"> |
| 2025 |
<a href="#section-8.2" class="section-number selfRef">8.2. </a><a href="#name-informative-references" class="section-name selfRef">Informative References</a> |
| 2026 |
</h3> |
| 2027 |
<dl class="references"> |
| 2028 |
<dt id="I-D.ietf-tsvwg-ecn-encap-guidelines">[ENCAP-GUIDE]</dt> |
| 2029 |
<dd> |
| 2030 |
<span class="refAuthor">Briscoe, B.</span> and <span class="refAuthor">J. Kaippallimalil</span>, <span class="refTitle">"Guidelines for Adding Congestion Notification to Protocols that Encapsulate IP"</span>, <span class="refContent">Work in Progress</span>, <span class="seriesInfo">Internet-Draft, draft-ietf-tsvwg-ecn-encap-guidelines-17</span>, <time datetime="2022-07-11" class="refDate">11 July 2022</time>, <span><<a href="https://datatracker.ietf.org/doc/html/draft-ietf-tsvwg-ecn-encap-guidelines-17">https://datatracker.ietf.org/doc/html/draft-ietf-tsvwg-ecn-encap-guidelines-17</a>></span>. </dd> |
| 2031 |
<dd class="break"></dd> |
| 2032 |
<dt id="RFC2003">[RFC2003]</dt> |
| 2033 |
<dd> |
| 2034 |
<span class="refAuthor">Perkins, C.</span>, <span class="refTitle">"IP Encapsulation within IP"</span>, <span class="seriesInfo">RFC 2003</span>, <span class="seriesInfo">DOI 10.17487/RFC2003</span>, <time datetime="1996-10" class="refDate">October 1996</time>, <span><<a href="https://www.rfc-editor.org/info/rfc2003">https://www.rfc-editor.org/info/rfc2003</a>></span>. </dd> |
| 2035 |
<dd class="break"></dd> |
| 2036 |
<dt id="RFC2474">[RFC2474]</dt> |
| 2037 |
<dd> |
| 2038 |
<span class="refAuthor">Nichols, K.</span>, <span class="refAuthor">Blake, S.</span>, <span class="refAuthor">Baker, F.</span>, and <span class="refAuthor">D. Black</span>, <span class="refTitle">"Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers"</span>, <span class="seriesInfo">RFC 2474</span>, <span class="seriesInfo">DOI 10.17487/RFC2474</span>, <time datetime="1998-12" class="refDate">December 1998</time>, <span><<a href="https://www.rfc-editor.org/info/rfc2474">https://www.rfc-editor.org/info/rfc2474</a>></span>. </dd> |
| 2039 |
<dd class="break"></dd> |
| 2040 |
<dt id="RFC2983">[RFC2983]</dt> |
| 2041 |
<dd> |
| 2042 |
<span class="refAuthor">Black, D.</span>, <span class="refTitle">"Differentiated Services and Tunnels"</span>, <span class="seriesInfo">RFC 2983</span>, <span class="seriesInfo">DOI 10.17487/RFC2983</span>, <time datetime="2000-10" class="refDate">October 2000</time>, <span><<a href="https://www.rfc-editor.org/info/rfc2983">https://www.rfc-editor.org/info/rfc2983</a>></span>. </dd> |
| 2043 |
<dd class="break"></dd> |
| 2044 |
<dt id="RFC3168">[RFC3168]</dt> |
| 2045 |
<dd> |
| 2046 |
<span class="refAuthor">Ramakrishnan, K.</span>, <span class="refAuthor">Floyd, S.</span>, and <span class="refAuthor">D. Black</span>, <span class="refTitle">"The Addition of Explicit Congestion Notification (ECN) to IP"</span>, <span class="seriesInfo">RFC 3168</span>, <span class="seriesInfo">DOI 10.17487/RFC3168</span>, <time datetime="2001-09" class="refDate">September 2001</time>, <span><<a href="https://www.rfc-editor.org/info/rfc3168">https://www.rfc-editor.org/info/rfc3168</a>></span>. </dd> |
| 2047 |
<dd class="break"></dd> |
| 2048 |
<dt id="RFC3692">[RFC3692]</dt> |
| 2049 |
<dd> |
| 2050 |
<span class="refAuthor">Narten, T.</span>, <span class="refTitle">"Assigning Experimental and Testing Numbers Considered Useful"</span>, <span class="seriesInfo">BCP 82</span>, <span class="seriesInfo">RFC 3692</span>, <span class="seriesInfo">DOI 10.17487/RFC3692</span>, <time datetime="2004-01" class="refDate">January 2004</time>, <span><<a href="https://www.rfc-editor.org/info/rfc3692">https://www.rfc-editor.org/info/rfc3692</a>></span>. </dd> |
| 2051 |
<dd class="break"></dd> |
| 2052 |
<dt id="RFC6935">[RFC6935]</dt> |
| 2053 |
<dd> |
| 2054 |
<span class="refAuthor">Eubanks, M.</span>, <span class="refAuthor">Chimento, P.</span>, and <span class="refAuthor">M. Westerlund</span>, <span class="refTitle">"IPv6 and UDP Checksums for Tunneled Packets"</span>, <span class="seriesInfo">RFC 6935</span>, <span class="seriesInfo">DOI 10.17487/RFC6935</span>, <time datetime="2013-04" class="refDate">April 2013</time>, <span><<a href="https://www.rfc-editor.org/info/rfc6935">https://www.rfc-editor.org/info/rfc6935</a>></span>. </dd> |
| 2055 |
<dd class="break"></dd> |
| 2056 |
<dt id="RFC6936">[RFC6936]</dt> |
| 2057 |
<dd> |
| 2058 |
<span class="refAuthor">Fairhurst, G.</span> and <span class="refAuthor">M. Westerlund</span>, <span class="refTitle">"Applicability Statement for the Use of IPv6 UDP Datagrams with Zero Checksums"</span>, <span class="seriesInfo">RFC 6936</span>, <span class="seriesInfo">DOI 10.17487/RFC6936</span>, <time datetime="2013-04" class="refDate">April 2013</time>, <span><<a href="https://www.rfc-editor.org/info/rfc6936">https://www.rfc-editor.org/info/rfc6936</a>></span>. </dd> |
| 2059 |
<dd class="break"></dd> |
| 2060 |
<dt id="RFC7348">[RFC7348]</dt> |
| 2061 |
<dd> |
| 2062 |
<span class="refAuthor">Mahalingam, M.</span>, <span class="refAuthor">Dutt, D.</span>, <span class="refAuthor">Duda, K.</span>, <span class="refAuthor">Agarwal, P.</span>, <span class="refAuthor">Kreeger, L.</span>, <span class="refAuthor">Sridhar, T.</span>, <span class="refAuthor">Bursell, M.</span>, and <span class="refAuthor">C. Wright</span>, <span class="refTitle">"Virtual eXtensible Local Area Network (VXLAN): A Framework for Overlaying Virtualized Layer 2 Networks over Layer 3 Networks"</span>, <span class="seriesInfo">RFC 7348</span>, <span class="seriesInfo">DOI 10.17487/RFC7348</span>, <time datetime="2014-08" class="refDate">August 2014</time>, <span><<a href="https://www.rfc-editor.org/info/rfc7348">https://www.rfc-editor.org/info/rfc7348</a>></span>. </dd> |
| 2063 |
<dd class="break"></dd> |
| 2064 |
<dt id="RFC7835">[RFC7835]</dt> |
| 2065 |
<dd> |
| 2066 |
<span class="refAuthor">Saucez, D.</span>, <span class="refAuthor">Iannone, L.</span>, and <span class="refAuthor">O. Bonaventure</span>, <span class="refTitle">"Locator/ID Separation Protocol (LISP) Threat Analysis"</span>, <span class="seriesInfo">RFC 7835</span>, <span class="seriesInfo">DOI 10.17487/RFC7835</span>, <time datetime="2016-04" class="refDate">April 2016</time>, <span><<a href="https://www.rfc-editor.org/info/rfc7835">https://www.rfc-editor.org/info/rfc7835</a>></span>. </dd> |
| 2067 |
<dd class="break"></dd> |
| 2068 |
<dt id="RFC8085">[RFC8085]</dt> |
| 2069 |
<dd> |
| 2070 |
<span class="refAuthor">Eggert, L.</span>, <span class="refAuthor">Fairhurst, G.</span>, and <span class="refAuthor">G. Shepherd</span>, <span class="refTitle">"UDP Usage Guidelines"</span>, <span class="seriesInfo">BCP 145</span>, <span class="seriesInfo">RFC 8085</span>, <span class="seriesInfo">DOI 10.17487/RFC8085</span>, <time datetime="2017-03" class="refDate">March 2017</time>, <span><<a href="https://www.rfc-editor.org/info/rfc8085">https://www.rfc-editor.org/info/rfc8085</a>></span>. </dd> |
| 2071 |
<dd class="break"></dd> |
| 2072 |
<dt id="RFC8086">[RFC8086]</dt> |
| 2073 |
<dd> |
| 2074 |
<span class="refAuthor">Yong, L., Ed.</span>, <span class="refAuthor">Crabbe, E.</span>, <span class="refAuthor">Xu, X.</span>, and <span class="refAuthor">T. Herbert</span>, <span class="refTitle">"GRE-in-UDP Encapsulation"</span>, <span class="seriesInfo">RFC 8086</span>, <span class="seriesInfo">DOI 10.17487/RFC8086</span>, <time datetime="2017-03" class="refDate">March 2017</time>, <span><<a href="https://www.rfc-editor.org/info/rfc8086">https://www.rfc-editor.org/info/rfc8086</a>></span>. </dd> |
| 2075 |
<dd class="break"></dd> |
| 2076 |
<dt id="RFC8126">[RFC8126]</dt> |
| 2077 |
<dd> |
| 2078 |
<span class="refAuthor">Cotton, M.</span>, <span class="refAuthor">Leiba, B.</span>, and <span class="refAuthor">T. Narten</span>, <span class="refTitle">"Guidelines for Writing an IANA Considerations Section in RFCs"</span>, <span class="seriesInfo">BCP 26</span>, <span class="seriesInfo">RFC 8126</span>, <span class="seriesInfo">DOI 10.17487/RFC8126</span>, <time datetime="2017-06" class="refDate">June 2017</time>, <span><<a href="https://www.rfc-editor.org/info/rfc8126">https://www.rfc-editor.org/info/rfc8126</a>></span>. </dd> |
| 2079 |
<dd class="break"></dd> |
| 2080 |
<dt id="RFC8200">[RFC8200]</dt> |
| 2081 |
<dd> |
| 2082 |
<span class="refAuthor">Deering, S.</span> and <span class="refAuthor">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" class="refDate">July 2017</time>, <span><<a href="https://www.rfc-editor.org/info/rfc8200">https://www.rfc-editor.org/info/rfc8200</a>></span>. </dd> |
| 2083 |
<dd class="break"></dd> |
| 2084 |
<dt id="RFC8300">[RFC8300]</dt> |
| 2085 |
<dd> |
| 2086 |
<span class="refAuthor">Quinn, P., Ed.</span>, <span class="refAuthor">Elzur, U., Ed.</span>, and <span class="refAuthor">C. Pignataro, Ed.</span>, <span class="refTitle">"Network Service Header (NSH)"</span>, <span class="seriesInfo">RFC 8300</span>, <span class="seriesInfo">DOI 10.17487/RFC8300</span>, <time datetime="2018-01" class="refDate">January 2018</time>, <span><<a href="https://www.rfc-editor.org/info/rfc8300">https://www.rfc-editor.org/info/rfc8300</a>></span>. </dd> |
| 2087 |
<dd class="break"></dd> |
| 2088 |
<dt id="VXLAN-GPE">[VXLAN-GPE]</dt> |
| 2089 |
<dd> |
| 2090 |
<span class="refAuthor">Brockners, F.</span>, <span class="refAuthor">Bhandari, S.</span>, <span class="refAuthor">Govindan, V.</span>, <span class="refAuthor">Pignataro, C.</span>, <span class="refAuthor">Gredler, H.</span>, <span class="refAuthor">Leddy, J.</span>, <span class="refAuthor">Youell, S.</span>, <span class="refAuthor">Mizrahi, T.</span>, <span class="refAuthor">Kfir, A.</span>, <span class="refAuthor">Gafni, B.</span>, <span class="refAuthor">Lapukhov, P.</span>, and <span class="refAuthor">M. Spiegel</span>, <span class="refTitle">"VXLAN-GPE Encapsulation for In-situ OAM Data"</span>, <span class="refContent">Work in Progress</span>, <span class="seriesInfo">Internet-Draft, draft-brockners-ippm-ioam-vxlan-gpe-03</span>, <time datetime="2019-11-04" class="refDate">4 November 2019</time>, <span><<a href="https://datatracker.ietf.org/doc/html/draft-brockners-ippm-ioam-vxlan-gpe-03">https://datatracker.ietf.org/doc/html/draft-brockners-ippm-ioam-vxlan-gpe-03</a>></span>. </dd> |
| 2091 |
<dd class="break"></dd> |
| 2092 |
<dt id="VXLAN-LISP">[VXLAN-LISP]</dt> |
| 2093 |
<dd> |
| 2094 |
<span class="refAuthor">Lemon, J., Ed.</span>, <span class="refAuthor">Maino, F.</span>, <span class="refAuthor">Smith, M.</span>, and <span class="refAuthor">A. Isaac</span>, <span class="refTitle">"Group Policy Encoding with VXLAN-GPE and LISP-GPE"</span>, <span class="refContent">Work in Progress</span>, <span class="seriesInfo">Internet-Draft, draft-lemon-vxlan-lisp-gpe-gbp-02</span>, <time datetime="2019-04-30" class="refDate">30 April 2019</time>, <span><<a href="https://datatracker.ietf.org/doc/html/draft-lemon-vxlan-lisp-gpe-gbp-02">https://datatracker.ietf.org/doc/html/draft-lemon-vxlan-lisp-gpe-gbp-02</a>></span>. </dd> |
| 2095 |
<dd class="break"></dd> |
| 2096 |
</dl> |
| 2097 |
</section> |
| 2098 |
</section> |
| 2099 |
<div id="Acknowledgments"> |
| 2100 |
<section id="appendix-A"> |
| 2101 |
<h2 id="name-acknowledgments"> |
| 2102 |
<a href="#name-acknowledgments" class="section-name selfRef">Acknowledgments</a> |
| 2103 |
</h2> |
| 2104 |
<p id="appendix-A-1">A special thank you goes to <span class="contact-name">Dino Farinacci</span> for his guidance and |
| 2105 |
detailed review. Thanks to <span class="contact-name">Tom Herbert</span> for the suggestion to assign |
| 2106 |
codepoints for experimentations and testing.<a href="#appendix-A-1" class="pilcrow">¶</a></p> |
| 2107 |
</section> |
| 2108 |
</div> |
| 2109 |
<div id="Contributors"> |
| 2110 |
<section id="appendix-B"> |
| 2111 |
<h2 id="name-contributors"> |
| 2112 |
<a href="#name-contributors" class="section-name selfRef">Contributors</a> |
| 2113 |
</h2> |
| 2114 |
<p id="appendix-B-1">The editor of this document would like to thank and recognize the |
| 2115 |
following coauthors and contributors for their contributions. These |
| 2116 |
coauthors and contributors provided invaluable concepts and content |
| 2117 |
for this document's creation.<a href="#appendix-B-1" class="pilcrow">¶</a></p> |
| 2118 |
<address class="vcard"> |
| 2119 |
<div dir="auto" class="left"><span class="fn nameRole">Darrel Lewis</span></div> |
| 2120 |
<div dir="auto" class="left"><span class="org">Cisco Systems, Inc.</span></div> |
| 2121 |
</address> |
| 2122 |
<address class="vcard"> |
| 2123 |
<div dir="auto" class="left"><span class="fn nameRole">Fabio Maino</span></div> |
| 2124 |
<div dir="auto" class="left"><span class="org">Cisco Systems, Inc.</span></div> |
| 2125 |
</address> |
| 2126 |
<address class="vcard"> |
| 2127 |
<div dir="auto" class="left"><span class="fn nameRole">Paul Quinn</span></div> |
| 2128 |
<div dir="auto" class="left"><span class="org">Cisco Systems, Inc.</span></div> |
| 2129 |
</address> |
| 2130 |
<address class="vcard"> |
| 2131 |
<div dir="auto" class="left"><span class="fn nameRole">Michael Smith</span></div> |
| 2132 |
<div dir="auto" class="left"><span class="org">Cisco Systems, Inc.</span></div> |
| 2133 |
</address> |
| 2134 |
<address class="vcard"> |
| 2135 |
<div dir="auto" class="left"><span class="fn nameRole">Navindra Yadav</span></div> |
| 2136 |
<div dir="auto" class="left"><span class="org">Cisco Systems, Inc.</span></div> |
| 2137 |
</address> |
| 2138 |
<address class="vcard"> |
| 2139 |
<div dir="auto" class="left"><span class="fn nameRole">Larry Kreeger</span></div> |
| 2140 |
</address> |
| 2141 |
<address class="vcard"> |
| 2142 |
<div dir="auto" class="left"><span class="fn nameRole">Jennifer Lemon</span></div> |
| 2143 |
<div dir="auto" class="left"><span class="org">Broadcom</span></div> |
| 2144 |
</address> |
| 2145 |
<address class="vcard"> |
| 2146 |
<div dir="auto" class="left"><span class="fn nameRole">Puneet Agarwal</span></div> |
| 2147 |
<div dir="auto" class="left"><span class="org">Innovium</span></div> |
| 2148 |
</address> |
| 2149 |
</section> |
| 2150 |
</div> |
| 2151 |
<div id="authors-addresses"> |
| 2152 |
<section id="appendix-C"> |
| 2153 |
<h2 id="name-authors-addresses"> |
| 2154 |
<a href="#name-authors-addresses" class="section-name selfRef">Authors' Addresses</a> |
| 2155 |
</h2> |
| 2156 |
<address class="vcard"> |
| 2157 |
<div dir="auto" class="left"><span class="fn nameRole">Fabio Maino (<span class="role">editor</span>)</span></div> |
| 2158 |
<div dir="auto" class="left"><span class="org">Cisco Systems</span></div> |
| 2159 |
<div dir="auto" class="left"> |
| 2160 |
<span class="locality">San Jose</span>, <span class="region">CA</span> </div> |
| 2161 |
<div dir="auto" class="left"><span class="country-name">United States of America</span></div> |
| 2162 |
<div class="email"> |
| 2163 |
<span>Email:</span> |
| 2164 |
<a href="mailto:[email protected]" class="email">[email protected]</a> |
| 2165 |
</div> |
| 2166 |
</address> |
| 2167 |
<address class="vcard"> |
| 2168 |
<div dir="auto" class="left"><span class="fn nameRole">Jennifer Lemon</span></div> |
| 2169 |
<div class="email"> |
| 2170 |
<span>Email:</span> |
| 2171 |
<a href="mailto:[email protected]" class="email">[email protected]</a> |
| 2172 |
</div> |
| 2173 |
</address> |
| 2174 |
<address class="vcard"> |
| 2175 |
<div dir="auto" class="left"><span class="fn nameRole">Puneet Agarwal</span></div> |
| 2176 |
<div dir="auto" class="left"><span class="org">Innovium</span></div> |
| 2177 |
<div dir="auto" class="left"><span class="country-name">United States of America</span></div> |
| 2178 |
<div class="email"> |
| 2179 |
<span>Email:</span> |
| 2180 |
<a href="mailto:[email protected]" class="email">[email protected]</a> |
| 2181 |
</div> |
| 2182 |
</address> |
| 2183 |
<address class="vcard"> |
| 2184 |
<div dir="auto" class="left"><span class="fn nameRole">Darrel Lewis</span></div> |
| 2185 |
<div dir="auto" class="left"><span class="org">Cisco Systems</span></div> |
| 2186 |
<div dir="auto" class="left"> |
| 2187 |
<span class="locality">San Jose</span>, <span class="region">CA</span> </div> |
| 2188 |
<div dir="auto" class="left"><span class="country-name">United States of America</span></div> |
| 2189 |
<div class="email"> |
| 2190 |
<span>Email:</span> |
| 2191 |
<a href="mailto:[email protected]" class="email">[email protected]</a> |
| 2192 |
</div> |
| 2193 |
</address> |
| 2194 |
<address class="vcard"> |
| 2195 |
<div dir="auto" class="left"><span class="fn nameRole">Michael Smith</span></div> |
| 2196 |
<div dir="auto" class="left"><span class="org">Cisco Systems</span></div> |
| 2197 |
<div dir="auto" class="left"> |
| 2198 |
<span class="locality">San Jose</span>, <span class="region">CA</span> <span class="postal-code">95134</span> |
| 2199 |
</div> |
| 2200 |
<div dir="auto" class="left"><span class="country-name">United States of America</span></div> |
| 2201 |
<div class="email"> |
| 2202 |
<span>Email:</span> |
| 2203 |
<a href="mailto:[email protected]" class="email">[email protected]</a> |
| 2204 |
</div> |
| 2205 |
</address> |
| 2206 |
</section> |
| 2207 |
</div> |
| 2208 |
<script>const toc = document.getElementById("toc"); |
| 2209 |
toc.querySelector("h2").addEventListener("click", e => { |
| 2210 |
toc.classList.toggle("active"); |
| 2211 |
}); |
| 2212 |
toc.querySelector("nav").addEventListener("click", e => { |
| 2213 |
toc.classList.remove("active"); |
| 2214 |
}); |
| 2215 |
</script> |
| 2216 |
</body> |
| 2217 |
</html> |