| 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 8661: Segment Routing MPLS Interworking with LDP</title> |
| 8 |
<meta content="Ahmed Bashandy" name="author"> |
| 9 |
<meta content="Clarence Filsfils" name="author"> |
| 10 |
<meta content="Stefano Previdi" name="author"> |
| 11 |
<meta content="Bruno Decraene" name="author"> |
| 12 |
<meta content="Stephane Litkowski" name="author"> |
| 13 |
<meta content=" |
| 14 |
A Segment Routing (SR) node steers a packet through a controlled set |
| 15 |
of instructions, called segments, by prepending the packet with an SR |
| 16 |
header. A segment can represent any instruction, topological or |
| 17 |
service based. SR allows enforcing a flow through any topological path |
| 18 |
while maintaining per-flow state only at the ingress node to the SR |
| 19 |
domain. |
| 20 |
The Segment Routing architecture can be directly applied to the MPLS |
| 21 |
data plane with no change in the forwarding plane. This document |
| 22 |
describes how Segment Routing MPLS operates in a network where LDP is |
| 23 |
deployed and in the case where SR-capable and non-SR-capable nodes |
| 24 |
coexist. |
| 25 |
" name="description"> |
| 26 |
<meta content="xml2rfc 2.35.0" name="generator"> |
| 27 |
<meta content="SR-MPLS" name="keyword"> |
| 28 |
<meta content="8661" name="rfc.number"> |
| 29 |
<link href="rfc8661.xml" type="application/rfc+xml" rel="alternate"> |
| 30 |
<link href="#copyright" rel="license"> |
| 31 |
<style type="text/css">/* |
| 32 |
|
| 33 |
NOTE: Changes at the bottom of this file overrides some earlier settings. |
| 34 |
|
| 35 |
Once the style has stabilized and has been adopted as an official RFC style, |
| 36 |
this can be consolidated so that style settings occur only in one place, but |
| 37 |
for now the contents of this file consists first of the initial CSS work as |
| 38 |
provided to the RFC Formatter (xml2rfc) work, followed by itemized and |
| 39 |
commented changes found necssary during the development of the v3 |
| 40 |
formatters. |
| 41 |
|
| 42 |
*/ |
| 43 |
|
| 44 |
/* fonts */ |
| 45 |
@import url('https://fonts.googleapis.com/css?family=Noto+Sans'); /* Sans-serif */ |
| 46 |
@import url('https://fonts.googleapis.com/css?family=Noto+Serif'); /* Serif (print) */ |
| 47 |
@import url('https://fonts.googleapis.com/css?family=Roboto+Mono'); /* Monospace */ |
| 48 |
|
| 49 |
@viewport { |
| 50 |
zoom: 1.0; |
| 51 |
width: extend-to-zoom; |
| 52 |
} |
| 53 |
@-ms-viewport { |
| 54 |
width: extend-to-zoom; |
| 55 |
zoom: 1.0; |
| 56 |
} |
| 57 |
/* general and mobile first */ |
| 58 |
html { |
| 59 |
} |
| 60 |
body { |
| 61 |
max-width: 90%; |
| 62 |
margin: 1.5em auto; |
| 63 |
color: #222; |
| 64 |
background-color: #fff; |
| 65 |
font-size: 14px; |
| 66 |
font-family: 'Noto Sans', Arial, Helvetica, sans-serif; |
| 67 |
line-height: 1.6; |
| 68 |
scroll-behavior: smooth; |
| 69 |
} |
| 70 |
.ears { |
| 71 |
display: none; |
| 72 |
} |
| 73 |
|
| 74 |
/* headings */ |
| 75 |
#title, h1, h2, h3, h4, h5, h6 { |
| 76 |
margin: 1em 0 0.5em; |
| 77 |
font-weight: bold; |
| 78 |
line-height: 1.3; |
| 79 |
} |
| 80 |
#title { |
| 81 |
clear: both; |
| 82 |
border-bottom: 1px solid #ddd; |
| 83 |
margin: 0 0 0.5em 0; |
| 84 |
padding: 1em 0 0.5em; |
| 85 |
} |
| 86 |
.author { |
| 87 |
padding-bottom: 4px; |
| 88 |
} |
| 89 |
h1 { |
| 90 |
font-size: 26px; |
| 91 |
margin: 1em 0; |
| 92 |
} |
| 93 |
h2 { |
| 94 |
font-size: 22px; |
| 95 |
margin-top: -20px; /* provide offset for in-page anchors */ |
| 96 |
padding-top: 33px; |
| 97 |
} |
| 98 |
h3 { |
| 99 |
font-size: 18px; |
| 100 |
margin-top: -36px; /* provide offset for in-page anchors */ |
| 101 |
padding-top: 42px; |
| 102 |
} |
| 103 |
h4 { |
| 104 |
font-size: 16px; |
| 105 |
margin-top: -36px; /* provide offset for in-page anchors */ |
| 106 |
padding-top: 42px; |
| 107 |
} |
| 108 |
h5, h6 { |
| 109 |
font-size: 14px; |
| 110 |
} |
| 111 |
#n-copyright-notice { |
| 112 |
border-bottom: 1px solid #ddd; |
| 113 |
padding-bottom: 1em; |
| 114 |
margin-bottom: 1em; |
| 115 |
} |
| 116 |
/* general structure */ |
| 117 |
p { |
| 118 |
padding: 0; |
| 119 |
margin: 0 0 1em 0; |
| 120 |
text-align: left; |
| 121 |
} |
| 122 |
div, span { |
| 123 |
position: relative; |
| 124 |
} |
| 125 |
div { |
| 126 |
margin: 0; |
| 127 |
} |
| 128 |
.alignRight.art-text { |
| 129 |
background-color: #f9f9f9; |
| 130 |
border: 1px solid #eee; |
| 131 |
border-radius: 3px; |
| 132 |
padding: 1em 1em 0; |
| 133 |
margin-bottom: 1.5em; |
| 134 |
} |
| 135 |
.alignRight.art-text pre { |
| 136 |
padding: 0; |
| 137 |
} |
| 138 |
.alignRight { |
| 139 |
margin: 1em 0; |
| 140 |
} |
| 141 |
.alignRight > *:first-child { |
| 142 |
border: none; |
| 143 |
margin: 0; |
| 144 |
float: right; |
| 145 |
clear: both; |
| 146 |
} |
| 147 |
.alignRight > *:nth-child(2) { |
| 148 |
clear: both; |
| 149 |
display: block; |
| 150 |
border: none; |
| 151 |
} |
| 152 |
svg { |
| 153 |
display: block; |
| 154 |
} |
| 155 |
.alignCenter.art-text { |
| 156 |
background-color: #f9f9f9; |
| 157 |
border: 1px solid #eee; |
| 158 |
border-radius: 3px; |
| 159 |
padding: 1em 1em 0; |
| 160 |
margin-bottom: 1.5em; |
| 161 |
} |
| 162 |
.alignCenter.art-text pre { |
| 163 |
padding: 0; |
| 164 |
} |
| 165 |
.alignCenter { |
| 166 |
margin: 1em 0; |
| 167 |
} |
| 168 |
.alignCenter > *:first-child { |
| 169 |
border: none; |
| 170 |
/* this isn't optimal, but it's an existence proof. PrinceXML doesn't |
| 171 |
support flexbox yet. |
| 172 |
*/ |
| 173 |
display: table; |
| 174 |
margin: 0 auto; |
| 175 |
} |
| 176 |
|
| 177 |
/* lists */ |
| 178 |
ol, ul { |
| 179 |
padding: 0; |
| 180 |
margin: 0 0 1em 2em; |
| 181 |
} |
| 182 |
ol ol, ul ul, ol ul, ul ol { |
| 183 |
margin-left: 1em; |
| 184 |
} |
| 185 |
li { |
| 186 |
margin: 0 0 0.25em 0; |
| 187 |
} |
| 188 |
.ulCompact li { |
| 189 |
margin: 0; |
| 190 |
} |
| 191 |
ul.empty, .ulEmpty { |
| 192 |
list-style-type: none; |
| 193 |
} |
| 194 |
ul.empty li, .ulEmpty li { |
| 195 |
margin-top: 0.5em; |
| 196 |
} |
| 197 |
ul.compact, .ulCompact, |
| 198 |
ol.compact, .olCompact { |
| 199 |
line-height: 100%; |
| 200 |
margin: 0 0 0 2em; |
| 201 |
} |
| 202 |
|
| 203 |
/* definition lists */ |
| 204 |
dl { |
| 205 |
} |
| 206 |
dl > dt { |
| 207 |
float: left; |
| 208 |
margin-right: 1em; |
| 209 |
} |
| 210 |
/* |
| 211 |
dl.nohang > dt { |
| 212 |
float: none; |
| 213 |
} |
| 214 |
*/ |
| 215 |
dl > dd { |
| 216 |
margin-bottom: .8em; |
| 217 |
min-height: 1.3em; |
| 218 |
} |
| 219 |
dl.compact > dd, .dlCompact > dd { |
| 220 |
margin-bottom: 0em; |
| 221 |
} |
| 222 |
dl > dd > dl { |
| 223 |
margin-top: 0.5em; |
| 224 |
margin-bottom: 0em; |
| 225 |
} |
| 226 |
|
| 227 |
/* links */ |
| 228 |
a { |
| 229 |
text-decoration: none; |
| 230 |
} |
| 231 |
a[href] { |
| 232 |
color: #22e; /* Arlen: WCAG 2019 */ |
| 233 |
} |
| 234 |
a[href]:hover { |
| 235 |
background-color: #f2f2f2; |
| 236 |
} |
| 237 |
figcaption a[href], |
| 238 |
a[href].selfRef { |
| 239 |
color: #222; |
| 240 |
} |
| 241 |
/* XXX probably not this: |
| 242 |
a.selfRef:hover { |
| 243 |
background-color: transparent; |
| 244 |
cursor: default; |
| 245 |
} */ |
| 246 |
|
| 247 |
/* Figures */ |
| 248 |
tt, code, pre, code { |
| 249 |
background-color: #f9f9f9; |
| 250 |
font-family: 'Roboto Mono', monospace; |
| 251 |
} |
| 252 |
pre { |
| 253 |
border: 1px solid #eee; |
| 254 |
margin: 0; |
| 255 |
padding: 1em; |
| 256 |
} |
| 257 |
img { |
| 258 |
max-width: 100%; |
| 259 |
} |
| 260 |
figure { |
| 261 |
margin: 0; |
| 262 |
} |
| 263 |
figure blockquote { |
| 264 |
margin: 0.8em 0.4em 0.4em; |
| 265 |
} |
| 266 |
figcaption { |
| 267 |
font-style: italic; |
| 268 |
margin: 0 0 1em 0; |
| 269 |
} |
| 270 |
@media screen { |
| 271 |
pre { |
| 272 |
overflow-x: auto; |
| 273 |
max-width: 100%; |
| 274 |
max-width: calc(100% - 22px); |
| 275 |
} |
| 276 |
} |
| 277 |
|
| 278 |
/* aside, blockquote */ |
| 279 |
aside, blockquote { |
| 280 |
margin-left: 0; |
| 281 |
padding: 1.2em 2em; |
| 282 |
} |
| 283 |
blockquote { |
| 284 |
background-color: #f9f9f9; |
| 285 |
color: #111; /* Arlen: WCAG 2019 */ |
| 286 |
border: 1px solid #ddd; |
| 287 |
border-radius: 3px; |
| 288 |
margin: 1em 0; |
| 289 |
} |
| 290 |
cite { |
| 291 |
display: block; |
| 292 |
text-align: right; |
| 293 |
font-style: italic; |
| 294 |
} |
| 295 |
|
| 296 |
/* tables */ |
| 297 |
table { |
| 298 |
width: 100%; |
| 299 |
margin: 0 0 1em; |
| 300 |
border-collapse: collapse; |
| 301 |
border: 1px solid #eee; |
| 302 |
} |
| 303 |
th, td { |
| 304 |
text-align: left; |
| 305 |
vertical-align: top; |
| 306 |
padding: 0.5em 0.75em; |
| 307 |
} |
| 308 |
th { |
| 309 |
text-align: left; |
| 310 |
background-color: #e9e9e9; |
| 311 |
} |
| 312 |
tr:nth-child(2n+1) > td { |
| 313 |
background-color: #f5f5f5; |
| 314 |
} |
| 315 |
table caption { |
| 316 |
font-style: italic; |
| 317 |
margin: 0; |
| 318 |
padding: 0; |
| 319 |
text-align: left; |
| 320 |
} |
| 321 |
table p { |
| 322 |
/* XXX to avoid bottom margin on table row signifiers. If paragraphs should |
| 323 |
be allowed within tables more generally, it would be far better to select on a class. */ |
| 324 |
margin: 0; |
| 325 |
} |
| 326 |
|
| 327 |
/* pilcrow */ |
| 328 |
a.pilcrow { |
| 329 |
color: #666; /* Arlen: AHDJ 2019 */ |
| 330 |
text-decoration: none; |
| 331 |
visibility: hidden; |
| 332 |
user-select: none; |
| 333 |
-ms-user-select: none; |
| 334 |
-o-user-select:none; |
| 335 |
-moz-user-select: none; |
| 336 |
-khtml-user-select: none; |
| 337 |
-webkit-user-select: none; |
| 338 |
-webkit-touch-callout: none; |
| 339 |
} |
| 340 |
@media screen { |
| 341 |
aside:hover > a.pilcrow, |
| 342 |
p:hover > a.pilcrow, |
| 343 |
blockquote:hover > a.pilcrow, |
| 344 |
div:hover > a.pilcrow, |
| 345 |
li:hover > a.pilcrow, |
| 346 |
pre:hover > a.pilcrow { |
| 347 |
visibility: visible; |
| 348 |
} |
| 349 |
a.pilcrow:hover { |
| 350 |
background-color: transparent; |
| 351 |
} |
| 352 |
} |
| 353 |
|
| 354 |
/* misc */ |
| 355 |
hr { |
| 356 |
border: 0; |
| 357 |
border-top: 1px solid #eee; |
| 358 |
} |
| 359 |
.bcp14 { |
| 360 |
font-variant: small-caps; |
| 361 |
} |
| 362 |
|
| 363 |
.role { |
| 364 |
font-variant: all-small-caps; |
| 365 |
} |
| 366 |
|
| 367 |
/* info block */ |
| 368 |
#identifiers { |
| 369 |
margin: 0; |
| 370 |
font-size: 0.9em; |
| 371 |
} |
| 372 |
#identifiers dt { |
| 373 |
width: 3em; |
| 374 |
clear: left; |
| 375 |
} |
| 376 |
#identifiers dd { |
| 377 |
float: left; |
| 378 |
margin-bottom: 0; |
| 379 |
} |
| 380 |
#identifiers .authors .author { |
| 381 |
display: inline-block; |
| 382 |
margin-right: 1.5em; |
| 383 |
} |
| 384 |
#identifiers .authors .org { |
| 385 |
font-style: italic; |
| 386 |
} |
| 387 |
|
| 388 |
/* The prepared/rendered info at the very bottom of the page */ |
| 389 |
.docInfo { |
| 390 |
color: #666; /* Arlen: WCAG 2019 */ |
| 391 |
font-size: 0.9em; |
| 392 |
font-style: italic; |
| 393 |
margin-top: 2em; |
| 394 |
} |
| 395 |
.docInfo .prepared { |
| 396 |
float: left; |
| 397 |
} |
| 398 |
.docInfo .prepared { |
| 399 |
float: right; |
| 400 |
} |
| 401 |
|
| 402 |
/* table of contents */ |
| 403 |
#toc { |
| 404 |
padding: 0.75em 0 2em 0; |
| 405 |
margin-bottom: 1em; |
| 406 |
} |
| 407 |
nav.toc ul { |
| 408 |
margin: 0 0.5em 0 0; |
| 409 |
padding: 0; |
| 410 |
list-style: none; |
| 411 |
} |
| 412 |
nav.toc li { |
| 413 |
line-height: 1.3em; |
| 414 |
margin: 0.75em 0; |
| 415 |
padding-left: 1.2em; |
| 416 |
text-indent: -1.2em; |
| 417 |
} |
| 418 |
/* references */ |
| 419 |
.references dt { |
| 420 |
text-align: right; |
| 421 |
font-weight: bold; |
| 422 |
min-width: 7em; |
| 423 |
} |
| 424 |
.references dd { |
| 425 |
margin-left: 8em; |
| 426 |
overflow: auto; |
| 427 |
} |
| 428 |
|
| 429 |
.refInstance { |
| 430 |
margin-bottom: 1.25em; |
| 431 |
} |
| 432 |
|
| 433 |
.references .ascii { |
| 434 |
margin-bottom: 0.25em; |
| 435 |
} |
| 436 |
|
| 437 |
/* index */ |
| 438 |
.index ul { |
| 439 |
margin: 0 0 0 1em; |
| 440 |
padding: 0; |
| 441 |
list-style: none; |
| 442 |
} |
| 443 |
.index ul ul { |
| 444 |
margin: 0; |
| 445 |
} |
| 446 |
.index li { |
| 447 |
margin: 0; |
| 448 |
text-indent: -2em; |
| 449 |
padding-left: 2em; |
| 450 |
padding-bottom: 5px; |
| 451 |
} |
| 452 |
.indexIndex { |
| 453 |
margin: 0.5em 0 1em; |
| 454 |
} |
| 455 |
.index a { |
| 456 |
font-weight: 700; |
| 457 |
} |
| 458 |
/* make the index two-column on all but the smallest screens */ |
| 459 |
@media (min-width: 600px) { |
| 460 |
.index ul { |
| 461 |
-moz-column-count: 2; |
| 462 |
-moz-column-gap: 20px; |
| 463 |
} |
| 464 |
.index ul ul { |
| 465 |
-moz-column-count: 1; |
| 466 |
-moz-column-gap: 0; |
| 467 |
} |
| 468 |
} |
| 469 |
|
| 470 |
/* authors */ |
| 471 |
address.vcard { |
| 472 |
font-style: normal; |
| 473 |
margin: 1em 0; |
| 474 |
} |
| 475 |
|
| 476 |
address.vcard .nameRole { |
| 477 |
font-weight: 700; |
| 478 |
margin-left: 0; |
| 479 |
} |
| 480 |
address.vcard .label { |
| 481 |
font-family: "Noto Sans",Arial,Helvetica,sans-serif; |
| 482 |
margin: 0.5em 0; |
| 483 |
} |
| 484 |
address.vcard .type { |
| 485 |
display: none; |
| 486 |
} |
| 487 |
.alternative-contact { |
| 488 |
margin: 1.5em 0 1em; |
| 489 |
} |
| 490 |
hr.addr { |
| 491 |
border-top: 1px dashed; |
| 492 |
margin: 0; |
| 493 |
color: #ddd; |
| 494 |
max-width: calc(100% - 16px); |
| 495 |
} |
| 496 |
|
| 497 |
/* temporary notes */ |
| 498 |
.rfcEditorRemove::before { |
| 499 |
position: absolute; |
| 500 |
top: 0.2em; |
| 501 |
right: 0.2em; |
| 502 |
padding: 0.2em; |
| 503 |
content: "The RFC Editor will remove this note"; |
| 504 |
color: #9e2a00; /* Arlen: WCAG 2019 */ |
| 505 |
background-color: #ffd; /* Arlen: WCAG 2019 */ |
| 506 |
} |
| 507 |
.rfcEditorRemove { |
| 508 |
position: relative; |
| 509 |
padding-top: 1.8em; |
| 510 |
background-color: #ffd; /* Arlen: WCAG 2019 */ |
| 511 |
border-radius: 3px; |
| 512 |
} |
| 513 |
.cref { |
| 514 |
background-color: #ffd; /* Arlen: WCAG 2019 */ |
| 515 |
padding: 2px 4px; |
| 516 |
} |
| 517 |
.crefSource { |
| 518 |
font-style: italic; |
| 519 |
} |
| 520 |
/* alternative layout for smaller screens */ |
| 521 |
@media screen and (max-width: 1023px) { |
| 522 |
body { |
| 523 |
padding-top: 2em; |
| 524 |
} |
| 525 |
#title { |
| 526 |
padding: 1em 0; |
| 527 |
} |
| 528 |
h1 { |
| 529 |
font-size: 24px; |
| 530 |
} |
| 531 |
h2 { |
| 532 |
font-size: 20px; |
| 533 |
margin-top: -18px; /* provide offset for in-page anchors */ |
| 534 |
padding-top: 38px; |
| 535 |
} |
| 536 |
#identifiers dd { |
| 537 |
max-width: 60%; |
| 538 |
} |
| 539 |
#toc { |
| 540 |
position: fixed; |
| 541 |
z-index: 2; |
| 542 |
top: 0; |
| 543 |
right: 0; |
| 544 |
padding: 0; |
| 545 |
margin: 0; |
| 546 |
background-color: inherit; |
| 547 |
border-bottom: 1px solid #ccc; |
| 548 |
} |
| 549 |
#toc h2 { |
| 550 |
margin: -1px 0 0 0; |
| 551 |
padding: 4px 0 4px 6px; |
| 552 |
padding-right: 1em; |
| 553 |
min-width: 190px; |
| 554 |
font-size: 1.1em; |
| 555 |
text-align: right; |
| 556 |
background-color: #444; |
| 557 |
color: white; |
| 558 |
cursor: pointer; |
| 559 |
} |
| 560 |
#toc h2::before { /* css hamburger */ |
| 561 |
float: right; |
| 562 |
position: relative; |
| 563 |
width: 1em; |
| 564 |
height: 1px; |
| 565 |
left: -164px; |
| 566 |
margin: 6px 0 0 0; |
| 567 |
background: white none repeat scroll 0 0; |
| 568 |
box-shadow: 0 4px 0 0 white, 0 8px 0 0 white; |
| 569 |
content: ""; |
| 570 |
} |
| 571 |
#toc nav { |
| 572 |
display: none; |
| 573 |
padding: 0.5em 1em 1em; |
| 574 |
overflow: auto; |
| 575 |
height: calc(100vh - 48px); |
| 576 |
border-left: 1px solid #ddd; |
| 577 |
} |
| 578 |
} |
| 579 |
|
| 580 |
/* alternative layout for wide screens */ |
| 581 |
@media screen and (min-width: 1024px) { |
| 582 |
body { |
| 583 |
max-width: 724px; |
| 584 |
margin: 42px auto; |
| 585 |
padding-left: 1.5em; |
| 586 |
padding-right: 29em; |
| 587 |
} |
| 588 |
#toc { |
| 589 |
position: fixed; |
| 590 |
top: 42px; |
| 591 |
right: 42px; |
| 592 |
width: 25%; |
| 593 |
margin: 0; |
| 594 |
padding: 0 1em; |
| 595 |
z-index: 1; |
| 596 |
} |
| 597 |
#toc h2 { |
| 598 |
border-top: none; |
| 599 |
border-bottom: 1px solid #ddd; |
| 600 |
font-size: 1em; |
| 601 |
font-weight: normal; |
| 602 |
margin: 0; |
| 603 |
padding: 0.25em 1em 1em 0; |
| 604 |
} |
| 605 |
#toc nav { |
| 606 |
display: block; |
| 607 |
height: calc(90vh - 84px); |
| 608 |
bottom: 0; |
| 609 |
padding: 0.5em 0 0; |
| 610 |
overflow: auto; |
| 611 |
} |
| 612 |
img { /* future proofing */ |
| 613 |
max-width: 100%; |
| 614 |
height: auto; |
| 615 |
} |
| 616 |
} |
| 617 |
|
| 618 |
/* pagination */ |
| 619 |
@media print { |
| 620 |
body { |
| 621 |
|
| 622 |
width: 100%; |
| 623 |
} |
| 624 |
p { |
| 625 |
orphans: 3; |
| 626 |
widows: 3; |
| 627 |
} |
| 628 |
#n-copyright-notice { |
| 629 |
border-bottom: none; |
| 630 |
} |
| 631 |
#toc, #n-introduction { |
| 632 |
page-break-before: always; |
| 633 |
} |
| 634 |
#toc { |
| 635 |
border-top: none; |
| 636 |
padding-top: 0; |
| 637 |
} |
| 638 |
figure, pre { |
| 639 |
page-break-inside: avoid; |
| 640 |
} |
| 641 |
figure { |
| 642 |
overflow: scroll; |
| 643 |
} |
| 644 |
h1, h2, h3, h4, h5, h6 { |
| 645 |
page-break-after: avoid; |
| 646 |
} |
| 647 |
h2+*, h3+*, h4+*, h5+*, h6+* { |
| 648 |
page-break-before: avoid; |
| 649 |
} |
| 650 |
pre { |
| 651 |
white-space: pre-wrap; |
| 652 |
word-wrap: break-word; |
| 653 |
font-size: 10pt; |
| 654 |
} |
| 655 |
table { |
| 656 |
border: 1px solid #ddd; |
| 657 |
} |
| 658 |
td { |
| 659 |
border-top: 1px solid #ddd; |
| 660 |
} |
| 661 |
} |
| 662 |
|
| 663 |
/* This is commented out here, as the string-set: doesn't |
| 664 |
pass W3C validation currently */ |
| 665 |
/* |
| 666 |
.ears thead .left { |
| 667 |
string-set: ears-top-left content(); |
| 668 |
} |
| 669 |
|
| 670 |
.ears thead .center { |
| 671 |
string-set: ears-top-center content(); |
| 672 |
} |
| 673 |
|
| 674 |
.ears thead .right { |
| 675 |
string-set: ears-top-right content(); |
| 676 |
} |
| 677 |
|
| 678 |
.ears tfoot .left { |
| 679 |
string-set: ears-bottom-left content(); |
| 680 |
} |
| 681 |
|
| 682 |
.ears tfoot .center { |
| 683 |
string-set: ears-bottom-center content(); |
| 684 |
} |
| 685 |
|
| 686 |
.ears tfoot .right { |
| 687 |
string-set: ears-bottom-right content(); |
| 688 |
} |
| 689 |
*/ |
| 690 |
|
| 691 |
@page :first { |
| 692 |
padding-top: 0; |
| 693 |
@top-left { |
| 694 |
content: normal; |
| 695 |
border: none; |
| 696 |
} |
| 697 |
@top-center { |
| 698 |
content: normal; |
| 699 |
border: none; |
| 700 |
} |
| 701 |
@top-right { |
| 702 |
content: normal; |
| 703 |
border: none; |
| 704 |
} |
| 705 |
} |
| 706 |
|
| 707 |
@page { |
| 708 |
size: A4; |
| 709 |
margin-bottom: 45mm; |
| 710 |
padding-top: 20px; |
| 711 |
/* The follwing is commented out here, but set appropriately by in code, as |
| 712 |
the content depends on the document */ |
| 713 |
/* |
| 714 |
@top-left { |
| 715 |
content: 'Internet-Draft'; |
| 716 |
vertical-align: bottom; |
| 717 |
border-bottom: solid 1px #ccc; |
| 718 |
} |
| 719 |
@top-left { |
| 720 |
content: string(ears-top-left); |
| 721 |
vertical-align: bottom; |
| 722 |
border-bottom: solid 1px #ccc; |
| 723 |
} |
| 724 |
@top-center { |
| 725 |
content: string(ears-top-center); |
| 726 |
vertical-align: bottom; |
| 727 |
border-bottom: solid 1px #ccc; |
| 728 |
} |
| 729 |
@top-right { |
| 730 |
content: string(ears-top-right); |
| 731 |
vertical-align: bottom; |
| 732 |
border-bottom: solid 1px #ccc; |
| 733 |
} |
| 734 |
@bottom-left { |
| 735 |
content: string(ears-bottom-left); |
| 736 |
vertical-align: top; |
| 737 |
border-top: solid 1px #ccc; |
| 738 |
} |
| 739 |
@bottom-center { |
| 740 |
content: string(ears-bottom-center); |
| 741 |
vertical-align: top; |
| 742 |
border-top: solid 1px #ccc; |
| 743 |
} |
| 744 |
@bottom-right { |
| 745 |
content: '[Page ' counter(page) ']'; |
| 746 |
vertical-align: top; |
| 747 |
border-top: solid 1px #ccc; |
| 748 |
} |
| 749 |
*/ |
| 750 |
|
| 751 |
} |
| 752 |
|
| 753 |
/* Changes introduced to fix issues found during implementation */ |
| 754 |
/* Make sure links are clickable even if overlapped by following H* */ |
| 755 |
a { |
| 756 |
z-index: 2; |
| 757 |
} |
| 758 |
/* Separate body from document info even without intervening H1 */ |
| 759 |
section { |
| 760 |
clear: both; |
| 761 |
} |
| 762 |
|
| 763 |
|
| 764 |
/* Top align author divs, to avoid names without organization dropping level with org names */ |
| 765 |
.author { |
| 766 |
vertical-align: top; |
| 767 |
} |
| 768 |
|
| 769 |
/* Leave room in document info to show Internet-Draft on one line */ |
| 770 |
#identifiers dt { |
| 771 |
width: 8em; |
| 772 |
} |
| 773 |
|
| 774 |
/* Don't waste quite as much whitespace between label and value in doc info */ |
| 775 |
#identifiers dd { |
| 776 |
margin-left: 1em; |
| 777 |
} |
| 778 |
|
| 779 |
/* Give floating toc a background color (needed when it's a div inside section */ |
| 780 |
#toc { |
| 781 |
background-color: white; |
| 782 |
} |
| 783 |
|
| 784 |
/* Make the collapsed ToC header render white on gray also when it's a link */ |
| 785 |
@media screen and (max-width: 1023px) { |
| 786 |
#toc h2 a, |
| 787 |
#toc h2 a:link, |
| 788 |
#toc h2 a:focus, |
| 789 |
#toc h2 a:hover, |
| 790 |
#toc a.toplink, |
| 791 |
#toc a.toplink:hover { |
| 792 |
color: white; |
| 793 |
background-color: #444; |
| 794 |
text-decoration: none; |
| 795 |
} |
| 796 |
} |
| 797 |
|
| 798 |
/* Give the bottom of the ToC some whitespace */ |
| 799 |
@media screen and (min-width: 1024px) { |
| 800 |
#toc { |
| 801 |
padding: 0 0 1em 1em; |
| 802 |
} |
| 803 |
} |
| 804 |
|
| 805 |
/* Style section numbers with more space between number and title */ |
| 806 |
.section-number { |
| 807 |
padding-right: 0.5em; |
| 808 |
} |
| 809 |
|
| 810 |
/* prevent monospace from becoming overly large */ |
| 811 |
tt, code, pre, code { |
| 812 |
font-size: 95%; |
| 813 |
} |
| 814 |
|
| 815 |
/* Fix the height/width aspect for ascii art*/ |
| 816 |
pre.sourcecode, |
| 817 |
.art-text pre { |
| 818 |
line-height: 1.12; |
| 819 |
} |
| 820 |
|
| 821 |
|
| 822 |
/* Add styling for a link in the ToC that points to the top of the document */ |
| 823 |
a.toplink { |
| 824 |
float: right; |
| 825 |
margin-right: 0.5em; |
| 826 |
} |
| 827 |
|
| 828 |
/* Fix the dl styling to match the RFC 7992 attributes */ |
| 829 |
dl > dt, |
| 830 |
dl.dlParallel > dt { |
| 831 |
float: left; |
| 832 |
margin-right: 1em; |
| 833 |
} |
| 834 |
dl.dlNewline > dt { |
| 835 |
float: none; |
| 836 |
} |
| 837 |
|
| 838 |
/* Provide styling for table cell text alignment */ |
| 839 |
table td.text-left, |
| 840 |
table th.text-left { |
| 841 |
text-align: left; |
| 842 |
} |
| 843 |
table td.text-center, |
| 844 |
table th.text-center { |
| 845 |
text-align: center; |
| 846 |
} |
| 847 |
table td.text-right, |
| 848 |
table th.text-right { |
| 849 |
text-align: right; |
| 850 |
} |
| 851 |
|
| 852 |
/* Make the alternative author contact informatio look less like just another |
| 853 |
author, and group it closer with the primary author contact information */ |
| 854 |
.alternative-contact { |
| 855 |
margin: 0.5em 0 0.25em 0; |
| 856 |
} |
| 857 |
address .non-ascii { |
| 858 |
margin: 0 0 0 2em; |
| 859 |
} |
| 860 |
|
| 861 |
/* With it being possible to set tables with alignment |
| 862 |
left, center, and right, { width: 100%; } does not make sense */ |
| 863 |
table { |
| 864 |
width: auto; |
| 865 |
} |
| 866 |
|
| 867 |
/* Avoid reference text that sits in a block with very wide left margin, |
| 868 |
because of a long floating dt label.*/ |
| 869 |
.references dd { |
| 870 |
overflow: visible; |
| 871 |
} |
| 872 |
|
| 873 |
/* Control caption placement */ |
| 874 |
caption { |
| 875 |
caption-side: bottom; |
| 876 |
} |
| 877 |
|
| 878 |
/* Limit the width of the author address vcard, so names in right-to-left |
| 879 |
script don't end up on the other side of the page. */ |
| 880 |
|
| 881 |
address.vcard { |
| 882 |
max-width: 30em; |
| 883 |
margin-right: auto; |
| 884 |
} |
| 885 |
|
| 886 |
/* For address alignment dependent on LTR or RTL scripts */ |
| 887 |
address div.left { |
| 888 |
text-align: left; |
| 889 |
} |
| 890 |
address div.right { |
| 891 |
text-align: right; |
| 892 |
} |
| 893 |
|
| 894 |
/* Provide table alignment support. We can't use the alignX classes above |
| 895 |
since they do unwanted things with caption and other styling. */ |
| 896 |
table.right { |
| 897 |
margin-left: auto; |
| 898 |
margin-right: 0; |
| 899 |
} |
| 900 |
table.center { |
| 901 |
margin-left: auto; |
| 902 |
margin-right: auto; |
| 903 |
} |
| 904 |
table.left { |
| 905 |
margin-left: 0; |
| 906 |
margin-right: auto; |
| 907 |
} |
| 908 |
|
| 909 |
/* Give the table caption label the same styling as the figcaption */ |
| 910 |
caption a[href] { |
| 911 |
color: #222; |
| 912 |
} |
| 913 |
|
| 914 |
@media print { |
| 915 |
.toplink { |
| 916 |
display: none; |
| 917 |
} |
| 918 |
|
| 919 |
/* avoid overwriting the top border line with the ToC header */ |
| 920 |
#toc { |
| 921 |
padding-top: 1px; |
| 922 |
} |
| 923 |
|
| 924 |
/* Avoid page breaks inside dl and author address entries */ |
| 925 |
.vcard { |
| 926 |
page-break-inside: avoid; |
| 927 |
} |
| 928 |
|
| 929 |
} |
| 930 |
/* Avoid wrapping of URLs in references */ |
| 931 |
@media screen { |
| 932 |
.references a { |
| 933 |
white-space: nowrap; |
| 934 |
} |
| 935 |
} |
| 936 |
/* Tweak the bcp14 keyword presentation */ |
| 937 |
.bcp14 { |
| 938 |
font-variant: small-caps; |
| 939 |
font-weight: bold; |
| 940 |
font-size: 0.9em; |
| 941 |
} |
| 942 |
/* Tweak the invisible space above H* in order not to overlay links in text above */ |
| 943 |
h2 { |
| 944 |
margin-top: -18px; /* provide offset for in-page anchors */ |
| 945 |
padding-top: 31px; |
| 946 |
} |
| 947 |
h3 { |
| 948 |
margin-top: -18px; /* provide offset for in-page anchors */ |
| 949 |
padding-top: 24px; |
| 950 |
} |
| 951 |
h4 { |
| 952 |
margin-top: -18px; /* provide offset for in-page anchors */ |
| 953 |
padding-top: 24px; |
| 954 |
} |
| 955 |
/* Float artwork pilcrow to the right */ |
| 956 |
@media screen { |
| 957 |
.artwork a.pilcrow { |
| 958 |
display: block; |
| 959 |
line-height: 0.7; |
| 960 |
margin-top: 0.15em; |
| 961 |
} |
| 962 |
} |
| 963 |
/* Make pilcrows on dd visible */ |
| 964 |
@media screen { |
| 965 |
dd:hover > a.pilcrow { |
| 966 |
visibility: visible; |
| 967 |
} |
| 968 |
} |
| 969 |
/* Make the placement of figcaption match that of a table's caption |
| 970 |
by removing the figure's added bottom margin */ |
| 971 |
.alignLeft.art-text, |
| 972 |
.alignCenter.art-text, |
| 973 |
.alignRight.art-text { |
| 974 |
margin-bottom: 0; |
| 975 |
} |
| 976 |
.alignLeft, |
| 977 |
.alignCenter, |
| 978 |
.alignRight { |
| 979 |
margin: 1em 0 0 0; |
| 980 |
} |
| 981 |
/* In print, the pilcrow won't show on hover, so prevent it from taking up space, |
| 982 |
possibly even requiring a new line */ |
| 983 |
@media print { |
| 984 |
a.pilcrow { |
| 985 |
display: none; |
| 986 |
} |
| 987 |
} |
| 988 |
/* Styling for the external metadata */ |
| 989 |
div#external-metadata { |
| 990 |
background-color: #eee; |
| 991 |
padding: 0.5em; |
| 992 |
margin-bottom: 0.5em; |
| 993 |
display: none; |
| 994 |
} |
| 995 |
div#internal-metadata { |
| 996 |
padding: 0.5em; /* to match the external-metadata padding */ |
| 997 |
} |
| 998 |
/* Styling for title RFC Number */ |
| 999 |
h1#rfcnum { |
| 1000 |
clear: both; |
| 1001 |
margin: 0 0 -1em; |
| 1002 |
padding: 1em 0 0 0; |
| 1003 |
} |
| 1004 |
/* Make .olPercent look the same as <ol><li> */ |
| 1005 |
dl.olPercent > dd { |
| 1006 |
margin: 0 0 0.25em 0; |
| 1007 |
min-height: initial; |
| 1008 |
} |
| 1009 |
/* Give aside some styling to set it apart */ |
| 1010 |
aside { |
| 1011 |
border-left: 1px solid #ddd; |
| 1012 |
margin: 1em 0 1em 2em; |
| 1013 |
padding: 0.2em 2em; |
| 1014 |
} |
| 1015 |
aside > dl, |
| 1016 |
aside > ol, |
| 1017 |
aside > ul, |
| 1018 |
aside > table, |
| 1019 |
aside > p { |
| 1020 |
margin-bottom: 0; |
| 1021 |
} |
| 1022 |
/* Additional page break settings */ |
| 1023 |
@media print { |
| 1024 |
figcaption, table caption { |
| 1025 |
page-break-before: avoid; |
| 1026 |
} |
| 1027 |
} |
| 1028 |
/* Font size adjustments for print */ |
| 1029 |
@media print { |
| 1030 |
body { font-size: 10pt; line-height: normal; max-width: 96%; } |
| 1031 |
h1 { font-size: 1.72em; padding-top: 1.5em; } /* 1*1.2*1.2*1.2 */ |
| 1032 |
h2 { font-size: 1.44em; padding-top: 1.5em; } /* 1*1.2*1.2 */ |
| 1033 |
h3 { font-size: 1.2em; padding-top: 1.5em; } /* 1*1.2 */ |
| 1034 |
h4 { font-size: 1em; padding-top: 1.5em; } |
| 1035 |
h5, h6 { font-size: 1em; margin: initial; padding: 0.5em 0 0.3em; } |
| 1036 |
} |
| 1037 |
/* Sourcecode margin in print, when there's no pilcrow */ |
| 1038 |
@media print { |
| 1039 |
.sourcecode { |
| 1040 |
margin-bottom: 1em; |
| 1041 |
} |
| 1042 |
}</style> |
| 1043 |
<link href="rfc-local.css" type="text/css" rel="stylesheet"> |
| 1044 |
<link href="https://dx.doi.org/10.17487/rfc8661" rel="alternate"> |
| 1045 |
<link href="urn:issn:2070-1721" rel="alternate"> |
| 1046 |
<link href="https://datatracker.ietf.org/doc/draft-ietf-spring-segment-routing-ldp-interop-15" rel="prev"> |
| 1047 |
</head> |
| 1048 |
<body> |
| 1049 |
<script src="https://www.rfc-editor.org/js/metadata.min.js"></script> |
| 1050 |
<table class="ears"> |
| 1051 |
<thead><tr> |
| 1052 |
<td class="left">RFC 8661</td> |
| 1053 |
<td class="center">Segment Routing and LDP</td> |
| 1054 |
<td class="right">December 2019</td> |
| 1055 |
</tr></thead> |
| 1056 |
<tfoot><tr> |
| 1057 |
<td class="left">Bashandy, et al.</td> |
| 1058 |
<td class="center">Standards Track</td> |
| 1059 |
<td class="right">[Page]</td> |
| 1060 |
</tr></tfoot> |
| 1061 |
</table> |
| 1062 |
<div id="external-metadata" class="document-information"></div> |
| 1063 |
<div id="internal-metadata" class="document-information"> |
| 1064 |
<dl id="identifiers"> |
| 1065 |
<dt class="label-stream">Stream:</dt> |
| 1066 |
<dd class="stream">Internet Engineering Task Force (IETF)</dd> |
| 1067 |
<dt class="label-rfc">RFC:</dt> |
| 1068 |
<dd class="rfc"><a href="https://www.rfc-editor.org/rfc/rfc8661" class="eref">8661</a></dd> |
| 1069 |
<dt class="label-category">Category:</dt> |
| 1070 |
<dd class="category">Standards Track</dd> |
| 1071 |
<dt class="label-published">Published:</dt> |
| 1072 |
<dd class="published"> |
| 1073 |
<time datetime="2019-12" class="published">December 2019</time> |
| 1074 |
</dd> |
| 1075 |
<dt class="label-issn">ISSN:</dt> |
| 1076 |
<dd class="issn">2070-1721</dd> |
| 1077 |
<dt class="label-authors">Authors:</dt> |
| 1078 |
<dd class="authors"> |
| 1079 |
<div class="author"> |
| 1080 |
<div class="author-name">A. Bashandy, <span class="editor">Ed.</span> |
| 1081 |
</div> |
| 1082 |
<div class="org">Individual</div> |
| 1083 |
</div> |
| 1084 |
<div class="author"> |
| 1085 |
<div class="author-name">C. Filsfils, <span class="editor">Ed.</span> |
| 1086 |
</div> |
| 1087 |
<div class="org">Cisco Systems, Inc.</div> |
| 1088 |
</div> |
| 1089 |
<div class="author"> |
| 1090 |
<div class="author-name">S. Previdi</div> |
| 1091 |
<div class="org">Huawei Technologies</div> |
| 1092 |
</div> |
| 1093 |
<div class="author"> |
| 1094 |
<div class="author-name">B. Decraene</div> |
| 1095 |
<div class="org">Orange</div> |
| 1096 |
</div> |
| 1097 |
<div class="author"> |
| 1098 |
<div class="author-name">S. Litkowski</div> |
| 1099 |
<div class="org">Orange</div> |
| 1100 |
</div> |
| 1101 |
</dd> |
| 1102 |
</dl> |
| 1103 |
</div> |
| 1104 |
<h1 id="rfcnum">RFC 8661</h1> |
| 1105 |
<h1 id="title">Segment Routing MPLS Interworking with LDP</h1> |
| 1106 |
<section id="section-abstract"> |
| 1107 |
<h2 id="abstract"><a href="#abstract" class="selfRef">Abstract</a></h2> |
| 1108 |
<p id="section-abstract-1">A Segment Routing (SR) node steers a packet through a controlled set |
| 1109 |
of instructions, called segments, by prepending the packet with an SR |
| 1110 |
header. A segment can represent any instruction, topological or |
| 1111 |
service based. SR allows enforcing a flow through any topological path |
| 1112 |
while maintaining per-flow state only at the ingress node to the SR |
| 1113 |
domain.<a href="#section-abstract-1" class="pilcrow">¶</a></p> |
| 1114 |
<p id="section-abstract-2">The Segment Routing architecture can be directly applied to the MPLS |
| 1115 |
data plane with no change in the forwarding plane. This document |
| 1116 |
describes how Segment Routing MPLS operates in a network where LDP is |
| 1117 |
deployed and in the case where SR-capable and non-SR-capable nodes |
| 1118 |
coexist.<a href="#section-abstract-2" class="pilcrow">¶</a></p> |
| 1119 |
</section> |
| 1120 |
<div id="status-of-memo"> |
| 1121 |
<section id="section-boilerplate.1"> |
| 1122 |
<h2 id="name-status-of-this-memo"> |
| 1123 |
<a href="#name-status-of-this-memo" class="section-name selfRef">Status of This Memo</a> |
| 1124 |
</h2> |
| 1125 |
<p id="section-boilerplate.1-1"> |
| 1126 |
This is an Internet Standards Track document.<a href="#section-boilerplate.1-1" class="pilcrow">¶</a></p> |
| 1127 |
<p id="section-boilerplate.1-2"> |
| 1128 |
This document is a product of the Internet Engineering Task Force |
| 1129 |
(IETF). It represents the consensus of the IETF community. It has |
| 1130 |
received public review and has been approved for publication by |
| 1131 |
the Internet Engineering Steering Group (IESG). Further |
| 1132 |
information on Internet Standards is available in Section 2 of |
| 1133 |
RFC 7841.<a href="#section-boilerplate.1-2" class="pilcrow">¶</a></p> |
| 1134 |
<p id="section-boilerplate.1-3"> |
| 1135 |
Information about the current status of this document, any |
| 1136 |
errata, and how to provide feedback on it may be obtained at |
| 1137 |
<span><a href="https://www.rfc-editor.org/info/rfc8661">https://www.rfc-editor.org/info/rfc8661</a></span>.<a href="#section-boilerplate.1-3" class="pilcrow">¶</a></p> |
| 1138 |
</section> |
| 1139 |
</div> |
| 1140 |
<div id="copyright"> |
| 1141 |
<section id="section-boilerplate.2"> |
| 1142 |
<h2 id="name-copyright-notice"> |
| 1143 |
<a href="#name-copyright-notice" class="section-name selfRef">Copyright Notice</a> |
| 1144 |
</h2> |
| 1145 |
<p id="section-boilerplate.2-1"> |
| 1146 |
Copyright (c) 2019 IETF Trust and the persons identified as the |
| 1147 |
document authors. All rights reserved.<a href="#section-boilerplate.2-1" class="pilcrow">¶</a></p> |
| 1148 |
<p id="section-boilerplate.2-2"> |
| 1149 |
This document is subject to BCP 78 and the IETF Trust's Legal |
| 1150 |
Provisions Relating to IETF Documents |
| 1151 |
(<span><a href="https://trustee.ietf.org/license-info">https://trustee.ietf.org/license-info</a></span>) in effect on the date of |
| 1152 |
publication of this document. Please review these documents |
| 1153 |
carefully, as they describe your rights and restrictions with |
| 1154 |
respect to this document. Code Components extracted from this |
| 1155 |
document must include Simplified BSD License text as described in |
| 1156 |
Section 4.e of the Trust Legal Provisions and are provided without |
| 1157 |
warranty as described in the Simplified BSD License.<a href="#section-boilerplate.2-2" class="pilcrow">¶</a></p> |
| 1158 |
</section> |
| 1159 |
</div> |
| 1160 |
<div id="toc"> |
| 1161 |
<section id="section-toc.1"> |
| 1162 |
<a href="#" onclick="scroll(0,0)" class="toplink">▲</a><h2 id="name-table-of-contents"> |
| 1163 |
<a href="#name-table-of-contents" class="section-name selfRef">Table of Contents</a> |
| 1164 |
</h2> |
| 1165 |
<nav class="toc"><ul class="toc ulEmpty"> |
| 1166 |
<li class="toc ulEmpty" id="section-toc.1-1.1"> |
| 1167 |
<p id="section-toc.1-1.1.1"><a href="#section-1" class="xref">1</a>. <a href="#name-introduction" class="xref">Introduction</a><a href="#section-toc.1-1.1.1" class="pilcrow">¶</a></p> |
| 1168 |
<ul class="toc ulEmpty"> |
| 1169 |
<li class="toc ulEmpty" id="section-toc.1-1.1.2.1"> |
| 1170 |
<p id="section-toc.1-1.1.2.1.1"><a href="#section-1.1" class="xref">1.1</a>. <a href="#name-requirements-language" class="xref">Requirements Language</a><a href="#section-toc.1-1.1.2.1.1" class="pilcrow">¶</a></p> |
| 1171 |
</li> |
| 1172 |
</ul> |
| 1173 |
</li> |
| 1174 |
<li class="toc ulEmpty" id="section-toc.1-1.2"> |
| 1175 |
<p id="section-toc.1-1.2.1"><a href="#section-2" class="xref">2</a>. <a href="#name-sr-ldp-ships-in-the-night-c" class="xref">SR-LDP Ships-in-the-Night Coexistence</a><a href="#section-toc.1-1.2.1" class="pilcrow">¶</a></p> |
| 1176 |
<ul class="toc ulEmpty"> |
| 1177 |
<li class="toc ulEmpty" id="section-toc.1-1.2.2.1"> |
| 1178 |
<p id="section-toc.1-1.2.2.1.1"><a href="#section-2.1" class="xref">2.1</a>. <a href="#name-mpls2mpls-mpls2ip-and-ip2mp" class="xref">MPLS2MPLS, MPLS2IP, and IP2MPLS Coexistence</a><a href="#section-toc.1-1.2.2.1.1" class="pilcrow">¶</a></p> |
| 1179 |
</li> |
| 1180 |
</ul> |
| 1181 |
</li> |
| 1182 |
<li class="toc ulEmpty" id="section-toc.1-1.3"> |
| 1183 |
<p id="section-toc.1-1.3.1"><a href="#section-3" class="xref">3</a>. <a href="#name-sr-and-ldp-interworking" class="xref">SR and LDP Interworking</a><a href="#section-toc.1-1.3.1" class="pilcrow">¶</a></p> |
| 1184 |
<ul class="toc ulEmpty"> |
| 1185 |
<li class="toc ulEmpty" id="section-toc.1-1.3.2.1"> |
| 1186 |
<p id="section-toc.1-1.3.2.1.1"><a href="#section-3.1" class="xref">3.1</a>. <a href="#name-ldp-to-sr" class="xref">LDP to SR</a><a href="#section-toc.1-1.3.2.1.1" class="pilcrow">¶</a></p> |
| 1187 |
<ul class="toc ulEmpty"> |
| 1188 |
<li class="toc ulEmpty" id="section-toc.1-1.3.2.1.2.1"> |
| 1189 |
<p id="section-toc.1-1.3.2.1.2.1.1"><a href="#section-3.1.1" class="xref">3.1.1</a>. <a href="#name-ldp-to-sr-behavior" class="xref">LDP to SR Behavior</a><a href="#section-toc.1-1.3.2.1.2.1.1" class="pilcrow">¶</a></p> |
| 1190 |
</li> |
| 1191 |
</ul> |
| 1192 |
</li> |
| 1193 |
<li class="toc ulEmpty" id="section-toc.1-1.3.2.2"> |
| 1194 |
<p id="section-toc.1-1.3.2.2.1"><a href="#section-3.2" class="xref">3.2</a>. <a href="#name-sr-to-ldp" class="xref">SR to LDP</a><a href="#section-toc.1-1.3.2.2.1" class="pilcrow">¶</a></p> |
| 1195 |
<ul class="toc ulEmpty"> |
| 1196 |
<li class="toc ulEmpty" id="section-toc.1-1.3.2.2.2.1"> |
| 1197 |
<p id="section-toc.1-1.3.2.2.2.1.1"><a href="#section-3.2.1" class="xref">3.2.1</a>. <a href="#name-segment-routing-mapping-ser" class="xref">Segment Routing Mapping Server (SRMS)</a><a href="#section-toc.1-1.3.2.2.2.1.1" class="pilcrow">¶</a></p> |
| 1198 |
</li> |
| 1199 |
<li class="toc ulEmpty" id="section-toc.1-1.3.2.2.2.2"> |
| 1200 |
<p id="section-toc.1-1.3.2.2.2.2.1"><a href="#section-3.2.2" class="xref">3.2.2</a>. <a href="#name-sr-to-ldp-behavior" class="xref">SR to LDP Behavior</a><a href="#section-toc.1-1.3.2.2.2.2.1" class="pilcrow">¶</a></p> |
| 1201 |
</li> |
| 1202 |
<li class="toc ulEmpty" id="section-toc.1-1.3.2.2.2.3"> |
| 1203 |
<p id="section-toc.1-1.3.2.2.2.3.1"><a href="#section-3.2.3" class="xref">3.2.3</a>. <a href="#name-interoperability-of-multipl" class="xref">Interoperability of Multiple SRMSes and Prefix-SID Advertisements</a><a href="#section-toc.1-1.3.2.2.2.3.1" class="pilcrow">¶</a></p> |
| 1204 |
</li> |
| 1205 |
</ul> |
| 1206 |
</li> |
| 1207 |
</ul> |
| 1208 |
</li> |
| 1209 |
<li class="toc ulEmpty" id="section-toc.1-1.4"> |
| 1210 |
<p id="section-toc.1-1.4.1"><a href="#section-4" class="xref">4</a>. <a href="#name-sr-ldp-interworking-use-cas" class="xref">SR-LDP Interworking Use Cases</a><a href="#section-toc.1-1.4.1" class="pilcrow">¶</a></p> |
| 1211 |
<ul class="toc ulEmpty"> |
| 1212 |
<li class="toc ulEmpty" id="section-toc.1-1.4.2.1"> |
| 1213 |
<p id="section-toc.1-1.4.2.1.1"><a href="#section-4.1" class="xref">4.1</a>. <a href="#name-sr-protection-of-ldp-based-" class="xref">SR Protection of LDP-Based Traffic</a><a href="#section-toc.1-1.4.2.1.1" class="pilcrow">¶</a></p> |
| 1214 |
</li> |
| 1215 |
<li class="toc ulEmpty" id="section-toc.1-1.4.2.2"> |
| 1216 |
<p id="section-toc.1-1.4.2.2.1"><a href="#section-4.2" class="xref">4.2</a>. <a href="#name-eliminating-targeted-ldp-se" class="xref">Eliminating Targeted LDP Sessions</a><a href="#section-toc.1-1.4.2.2.1" class="pilcrow">¶</a></p> |
| 1217 |
</li> |
| 1218 |
<li class="toc ulEmpty" id="section-toc.1-1.4.2.3"> |
| 1219 |
<p id="section-toc.1-1.4.2.3.1"><a href="#section-4.3" class="xref">4.3</a>. <a href="#name-guaranteed-frr-coverage" class="xref">Guaranteed FRR Coverage</a><a href="#section-toc.1-1.4.2.3.1" class="pilcrow">¶</a></p> |
| 1220 |
</li> |
| 1221 |
<li class="toc ulEmpty" id="section-toc.1-1.4.2.4"> |
| 1222 |
<p id="section-toc.1-1.4.2.4.1"><a href="#section-4.4" class="xref">4.4</a>. <a href="#name-inter-as-option-c-carriers-" class="xref">Inter-AS Option C, Carrier's Carrier</a><a href="#section-toc.1-1.4.2.4.1" class="pilcrow">¶</a></p> |
| 1223 |
</li> |
| 1224 |
</ul> |
| 1225 |
</li> |
| 1226 |
<li class="toc ulEmpty" id="section-toc.1-1.5"> |
| 1227 |
<p id="section-toc.1-1.5.1"><a href="#section-5" class="xref">5</a>. <a href="#name-iana-considerations" class="xref">IANA Considerations</a><a href="#section-toc.1-1.5.1" class="pilcrow">¶</a></p> |
| 1228 |
</li> |
| 1229 |
<li class="toc ulEmpty" id="section-toc.1-1.6"> |
| 1230 |
<p id="section-toc.1-1.6.1"><a href="#section-6" class="xref">6</a>. <a href="#name-manageability-consideration" class="xref">Manageability Considerations</a><a href="#section-toc.1-1.6.1" class="pilcrow">¶</a></p> |
| 1231 |
<ul class="toc ulEmpty"> |
| 1232 |
<li class="toc ulEmpty" id="section-toc.1-1.6.2.1"> |
| 1233 |
<p id="section-toc.1-1.6.2.1.1"><a href="#section-6.1" class="xref">6.1</a>. <a href="#name-sr-and-ldp-coexistence" class="xref">SR and LDP Coexistence</a><a href="#section-toc.1-1.6.2.1.1" class="pilcrow">¶</a></p> |
| 1234 |
</li> |
| 1235 |
<li class="toc ulEmpty" id="section-toc.1-1.6.2.2"> |
| 1236 |
<p id="section-toc.1-1.6.2.2.1"><a href="#section-6.2" class="xref">6.2</a>. <a href="#name-data-plane-verification" class="xref">Data-Plane Verification</a><a href="#section-toc.1-1.6.2.2.1" class="pilcrow">¶</a></p> |
| 1237 |
</li> |
| 1238 |
</ul> |
| 1239 |
</li> |
| 1240 |
<li class="toc ulEmpty" id="section-toc.1-1.7"> |
| 1241 |
<p id="section-toc.1-1.7.1"><a href="#section-7" class="xref">7</a>. <a href="#name-security-considerations" class="xref">Security Considerations</a><a href="#section-toc.1-1.7.1" class="pilcrow">¶</a></p> |
| 1242 |
</li> |
| 1243 |
<li class="toc ulEmpty" id="section-toc.1-1.8"> |
| 1244 |
<p id="section-toc.1-1.8.1"><a href="#section-8" class="xref">8</a>. <a href="#name-references" class="xref">References</a><a href="#section-toc.1-1.8.1" class="pilcrow">¶</a></p> |
| 1245 |
<ul class="toc ulEmpty"> |
| 1246 |
<li class="toc ulEmpty" id="section-toc.1-1.8.2.1"> |
| 1247 |
<p id="section-toc.1-1.8.2.1.1"><a href="#section-8.1" class="xref">8.1</a>. <a href="#name-normative-references" class="xref">Normative References</a><a href="#section-toc.1-1.8.2.1.1" class="pilcrow">¶</a></p> |
| 1248 |
</li> |
| 1249 |
<li class="toc ulEmpty" id="section-toc.1-1.8.2.2"> |
| 1250 |
<p id="section-toc.1-1.8.2.2.1"><a href="#section-8.2" class="xref">8.2</a>. <a href="#name-informative-references" class="xref">Informative References</a><a href="#section-toc.1-1.8.2.2.1" class="pilcrow">¶</a></p> |
| 1251 |
</li> |
| 1252 |
</ul> |
| 1253 |
</li> |
| 1254 |
<li class="toc ulEmpty" id="section-toc.1-1.9"> |
| 1255 |
<p id="section-toc.1-1.9.1"><a href="#section-appendix.a" class="xref">Appendix A</a>. <a href="#name-migration-from-ldp-to-sr" class="xref">Migration from LDP to SR</a><a href="#section-toc.1-1.9.1" class="pilcrow">¶</a></p> |
| 1256 |
</li> |
| 1257 |
<li class="toc ulEmpty" id="section-toc.1-1.10"> |
| 1258 |
<p id="section-toc.1-1.10.1"><a href="#section-appendix.b" class="xref"></a><a href="#name-acknowledgements" class="xref">Acknowledgements</a><a href="#section-toc.1-1.10.1" class="pilcrow">¶</a></p> |
| 1259 |
</li> |
| 1260 |
<li class="toc ulEmpty" id="section-toc.1-1.11"> |
| 1261 |
<p id="section-toc.1-1.11.1"><a href="#section-appendix.c" class="xref"></a><a href="#name-contributors" class="xref">Contributors</a><a href="#section-toc.1-1.11.1" class="pilcrow">¶</a></p> |
| 1262 |
</li> |
| 1263 |
<li class="toc ulEmpty" id="section-toc.1-1.12"> |
| 1264 |
<p id="section-toc.1-1.12.1"><a href="#section-appendix.d" class="xref"></a><a href="#name-authors-addresses" class="xref">Authors' Addresses</a><a href="#section-toc.1-1.12.1" class="pilcrow">¶</a></p> |
| 1265 |
</li> |
| 1266 |
</ul> |
| 1267 |
</nav> |
| 1268 |
</section> |
| 1269 |
</div> |
| 1270 |
<div id="sec-1"> |
| 1271 |
<section id="section-1"> |
| 1272 |
<h2 id="name-introduction"> |
| 1273 |
<a href="#section-1" class="section-number selfRef">1. </a><a href="#name-introduction" class="section-name selfRef">Introduction</a> |
| 1274 |
</h2> |
| 1275 |
<p id="section-1-1">Segment Routing, as described in <span>[<a href="#RFC8402" class="xref">RFC8402</a>]</span>, can be used on top of the |
| 1276 |
MPLS data plane without any modification as described in <span>[<a href="#RFC8660" class="xref">RFC8660</a>]</span>.<a href="#section-1-1" class="pilcrow">¶</a></p> |
| 1277 |
<p id="section-1-2">Segment Routing control plane can coexist with current label |
| 1278 |
distribution protocols such as LDP <span>[<a href="#RFC5036" class="xref">RFC5036</a>]</span>.<a href="#section-1-2" class="pilcrow">¶</a></p> |
| 1279 |
<p id="section-1-3">This document outlines the mechanisms through which SR interworks |
| 1280 |
with LDP in cases where a mix of SR-capable and non-SR-capable routers |
| 1281 |
coexist within the same network and more precisely in the same routing |
| 1282 |
domain.<a href="#section-1-3" class="pilcrow">¶</a></p> |
| 1283 |
<p id="section-1-4"><a href="#sec-2" class="xref">Section 2</a> describes the coexistence of SR with |
| 1284 |
other MPLS control-plane protocols. <a href="#sec-4" class="xref">Section 3</a> documents |
| 1285 |
the interworking between SR and LDP in the case of nonhomogeneous |
| 1286 |
deployment. <a href="#sec-5" class="xref">Section 4</a> describes how a partial SR |
| 1287 |
deployment can be used to provide SR benefits to LDP-based traffic |
| 1288 |
including a possible application of SR in the context of interdomain |
| 1289 |
MPLS use cases. <a href="#Appendix-A" class="xref">Appendix A</a> documents a method to |
| 1290 |
migrate from LDP to SR-based MPLS tunneling.<a href="#section-1-4" class="pilcrow">¶</a></p> |
| 1291 |
<p id="section-1-5">Typically, an implementation will allow an operator to select |
| 1292 |
(through configuration) which of the described modes of SR and LDP |
| 1293 |
coexistence to use.<a href="#section-1-5" class="pilcrow">¶</a></p> |
| 1294 |
<section id="section-1.1"> |
| 1295 |
<h3 id="name-requirements-language"> |
| 1296 |
<a href="#section-1.1" class="section-number selfRef">1.1. </a><a href="#name-requirements-language" class="section-name selfRef">Requirements Language</a> |
| 1297 |
</h3> |
| 1298 |
<p id="section-1.1-1"> |
| 1299 |
The key words "<span class="bcp14">MUST</span>", "<span class="bcp14">MUST NOT</span>", "<span class="bcp14">REQUIRED</span>", "<span class="bcp14">SHALL</span>", "<span class="bcp14">SHALL NOT</span>", "<span class="bcp14">SHOULD</span>", "<span class="bcp14">SHOULD NOT</span>", "<span class="bcp14">RECOMMENDED</span>", "<span class="bcp14">NOT RECOMMENDED</span>", |
| 1300 |
"<span class="bcp14">MAY</span>", and "<span class="bcp14">OPTIONAL</span>" in this document are to be interpreted as |
| 1301 |
described in BCP 14 <span>[<a href="#RFC2119" class="xref">RFC2119</a>]</span> <span>[<a href="#RFC8174" class="xref">RFC8174</a>]</span> |
| 1302 |
when, and only when, they appear in all capitals, as shown here.<a href="#section-1.1-1" class="pilcrow">¶</a></p> |
| 1303 |
</section> |
| 1304 |
</section> |
| 1305 |
</div> |
| 1306 |
<div id="sec-2"> |
| 1307 |
<section id="section-2"> |
| 1308 |
<h2 id="name-sr-ldp-ships-in-the-night-c"> |
| 1309 |
<a href="#section-2" class="section-number selfRef">2. </a><a href="#name-sr-ldp-ships-in-the-night-c" class="section-name selfRef">SR-LDP Ships-in-the-Night Coexistence</a> |
| 1310 |
</h2> |
| 1311 |
<p id="section-2-1">"MPLS Control-Plane Client (MCC)" refers to any control-plane |
| 1312 |
protocol installing forwarding entries in the MPLS data plane. SR, LDP |
| 1313 |
<span>[<a href="#RFC5036" class="xref">RFC5036</a>]</span>, RSVP-TE <span>[<a href="#RFC3209" class="xref">RFC3209</a>]</span>, BGP <span>[<a href="#RFC8277" class="xref">RFC8277</a>]</span>, etc., are examples of MCCs.<a href="#section-2-1" class="pilcrow">¶</a></p> |
| 1314 |
<p id="section-2-2">An MCC, operating at Node N, must ensure that the incoming label it |
| 1315 |
installs in the MPLS data plane of Node N has been uniquely allocated to |
| 1316 |
itself.<a href="#section-2-2" class="pilcrow">¶</a></p> |
| 1317 |
<p id="section-2-3">Segment Routing makes use of the Segment Routing Global Block (SRGB, |
| 1318 |
as defined in <span>[<a href="#RFC8402" class="xref">RFC8402</a>]</span>) for the |
| 1319 |
label allocation. The use of the SRGB allows SR to coexist with any |
| 1320 |
other MCC.<a href="#section-2-3" class="pilcrow">¶</a></p> |
| 1321 |
<p id="section-2-4">This is clearly the case for the adjacency segment: it is a local |
| 1322 |
label allocated by the label manager, as is the case for any MCC.<a href="#section-2-4" class="pilcrow">¶</a></p> |
| 1323 |
<p id="section-2-5">This is clearly the case for the prefix segment: the label manager |
| 1324 |
allocates the SRGB set of labels to the SR MCC client, and the operator |
| 1325 |
ensures the unique allocation of each global prefix segment or label |
| 1326 |
within the allocated SRGB set.<a href="#section-2-5" class="pilcrow">¶</a></p> |
| 1327 |
<p id="section-2-6">Note that this static label-allocation capability of the label |
| 1328 |
manager has existed for many years across several vendors and is |
| 1329 |
therefore not new. Furthermore, note that the label manager's ability to |
| 1330 |
statically allocate a range of labels to a specific application is not |
| 1331 |
new either. This is required for MPLS-TP operation. In this case, the |
| 1332 |
range is reserved by the label manager, and it is the MPLS-TP <span>[<a href="#RFC5960" class="xref">RFC5960</a>]</span> Network Management System (acting as an MCC) that ensures the unique |
| 1333 |
allocation of any label within the allocated range and the creation of |
| 1334 |
the related MPLS forwarding entry.<a href="#section-2-6" class="pilcrow">¶</a></p> |
| 1335 |
<p id="section-2-7">Let us illustrate an example of ship-in-the-night (SIN) coexistence.<a href="#section-2-7" class="pilcrow">¶</a></p> |
| 1336 |
<span id="name-sin-coexistence"></span><div id="ref-sin-coexistence"> |
| 1337 |
<figure id="figure-1"> |
| 1338 |
<div class="artwork art-text alignLeft" id="section-2-8.1"> |
| 1339 |
<pre> |
| 1340 |
PE2 PE4 |
| 1341 |
\ / |
| 1342 |
PE1----A----B---C---PE3 |
| 1343 |
</pre> |
| 1344 |
</div> |
| 1345 |
<figcaption><a href="#figure-1" class="selfRef">Figure 1</a>: |
| 1346 |
<a href="#name-sin-coexistence" class="selfRef">SIN Coexistence</a> |
| 1347 |
</figcaption></figure> |
| 1348 |
</div> |
| 1349 |
<p id="section-2-9">The EVEN VPN service is supported by PE2 and PE4 while the ODD VPN |
| 1350 |
service is supported by PE1 and PE3. The operator wants to tunnel the |
| 1351 |
ODD service via LDP and the EVEN service via SR.<a href="#section-2-9" class="pilcrow">¶</a></p> |
| 1352 |
<p id="section-2-10">This can be achieved in the following manner:<a href="#section-2-10" class="pilcrow">¶</a></p> |
| 1353 |
<ul> |
| 1354 |
<li id="section-2-11.1">The operator configures PE1, PE2, PE3, and PE4 with respective loopbacks |
| 1355 |
192.0.2.201/32, 192.0.2.202/32, 192.0.2.203/32, and 192.0.2.204/32. These PEs |
| 1356 |
advertised their VPN routes with next hop set on their respective loopback |
| 1357 |
address.<a href="#section-2-11.1" class="pilcrow">¶</a> |
| 1358 |
</li> |
| 1359 |
<li id="section-2-11.2">The operator configures A, B, C with respective loopbacks 192.0.2.1/32, |
| 1360 |
192.0.2.2/32, 192.0.2.3/32.<a href="#section-2-11.2" class="pilcrow">¶</a> |
| 1361 |
</li> |
| 1362 |
<li id="section-2-11.3">The operator configures PE2, A, B, C, and PE4 with SRGB [100, 300].<a href="#section-2-11.3" class="pilcrow">¶</a> |
| 1363 |
</li> |
| 1364 |
<li id="section-2-11.4">The operator attaches the respective Node Segment Identifiers (Node SIDs, |
| 1365 |
as defined in <span>[<a href="#RFC8402" class="xref">RFC8402</a>]</span>), 202, 101, 102, 103, |
| 1366 |
and 204, to the loopbacks of nodes PE2, A, B, C, and PE4. The Node SIDs are |
| 1367 |
configured to request Penultimate Hop Popping.<a href="#section-2-11.4" class="pilcrow">¶</a> |
| 1368 |
</li> |
| 1369 |
<li id="section-2-11.5">PE1, A, B, C, and PE3 are LDP capable.<a href="#section-2-11.5" class="pilcrow">¶</a> |
| 1370 |
</li> |
| 1371 |
<li id="section-2-11.6">PE1 and PE3 are not SR capable.<a href="#section-2-11.6" class="pilcrow">¶</a> |
| 1372 |
</li> |
| 1373 |
</ul> |
| 1374 |
<p id="section-2-12">PE3 sends an ODD VPN route to PE1 with next-hop 192.0.2.203 and VPN |
| 1375 |
label 10001.<a href="#section-2-12" class="pilcrow">¶</a></p> |
| 1376 |
<p id="section-2-13">From an LDP viewpoint, PE1 received an LDP label binding (1037) for a |
| 1377 |
Forwarding Equivalence Class (FEC) 192.0.2.203/32 from its next-hop A; A |
| 1378 |
received an LDP label binding (2048) for that FEC from its next-hop B; B |
| 1379 |
received an LDP label binding (3059) for that FEC from its next-hop C; |
| 1380 |
and C received implicit NULL LDP binding from its next-hop PE3.<a href="#section-2-13" class="pilcrow">¶</a></p> |
| 1381 |
<p id="section-2-14">As a result, PE1 sends its traffic to the ODD service route |
| 1382 |
advertised by PE3 to next-hop A with two labels: the top label is 1037 |
| 1383 |
and the bottom label is 10001. Node A swaps 1037 with 2048 and forwards |
| 1384 |
to B; B swaps 2048 with 3059 and forwards to C; C pops 3059 and forwards |
| 1385 |
to PE3.<a href="#section-2-14" class="pilcrow">¶</a></p> |
| 1386 |
<p id="section-2-15">PE4 sends an EVEN VPN route to PE2 with next-hop 192.0.2.204 and VPN |
| 1387 |
label 10002.<a href="#section-2-15" class="pilcrow">¶</a></p> |
| 1388 |
<p id="section-2-16">From an SR viewpoint, PE2 maps the IGP route 192.0.2.204/32 onto |
| 1389 |
Node SID 204; Node A swaps 204 with 204 and forwards to B; B swaps 204 |
| 1390 |
with 204 and forwards to C; and C pops 204 and forwards to PE4.<a href="#section-2-16" class="pilcrow">¶</a></p> |
| 1391 |
<p id="section-2-17">As a result, PE2 sends its traffic to the VPN service route |
| 1392 |
advertised by PE4 to next-hop A with two labels: the top label is 204 |
| 1393 |
and the bottom label is 10002. Node A swaps 204 with 204 and forwards to |
| 1394 |
B. B swaps 204 with 204 and forwards to C. C pops 204 and forwards to |
| 1395 |
PE4.<a href="#section-2-17" class="pilcrow">¶</a></p> |
| 1396 |
<p id="section-2-18">The two modes of MPLS tunneling coexist.<a href="#section-2-18" class="pilcrow">¶</a></p> |
| 1397 |
<ul> |
| 1398 |
<li id="section-2-19.1">The ODD service is tunneled from PE1 to PE3 through a continuous LDP LSP |
| 1399 |
traversing A, B, and C.<a href="#section-2-19.1" class="pilcrow">¶</a> |
| 1400 |
</li> |
| 1401 |
<li id="section-2-19.2">The EVEN service is tunneled from PE2 to PE4 through a continuous SR node |
| 1402 |
segment traversing A, B, and C.<a href="#section-2-19.2" class="pilcrow">¶</a> |
| 1403 |
</li> |
| 1404 |
</ul> |
| 1405 |
<div id="sec-2.1"> |
| 1406 |
<section id="section-2.1"> |
| 1407 |
<h3 id="name-mpls2mpls-mpls2ip-and-ip2mp"> |
| 1408 |
<a href="#section-2.1" class="section-number selfRef">2.1. </a><a href="#name-mpls2mpls-mpls2ip-and-ip2mp" class="section-name selfRef">MPLS2MPLS, MPLS2IP, and IP2MPLS Coexistence</a> |
| 1409 |
</h3> |
| 1410 |
<p id="section-2.1-1">MPLS2MPLS refers to the forwarding behavior where a router receives |
| 1411 |
a labeled packet and switches it out as a labeled packet. Several |
| 1412 |
MPLS2MPLS entries may be installed in the data plane for the same |
| 1413 |
prefix.<a href="#section-2.1-1" class="pilcrow">¶</a></p> |
| 1414 |
<p id="section-2.1-2">Let us examine A's MPLS forwarding table as an example:<a href="#section-2.1-2" class="pilcrow">¶</a></p> |
| 1415 |
<ul class="ulEmpty"> |
| 1416 |
<li class="ulEmpty" id="section-2.1-3.1"> |
| 1417 |
<p id="section-2.1-3.1.1">Incoming label: 1037<a href="#section-2.1-3.1.1" class="pilcrow">¶</a></p> |
| 1418 |
<ul> |
| 1419 |
<li id="section-2.1-3.1.2.1">Outgoing label: 2048<a href="#section-2.1-3.1.2.1" class="pilcrow">¶</a> |
| 1420 |
</li> |
| 1421 |
<li id="section-2.1-3.1.2.2">Outgoing next hop: B<a href="#section-2.1-3.1.2.2" class="pilcrow">¶</a> |
| 1422 |
</li> |
| 1423 |
</ul> |
| 1424 |
<p id="section-2.1-3.1.3">Note: This entry is programmed by LDP for 192.0.2.203/32.<a href="#section-2.1-3.1.3" class="pilcrow">¶</a></p> |
| 1425 |
</li> |
| 1426 |
</ul> |
| 1427 |
<ul class="ulEmpty"> |
| 1428 |
<li class="ulEmpty" id="section-2.1-4.1"> |
| 1429 |
<p id="section-2.1-4.1.1">Incoming label: 203<a href="#section-2.1-4.1.1" class="pilcrow">¶</a></p> |
| 1430 |
<ul> |
| 1431 |
<li id="section-2.1-4.1.2.1">Outgoing label: 203<a href="#section-2.1-4.1.2.1" class="pilcrow">¶</a> |
| 1432 |
</li> |
| 1433 |
<li id="section-2.1-4.1.2.2">Outgoing next hop: B<a href="#section-2.1-4.1.2.2" class="pilcrow">¶</a> |
| 1434 |
</li> |
| 1435 |
</ul> |
| 1436 |
<p id="section-2.1-4.1.3">Note: This entry is programmed by SR for 192.0.2.203/32.<a href="#section-2.1-4.1.3" class="pilcrow">¶</a></p> |
| 1437 |
</li> |
| 1438 |
</ul> |
| 1439 |
<p id="section-2.1-5">These two entries can coexist because their incoming label is |
| 1440 |
unique. The uniqueness is guaranteed by the label manager allocation |
| 1441 |
rules.<a href="#section-2.1-5" class="pilcrow">¶</a></p> |
| 1442 |
<p id="section-2.1-6">The same applies for the MPLS2IP forwarding entries. MPLS2IP is the |
| 1443 |
forwarding behavior where a router receives a labeled IPv4/IPv6 packet |
| 1444 |
with one label only, pops the label, and switches the packet out as |
| 1445 |
IPv4/IPv6. For IP2MPLS coexistence, refer to <a href="#sec-7.1" class="xref">Section 6.1</a>.<a href="#section-2.1-6" class="pilcrow">¶</a></p> |
| 1446 |
</section> |
| 1447 |
</div> |
| 1448 |
</section> |
| 1449 |
</div> |
| 1450 |
<div id="sec-4"> |
| 1451 |
<section id="section-3"> |
| 1452 |
<h2 id="name-sr-and-ldp-interworking"> |
| 1453 |
<a href="#section-3" class="section-number selfRef">3. </a><a href="#name-sr-and-ldp-interworking" class="section-name selfRef">SR and LDP Interworking</a> |
| 1454 |
</h2> |
| 1455 |
<p id="section-3-1">This section analyzes the case where SR is available in one part of |
| 1456 |
the network and LDP is available in another part. It describes how a |
| 1457 |
continuous MPLS tunnel can be built throughout the network.<a href="#section-3-1" class="pilcrow">¶</a></p> |
| 1458 |
<span id="name-sr-and-ldp-interworking-2"></span><div id="ref-sr-and-ldp-interworking"> |
| 1459 |
<figure id="figure-2"> |
| 1460 |
<div class="artwork art-text alignLeft" id="section-3-2.1"> |
| 1461 |
<pre> |
| 1462 |
PE2 PE4 |
| 1463 |
\ / |
| 1464 |
PE1----P5--P6--P7--P8---PE3 |
| 1465 |
|
| 1466 |
<-----SR----> |
| 1467 |
<------LDP------> |
| 1468 |
</pre> |
| 1469 |
</div> |
| 1470 |
<figcaption><a href="#figure-2" class="selfRef">Figure 2</a>: |
| 1471 |
<a href="#name-sr-and-ldp-interworking-2" class="selfRef">SR and LDP Interworking</a> |
| 1472 |
</figcaption></figure> |
| 1473 |
</div> |
| 1474 |
<p id="section-3-3">Let us analyze the following example:<a href="#section-3-3" class="pilcrow">¶</a></p> |
| 1475 |
<ul> |
| 1476 |
<li id="section-3-4.1">P6, P7, P8, PE4, and PE3 are LDP capable.<a href="#section-3-4.1" class="pilcrow">¶</a> |
| 1477 |
</li> |
| 1478 |
<li id="section-3-4.2">PE1, PE2, P5, and P6 are SR capable. PE1, PE2, P5, and P6 are configured |
| 1479 |
with SRGB (100, 200) and with node segments 101, 102, 105, and 106, respectively.<a href="#section-3-4.2" class="pilcrow">¶</a> |
| 1480 |
</li> |
| 1481 |
<li id="section-3-4.3">A service flow must be tunneled from PE1 to PE3 over a continuous MPLS |
| 1482 |
tunnel encapsulation; therefore, SR and LDP need to interwork.<a href="#section-3-4.3" class="pilcrow">¶</a> |
| 1483 |
</li> |
| 1484 |
</ul> |
| 1485 |
<div id="sec-4.1"> |
| 1486 |
<section id="section-3.1"> |
| 1487 |
<h3 id="name-ldp-to-sr"> |
| 1488 |
<a href="#section-3.1" class="section-number selfRef">3.1. </a><a href="#name-ldp-to-sr" class="section-name selfRef">LDP to SR</a> |
| 1489 |
</h3> |
| 1490 |
<p id="section-3.1-1">In this section, a right-to-left traffic flow is analyzed.<a href="#section-3.1-1" class="pilcrow">¶</a></p> |
| 1491 |
<p id="section-3.1-2">PE3 has learned a service route whose next hop is PE1. PE3 has an |
| 1492 |
LDP label binding from the next-hop P8 for the FEC "PE1". Therefore, PE3 |
| 1493 |
sends its service packet to P8 as per classic LDP behavior.<a href="#section-3.1-2" class="pilcrow">¶</a></p> |
| 1494 |
<p id="section-3.1-3">P8 has an LDP label binding from its next-hop P7 for the FEC "PE1" |
| 1495 |
and therefore, P8 forwards to P7 as per classic LDP behavior.<a href="#section-3.1-3" class="pilcrow">¶</a></p> |
| 1496 |
<p id="section-3.1-4">P7 has an LDP label binding from its next-hop P6 for the FEC "PE1" |
| 1497 |
and therefore, P7 forwards to P6 as per classic LDP behavior.<a href="#section-3.1-4" class="pilcrow">¶</a></p> |
| 1498 |
<p id="section-3.1-5">P6 does not have an LDP binding from its next-hop P5 for the FEC |
| 1499 |
"PE1". However, P6 has an SR node segment to the IGP route "PE1". |
| 1500 |
Hence, P6 forwards the packet to P5 and swaps its local LDP label for |
| 1501 |
FEC "PE1" by the equivalent node segment (i.e., 101).<a href="#section-3.1-5" class="pilcrow">¶</a></p> |
| 1502 |
<p id="section-3.1-6">P5 pops 101 (assuming PE1 advertised its node segment 101 with the |
| 1503 |
penultimate-pop flag set) and forwards to PE1.<a href="#section-3.1-6" class="pilcrow">¶</a></p> |
| 1504 |
<p id="section-3.1-7">PE1 receives the tunneled packet and processes the service |
| 1505 |
label.<a href="#section-3.1-7" class="pilcrow">¶</a></p> |
| 1506 |
<p id="section-3.1-8">The end-to-end MPLS tunnel is built by stitching an LDP LSP from PE3 to P6 |
| 1507 |
and the related node segment from P6 to PE1.<a href="#section-3.1-8" class="pilcrow">¶</a></p> |
| 1508 |
<div id="sec-4.1.1"> |
| 1509 |
<section id="section-3.1.1"> |
| 1510 |
<h4 id="name-ldp-to-sr-behavior"> |
| 1511 |
<a href="#section-3.1.1" class="section-number selfRef">3.1.1. </a><a href="#name-ldp-to-sr-behavior" class="section-name selfRef">LDP to SR Behavior</a> |
| 1512 |
</h4> |
| 1513 |
<p id="section-3.1.1-1">It has to be noted that no additional signaling or state is |
| 1514 |
required in order to provide interworking in the direction LDP to |
| 1515 |
SR.<a href="#section-3.1.1-1" class="pilcrow">¶</a></p> |
| 1516 |
<p id="section-3.1.1-2">An SR node having LDP neighbors <span class="bcp14">MUST</span> create LDP bindings for each |
| 1517 |
Prefix-SID learned in the SR domain by treating SR-learned labels as |
| 1518 |
if they were learned through an LDP neighbor. In addition, for each |
| 1519 |
FEC, the SR node stitches the incoming LDP label to the outgoing SR |
| 1520 |
label. This has to be done in both LDP-independent and ordered label |
| 1521 |
distribution control modes as defined in <span>[<a href="#RFC5036" class="xref">RFC5036</a>]</span>.<a href="#section-3.1.1-2" class="pilcrow">¶</a></p> |
| 1522 |
</section> |
| 1523 |
</div> |
| 1524 |
</section> |
| 1525 |
</div> |
| 1526 |
<div id="sec-4.2"> |
| 1527 |
<section id="section-3.2"> |
| 1528 |
<h3 id="name-sr-to-ldp"> |
| 1529 |
<a href="#section-3.2" class="section-number selfRef">3.2. </a><a href="#name-sr-to-ldp" class="section-name selfRef">SR to LDP</a> |
| 1530 |
</h3> |
| 1531 |
<p id="section-3.2-1">In this section, the left-to-right traffic flow is analyzed.<a href="#section-3.2-1" class="pilcrow">¶</a></p> |
| 1532 |
<p id="section-3.2-2">This section defines the Segment Routing Mapping Server (SRMS). The |
| 1533 |
SRMS is an IGP node advertising mapping between Segment Identifiers |
| 1534 |
(SID) and prefixes advertised by other IGP nodes. The SRMS uses a |
| 1535 |
dedicated IGP extension (IS-IS, OSPFv2, and OSPFv3), which is protocol |
| 1536 |
specific and defined in <span>[<a href="#RFC8665" class="xref">RFC8665</a>]</span>, <span>[<a href="#RFC8666" class="xref">RFC8666</a>]</span>, and <span>[<a href="#RFC8667" class="xref">RFC8667</a>]</span>.<a href="#section-3.2-2" class="pilcrow">¶</a></p> |
| 1537 |
<p id="section-3.2-3">The SRMS function of an SR-capable router allows distribution of |
| 1538 |
mappings for prefixes not locally attached to the advertising router |
| 1539 |
and therefore allows advertisement of mappings on behalf of |
| 1540 |
non-SR-capable routers.<a href="#section-3.2-3" class="pilcrow">¶</a></p> |
| 1541 |
<p id="section-3.2-4">The SRMS is a control-plane-only function that may be located |
| 1542 |
anywhere in the IGP flooding scope. At least one SRMS server <span class="bcp14">MUST</span> |
| 1543 |
exist in a routing domain to advertise Prefix-SIDs on behalf of non‑SR |
| 1544 |
nodes, thereby allowing non-LDP routers to send and receive labeled |
| 1545 |
traffic from LDP-only routers. Multiple SRMSes may be present in the |
| 1546 |
same network (for redundancy). This implies that there are multiple |
| 1547 |
ways a prefix-to-SID mapping can be advertised. Conflicts resulting |
| 1548 |
from inconsistent advertisements are addressed by <span>[<a href="#RFC8660" class="xref">RFC8660</a>]</span>.<a href="#section-3.2-4" class="pilcrow">¶</a></p> |
| 1549 |
<p id="section-3.2-5">The example depicted in <a href="#ref-sr-and-ldp-interworking" class="xref">Figure 2</a> assumes that the operator |
| 1550 |
configures P5 to act as a Segment Routing Mapping Server and |
| 1551 |
advertises the following mappings: (P7, 107), (P8, 108), (PE3, 103), |
| 1552 |
and (PE4, 104).<a href="#section-3.2-5" class="pilcrow">¶</a></p> |
| 1553 |
<p id="section-3.2-6">The mappings advertised by one or more SRMSes result from local |
| 1554 |
policy information configured by the operator.<a href="#section-3.2-6" class="pilcrow">¶</a></p> |
| 1555 |
<p id="section-3.2-7">If PE3 had been SR capable, the operator would have configured PE3 |
| 1556 |
with node segment 103. Instead, as PE3 is not SR capable, the operator |
| 1557 |
configures that policy at the SRMS and it is the latter that |
| 1558 |
advertises the mapping.<a href="#section-3.2-7" class="pilcrow">¶</a></p> |
| 1559 |
<p id="section-3.2-8">The Mapping Server Advertisements are only understood by SR-capable |
| 1560 |
routers. The SR-capable routers install the related node segments in |
| 1561 |
the MPLS data plane exactly like the node segments had been advertised |
| 1562 |
by the nodes themselves.<a href="#section-3.2-8" class="pilcrow">¶</a></p> |
| 1563 |
<p id="section-3.2-9">For example, PE1 installs the node segment 103 with next-hop P5 |
| 1564 |
exactly as if PE3 had advertised node segment 103.<a href="#section-3.2-9" class="pilcrow">¶</a></p> |
| 1565 |
<p id="section-3.2-10">PE1 has a service route whose next hop is PE3. PE1 has a node |
| 1566 |
segment for that IGP route: 103 with next-hop P5. Hence, PE1 sends its |
| 1567 |
service packet to P5 with two labels: the bottom label is the service |
| 1568 |
label and the top label is 103.<a href="#section-3.2-10" class="pilcrow">¶</a></p> |
| 1569 |
<p id="section-3.2-11">P5 swaps 103 for 103 and forwards to P6.<a href="#section-3.2-11" class="pilcrow">¶</a></p> |
| 1570 |
<p id="section-3.2-12">P6's next hop for the IGP route "PE3" is not SR capable (P7 does |
| 1571 |
not advertise the SR capability). However, P6 has an LDP label binding |
| 1572 |
from that next hop for the same FEC (e.g., LDP label 1037). Hence, P6 |
| 1573 |
swaps 103 for 1037 and forwards to P7.<a href="#section-3.2-12" class="pilcrow">¶</a></p> |
| 1574 |
<p id="section-3.2-13">P7 swaps this label with the LDP label received from P8 and |
| 1575 |
forwards to P8.<a href="#section-3.2-13" class="pilcrow">¶</a></p> |
| 1576 |
<p id="section-3.2-14">P8 pops the LDP label and forwards to PE3.<a href="#section-3.2-14" class="pilcrow">¶</a></p> |
| 1577 |
<p id="section-3.2-15">PE3 receives the tunneled packet and processes the service |
| 1578 |
label.<a href="#section-3.2-15" class="pilcrow">¶</a></p> |
| 1579 |
<p id="section-3.2-16">The end-to-end MPLS tunnel is built by stitching an SR node segment from |
| 1580 |
PE1 to P6 and an LDP LSP from P6 to PE3.<a href="#section-3.2-16" class="pilcrow">¶</a></p> |
| 1581 |
<p id="section-3.2-17">SR-mapping advertisement for a given prefix provides no information |
| 1582 |
about Penultimate Hop Popping. Other mechanisms, such as IGP-specific |
| 1583 |
mechanisms (<span>[<a href="#RFC8665" class="xref">RFC8665</a>]</span>, |
| 1584 |
<span>[<a href="#RFC8666" class="xref">RFC8666</a>]</span>, and <span>[<a href="#RFC8667" class="xref">RFC8667</a>]</span>), <span class="bcp14">MAY</span> be |
| 1585 |
used to determine the Penultimate Hop Popping in such case.<a href="#section-3.2-17" class="pilcrow">¶</a></p> |
| 1586 |
<aside id="section-3.2-18"> |
| 1587 |
<p id="section-3.2-18.1">Note: In the previous example, Penultimate Hop Popping is not |
| 1588 |
performed at the SR-LDP border for segment 103 (PE3), because none of |
| 1589 |
the routers in the SR domain are Penultimate Hop for segment 103. In |
| 1590 |
this case, P6 requires the presence of the segment 103 such as to map |
| 1591 |
it to the LDP label 1037.<a href="#section-3.2-18.1" class="pilcrow">¶</a></p> |
| 1592 |
</aside> |
| 1593 |
<div id="sec-4.2.1"> |
| 1594 |
<section id="section-3.2.1"> |
| 1595 |
<h4 id="name-segment-routing-mapping-ser"> |
| 1596 |
<a href="#section-3.2.1" class="section-number selfRef">3.2.1. </a><a href="#name-segment-routing-mapping-ser" class="section-name selfRef">Segment Routing Mapping Server (SRMS)</a> |
| 1597 |
</h4> |
| 1598 |
<p id="section-3.2.1-1">This section specifies the concept and externally visible |
| 1599 |
functionality of a Segment Routing Mapping Server (SRMS).<a href="#section-3.2.1-1" class="pilcrow">¶</a></p> |
| 1600 |
<p id="section-3.2.1-2">The purpose of SRMS functionality is to support the |
| 1601 |
advertisement of Prefix-SIDs to a prefix without the need to |
| 1602 |
explicitly advertise such assignment within a prefix reachability |
| 1603 |
advertisement. Examples of explicit Prefix-SID Advertisement are the |
| 1604 |
Prefix-SID sub-TLVs defined in <span>[<a href="#RFC8665" class="xref">RFC8665</a>]</span>, <span>[<a href="#RFC8666" class="xref">RFC8666</a>]</span>, and <span>[<a href="#RFC8667" class="xref">RFC8667</a>]</span>.<a href="#section-3.2.1-2" class="pilcrow">¶</a></p> |
| 1605 |
<p id="section-3.2.1-3">The SRMS functionality allows assigning of Prefix-SIDs to |
| 1606 |
prefixes owned by non-SR-capable routers as well as to prefixes |
| 1607 |
owned by SR-capable nodes. It is the former capability that is |
| 1608 |
essential to the SR-LDP interworking described later in this |
| 1609 |
section.<a href="#section-3.2.1-3" class="pilcrow">¶</a></p> |
| 1610 |
<p id="section-3.2.1-4">The SRMS functionality consists of two functional blocks: the |
| 1611 |
Mapping Server (MS) and Mapping Client (MC).<a href="#section-3.2.1-4" class="pilcrow">¶</a></p> |
| 1612 |
<p id="section-3.2.1-5">An MS is a node that advertises an SR mappings. Advertisements |
| 1613 |
sent by an MS define the assignment of a Prefix-SID to a prefix |
| 1614 |
independent of the advertisement of reachability to the prefix |
| 1615 |
itself. An MS <span class="bcp14">MAY</span> advertise SR mappings for any prefix whether or |
| 1616 |
not it advertises reachability for the prefix and irrespective of |
| 1617 |
whether that prefix is advertised by or even reachable through any |
| 1618 |
router in the network.<a href="#section-3.2.1-5" class="pilcrow">¶</a></p> |
| 1619 |
<p id="section-3.2.1-6">An MC is a node that receives and uses the MS mapping |
| 1620 |
advertisements. Note that a node may be both an MS and an MC. An MC |
| 1621 |
interprets the SR-mapping advertisement as an assignment of a |
| 1622 |
Prefix-SID to a prefix. For a given prefix, if an MC receives an |
| 1623 |
SR-mapping advertisement from a Mapping Server and also has received |
| 1624 |
a Prefix-SID Advertisement for that same prefix in a prefix |
| 1625 |
reachability advertisement, then the MC <span class="bcp14">MUST</span> prefer the SID |
| 1626 |
advertised in the prefix reachability advertisement over the |
| 1627 |
Mapping Server Advertisement, i.e., the Mapping Server Advertisement |
| 1628 |
<span class="bcp14">MUST</span> be ignored for that prefix. Hence, assigning a Prefix-SID to a |
| 1629 |
prefix using the SRMS functionality does not preclude assigning the |
| 1630 |
same or different Prefix-SID(s) to the same prefix using explicit |
| 1631 |
Prefix-SID Advertisement such as the aforementioned Prefix-SID |
| 1632 |
sub-TLVs.<a href="#section-3.2.1-6" class="pilcrow">¶</a></p> |
| 1633 |
<p id="section-3.2.1-7">For example, consider an IPv4 prefix advertisement received by an |
| 1634 |
IS‑IS router in the Extended IP reachability TLV (TLV 135). Suppose |
| 1635 |
TLV 135 contained the Prefix-SID sub-TLV. If the router that |
| 1636 |
receives TLV 135 with the Prefix-SID sub-TLV also received an |
| 1637 |
SR-mapping advertisement for the same prefix through the |
| 1638 |
SID/Label Binding TLV, then the receiving router must prefer the |
| 1639 |
Prefix-SID sub-TLV over the SID/Label Binding TLV for that |
| 1640 |
prefix. Refer to <span>[<a href="#RFC8667" class="xref">RFC8667</a>]</span> for details |
| 1641 |
about the Prefix-SID sub-TLV and SID/Label Binding TLV.<a href="#section-3.2.1-7" class="pilcrow">¶</a></p> |
| 1642 |
</section> |
| 1643 |
</div> |
| 1644 |
<div id="sec-4.2.2"> |
| 1645 |
<section id="section-3.2.2"> |
| 1646 |
<h4 id="name-sr-to-ldp-behavior"> |
| 1647 |
<a href="#section-3.2.2" class="section-number selfRef">3.2.2. </a><a href="#name-sr-to-ldp-behavior" class="section-name selfRef">SR to LDP Behavior</a> |
| 1648 |
</h4> |
| 1649 |
<p id="section-3.2.2-1">SR to LDP interworking requires an SRMS as defined above.<a href="#section-3.2.2-1" class="pilcrow">¶</a></p> |
| 1650 |
<p id="section-3.2.2-2">Each SR-capable router installs in the MPLS data-plane Node SIDs |
| 1651 |
learned from the SRMS exactly as if these SIDs had been advertised |
| 1652 |
by the nodes themselves.<a href="#section-3.2.2-2" class="pilcrow">¶</a></p> |
| 1653 |
<p id="section-3.2.2-3">An SR node having LDP-only neighbors <span class="bcp14">MUST</span> stitch the incoming SR label |
| 1654 |
(whose SID is advertised by the SRMS) to the outgoing LDP label.<a href="#section-3.2.2-3" class="pilcrow">¶</a></p> |
| 1655 |
<p id="section-3.2.2-4">It has to be noted that the SR to LDP behavior does not propagate |
| 1656 |
the status of the LDP FEC that was signaled by LDP when configured |
| 1657 |
in ordered mode.<a href="#section-3.2.2-4" class="pilcrow">¶</a></p> |
| 1658 |
<p id="section-3.2.2-5">It has to be noted that in the case of SR to LDP, the label |
| 1659 |
binding is equivalent to the independent LDP Label Distribution |
| 1660 |
Control Mode <span>[<a href="#RFC5036" class="xref">RFC5036</a>]</span> where a label is bound to a |
| 1661 |
FEC independently from the received binding for the same FEC.<a href="#section-3.2.2-5" class="pilcrow">¶</a></p> |
| 1662 |
</section> |
| 1663 |
</div> |
| 1664 |
<div id="sec-4.2.3"> |
| 1665 |
<section id="section-3.2.3"> |
| 1666 |
<h4 id="name-interoperability-of-multipl"> |
| 1667 |
<a href="#section-3.2.3" class="section-number selfRef">3.2.3. </a><a href="#name-interoperability-of-multipl" class="section-name selfRef">Interoperability of Multiple SRMSes and Prefix-SID Advertisements</a> |
| 1668 |
</h4> |
| 1669 |
<p id="section-3.2.3-1">In the case of SR-LDP interoperability through the use of an SRMS, |
| 1670 |
mappings are advertised by one or more SRMSes.<a href="#section-3.2.3-1" class="pilcrow">¶</a></p> |
| 1671 |
<p id="section-3.2.3-2">SRMS functionality is implemented in the link-state protocol (such as |
| 1672 |
IS-IS and OSPF). Link-state protocols allow propagation of updates |
| 1673 |
across area boundaries and, therefore, SRMS advertisements are |
| 1674 |
propagated through the usual inter-area advertisement procedures in |
| 1675 |
link-state protocols.<a href="#section-3.2.3-2" class="pilcrow">¶</a></p> |
| 1676 |
<p id="section-3.2.3-3">Multiple SRMSes can be provisioned in a network for redundancy. |
| 1677 |
Moreover, a preference mechanism may also be used among SRMSes to |
| 1678 |
deploy a primary/secondary SRMS scheme allowing controlled |
| 1679 |
modification or migration of SIDs.<a href="#section-3.2.3-3" class="pilcrow">¶</a></p> |
| 1680 |
<p id="section-3.2.3-4">The content of SRMS advertisement (i.e., mappings) are a matter |
| 1681 |
of local policy determined by the operator. When multiple SRMSes are |
| 1682 |
active, it is necessary that the information (mappings) advertised |
| 1683 |
by the different SRMSes is aligned and consistent. The following |
| 1684 |
mechanism is applied to determine the preference of SRMS |
| 1685 |
advertisements:<a href="#section-3.2.3-4" class="pilcrow">¶</a></p> |
| 1686 |
<p id="section-3.2.3-5">If a node acts as an SRMS, it <span class="bcp14">MAY</span> advertise a preference to be |
| 1687 |
associated with all SRMS SID Advertisements sent by that node. The |
| 1688 |
means of advertising the preference is defined in the |
| 1689 |
protocol-specific documents, e.g., <span>[<a href="#RFC8665" class="xref">RFC8665</a>]</span>, <span>[<a href="#RFC8666" class="xref">RFC8666</a>]</span>, and <span>[<a href="#RFC8667" class="xref">RFC8667</a>]</span>. The |
| 1690 |
preference value is an unsigned 8-bit integer with the following |
| 1691 |
properties:<a href="#section-3.2.3-5" class="pilcrow">¶</a></p> |
| 1692 |
<div id="table_1"> |
| 1693 |
<table class="center" id="table-1"> |
| 1694 |
<caption><a href="#table-1" class="selfRef">Table 1</a></caption> |
| 1695 |
<tbody> |
| 1696 |
<tr> |
| 1697 |
<td class="text-center" rowspan="1" colspan="1">0</td> |
| 1698 |
<td class="text-left" rowspan="1" colspan="1">Reserved value indicating advertisements from that |
| 1699 |
node <span class="bcp14">MUST NOT</span> be used</td> |
| 1700 |
</tr> |
| 1701 |
<tr> |
| 1702 |
<td class="text-center" rowspan="1" colspan="1">1-255</td> |
| 1703 |
<td class="text-left" rowspan="1" colspan="1">Preference value (255 is most preferred)</td> |
| 1704 |
</tr> |
| 1705 |
</tbody> |
| 1706 |
</table> |
| 1707 |
</div> |
| 1708 |
<p id="section-3.2.3-7">Advertisement of a preference value is optional. Nodes |
| 1709 |
that do not advertise a preference value are assigned a preference |
| 1710 |
value of 128.<a href="#section-3.2.3-7" class="pilcrow">¶</a></p> |
| 1711 |
<p id="section-3.2.3-8">An MCC on a node receiving one or more SRMS mapping advertisements |
| 1712 |
applies them as follows:<a href="#section-3.2.3-8" class="pilcrow">¶</a></p> |
| 1713 |
<ul> |
| 1714 |
<li id="section-3.2.3-9.1">For any prefix for which it did not receive a Prefix-SID |
| 1715 |
Advertisement, the MCC applies the SRMS mapping advertisements |
| 1716 |
with the highest preference. The mechanism by which a Prefix-SID |
| 1717 |
is advertised for a given prefix is defined in the protocol |
| 1718 |
specifications <span>[<a href="#RFC8665" class="xref">RFC8665</a>]</span>, |
| 1719 |
<span>[<a href="#RFC8666" class="xref">RFC8666</a>]</span>, and |
| 1720 |
<span>[<a href="#RFC8667" class="xref">RFC8667</a>]</span>.<a href="#section-3.2.3-9.1" class="pilcrow">¶</a> |
| 1721 |
</li> |
| 1722 |
<li id="section-3.2.3-9.2">If there is an incoming label collision as specified in <span>[<a href="#RFC8660" class="xref">RFC8660</a>]</span>, apply the |
| 1723 |
steps specified in <span>[<a href="#RFC8660" class="xref">RFC8660</a>]</span> to resolve the |
| 1724 |
collision.<a href="#section-3.2.3-9.2" class="pilcrow">¶</a> |
| 1725 |
</li> |
| 1726 |
</ul> |
| 1727 |
<p id="section-3.2.3-10">When the SRMS advertises mappings, an implementation should |
| 1728 |
provide a mechanism through which the operator determines which of |
| 1729 |
the IP2MPLS mappings are preferred among the one advertised by the |
| 1730 |
SRMS and the ones advertised by LDP.<a href="#section-3.2.3-10" class="pilcrow">¶</a></p> |
| 1731 |
</section> |
| 1732 |
</div> |
| 1733 |
</section> |
| 1734 |
</div> |
| 1735 |
</section> |
| 1736 |
</div> |
| 1737 |
<div id="sec-5"> |
| 1738 |
<section id="section-4"> |
| 1739 |
<h2 id="name-sr-ldp-interworking-use-cas"> |
| 1740 |
<a href="#section-4" class="section-number selfRef">4. </a><a href="#name-sr-ldp-interworking-use-cas" class="section-name selfRef">SR-LDP Interworking Use Cases</a> |
| 1741 |
</h2> |
| 1742 |
<p id="section-4-1">SR can be deployed, for example, to enhance LDP transport. The SR |
| 1743 |
deployment can be limited to the network region where the SR benefits |
| 1744 |
are most desired.<a href="#section-4-1" class="pilcrow">¶</a></p> |
| 1745 |
<div id="sec-5.1"> |
| 1746 |
<section id="section-4.1"> |
| 1747 |
<h3 id="name-sr-protection-of-ldp-based-"> |
| 1748 |
<a href="#section-4.1" class="section-number selfRef">4.1. </a><a href="#name-sr-protection-of-ldp-based-" class="section-name selfRef">SR Protection of LDP-Based Traffic</a> |
| 1749 |
</h3> |
| 1750 |
<p id="section-4.1-1">In <a href="#ref-sr-ldp-interworking-example" class="xref">Figure 3</a>, let us assume:<a href="#section-4.1-1" class="pilcrow">¶</a></p> |
| 1751 |
<ul> |
| 1752 |
<li id="section-4.1-2.1"> |
| 1753 |
All link costs are 10 except FG, which is 30.<a href="#section-4.1-2.1" class="pilcrow">¶</a> |
| 1754 |
</li> |
| 1755 |
<li id="section-4.1-2.2"> All routers are LDP capable.<a href="#section-4.1-2.2" class="pilcrow">¶</a> |
| 1756 |
</li> |
| 1757 |
<li id="section-4.1-2.3"> X, Y, and Z are PEs participating in an important service S.<a href="#section-4.1-2.3" class="pilcrow">¶</a> |
| 1758 |
</li> |
| 1759 |
<li id="section-4.1-2.4"> The operator requires 50 msec link-based Fast Reroute (FRR) for service S.<a href="#section-4.1-2.4" class="pilcrow">¶</a> |
| 1760 |
</li> |
| 1761 |
<li id="section-4.1-2.5"> A, B, C, D, E, F, and G are SR capable.<a href="#section-4.1-2.5" class="pilcrow">¶</a> |
| 1762 |
</li> |
| 1763 |
<li id="section-4.1-2.6"> X, Y, and Z are not SR capable, e.g., as part of a |
| 1764 |
staged migration from LDP to SR, the operator deploys SR first in |
| 1765 |
a subpart of the network and then everywhere.<a href="#section-4.1-2.6" class="pilcrow">¶</a> |
| 1766 |
</li> |
| 1767 |
</ul> |
| 1768 |
<span id="name-sr-ldp-interworking-example"></span><div id="ref-sr-ldp-interworking-example"> |
| 1769 |
<figure id="figure-3"> |
| 1770 |
<div class="artwork art-text alignLeft" id="section-4.1-3.1"> |
| 1771 |
<pre> |
| 1772 |
X |
| 1773 |
| |
| 1774 |
Y--A---B---E--Z |
| 1775 |
| | \ |
| 1776 |
D---C--F--G |
| 1777 |
30 |
| 1778 |
</pre> |
| 1779 |
</div> |
| 1780 |
<figcaption><a href="#figure-3" class="selfRef">Figure 3</a>: |
| 1781 |
<a href="#name-sr-ldp-interworking-example" class="selfRef">SR-LDP Interworking Example</a> |
| 1782 |
</figcaption></figure> |
| 1783 |
</div> |
| 1784 |
<p id="section-4.1-4">The operator would like to resolve the following issues:<a href="#section-4.1-4" class="pilcrow">¶</a></p> |
| 1785 |
<ul> |
| 1786 |
<li id="section-4.1-5.1">To protect the link BA along the shortest-path of the important flow XY, |
| 1787 |
B requires a Remote Loop-Free Alternate (RLFA; see <span>[<a href="#RFC7490" class="xref">RFC7490</a>]</span>) repair tunnel to D and, therefore, a targeted LDP session |
| 1788 |
from B to D. Typically, network operators prefer avoiding these dynamically |
| 1789 |
established multi-hop LDP sessions in order to reduce the number of protocols |
| 1790 |
running in the network and, therefore, simplify network operations.<a href="#section-4.1-5.1" class="pilcrow">¶</a> |
| 1791 |
</li> |
| 1792 |
<li id="section-4.1-5.2">There is no LFA/RLFA solution to protect the link BE along the shortest |
| 1793 |
path of the important flow XZ. The operator wants a guaranteed link-based FRR solution.<a href="#section-4.1-5.2" class="pilcrow">¶</a> |
| 1794 |
</li> |
| 1795 |
</ul> |
| 1796 |
<p id="section-4.1-6">The operator can meet these objectives by deploying SR only on A, |
| 1797 |
B, C, D, E, F, and G:<a href="#section-4.1-6" class="pilcrow">¶</a></p> |
| 1798 |
<ul> |
| 1799 |
<li id="section-4.1-7.1">The operator configures A, B, C, D, E, F, and G with SRGB [100, 200] and |
| 1800 |
with node segments 101, 102, 103, 104, 105, 106, and 107, respectively.<a href="#section-4.1-7.1" class="pilcrow">¶</a> |
| 1801 |
</li> |
| 1802 |
<li id="section-4.1-7.2">The operator configures D as an SR Mapping Server with the following |
| 1803 |
policy mapping: (X, 201), (Y, 202), and (Z, 203).<a href="#section-4.1-7.2" class="pilcrow">¶</a> |
| 1804 |
</li> |
| 1805 |
<li id="section-4.1-7.3">Each SR node automatically advertises a local adjacency segment for its |
| 1806 |
IGP adjacencies. Specifically, F advertises adjacency segment 9001 for its |
| 1807 |
adjacency FG.<a href="#section-4.1-7.3" class="pilcrow">¶</a> |
| 1808 |
</li> |
| 1809 |
</ul> |
| 1810 |
<p id="section-4.1-8">A, B, C, D, E, F, and G keep their LDP capability. Therefore, the |
| 1811 |
flows XY and XZ are transported over end-to-end LDP LSPs.<a href="#section-4.1-8" class="pilcrow">¶</a></p> |
| 1812 |
<p id="section-4.1-9">For example, LDP at B installs the following MPLS data-plane |
| 1813 |
entries:<a href="#section-4.1-9" class="pilcrow">¶</a></p> |
| 1814 |
<ul class="ulEmpty"> |
| 1815 |
<li class="ulEmpty" id="section-4.1-10.1"> |
| 1816 |
<p id="section-4.1-10.1.1">Incoming label: local LDP label bound by B for FEC Y<a href="#section-4.1-10.1.1" class="pilcrow">¶</a></p> |
| 1817 |
<ul> |
| 1818 |
<li id="section-4.1-10.1.2.1">Outgoing label: LDP label bound by A for FEC Y<a href="#section-4.1-10.1.2.1" class="pilcrow">¶</a> |
| 1819 |
</li> |
| 1820 |
<li id="section-4.1-10.1.2.2">Outgoing next hop: A<a href="#section-4.1-10.1.2.2" class="pilcrow">¶</a> |
| 1821 |
</li> |
| 1822 |
</ul> |
| 1823 |
</li> |
| 1824 |
<li class="ulEmpty" id="section-4.1-10.2"> |
| 1825 |
<p id="section-4.1-10.2.1">Incoming label: local LDP label bound by B for FEC Z<a href="#section-4.1-10.2.1" class="pilcrow">¶</a></p> |
| 1826 |
<ul> |
| 1827 |
<li id="section-4.1-10.2.2.1">Outgoing label: LDP label bound by E for FEC Z<a href="#section-4.1-10.2.2.1" class="pilcrow">¶</a> |
| 1828 |
</li> |
| 1829 |
<li id="section-4.1-10.2.2.2">Outgoing next hop: E<a href="#section-4.1-10.2.2.2" class="pilcrow">¶</a> |
| 1830 |
</li> |
| 1831 |
</ul> |
| 1832 |
</li> |
| 1833 |
</ul> |
| 1834 |
<p id="section-4.1-11">The novelty comes from how the backup chains are computed for these |
| 1835 |
LDP-based entries. While LDP labels are used for the primary next- hop |
| 1836 |
and outgoing labels, SR information is used for the FRR construction. |
| 1837 |
In steady state, the traffic is transported over LDP LSP. In transient |
| 1838 |
FRR state, the traffic is backup thanks to the SR-enhanced |
| 1839 |
capabilities.<a href="#section-4.1-11" class="pilcrow">¶</a></p> |
| 1840 |
<p id="section-4.1-12">The RLFA paths are dynamically precomputed as defined in <span>[<a href="#RFC7490" class="xref">RFC7490</a>]</span>. Typically, implementations allow to enable an RLFA |
| 1841 |
mechanism through a simple configuration command that triggers both |
| 1842 |
the precomputation and installation of the repair path. The details |
| 1843 |
on how RLFA mechanisms are implemented and configured is outside the |
| 1844 |
scope of this document and not relevant to the aspects of SR-LDP |
| 1845 |
interwork explained in this document.<a href="#section-4.1-12" class="pilcrow">¶</a></p> |
| 1846 |
<p id="section-4.1-13">This helps meet the requirements of the operator:<a href="#section-4.1-13" class="pilcrow">¶</a></p> |
| 1847 |
<ul> |
| 1848 |
<li id="section-4.1-14.1">Eliminate targeted LDP sessions.<a href="#section-4.1-14.1" class="pilcrow">¶</a> |
| 1849 |
</li> |
| 1850 |
<li id="section-4.1-14.2">Provide guaranteed FRR coverage.<a href="#section-4.1-14.2" class="pilcrow">¶</a> |
| 1851 |
</li> |
| 1852 |
<li id="section-4.1-14.3">Keep the traffic over LDP LSP in steady state.<a href="#section-4.1-14.3" class="pilcrow">¶</a> |
| 1853 |
</li> |
| 1854 |
<li id="section-4.1-14.4">Partially deploy SR only where needed.<a href="#section-4.1-14.4" class="pilcrow">¶</a> |
| 1855 |
</li> |
| 1856 |
</ul> |
| 1857 |
</section> |
| 1858 |
</div> |
| 1859 |
<div id="sec-5.2"> |
| 1860 |
<section id="section-4.2"> |
| 1861 |
<h3 id="name-eliminating-targeted-ldp-se"> |
| 1862 |
<a href="#section-4.2" class="section-number selfRef">4.2. </a><a href="#name-eliminating-targeted-ldp-se" class="section-name selfRef">Eliminating Targeted LDP Sessions</a> |
| 1863 |
</h3> |
| 1864 |
<p id="section-4.2-1">B's MPLS entry to Y becomes:<a href="#section-4.2-1" class="pilcrow">¶</a></p> |
| 1865 |
<ul class="ulEmpty"> |
| 1866 |
<li class="ulEmpty" id="section-4.2-2.1"> |
| 1867 |
<p id="section-4.2-2.1.1">Incoming label: local LDP label bound by B for FEC Y<a href="#section-4.2-2.1.1" class="pilcrow">¶</a></p> |
| 1868 |
<ul> |
| 1869 |
<li id="section-4.2-2.1.2.1">Outgoing label: LDP label bound by A for FEC Y<a href="#section-4.2-2.1.2.1" class="pilcrow">¶</a> |
| 1870 |
</li> |
| 1871 |
<li id="section-4.2-2.1.2.2">Backup outgoing label: SR node segment for Y {202}<a href="#section-4.2-2.1.2.2" class="pilcrow">¶</a> |
| 1872 |
</li> |
| 1873 |
<li id="section-4.2-2.1.2.3">Outgoing next hop: A<a href="#section-4.2-2.1.2.3" class="pilcrow">¶</a> |
| 1874 |
</li> |
| 1875 |
<li id="section-4.2-2.1.2.4">Backup next hop: repair tunnel: node segment to D {104} with outgoing |
| 1876 |
next hop: C<a href="#section-4.2-2.1.2.4" class="pilcrow">¶</a> |
| 1877 |
</li> |
| 1878 |
</ul> |
| 1879 |
</li> |
| 1880 |
</ul> |
| 1881 |
<p id="section-4.2-3">It has to be noted that D is selected as a Remote Loop-Free Alternate |
| 1882 |
(RLFA) as defined in <span>[<a href="#RFC7490" class="xref">RFC7490</a>]</span>.<a href="#section-4.2-3" class="pilcrow">¶</a></p> |
| 1883 |
<p id="section-4.2-4">In steady state, X sends its Y-destined traffic to B with a top |
| 1884 |
label, which is the LDP label bound by B for FEC Y. B swaps that top |
| 1885 |
label for the LDP label bound by A for FEC Y and forwards to A. A pops |
| 1886 |
the LDP label and forwards to Y.<a href="#section-4.2-4" class="pilcrow">¶</a></p> |
| 1887 |
<p id="section-4.2-5">Upon failure of the link BA, B swaps the incoming top label with |
| 1888 |
the node segment for Y (202) and sends the packet onto a repair tunnel |
| 1889 |
to D (node segment 104). Thus, B sends the packet to C with the label |
| 1890 |
stack {104, 202}. C pops the node segment 104 and forwards to D. D |
| 1891 |
swaps 202 for 202 and forwards to A. A's next hop to Y is not SR |
| 1892 |
capable, and therefore, Node A swaps the incoming node segment 202 to the |
| 1893 |
LDP label announced by its next hop (in this case, implicit NULL).<a href="#section-4.2-5" class="pilcrow">¶</a></p> |
| 1894 |
<p id="section-4.2-6">After IGP convergence, B's MPLS entry to Y will become:<a href="#section-4.2-6" class="pilcrow">¶</a></p> |
| 1895 |
<ul class="ulEmpty"> |
| 1896 |
<li class="ulEmpty" id="section-4.2-7.1"> |
| 1897 |
<p id="section-4.2-7.1.1">Incoming label: local LDP label bound by B for FEC Y<a href="#section-4.2-7.1.1" class="pilcrow">¶</a></p> |
| 1898 |
<ul> |
| 1899 |
<li id="section-4.2-7.1.2.1">Outgoing label: LDP label bound by C for FEC Y<a href="#section-4.2-7.1.2.1" class="pilcrow">¶</a> |
| 1900 |
</li> |
| 1901 |
<li id="section-4.2-7.1.2.2">Outgoing next hop: C<a href="#section-4.2-7.1.2.2" class="pilcrow">¶</a> |
| 1902 |
</li> |
| 1903 |
</ul> |
| 1904 |
</li> |
| 1905 |
</ul> |
| 1906 |
<p id="section-4.2-8">And the traffic XY travels again over the LDP LSP.<a href="#section-4.2-8" class="pilcrow">¶</a></p> |
| 1907 |
<p id="section-4.2-9">Conclusion: the operator has eliminated the need for targeted LDP |
| 1908 |
sessions (no longer required) and the steady-state traffic is still |
| 1909 |
transported over LDP. The SR deployment is confined to the area where |
| 1910 |
these benefits are required.<a href="#section-4.2-9" class="pilcrow">¶</a></p> |
| 1911 |
<p id="section-4.2-10">Despite that, in general, an implementation would not require a |
| 1912 |
manual configuration of targeted LDP sessions. However, it is always a |
| 1913 |
gain if the operator is able to reduce the set of protocol sessions |
| 1914 |
running on the network infrastructure.<a href="#section-4.2-10" class="pilcrow">¶</a></p> |
| 1915 |
</section> |
| 1916 |
</div> |
| 1917 |
<div id="sec-5.3"> |
| 1918 |
<section id="section-4.3"> |
| 1919 |
<h3 id="name-guaranteed-frr-coverage"> |
| 1920 |
<a href="#section-4.3" class="section-number selfRef">4.3. </a><a href="#name-guaranteed-frr-coverage" class="section-name selfRef">Guaranteed FRR Coverage</a> |
| 1921 |
</h3> |
| 1922 |
<p id="section-4.3-1">As mentioned in <a href="#sec-5.1" class="xref">Section 4.1</a>, in the example |
| 1923 |
topology described in <a href="#ref-sr-ldp-interworking-example" class="xref">Figure 3</a>, there is no RLFA-based solution for |
| 1924 |
protecting the traffic flow YZ against the failure of link BE because |
| 1925 |
there is no intersection between the extended P-space and Q-space (see |
| 1926 |
<span>[<a href="#RFC7490" class="xref">RFC7490</a>]</span> for details). However:<a href="#section-4.3-1" class="pilcrow">¶</a></p> |
| 1927 |
<ul> |
| 1928 |
<li id="section-4.3-2.1">G belongs to the Q space of Z.<a href="#section-4.3-2.1" class="pilcrow">¶</a> |
| 1929 |
</li> |
| 1930 |
<li id="section-4.3-2.2">G can be reached from B via a "repair SR path" {106, 9001} that |
| 1931 |
is not affected by failure of link BE. (The method by which G and |
| 1932 |
the repair tunnel to it from B are identified are outside the scope of |
| 1933 |
this document.)<a href="#section-4.3-2.2" class="pilcrow">¶</a> |
| 1934 |
</li> |
| 1935 |
</ul> |
| 1936 |
<p id="section-4.3-3">B's MPLS entry to Z becomes:<a href="#section-4.3-3" class="pilcrow">¶</a></p> |
| 1937 |
<ul class="ulEmpty"> |
| 1938 |
<li class="ulEmpty" id="section-4.3-4.1"> |
| 1939 |
<p id="section-4.3-4.1.1">Incoming label: local LDP label bound by B for FEC Z<a href="#section-4.3-4.1.1" class="pilcrow">¶</a></p> |
| 1940 |
<ul> |
| 1941 |
<li id="section-4.3-4.1.2.1">Outgoing label: LDP label bound by E for FEC Z<a href="#section-4.3-4.1.2.1" class="pilcrow">¶</a> |
| 1942 |
</li> |
| 1943 |
<li id="section-4.3-4.1.2.2">Backup outgoing label: SR node segment for Z {203}<a href="#section-4.3-4.1.2.2" class="pilcrow">¶</a> |
| 1944 |
</li> |
| 1945 |
<li id="section-4.3-4.1.2.3">Outgoing next hop: E<a href="#section-4.3-4.1.2.3" class="pilcrow">¶</a> |
| 1946 |
</li> |
| 1947 |
<li id="section-4.3-4.1.2.4">Backup next hop: repair tunnel to G: {106, 9001}<a href="#section-4.3-4.1.2.4" class="pilcrow">¶</a> |
| 1948 |
</li> |
| 1949 |
</ul> |
| 1950 |
</li> |
| 1951 |
</ul> |
| 1952 |
<ul class="ulEmpty"> |
| 1953 |
<li class="ulEmpty" id="section-4.3-5.1"> |
| 1954 |
G is reachable from B via the combination of a |
| 1955 |
node segment to F {106} and an adjacency segment |
| 1956 |
FG {9001}.<a href="#section-4.3-5.1" class="pilcrow">¶</a> |
| 1957 |
</li> |
| 1958 |
<li class="ulEmpty" id="section-4.3-5.2"> |
| 1959 |
Note that {106, 107} would have equally worked. |
| 1960 |
Indeed, in many cases, P's shortest path to Q is |
| 1961 |
over the link PQ. The adjacency segment from P to |
| 1962 |
Q is required only in very rare topologies where |
| 1963 |
the shortest-path from P to Q is not via the link |
| 1964 |
PQ.<a href="#section-4.3-5.2" class="pilcrow">¶</a> |
| 1965 |
</li> |
| 1966 |
</ul> |
| 1967 |
<p id="section-4.3-6"> |
| 1968 |
|
| 1969 |
In steady state, X sends its Z-destined traffic to B with a top |
| 1970 |
label, which is the LDP label bound by B for FEC Z. B swaps that top |
| 1971 |
label for the LDP label bound by E for FEC Z and forwards to E. E pops |
| 1972 |
the LDP label and forwards to Z.<a href="#section-4.3-6" class="pilcrow">¶</a></p> |
| 1973 |
<p id="section-4.3-7">Upon failure of the link BE, B swaps the incoming top label with |
| 1974 |
the node segment for Z (203) and sends the packet onto a repair tunnel |
| 1975 |
to G (node segment 106 followed by adjacency segment 9001). Thus, B |
| 1976 |
sends the packet to C with the label stack {106, 9001, 203}. C pops |
| 1977 |
the node segment 106 and forwards to F. F pops the adjacency segment |
| 1978 |
9001 and forwards to G. G swaps 203 for 203 and forwards to E. E's |
| 1979 |
next hop to Z is not SR capable, and thus, E swaps the incoming node |
| 1980 |
segment 203 for the LDP label announced by its next hop (in this case, |
| 1981 |
implicit NULL).<a href="#section-4.3-7" class="pilcrow">¶</a></p> |
| 1982 |
<p id="section-4.3-8">After IGP convergence, B's MPLS entry to Z will become:<a href="#section-4.3-8" class="pilcrow">¶</a></p> |
| 1983 |
<ul class="ulEmpty"> |
| 1984 |
<li class="ulEmpty" id="section-4.3-9.1"> |
| 1985 |
<p id="section-4.3-9.1.1">Incoming label: local LDP label bound by B for FEC Z<a href="#section-4.3-9.1.1" class="pilcrow">¶</a></p> |
| 1986 |
<ul> |
| 1987 |
<li id="section-4.3-9.1.2.1">Outgoing label: LDP label bound by C for FEC Z<a href="#section-4.3-9.1.2.1" class="pilcrow">¶</a> |
| 1988 |
</li> |
| 1989 |
<li id="section-4.3-9.1.2.2">Outgoing next hop: C<a href="#section-4.3-9.1.2.2" class="pilcrow">¶</a> |
| 1990 |
</li> |
| 1991 |
</ul> |
| 1992 |
</li> |
| 1993 |
</ul> |
| 1994 |
<p id="section-4.3-10">And the traffic XZ travels again over the LDP LSP.<a href="#section-4.3-10" class="pilcrow">¶</a></p> |
| 1995 |
<p id="section-4.3-11">Conclusions:<a href="#section-4.3-11" class="pilcrow">¶</a></p> |
| 1996 |
<ul> |
| 1997 |
<li id="section-4.3-12.1">the operator has eliminated its second problem: guaranteed FRR |
| 1998 |
coverage is provided. The steady-state traffic is still |
| 1999 |
transported over LDP. The SR deployment is confined to the area |
| 2000 |
where these benefits are required.<a href="#section-4.3-12.1" class="pilcrow">¶</a> |
| 2001 |
</li> |
| 2002 |
<li id="section-4.3-12.2">FRR coverage has been achieved without any signaling for |
| 2003 |
setting up the repair LSP and without setting up a targeted LDP |
| 2004 |
session between B and G.<a href="#section-4.3-12.2" class="pilcrow">¶</a> |
| 2005 |
</li> |
| 2006 |
</ul> |
| 2007 |
</section> |
| 2008 |
</div> |
| 2009 |
<div id="sec-5.4"> |
| 2010 |
<section id="section-4.4"> |
| 2011 |
<h3 id="name-inter-as-option-c-carriers-"> |
| 2012 |
<a href="#section-4.4" class="section-number selfRef">4.4. </a><a href="#name-inter-as-option-c-carriers-" class="section-name selfRef">Inter-AS Option C, Carrier's Carrier</a> |
| 2013 |
</h3> |
| 2014 |
<p id="section-4.4-1">In inter-AS Option C <span>[<a href="#RFC4364" class="xref">RFC4364</a>]</span>, two interconnected |
| 2015 |
ASes sets up inter-AS MPLS connectivity. SR may be independently |
| 2016 |
deployed in each AS.<a href="#section-4.4-1" class="pilcrow">¶</a></p> |
| 2017 |
<span id="name-inter-as-option-c"></span><div id="ref-inter-as-option-c"> |
| 2018 |
<figure id="figure-4"> |
| 2019 |
<div class="artwork art-text alignLeft" id="section-4.4-2.1"> |
| 2020 |
<pre> |
| 2021 |
PE1---R1---B1---B2---R2---PE2 |
| 2022 |
<-----------> <-----------> |
| 2023 |
AS1 AS2 |
| 2024 |
</pre> |
| 2025 |
</div> |
| 2026 |
<figcaption><a href="#figure-4" class="selfRef">Figure 4</a>: |
| 2027 |
<a href="#name-inter-as-option-c" class="selfRef">Inter-AS Option C</a> |
| 2028 |
</figcaption></figure> |
| 2029 |
</div> |
| 2030 |
<p id="section-4.4-3">In Inter-AS Option C, B2 advertises to B1 a labeled BGP route <span>[<a href="#RFC8277" class="xref">RFC8277</a>]</span> for PE2, and B1 reflects it to its |
| 2031 |
internal peers, e.g., PE1. PE1 learns from a service route reflector a |
| 2032 |
service route whose next hop is PE2. PE1 resolves that service route |
| 2033 |
on the labeled BGP route to PE2. That labeled BGP route to PE2 is |
| 2034 |
itself resolved on the AS1 IGP route to B1.<a href="#section-4.4-3" class="pilcrow">¶</a></p> |
| 2035 |
<p id="section-4.4-4">If AS1 operates SR, then the tunnel from PE1 to B1 is provided by |
| 2036 |
the node segment from PE1 to B1.<a href="#section-4.4-4" class="pilcrow">¶</a></p> |
| 2037 |
<p id="section-4.4-5">PE1 sends a service packet with three labels: the top one is the |
| 2038 |
node segment to B1, the next one is the label in the labeled BGP route |
| 2039 |
provided by B1 for the route "PE2", and the bottom one is the service |
| 2040 |
label allocated by PE2.<a href="#section-4.4-5" class="pilcrow">¶</a></p> |
| 2041 |
</section> |
| 2042 |
</div> |
| 2043 |
</section> |
| 2044 |
</div> |
| 2045 |
<div id="sec-6"> |
| 2046 |
<section id="section-5"> |
| 2047 |
<h2 id="name-iana-considerations"> |
| 2048 |
<a href="#section-5" class="section-number selfRef">5. </a><a href="#name-iana-considerations" class="section-name selfRef">IANA Considerations</a> |
| 2049 |
</h2> |
| 2050 |
<p id="section-5-1"> This document has no IANA actions.<a href="#section-5-1" class="pilcrow">¶</a></p> |
| 2051 |
</section> |
| 2052 |
</div> |
| 2053 |
<div id="sec-7"> |
| 2054 |
<section id="section-6"> |
| 2055 |
<h2 id="name-manageability-consideration"> |
| 2056 |
<a href="#section-6" class="section-number selfRef">6. </a><a href="#name-manageability-consideration" class="section-name selfRef">Manageability Considerations</a> |
| 2057 |
</h2> |
| 2058 |
<div id="sec-7.1"> |
| 2059 |
<section id="section-6.1"> |
| 2060 |
<h3 id="name-sr-and-ldp-coexistence"> |
| 2061 |
<a href="#section-6.1" class="section-number selfRef">6.1. </a><a href="#name-sr-and-ldp-coexistence" class="section-name selfRef">SR and LDP Coexistence</a> |
| 2062 |
</h3> |
| 2063 |
<p id="section-6.1-1">When both SR and LDP coexist, the following applies:<a href="#section-6.1-1" class="pilcrow">¶</a></p> |
| 2064 |
<ul> |
| 2065 |
<li id="section-6.1-2.1">If both SR and LDP propose an IP2MPLS entry for the same IP |
| 2066 |
prefix, then by default the LDP route <span class="bcp14">SHOULD</span> be selected. This is |
| 2067 |
because it is expected that SR is introduced into networks that |
| 2068 |
contain routers that do not support SR. Hence, by having a behavior |
| 2069 |
that prefers LDP over SR, traffic flow is unlikely to be |
| 2070 |
disrupted.<a href="#section-6.1-2.1" class="pilcrow">¶</a> |
| 2071 |
</li> |
| 2072 |
<li id="section-6.1-2.2">A local policy on a router <span class="bcp14">MUST</span> allow to prefer the SR-provided |
| 2073 |
IP2MPLS entry.<a href="#section-6.1-2.2" class="pilcrow">¶</a> |
| 2074 |
</li> |
| 2075 |
<li id="section-6.1-2.3">Note that this policy <span class="bcp14">MAY</span> be locally defined. There is no |
| 2076 |
requirement that all routers use the same policy.<a href="#section-6.1-2.3" class="pilcrow">¶</a> |
| 2077 |
</li> |
| 2078 |
</ul> |
| 2079 |
</section> |
| 2080 |
</div> |
| 2081 |
<div id="sec-7.3"> |
| 2082 |
<section id="section-6.2"> |
| 2083 |
<h3 id="name-data-plane-verification"> |
| 2084 |
<a href="#section-6.2" class="section-number selfRef">6.2. </a><a href="#name-data-plane-verification" class="section-name selfRef">Data-Plane Verification</a> |
| 2085 |
</h3> |
| 2086 |
<p id="section-6.2-1">When Label switch paths (LSPs) are defined by stitching LDP LSPs |
| 2087 |
with SR LSPs, it is necessary to have mechanisms allowing the |
| 2088 |
verification of the LSP connectivity as well as validation of the |
| 2089 |
path. These mechanisms are described in <span>[<a href="#RFC8287" class="xref">RFC8287</a>]</span>.<a href="#section-6.2-1" class="pilcrow">¶</a></p> |
| 2090 |
</section> |
| 2091 |
</div> |
| 2092 |
</section> |
| 2093 |
</div> |
| 2094 |
<div id="sec-8"> |
| 2095 |
<section id="section-7"> |
| 2096 |
<h2 id="name-security-considerations"> |
| 2097 |
<a href="#section-7" class="section-number selfRef">7. </a><a href="#name-security-considerations" class="section-name selfRef">Security Considerations</a> |
| 2098 |
</h2> |
| 2099 |
<p id="section-7-1">This document does not introduce any change to the MPLS data plane |
| 2100 |
<span>[<a href="#RFC3031" class="xref">RFC3031</a>]</span> and therefore no additional security of the |
| 2101 |
MPLS data plane is required.<a href="#section-7-1" class="pilcrow">¶</a></p> |
| 2102 |
<p id="section-7-2"> |
| 2103 |
This document introduces another form of label binding advertisements. The |
| 2104 |
security associated with these advertisements is part of the security applied |
| 2105 |
to routing protocols such as IS-IS <span>[<a href="#RFC5304" class="xref">RFC5304</a>]</span> |
| 2106 |
and OSPF <span>[<a href="#RFC5709" class="xref">RFC5709</a>]</span>, which both optionally make |
| 2107 |
use of cryptographic authentication mechanisms. This form of advertisement is |
| 2108 |
more centralized, on behalf of the node advertising the IP reachability, which |
| 2109 |
presents a different risk profile. This document also specifies a mechanism by |
| 2110 |
which the ill effects of advertising conflicting label bindings can be |
| 2111 |
mitigated. In particular, advertisements from the node advertising the IP |
| 2112 |
reachability is more preferred than the centralized one. This document |
| 2113 |
recognizes that errors in configuration and/or programming may result in false |
| 2114 |
or conflicting label binding advertisements compromising traffic |
| 2115 |
forwarding. Therefore, this document recommends the operator implement strict |
| 2116 |
configuration/programmability control, the monitoring of the advertised SIDs, |
| 2117 |
the preference of an IP reachability SID Advertisement over a centralized SID |
| 2118 |
Advertisement, and the logging of any error message in order to avoid, or at |
| 2119 |
least significantly minimize, the possibility of such risk.<a href="#section-7-2" class="pilcrow">¶</a></p> |
| 2120 |
</section> |
| 2121 |
</div> |
| 2122 |
<section id="section-8"> |
| 2123 |
<h2 id="name-references"> |
| 2124 |
<a href="#section-8" class="section-number selfRef">8. </a><a href="#name-references" class="section-name selfRef">References</a> |
| 2125 |
</h2> |
| 2126 |
<section id="section-8.1"> |
| 2127 |
<h3 id="name-normative-references"> |
| 2128 |
<a href="#section-8.1" class="section-number selfRef">8.1. </a><a href="#name-normative-references" class="section-name selfRef">Normative References</a> |
| 2129 |
</h3> |
| 2130 |
<dl class="references"> |
| 2131 |
<dt id="RFC2119">[RFC2119]</dt> |
| 2132 |
<dd> |
| 2133 |
<span class="refAuthor">Bradner, S.</span>, <span class="refTitle">"Key words for use in RFCs to Indicate Requirement Levels"</span>, <span class="seriesInfo">BCP 14</span>, <span class="seriesInfo">RFC 2119</span>, <span class="seriesInfo">DOI 10.17487/RFC2119</span>, <time datetime="1997-03">March 1997</time>, <span><<a href="https://www.rfc-editor.org/info/rfc2119">https://www.rfc-editor.org/info/rfc2119</a>></span>. </dd> |
| 2134 |
<dt id="RFC5036">[RFC5036]</dt> |
| 2135 |
<dd> |
| 2136 |
<span class="refAuthor">Andersson, L., Ed.</span><span class="refAuthor">, Minei, I., Ed.</span><span class="refAuthor">, and B. Thomas, Ed.</span>, <span class="refTitle">"LDP Specification"</span>, <span class="seriesInfo">RFC 5036</span>, <span class="seriesInfo">DOI 10.17487/RFC5036</span>, <time datetime="2007-10">October 2007</time>, <span><<a href="https://www.rfc-editor.org/info/rfc5036">https://www.rfc-editor.org/info/rfc5036</a>></span>. </dd> |
| 2137 |
<dt id="RFC8174">[RFC8174]</dt> |
| 2138 |
<dd> |
| 2139 |
<span class="refAuthor">Leiba, B.</span>, <span class="refTitle">"Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words"</span>, <span class="seriesInfo">BCP 14</span>, <span class="seriesInfo">RFC 8174</span>, <span class="seriesInfo">DOI 10.17487/RFC8174</span>, <time datetime="2017-05">May 2017</time>, <span><<a href="https://www.rfc-editor.org/info/rfc8174">https://www.rfc-editor.org/info/rfc8174</a>></span>. </dd> |
| 2140 |
<dt id="RFC8402">[RFC8402]</dt> |
| 2141 |
<dd> |
| 2142 |
<span class="refAuthor">Filsfils, C., Ed.</span><span class="refAuthor">, Previdi, S., Ed.</span><span class="refAuthor">, Ginsberg, L.</span><span class="refAuthor">, Decraene, B.</span><span class="refAuthor">, Litkowski, S.</span><span class="refAuthor">, and R. Shakir</span>, <span class="refTitle">"Segment Routing Architecture"</span>, <span class="seriesInfo">RFC 8402</span>, <span class="seriesInfo">DOI 10.17487/RFC8402</span>, <time datetime="2018-07">July 2018</time>, <span><<a href="https://www.rfc-editor.org/info/rfc8402">https://www.rfc-editor.org/info/rfc8402</a>></span>. </dd> |
| 2143 |
<dt id="RFC8660">[RFC8660]</dt> |
| 2144 |
<dd> |
| 2145 |
<span class="refAuthor">Bashandy, A., Ed.</span><span class="refAuthor">, Filsfils, C., Ed.</span><span class="refAuthor">, Previdi, S.</span><span class="refAuthor">, Decraene, B.</span><span class="refAuthor">, Litkowski, S.</span><span class="refAuthor">, and R. Shakir</span>, <span class="refTitle">"Segment Routing with MPLS Data Plane"</span>, <span class="seriesInfo">RFC 8660</span>, <span class="seriesInfo">DOI 10.17487/RFC8660</span>, <time datetime="2019-12">December 2019</time>, <span><<a href="https://www.rfc-editor.org/info/rfc8660">https://www.rfc-editor.org/info/rfc8660</a>></span>. </dd> |
| 2146 |
</dl> |
| 2147 |
</section> |
| 2148 |
<section id="section-8.2"> |
| 2149 |
<h3 id="name-informative-references"> |
| 2150 |
<a href="#section-8.2" class="section-number selfRef">8.2. </a><a href="#name-informative-references" class="section-name selfRef">Informative References</a> |
| 2151 |
</h3> |
| 2152 |
<dl class="references"> |
| 2153 |
<dt id="RFC3031">[RFC3031]</dt> |
| 2154 |
<dd> |
| 2155 |
<span class="refAuthor">Rosen, E.</span><span class="refAuthor">, Viswanathan, A.</span><span class="refAuthor">, and R. Callon</span>, <span class="refTitle">"Multiprotocol Label Switching Architecture"</span>, <span class="seriesInfo">RFC 3031</span>, <span class="seriesInfo">DOI 10.17487/RFC3031</span>, <time datetime="2001-01">January 2001</time>, <span><<a href="https://www.rfc-editor.org/info/rfc3031">https://www.rfc-editor.org/info/rfc3031</a>></span>. </dd> |
| 2156 |
<dt id="RFC3209">[RFC3209]</dt> |
| 2157 |
<dd> |
| 2158 |
<span class="refAuthor">Awduche, D.</span><span class="refAuthor">, Berger, L.</span><span class="refAuthor">, Gan, D.</span><span class="refAuthor">, Li, T.</span><span class="refAuthor">, Srinivasan, V.</span><span class="refAuthor">, and G. Swallow</span>, <span class="refTitle">"RSVP-TE: Extensions to RSVP for LSP Tunnels"</span>, <span class="seriesInfo">RFC 3209</span>, <span class="seriesInfo">DOI 10.17487/RFC3209</span>, <time datetime="2001-12">December 2001</time>, <span><<a href="https://www.rfc-editor.org/info/rfc3209">https://www.rfc-editor.org/info/rfc3209</a>></span>. </dd> |
| 2159 |
<dt id="RFC4364">[RFC4364]</dt> |
| 2160 |
<dd> |
| 2161 |
<span class="refAuthor">Rosen, E.</span><span class="refAuthor"> and Y. Rekhter</span>, <span class="refTitle">"BGP/MPLS IP Virtual Private Networks (VPNs)"</span>, <span class="seriesInfo">RFC 4364</span>, <span class="seriesInfo">DOI 10.17487/RFC4364</span>, <time datetime="2006-02">February 2006</time>, <span><<a href="https://www.rfc-editor.org/info/rfc4364">https://www.rfc-editor.org/info/rfc4364</a>></span>. </dd> |
| 2162 |
<dt id="RFC5304">[RFC5304]</dt> |
| 2163 |
<dd> |
| 2164 |
<span class="refAuthor">Li, T.</span><span class="refAuthor"> and R. Atkinson</span>, <span class="refTitle">"IS-IS Cryptographic Authentication"</span>, <span class="seriesInfo">RFC 5304</span>, <span class="seriesInfo">DOI 10.17487/RFC5304</span>, <time datetime="2008-10">October 2008</time>, <span><<a href="https://www.rfc-editor.org/info/rfc5304">https://www.rfc-editor.org/info/rfc5304</a>></span>. </dd> |
| 2165 |
<dt id="RFC5709">[RFC5709]</dt> |
| 2166 |
<dd> |
| 2167 |
<span class="refAuthor">Bhatia, M.</span><span class="refAuthor">, Manral, V.</span><span class="refAuthor">, Fanto, M.</span><span class="refAuthor">, White, R.</span><span class="refAuthor">, Barnes, M.</span><span class="refAuthor">, Li, T.</span><span class="refAuthor">, and R. Atkinson</span>, <span class="refTitle">"OSPFv2 HMAC-SHA Cryptographic Authentication"</span>, <span class="seriesInfo">RFC 5709</span>, <span class="seriesInfo">DOI 10.17487/RFC5709</span>, <time datetime="2009-10">October 2009</time>, <span><<a href="https://www.rfc-editor.org/info/rfc5709">https://www.rfc-editor.org/info/rfc5709</a>></span>. </dd> |
| 2168 |
<dt id="RFC5960">[RFC5960]</dt> |
| 2169 |
<dd> |
| 2170 |
<span class="refAuthor">Frost, D., Ed.</span><span class="refAuthor">, Bryant, S., Ed.</span><span class="refAuthor">, and M. Bocci, Ed.</span>, <span class="refTitle">"MPLS Transport Profile Data Plane Architecture"</span>, <span class="seriesInfo">RFC 5960</span>, <span class="seriesInfo">DOI 10.17487/RFC5960</span>, <time datetime="2010-08">August 2010</time>, <span><<a href="https://www.rfc-editor.org/info/rfc5960">https://www.rfc-editor.org/info/rfc5960</a>></span>. </dd> |
| 2171 |
<dt id="RFC7490">[RFC7490]</dt> |
| 2172 |
<dd> |
| 2173 |
<span class="refAuthor">Bryant, S.</span><span class="refAuthor">, Filsfils, C.</span><span class="refAuthor">, Previdi, S.</span><span class="refAuthor">, Shand, M.</span><span class="refAuthor">, and N. So</span>, <span class="refTitle">"Remote Loop-Free Alternate (LFA) Fast Reroute (FRR)"</span>, <span class="seriesInfo">RFC 7490</span>, <span class="seriesInfo">DOI 10.17487/RFC7490</span>, <time datetime="2015-04">April 2015</time>, <span><<a href="https://www.rfc-editor.org/info/rfc7490">https://www.rfc-editor.org/info/rfc7490</a>></span>. </dd> |
| 2174 |
<dt id="RFC8277">[RFC8277]</dt> |
| 2175 |
<dd> |
| 2176 |
<span class="refAuthor">Rosen, E.</span>, <span class="refTitle">"Using BGP to Bind MPLS Labels to Address Prefixes"</span>, <span class="seriesInfo">RFC 8277</span>, <span class="seriesInfo">DOI 10.17487/RFC8277</span>, <time datetime="2017-10">October 2017</time>, <span><<a href="https://www.rfc-editor.org/info/rfc8277">https://www.rfc-editor.org/info/rfc8277</a>></span>. </dd> |
| 2177 |
<dt id="RFC8287">[RFC8287]</dt> |
| 2178 |
<dd> |
| 2179 |
<span class="refAuthor">Kumar, N., Ed.</span><span class="refAuthor">, Pignataro, C., Ed.</span><span class="refAuthor">, Swallow, G.</span><span class="refAuthor">, Akiya, N.</span><span class="refAuthor">, Kini, S.</span><span class="refAuthor">, and M. Chen</span>, <span class="refTitle">"Label Switched Path (LSP) Ping/Traceroute for Segment Routing (SR) IGP-Prefix and IGP-Adjacency Segment Identifiers (SIDs) with MPLS Data Planes"</span>, <span class="seriesInfo">RFC 8287</span>, <span class="seriesInfo">DOI 10.17487/RFC8287</span>, <time datetime="2017-12">December 2017</time>, <span><<a href="https://www.rfc-editor.org/info/rfc8287">https://www.rfc-editor.org/info/rfc8287</a>></span>. </dd> |
| 2180 |
<dt id="RFC8355">[RFC8355]</dt> |
| 2181 |
<dd> |
| 2182 |
<span class="refAuthor">Filsfils, C., Ed.</span><span class="refAuthor">, Previdi, S., Ed.</span><span class="refAuthor">, Decraene, B.</span><span class="refAuthor">, and R. Shakir</span>, <span class="refTitle">"Resiliency Use Cases in Source Packet Routing in Networking (SPRING) Networks"</span>, <span class="seriesInfo">RFC 8355</span>, <span class="seriesInfo">DOI 10.17487/RFC8355</span>, <time datetime="2018-03">March 2018</time>, <span><<a href="https://www.rfc-editor.org/info/rfc8355">https://www.rfc-editor.org/info/rfc8355</a>></span>. </dd> |
| 2183 |
<dt id="RFC8665">[RFC8665]</dt> |
| 2184 |
<dd> |
| 2185 |
<span class="refAuthor">Psenak, P., Ed.</span><span class="refAuthor">, Previdi, S., Ed.</span><span class="refAuthor">, Filsfils, C.</span><span class="refAuthor">, Gredler, H.</span><span class="refAuthor">, Shakir, R.</span><span class="refAuthor">, Henderickx, W.</span><span class="refAuthor">, and J. Tantsura</span>, <span class="refTitle">"OSPF Extensions for Segment Routing"</span>, <span class="seriesInfo">RFC 8665</span>, <span class="seriesInfo">DOI 10.17487/RFC8665</span>, <time datetime="2019-12">December 2019</time>, <span><<a href="https://doi.org/10.17487/RFC8665">https://doi.org/10.17487/RFC8665</a>></span>. </dd> |
| 2186 |
<dt id="RFC8666">[RFC8666]</dt> |
| 2187 |
<dd> |
| 2188 |
<span class="refAuthor">Psenak, P., Ed.</span><span class="refAuthor"> and S. Previdi</span>, <span class="refTitle">"OSPFv3 Extensions for Segment Routing"</span>, <span class="seriesInfo">RFC 8666</span>, <span class="seriesInfo">DOI 10.17487/RFC8666</span>, <time datetime="2019-12">December 2019</time>, <span><<a href="https://doi.org/10.17487/RFC8666">https://doi.org/10.17487/RFC8666</a>></span>. </dd> |
| 2189 |
<dt id="RFC8667">[RFC8667]</dt> |
| 2190 |
<dd> |
| 2191 |
<span class="refAuthor">Previdi, S.</span><span class="refAuthor">, Ginsberg, L.</span><span class="refAuthor">, Filsfils, C.</span><span class="refAuthor">, Bashandy, A.</span><span class="refAuthor">, Gredler, H.</span><span class="refAuthor">, and B. Decraene</span>, <span class="refTitle">"IS-IS Extensions for Segment Routing"</span>, <span class="seriesInfo">RFC 8667</span>, <span class="seriesInfo">DOI 10.17487/RFC8667</span>, <time datetime="2019-12">December 2019</time>, <span><<a href="https://doi.org/10.17487/RFC8667">https://doi.org/10.17487/RFC8667</a>></span>. </dd> |
| 2192 |
</dl> |
| 2193 |
</section> |
| 2194 |
</section> |
| 2195 |
<div id="Appendix-A"> |
| 2196 |
<section id="section-appendix.a"> |
| 2197 |
<h2 id="name-migration-from-ldp-to-sr"> |
| 2198 |
<a href="#section-appendix.a" class="section-number selfRef">Appendix A. </a><a href="#name-migration-from-ldp-to-sr" class="section-name selfRef">Migration from LDP to SR</a> |
| 2199 |
</h2> |
| 2200 |
<span id="name-migration"></span><div id="ref-migration"> |
| 2201 |
<figure id="figure-5"> |
| 2202 |
<div class="artwork art-text alignLeft" id="section-appendix.a-1.1"> |
| 2203 |
<pre> |
| 2204 |
PE2 PE4 |
| 2205 |
\ / |
| 2206 |
PE1----P5--P6--P7---PE3 |
| 2207 |
</pre> |
| 2208 |
</div> |
| 2209 |
<figcaption><a href="#figure-5" class="selfRef">Figure 5</a>: |
| 2210 |
<a href="#name-migration" class="selfRef">Migration</a> |
| 2211 |
</figcaption></figure> |
| 2212 |
</div> |
| 2213 |
<p id="section-appendix.a-2">Several migration techniques are possible. The technique described |
| 2214 |
here is inspired by the commonly used method to migrate from one IGP to |
| 2215 |
another.<a href="#section-appendix.a-2" class="pilcrow">¶</a></p> |
| 2216 |
<p id="section-appendix.a-3">At time T0, all the routers run LDP. Any service is tunneled from an |
| 2217 |
ingress PE to an egress PE over a continuous LDP LSP.<a href="#section-appendix.a-3" class="pilcrow">¶</a></p> |
| 2218 |
<p id="section-appendix.a-4">At time T1, all the routers are upgraded to SR. They are configured |
| 2219 |
with the SRGB range [100, 300]. PE1, PE2, PE3, PE4, P5, P6, and P7 are |
| 2220 |
respectively configured with the node segments 101, 102, 103, 104, 105, |
| 2221 |
106, and 107 (attached to their service-recursing loopback).<a href="#section-appendix.a-4" class="pilcrow">¶</a></p> |
| 2222 |
<aside id="section-appendix.a-5"> |
| 2223 |
<p id="section-appendix.a-5.1"> |
| 2224 |
Note: At this time, the service traffic is still tunneled over LDP LSPs. |
| 2225 |
For example, PE1 has an SR node segment to PE3 and an LDP LSP to PE3. |
| 2226 |
As seen earlier, however, the LDP IP2MPLS encapsulation is |
| 2227 |
preferred by default. However, it has to be noted that the SR infrastructure is |
| 2228 |
usable, e.g., for Fast Reroute (FRR) or IGP Loop-Free Convergence to |
| 2229 |
protect existing IP and LDP traffic. FRR mechanisms are described in |
| 2230 |
<span>[<a href="#RFC8355" class="xref">RFC8355</a>]</span>.<a href="#section-appendix.a-5.1" class="pilcrow">¶</a></p> |
| 2231 |
</aside> |
| 2232 |
<p id="section-appendix.a-6">At time T2, the operator enables the local policy at PE1 to prefer SR |
| 2233 |
IP2MPLS encapsulation over LDP IP2MPLS.<a href="#section-appendix.a-6" class="pilcrow">¶</a></p> |
| 2234 |
<ul class="ulEmpty"> |
| 2235 |
<li class="ulEmpty" id="section-appendix.a-7.1">The service from PE1 to any other PE is now riding over SR. All |
| 2236 |
other service traffic is still transported over LDP LSPs.<a href="#section-appendix.a-7.1" class="pilcrow">¶</a> |
| 2237 |
</li> |
| 2238 |
</ul> |
| 2239 |
<p id="section-appendix.a-8">At time T3, gradually, the operator enables the preference for SR |
| 2240 |
IP2MPLS encapsulation across all the edge routers.<a href="#section-appendix.a-8" class="pilcrow">¶</a></p> |
| 2241 |
<ul class="ulEmpty"> |
| 2242 |
<li class="ulEmpty" id="section-appendix.a-9.1">All the service traffic is now transported over SR. LDP is still |
| 2243 |
operational and services could be reverted to LDP.<a href="#section-appendix.a-9.1" class="pilcrow">¶</a> |
| 2244 |
</li> |
| 2245 |
</ul> |
| 2246 |
<p id="section-appendix.a-10">At time T4, LDP is unconfigured from all routers.<a href="#section-appendix.a-10" class="pilcrow">¶</a></p> |
| 2247 |
</section> |
| 2248 |
</div> |
| 2249 |
<div id="sec-9"> |
| 2250 |
<section id="section-appendix.b"> |
| 2251 |
<h2 id="name-acknowledgements"> |
| 2252 |
<a href="#name-acknowledgements" class="section-name selfRef">Acknowledgements</a> |
| 2253 |
</h2> |
| 2254 |
<p id="section-appendix.b-1">The authors would like to thank Pierre Francois, Ruediger Geib, and |
| 2255 |
Alexander Vainshtein for their contributions to the content of this |
| 2256 |
document.<a href="#section-appendix.b-1" class="pilcrow">¶</a></p> |
| 2257 |
</section> |
| 2258 |
</div> |
| 2259 |
<div id="sec-10"> |
| 2260 |
<section id="section-appendix.c"> |
| 2261 |
<h2 id="name-contributors"> |
| 2262 |
<a href="#name-contributors" class="section-name selfRef">Contributors</a> |
| 2263 |
</h2> |
| 2264 |
<div class="artwork art-text alignLeft" id="section-appendix.c-1"> |
| 2265 |
<pre> |
| 2266 |
Edward Crabbe |
| 2267 |
Individual |
| 2268 |
Email: [email protected]</pre><a href="#section-appendix.c-1" class="pilcrow">¶</a> |
| 2269 |
</div> |
| 2270 |
<div class="artwork art-text alignLeft" id="section-appendix.c-2"> |
| 2271 |
<pre> |
| 2272 |
Igor Milojevic |
| 2273 |
Email: [email protected]</pre><a href="#section-appendix.c-2" class="pilcrow">¶</a> |
| 2274 |
</div> |
| 2275 |
<div class="artwork art-text alignLeft" id="section-appendix.c-3"> |
| 2276 |
<pre> |
| 2277 |
Saku Ytti |
| 2278 |
TDC |
| 2279 |
Email: [email protected]</pre><a href="#section-appendix.c-3" class="pilcrow">¶</a> |
| 2280 |
</div> |
| 2281 |
<div class="artwork art-text alignLeft" id="section-appendix.c-4"> |
| 2282 |
<pre> |
| 2283 |
Rob Shakir |
| 2284 |
Google |
| 2285 |
Email: [email protected]</pre><a href="#section-appendix.c-4" class="pilcrow">¶</a> |
| 2286 |
</div> |
| 2287 |
<div class="artwork art-text alignLeft" id="section-appendix.c-5"> |
| 2288 |
<pre> |
| 2289 |
Martin Horneffer |
| 2290 |
Deutsche Telekom |
| 2291 |
Email: [email protected]</pre><a href="#section-appendix.c-5" class="pilcrow">¶</a> |
| 2292 |
</div> |
| 2293 |
<div class="artwork art-text alignLeft" id="section-appendix.c-6"> |
| 2294 |
<pre> |
| 2295 |
Wim Henderickx |
| 2296 |
Nokia |
| 2297 |
Email: [email protected]</pre><a href="#section-appendix.c-6" class="pilcrow">¶</a> |
| 2298 |
</div> |
| 2299 |
<div class="artwork art-text alignLeft" id="section-appendix.c-7"> |
| 2300 |
<pre> |
| 2301 |
Jeff Tantsura |
| 2302 |
Apstra, Inc. |
| 2303 |
Email: [email protected]</pre><a href="#section-appendix.c-7" class="pilcrow">¶</a> |
| 2304 |
</div> |
| 2305 |
<div class="artwork art-text alignLeft" id="section-appendix.c-8"> |
| 2306 |
<pre> |
| 2307 |
Les Ginsberg |
| 2308 |
Cisco Systems |
| 2309 |
Email: [email protected]</pre><a href="#section-appendix.c-8" class="pilcrow">¶</a> |
| 2310 |
</div> |
| 2311 |
</section> |
| 2312 |
</div> |
| 2313 |
<div id="authors-addresses"> |
| 2314 |
<section id="section-appendix.d"> |
| 2315 |
<h2 id="name-authors-addresses"> |
| 2316 |
<a href="#name-authors-addresses" class="section-name selfRef">Authors' Addresses</a> |
| 2317 |
</h2> |
| 2318 |
<address class="vcard"> |
| 2319 |
<div dir="auto" class="left"><span class="fn nameRole">Ahmed Bashandy (<span class="role">editor</span>)</span></div> |
| 2320 |
<div dir="auto" class="left"><span class="org">Individual</span></div> |
| 2321 |
<div dir="auto" class="left"><span class="country-name">United States of America</span></div> |
| 2322 |
<div class="email"> |
| 2323 |
<span>Email:</span> |
| 2324 |
<a href="mailto:[email protected]" class="email">[email protected]</a> |
| 2325 |
</div> |
| 2326 |
</address> |
| 2327 |
<address class="vcard"> |
| 2328 |
<div dir="auto" class="left"><span class="fn nameRole">Clarence Filsfils (<span class="role">editor</span>)</span></div> |
| 2329 |
<div dir="auto" class="left"><span class="org">Cisco Systems, Inc.</span></div> |
| 2330 |
<div dir="auto" class="left"><span class="street-address">Brussels</span></div> |
| 2331 |
<div dir="auto" class="left"><span class="country-name">Belgium</span></div> |
| 2332 |
<div class="email"> |
| 2333 |
<span>Email:</span> |
| 2334 |
<a href="mailto:[email protected]" class="email">[email protected]</a> |
| 2335 |
</div> |
| 2336 |
</address> |
| 2337 |
<address class="vcard"> |
| 2338 |
<div dir="auto" class="left"><span class="fn nameRole">Stefano Previdi</span></div> |
| 2339 |
<div dir="auto" class="left"><span class="org">Huawei Technologies</span></div> |
| 2340 |
<div dir="auto" class="left"><span class="country-name">Italy</span></div> |
| 2341 |
<div class="email"> |
| 2342 |
<span>Email:</span> |
| 2343 |
<a href="mailto:[email protected]" class="email">[email protected]</a> |
| 2344 |
</div> |
| 2345 |
</address> |
| 2346 |
<address class="vcard"> |
| 2347 |
<div dir="auto" class="left"><span class="fn nameRole">Bruno Decraene</span></div> |
| 2348 |
<div dir="auto" class="left"><span class="org">Orange</span></div> |
| 2349 |
<div dir="auto" class="left"><span class="country-name">France</span></div> |
| 2350 |
<div class="email"> |
| 2351 |
<span>Email:</span> |
| 2352 |
<a href="mailto:[email protected]" class="email">[email protected]</a> |
| 2353 |
</div> |
| 2354 |
</address> |
| 2355 |
<address class="vcard"> |
| 2356 |
<div dir="auto" class="left"><span class="fn nameRole">Stephane Litkowski</span></div> |
| 2357 |
<div dir="auto" class="left"><span class="org">Orange</span></div> |
| 2358 |
<div dir="auto" class="left"><span class="country-name">France</span></div> |
| 2359 |
<div class="email"> |
| 2360 |
<span>Email:</span> |
| 2361 |
<a href="mailto:[email protected]" class="email">[email protected]</a> |
| 2362 |
</div> |
| 2363 |
</address> |
| 2364 |
</section> |
| 2365 |
</div> |
| 2366 |
<script>var toc = document.getElementById("toc"); |
| 2367 |
var tocToggle = toc.querySelector("h2"); |
| 2368 |
var tocNav = toc.querySelector("nav"); |
| 2369 |
|
| 2370 |
// mobile menu toggle |
| 2371 |
tocToggle.onclick = function(event) { |
| 2372 |
if (window.innerWidth < 1024) { |
| 2373 |
var tocNavDisplay = tocNav.currentStyle ? tocNav.currentStyle.display : getComputedStyle(tocNav, null).display; |
| 2374 |
if (tocNavDisplay == "none") { |
| 2375 |
tocNav.style.display = "block"; |
| 2376 |
} else { |
| 2377 |
tocNav.style.display = "none"; |
| 2378 |
} |
| 2379 |
} |
| 2380 |
} |
| 2381 |
|
| 2382 |
// toc anchor scroll to anchor |
| 2383 |
tocNav.addEventListener("click", function (event) { |
| 2384 |
event.preventDefault(); |
| 2385 |
if (event.target.nodeName == 'A') { |
| 2386 |
if (window.innerWidth < 1024) { |
| 2387 |
tocNav.style.display = "none"; |
| 2388 |
} |
| 2389 |
var href = event.target.getAttribute("href"); |
| 2390 |
var anchorId = href.substr(1); |
| 2391 |
var anchor = document.getElementById(anchorId); |
| 2392 |
anchor.scrollIntoView(true); |
| 2393 |
window.history.pushState("","",href); |
| 2394 |
} |
| 2395 |
}); |
| 2396 |
|
| 2397 |
// switch toc mode when window resized |
| 2398 |
window.onresize = function () { |
| 2399 |
if (window.innerWidth < 1024) { |
| 2400 |
tocNav.style.display = "none"; |
| 2401 |
} else { |
| 2402 |
tocNav.style.display = "block"; |
| 2403 |
} |
| 2404 |
} |
| 2405 |
</script> |
| 2406 |
</body> |
| 2407 |
</html> |