Debian Codegraph @

rfc8662.html

raw
1 <!DOCTYPE html>
2 <html lang="en" class="RFC">
3 <head>
4 <meta charset="utf-8">
5 <meta content="Common,Latin" name="scripts">
6 <meta content="initial-scale=1.0" name="viewport">
7 <title>RFC 8662: Entropy Label for Source Packet Routing in Networking (SPRING) Tunnels</title>
8 <meta content="Sriganesh Kini" name="author">
9 <meta content="Kireeti Kompella" name="author">
10 <meta content="Siva Sivabalan" name="author">
11 <meta content="Stephane Litkowski" name="author">
12 <meta content="Rob Shakir" name="author">
13 <meta content="Jeff Tantsura" name="author">
14 <meta content="
15
16 Segment Routing (SR) leverages the source-routing paradigm. A node steers a
17 packet through an ordered list of instructions, called segments. Segment
18 Routing can be applied to the Multiprotocol Label Switching (MPLS) data
19 plane. Entropy labels (ELs) are used in MPLS to improve load-balancing.
20 This document examines and describes how ELs are to be applied to Segment
21 Routing MPLS.
22
23 " name="description">
24 <meta content="xml2rfc 2.35.0" name="generator">
25 <meta content="Flow-aware load balancing" name="keyword">
26 <meta content="ECMP" name="keyword">
27 <meta content="equal-cost multipath" name="keyword">
28 <meta content="8662" name="rfc.number">
29 <link href="rfc8662.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/rfc8662" rel="alternate">
1045 <link href="urn:issn:2070-1721" rel="alternate">
1046 <link href="https://datatracker.ietf.org/doc/draft-ietf-mpls-spring-entropy-label-12" 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 8662</td>
1053 <td class="center">Entropy Labels for SPRING Tunnels</td>
1054 <td class="right">December 2019</td>
1055 </tr></thead>
1056 <tfoot><tr>
1057 <td class="left">Kini, 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/rfc8662" class="eref">8662</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">S. Kini</div>
1081 </div>
1082 <div class="author">
1083 <div class="author-name">K. Kompella</div>
1084 <div class="org">Juniper</div>
1085 </div>
1086 <div class="author">
1087 <div class="author-name">S. Sivabalan</div>
1088 <div class="org">Cisco</div>
1089 </div>
1090 <div class="author">
1091 <div class="author-name">S. Litkowski</div>
1092 <div class="org">Orange</div>
1093 </div>
1094 <div class="author">
1095 <div class="author-name">R. Shakir</div>
1096 <div class="org">Google</div>
1097 </div>
1098 <div class="author">
1099 <div class="author-name">J. Tantsura</div>
1100 <div class="org">Apstra, Inc.</div>
1101 </div>
1102 </dd>
1103 </dl>
1104 </div>
1105 <h1 id="rfcnum">RFC 8662</h1>
1106 <h1 id="title">Entropy Label for Source Packet Routing in Networking (SPRING) Tunnels</h1>
1107 <section id="section-abstract">
1108 <h2 id="abstract"><a href="#abstract" class="selfRef">Abstract</a></h2>
1109 <p id="section-abstract-1">
1110 Segment Routing (SR) leverages the source-routing paradigm. A node steers a
1111 packet through an ordered list of instructions, called segments. Segment
1112 Routing can be applied to the Multiprotocol Label Switching (MPLS) data
1113 plane. Entropy labels (ELs) are used in MPLS to improve load-balancing.
1114 This document examines and describes how ELs are to be applied to Segment
1115 Routing MPLS.<a href="#section-abstract-1" class="pilcrow">¶</a></p>
1116 </section>
1117 <div id="status-of-memo">
1118 <section id="section-boilerplate.1">
1119 <h2 id="name-status-of-this-memo">
1120 <a href="#name-status-of-this-memo" class="section-name selfRef">Status of This Memo</a>
1121 </h2>
1122 <p id="section-boilerplate.1-1">
1123 This is an Internet Standards Track document.<a href="#section-boilerplate.1-1" class="pilcrow">¶</a></p>
1124 <p id="section-boilerplate.1-2">
1125 This document is a product of the Internet Engineering Task Force
1126 (IETF). It represents the consensus of the IETF community. It has
1127 received public review and has been approved for publication by
1128 the Internet Engineering Steering Group (IESG). Further
1129 information on Internet Standards is available in Section 2 of
1130 RFC 7841.<a href="#section-boilerplate.1-2" class="pilcrow">¶</a></p>
1131 <p id="section-boilerplate.1-3">
1132 Information about the current status of this document, any
1133 errata, and how to provide feedback on it may be obtained at
1134 <span><a href="https://www.rfc-editor.org/info/rfc8662">https://www.rfc-editor.org/info/rfc8662</a></span>.<a href="#section-boilerplate.1-3" class="pilcrow">¶</a></p>
1135 </section>
1136 </div>
1137 <div id="copyright">
1138 <section id="section-boilerplate.2">
1139 <h2 id="name-copyright-notice">
1140 <a href="#name-copyright-notice" class="section-name selfRef">Copyright Notice</a>
1141 </h2>
1142 <p id="section-boilerplate.2-1">
1143 Copyright (c) 2019 IETF Trust and the persons identified as the
1144 document authors. All rights reserved.<a href="#section-boilerplate.2-1" class="pilcrow">¶</a></p>
1145 <p id="section-boilerplate.2-2">
1146 This document is subject to BCP 78 and the IETF Trust's Legal
1147 Provisions Relating to IETF Documents
1148 (<span><a href="https://trustee.ietf.org/license-info">https://trustee.ietf.org/license-info</a></span>) in effect on the date of
1149 publication of this document. Please review these documents
1150 carefully, as they describe your rights and restrictions with
1151 respect to this document. Code Components extracted from this
1152 document must include Simplified BSD License text as described in
1153 Section 4.e of the Trust Legal Provisions and are provided without
1154 warranty as described in the Simplified BSD License.<a href="#section-boilerplate.2-2" class="pilcrow">¶</a></p>
1155 </section>
1156 </div>
1157 <div id="toc">
1158 <section id="section-toc.1">
1159 <a href="#" onclick="scroll(0,0)" class="toplink">▲</a><h2 id="name-table-of-contents">
1160 <a href="#name-table-of-contents" class="section-name selfRef">Table of Contents</a>
1161 </h2>
1162 <nav class="toc"><ul class="toc ulEmpty">
1163 <li class="toc ulEmpty" id="section-toc.1-1.1">
1164 <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>
1165 <ul class="toc ulEmpty">
1166 <li class="toc ulEmpty" id="section-toc.1-1.1.2.1">
1167 <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>
1168 </li>
1169 </ul>
1170 </li>
1171 <li class="toc ulEmpty" id="section-toc.1-1.2">
1172 <p id="section-toc.1-1.2.1"><a href="#section-2" class="xref">2</a>.  <a href="#name-abbreviations-and-terminolo" class="xref">Abbreviations and Terminology</a><a href="#section-toc.1-1.2.1" class="pilcrow">¶</a></p>
1173 </li>
1174 <li class="toc ulEmpty" id="section-toc.1-1.3">
1175 <p id="section-toc.1-1.3.1"><a href="#section-3" class="xref">3</a>.  <a href="#name-use-case-requiring-multipat" class="xref">Use Case Requiring Multipath Load-Balancing</a><a href="#section-toc.1-1.3.1" class="pilcrow">¶</a></p>
1176 </li>
1177 <li class="toc ulEmpty" id="section-toc.1-1.4">
1178 <p id="section-toc.1-1.4.1"><a href="#section-4" class="xref">4</a>.  <a href="#name-entropy-readable-label-dept" class="xref">Entropy Readable Label Depth</a><a href="#section-toc.1-1.4.1" class="pilcrow">¶</a></p>
1179 </li>
1180 <li class="toc ulEmpty" id="section-toc.1-1.5">
1181 <p id="section-toc.1-1.5.1"><a href="#section-5" class="xref">5</a>.  <a href="#name-maximum-sid-depth" class="xref">Maximum SID Depth</a><a href="#section-toc.1-1.5.1" class="pilcrow">¶</a></p>
1182 </li>
1183 <li class="toc ulEmpty" id="section-toc.1-1.6">
1184 <p id="section-toc.1-1.6.1"><a href="#section-6" class="xref">6</a>.  <a href="#name-lsp-stitching-using-the-bin" class="xref">LSP Stitching Using the Binding SID</a><a href="#section-toc.1-1.6.1" class="pilcrow">¶</a></p>
1185 </li>
1186 <li class="toc ulEmpty" id="section-toc.1-1.7">
1187 <p id="section-toc.1-1.7.1"><a href="#section-7" class="xref">7</a>.  <a href="#name-insertion-of-entropy-labels" class="xref">Insertion of Entropy Labels for SPRING Path</a><a href="#section-toc.1-1.7.1" class="pilcrow">¶</a></p>
1188 <ul class="toc ulEmpty">
1189 <li class="toc ulEmpty" id="section-toc.1-1.7.2.1">
1190 <p id="section-toc.1-1.7.2.1.1"><a href="#section-7.1" class="xref">7.1</a>.  <a href="#name-overview" class="xref">Overview</a><a href="#section-toc.1-1.7.2.1.1" class="pilcrow">¶</a></p>
1191 <ul class="toc ulEmpty">
1192 <li class="toc ulEmpty" id="section-toc.1-1.7.2.1.2.1">
1193 <p id="section-toc.1-1.7.2.1.2.1.1"><a href="#section-7.1.1" class="xref">7.1.1</a>.  <a href="#name-example-1-the-ingress-node-" class="xref">Example 1: The Ingress Node Has a Sufficient MSD</a><a href="#section-toc.1-1.7.2.1.2.1.1" class="pilcrow">¶</a></p>
1194 </li>
1195 <li class="toc ulEmpty" id="section-toc.1-1.7.2.1.2.2">
1196 <p id="section-toc.1-1.7.2.1.2.2.1"><a href="#section-7.1.2" class="xref">7.1.2</a>.  <a href="#name-example-2-the-ingress-node-" class="xref">Example 2: The Ingress Node Does Not Have a Sufficient MSD</a><a href="#section-toc.1-1.7.2.1.2.2.1" class="pilcrow">¶</a></p>
1197 </li>
1198 </ul>
1199 </li>
1200 <li class="toc ulEmpty" id="section-toc.1-1.7.2.2">
1201 <p id="section-toc.1-1.7.2.2.1"><a href="#section-7.2" class="xref">7.2</a>.  <a href="#name-considerations-for-the-plac" class="xref">Considerations for the Placement of Entropy Labels</a><a href="#section-toc.1-1.7.2.2.1" class="pilcrow">¶</a></p>
1202 <ul class="toc ulEmpty">
1203 <li class="toc ulEmpty" id="section-toc.1-1.7.2.2.2.1">
1204 <p id="section-toc.1-1.7.2.2.2.1.1"><a href="#section-7.2.1" class="xref">7.2.1</a>.  <a href="#name-erld-value" class="xref">ERLD Value</a><a href="#section-toc.1-1.7.2.2.2.1.1" class="pilcrow">¶</a></p>
1205 </li>
1206 <li class="toc ulEmpty" id="section-toc.1-1.7.2.2.2.2">
1207 <p id="section-toc.1-1.7.2.2.2.2.1"><a href="#section-7.2.2" class="xref">7.2.2</a>.  <a href="#name-segment-type" class="xref">Segment Type</a><a href="#section-toc.1-1.7.2.2.2.2.1" class="pilcrow">¶</a></p>
1208 </li>
1209 <li class="toc ulEmpty" id="section-toc.1-1.7.2.2.2.3">
1210 <p id="section-toc.1-1.7.2.2.2.3.1"><a href="#section-7.2.3" class="xref">7.2.3</a>.  <a href="#name-maximizing-number-of-lsrs-t" class="xref">Maximizing Number of LSRs That Will Load-Balance</a><a href="#section-toc.1-1.7.2.2.2.3.1" class="pilcrow">¶</a></p>
1211 </li>
1212 <li class="toc ulEmpty" id="section-toc.1-1.7.2.2.2.4">
1213 <p id="section-toc.1-1.7.2.2.2.4.1"><a href="#section-7.2.4" class="xref">7.2.4</a>.  <a href="#name-preference-for-a-part-of-th" class="xref">Preference for a Part of the Path</a><a href="#section-toc.1-1.7.2.2.2.4.1" class="pilcrow">¶</a></p>
1214 </li>
1215 <li class="toc ulEmpty" id="section-toc.1-1.7.2.2.2.5">
1216 <p id="section-toc.1-1.7.2.2.2.5.1"><a href="#section-7.2.5" class="xref">7.2.5</a>.  <a href="#name-combining-criteria" class="xref">Combining Criteria</a><a href="#section-toc.1-1.7.2.2.2.5.1" class="pilcrow">¶</a></p>
1217 </li>
1218 </ul>
1219 </li>
1220 </ul>
1221 </li>
1222 <li class="toc ulEmpty" id="section-toc.1-1.8">
1223 <p id="section-toc.1-1.8.1"><a href="#section-8" class="xref">8</a>.  <a href="#name-a-simple-example-algorithm" class="xref">A Simple Example Algorithm</a><a href="#section-toc.1-1.8.1" class="pilcrow">¶</a></p>
1224 </li>
1225 <li class="toc ulEmpty" id="section-toc.1-1.9">
1226 <p id="section-toc.1-1.9.1"><a href="#section-9" class="xref">9</a>.  <a href="#name-deployment-considerations" class="xref">Deployment Considerations</a><a href="#section-toc.1-1.9.1" class="pilcrow">¶</a></p>
1227 </li>
1228 <li class="toc ulEmpty" id="section-toc.1-1.10">
1229 <p id="section-toc.1-1.10.1"><a href="#section-10" class="xref">10</a>. <a href="#name-options-considered" class="xref">Options Considered</a><a href="#section-toc.1-1.10.1" class="pilcrow">¶</a></p>
1230 <ul class="toc ulEmpty">
1231 <li class="toc ulEmpty" id="section-toc.1-1.10.2.1">
1232 <p id="section-toc.1-1.10.2.1.1"><a href="#section-10.1" class="xref">10.1</a>.  <a href="#name-single-el-at-the-bottom-of-" class="xref">Single EL at the Bottom of the Stack</a><a href="#section-toc.1-1.10.2.1.1" class="pilcrow">¶</a></p>
1233 </li>
1234 <li class="toc ulEmpty" id="section-toc.1-1.10.2.2">
1235 <p id="section-toc.1-1.10.2.2.1"><a href="#section-10.2" class="xref">10.2</a>.  <a href="#name-an-el-per-segment-in-the-st" class="xref">An EL per Segment in the Stack</a><a href="#section-toc.1-1.10.2.2.1" class="pilcrow">¶</a></p>
1236 </li>
1237 <li class="toc ulEmpty" id="section-toc.1-1.10.2.3">
1238 <p id="section-toc.1-1.10.2.3.1"><a href="#section-10.3" class="xref">10.3</a>.  <a href="#name-a-reusable-el-for-a-stack-o" class="xref">A Reusable EL for a Stack of Tunnels</a><a href="#section-toc.1-1.10.2.3.1" class="pilcrow">¶</a></p>
1239 </li>
1240 <li class="toc ulEmpty" id="section-toc.1-1.10.2.4">
1241 <p id="section-toc.1-1.10.2.4.1"><a href="#section-10.4" class="xref">10.4</a>.  <a href="#name-el-at-top-of-stack" class="xref">EL at Top of Stack</a><a href="#section-toc.1-1.10.2.4.1" class="pilcrow">¶</a></p>
1242 </li>
1243 <li class="toc ulEmpty" id="section-toc.1-1.10.2.5">
1244 <p id="section-toc.1-1.10.2.5.1"><a href="#section-10.5" class="xref">10.5</a>.  <a href="#name-els-at-readable-label-stack" class="xref">ELs at Readable Label Stack Depths</a><a href="#section-toc.1-1.10.2.5.1" class="pilcrow">¶</a></p>
1245 </li>
1246 </ul>
1247 </li>
1248 <li class="toc ulEmpty" id="section-toc.1-1.11">
1249 <p id="section-toc.1-1.11.1"><a href="#section-11" class="xref">11</a>. <a href="#name-iana-considerations" class="xref">IANA Considerations</a><a href="#section-toc.1-1.11.1" class="pilcrow">¶</a></p>
1250 </li>
1251 <li class="toc ulEmpty" id="section-toc.1-1.12">
1252 <p id="section-toc.1-1.12.1"><a href="#section-12" class="xref">12</a>. <a href="#name-security-considerations" class="xref">Security Considerations</a><a href="#section-toc.1-1.12.1" class="pilcrow">¶</a></p>
1253 </li>
1254 <li class="toc ulEmpty" id="section-toc.1-1.13">
1255 <p id="section-toc.1-1.13.1"><a href="#section-13" class="xref">13</a>. <a href="#name-references" class="xref">References</a><a href="#section-toc.1-1.13.1" class="pilcrow">¶</a></p>
1256 <ul class="toc ulEmpty">
1257 <li class="toc ulEmpty" id="section-toc.1-1.13.2.1">
1258 <p id="section-toc.1-1.13.2.1.1"><a href="#section-13.1" class="xref">13.1</a>.  <a href="#name-normative-references" class="xref">Normative References</a><a href="#section-toc.1-1.13.2.1.1" class="pilcrow">¶</a></p>
1259 </li>
1260 <li class="toc ulEmpty" id="section-toc.1-1.13.2.2">
1261 <p id="section-toc.1-1.13.2.2.1"><a href="#section-13.2" class="xref">13.2</a>.  <a href="#name-informative-references" class="xref">Informative References</a><a href="#section-toc.1-1.13.2.2.1" class="pilcrow">¶</a></p>
1262 </li>
1263 </ul>
1264 </li>
1265 <li class="toc ulEmpty" id="section-toc.1-1.14">
1266 <p id="section-toc.1-1.14.1"><a href="#section-appendix.a" class="xref"></a><a href="#name-acknowledgements" class="xref">Acknowledgements</a><a href="#section-toc.1-1.14.1" class="pilcrow">¶</a></p>
1267 </li>
1268 <li class="toc ulEmpty" id="section-toc.1-1.15">
1269 <p id="section-toc.1-1.15.1"><a href="#section-appendix.b" class="xref"></a><a href="#name-contributors" class="xref">Contributors</a><a href="#section-toc.1-1.15.1" class="pilcrow">¶</a></p>
1270 </li>
1271 <li class="toc ulEmpty" id="section-toc.1-1.16">
1272 <p id="section-toc.1-1.16.1"><a href="#section-appendix.c" class="xref"></a><a href="#name-authors-addresses" class="xref">Authors' Addresses</a><a href="#section-toc.1-1.16.1" class="pilcrow">¶</a></p>
1273 </li>
1274 </ul>
1275 </nav>
1276 </section>
1277 </div>
1278 <section id="section-1">
1279 <h2 id="name-introduction">
1280 <a href="#section-1" class="section-number selfRef">1. </a><a href="#name-introduction" class="section-name selfRef">Introduction</a>
1281 </h2>
1282 <p id="section-1-1">
1283 Segment Routing <span>[<a href="#RFC8402" class="xref">RFC8402</a>]</span> is based on
1284 source-routed tunnels to steer a packet along a particular path. This path
1285 is encoded as an ordered list of segments. When applied to the MPLS data
1286 plane <span>[<a href="#RFC8660" class="xref">RFC8660</a>]</span>, each segment is an LSP
1287 (Label Switched Path) with an associated MPLS label value. Hence, label
1288 stacking is used to represent the ordered list of segments, and the label
1289 stack associated with an SR tunnel can be seen as nested LSPs (LSP
1290 hierarchy) in the MPLS architecture.<a href="#section-1-1" class="pilcrow">¶</a></p>
1291 <p id="section-1-2">
1292 Using label stacking to encode the list of segments has implications on the label stack depth.<a href="#section-1-2" class="pilcrow">¶</a></p>
1293 <p id="section-1-3">
1294 Traffic load-balancing over ECMP (Equal-Cost Multipath) or LAGs (Link
1295 Aggregation Groups) is usually based on a hashing function. The local node
1296 that performs the load-balancing is required to read some header fields in
1297 the incoming packets and then compute a hash based on those fields. The
1298 result of the hash is finally mapped to a list of outgoing next hops. The
1299 hashing technique is required to perform a per-flow load-balancing and
1300 thus, prevents packet misordering. For IP traffic, the usual fields that
1301 are hashed are the source address, the destination address, the protocol
1302 type, and, if provided by the upper layer, the source port and destination
1303 port.<a href="#section-1-3" class="pilcrow">¶</a></p>
1304 <p id="section-1-4">
1305 The MPLS architecture brings some challenges when an LSR (Label Switching
1306 Router) tries to look up at header fields. An LSR needs be able to look up
1307 at header fields that are beyond the MPLS label stack while the MPLS header
1308 does not provide any information about the upper-layer protocol. An LSR
1309 must perform a deeper inspection compared to an ingress router, which could
1310 be challenging for some hardware. Entropy labels (ELs) <span>[<a href="#RFC6790" class="xref">RFC6790</a>]</span> are used in the MPLS data
1311 plane to provide entropy for load-balancing. The idea behind the entropy
1312 label is that the ingress router computes a hash based on several fields
1313 from a given packet and places the result in an additional label named
1314 "entropy label". Then, this entropy label can be used as part of the hash
1315 keys used by an LSR. Using the entropy label as part of the hash keys
1316 reduces the need for deep packet inspection in the LSR while keeping a good
1317 level of entropy in the load-balancing. When the entropy label is used,
1318 the keys used in the hashing functions are still a local configuration
1319 matter, and an LSR may use solely the entropy label or a combination of
1320 multiple fields from the incoming packet.<a href="#section-1-4" class="pilcrow">¶</a></p>
1321 <p id="section-1-5">
1322 When using LSP
1323 hierarchies, there are implications on how <span>[<a href="#RFC6790" class="xref">RFC6790</a>]</span> should be
1324 applied. The current document addresses the case where a hierarchy
1325 is created at a single LSR as required by Segment Routing.<a href="#section-1-5" class="pilcrow">¶</a></p>
1326 <p id="section-1-6">
1327 A use case requiring load-balancing with SR is given in <a href="#usecase" class="xref">Section 3</a>. A recommended solution is
1328 described in <a href="#solution" class="xref">Section 7</a> keeping in consideration the limitations of
1329 implementations when applying <span>[<a href="#RFC6790" class="xref">RFC6790</a>]</span> to deeper label stacks.
1330 Options that were considered to arrive at the recommended solution
1331 are documented for historical purposes in <a href="#other-options" class="xref">Section 10</a>.<a href="#section-1-6" class="pilcrow">¶</a></p>
1332 <section id="section-1.1">
1333 <h3 id="name-requirements-language">
1334 <a href="#section-1.1" class="section-number selfRef">1.1. </a><a href="#name-requirements-language" class="section-name selfRef">Requirements Language</a>
1335 </h3>
1336 <p id="section-1.1-1">
1337 The key words "<span class="bcp14">MUST</span>", "<span class="bcp14">MUST NOT</span>",
1338 "<span class="bcp14">REQUIRED</span>", "<span class="bcp14">SHALL</span>", "<span class="bcp14">SHALL NOT</span>",
1339 "<span class="bcp14">SHOULD</span>", "<span class="bcp14">SHOULD NOT</span>",
1340 "<span class="bcp14">RECOMMENDED</span>", "<span class="bcp14">NOT RECOMMENDED</span>",
1341 "<span class="bcp14">MAY</span>", and "<span class="bcp14">OPTIONAL</span>" in this document are to be
1342 interpreted as described in BCP 14 <span>[<a href="#RFC2119" class="xref">RFC2119</a>]</span> <span>[<a href="#RFC8174" class="xref">RFC8174</a>]</span> when, and only when, they appear in all capitals, as
1343 shown here.<a href="#section-1.1-1" class="pilcrow">¶</a></p>
1344 </section>
1345 </section>
1346 <section id="section-2">
1347 <h2 id="name-abbreviations-and-terminolo">
1348 <a href="#section-2" class="section-number selfRef">2. </a><a href="#name-abbreviations-and-terminolo" class="section-name selfRef">Abbreviations and Terminology</a>
1349 </h2>
1350 <dl class="dlParallel" id="section-2-1">
1351 <dt id="section-2-1.1">Adj-SID</dt>
1352 <dd style="margin-left: 5.0em" id="section-2-1.2">Adjacency Segment Identifier<a href="#section-2-1.2" class="pilcrow">¶</a>
1353 </dd>
1354 <dt id="section-2-1.3">ECMP</dt>
1355 <dd style="margin-left: 5.0em" id="section-2-1.4">Equal-Cost Multipath<a href="#section-2-1.4" class="pilcrow">¶</a>
1356 </dd>
1357 <dt id="section-2-1.5">EL</dt>
1358 <dd style="margin-left: 5.0em" id="section-2-1.6">Entropy Label<a href="#section-2-1.6" class="pilcrow">¶</a>
1359 </dd>
1360 <dt id="section-2-1.7">ELI</dt>
1361 <dd style="margin-left: 5.0em" id="section-2-1.8">Entropy Label Indicator<a href="#section-2-1.8" class="pilcrow">¶</a>
1362 </dd>
1363 <dt id="section-2-1.9">ELC</dt>
1364 <dd style="margin-left: 5.0em" id="section-2-1.10">Entropy Label Capability<a href="#section-2-1.10" class="pilcrow">¶</a>
1365 </dd>
1366 <dt id="section-2-1.11">ERLD</dt>
1367 <dd style="margin-left: 5.0em" id="section-2-1.12">Entropy Readable Label Depth<a href="#section-2-1.12" class="pilcrow">¶</a>
1368 </dd>
1369 <dt id="section-2-1.13">FEC</dt>
1370 <dd style="margin-left: 5.0em" id="section-2-1.14">Forwarding Equivalence Class<a href="#section-2-1.14" class="pilcrow">¶</a>
1371 </dd>
1372 <dt id="section-2-1.15">LAG</dt>
1373 <dd style="margin-left: 5.0em" id="section-2-1.16">Link Aggregation Group<a href="#section-2-1.16" class="pilcrow">¶</a>
1374 </dd>
1375 <dt id="section-2-1.17">LSP</dt>
1376 <dd style="margin-left: 5.0em" id="section-2-1.18">Label Switched Path<a href="#section-2-1.18" class="pilcrow">¶</a>
1377 </dd>
1378 <dt id="section-2-1.19">LSR</dt>
1379 <dd style="margin-left: 5.0em" id="section-2-1.20">Label Switching Router<a href="#section-2-1.20" class="pilcrow">¶</a>
1380 </dd>
1381 <dt id="section-2-1.21">MPLS</dt>
1382 <dd style="margin-left: 5.0em" id="section-2-1.22">Multiprotocol Label Switching<a href="#section-2-1.22" class="pilcrow">¶</a>
1383 </dd>
1384 <dt id="section-2-1.23">MSD</dt>
1385 <dd style="margin-left: 5.0em" id="section-2-1.24">Maximum SID Depth<a href="#section-2-1.24" class="pilcrow">¶</a>
1386 </dd>
1387 <dt id="section-2-1.25">Node SID</dt>
1388 <dd style="margin-left: 5.0em" id="section-2-1.26">Node Segment Identifier<a href="#section-2-1.26" class="pilcrow">¶</a>
1389 </dd>
1390 <dt id="section-2-1.27">OAM</dt>
1391 <dd style="margin-left: 5.0em" id="section-2-1.28">Operations, Administration, and Maintenance<a href="#section-2-1.28" class="pilcrow">¶</a>
1392 </dd>
1393 <dt id="section-2-1.29">RLD</dt>
1394 <dd style="margin-left: 5.0em" id="section-2-1.30">Readable Label Depth<a href="#section-2-1.30" class="pilcrow">¶</a>
1395 </dd>
1396 <dt id="section-2-1.31">SID</dt>
1397 <dd style="margin-left: 5.0em" id="section-2-1.32">Segment Identifier<a href="#section-2-1.32" class="pilcrow">¶</a>
1398 </dd>
1399 <dt id="section-2-1.33">SPT</dt>
1400 <dd style="margin-left: 5.0em" id="section-2-1.34">Shortest Path Tree<a href="#section-2-1.34" class="pilcrow">¶</a>
1401 </dd>
1402 <dt id="section-2-1.35">SR</dt>
1403 <dd style="margin-left: 5.0em" id="section-2-1.36">Segment Routing<a href="#section-2-1.36" class="pilcrow">¶</a>
1404 </dd>
1405 <dt id="section-2-1.37">SRGB</dt>
1406 <dd style="margin-left: 5.0em" id="section-2-1.38">Segment Routing Global Block<a href="#section-2-1.38" class="pilcrow">¶</a>
1407 </dd>
1408 <dt id="section-2-1.39">VPN</dt>
1409 <dd style="margin-left: 5.0em" id="section-2-1.40">Virtual Private Network<a href="#section-2-1.40" class="pilcrow">¶</a>
1410 </dd>
1411 </dl>
1412 </section>
1413 <div id="usecase">
1414 <section id="section-3">
1415 <h2 id="name-use-case-requiring-multipat">
1416 <a href="#section-3" class="section-number selfRef">3. </a><a href="#name-use-case-requiring-multipat" class="section-name selfRef">Use Case Requiring Multipath Load-Balancing</a>
1417 </h2>
1418 <p id="section-3-1">
1419 Traffic engineering is one of the applications of MPLS and is also a
1420 requirement for Segment Routing <span>[<a href="#RFC7855" class="xref">RFC7855</a>]</span>. Consider the
1421 topology shown in <a href="#fig_TE_use_case" class="xref">Figure 1</a>. The LSR S requires data to be sent to LSR D along
1422 a traffic-engineered path that goes over the link L1. Good load-balancing is
1423 also required across equal-cost paths (including parallel links). To steer
1424 traffic along a path that crosses link L1, the label stack that LSR S creates
1425 consists of a label to the Node SID of LSR P3 stacked over the label for the
1426 Adj-SID (Adjacency Segment Identifier) of link L1 and that in turn is stacked
1427 over the label to the Node SID of LSR D. For simplicity, lets assume that all
1428 LSRs use the same label space for Segment Routing (as a reminder, it is called
1429 the SRGB, Segment Routing Global Block). Let L_N-Px denote the label to be
1430 used to reach the Node SID of LSR Px. Let L_A-Ln denote the label used for
1431 the Adj-SID for link Ln. In our example, the LSR S must use the label stack
1432 &lt;L_N-P3, L_A-L1, L_N-D&gt;. However, to achieve good load-balancing over
1433 the equal-cost paths P2-P4-D, P2-P5-D, and the parallel links L3 and L4, a
1434 mechanism such as entropy labels <span>[<a href="#RFC6790" class="xref">RFC6790</a>]</span> should be adapted
1435 for Segment Routing. Indeed, the Source Packet Routing in Networking (SPRING)
1436 architecture with the MPLS data plane <span>[<a href="#RFC8660" class="xref">RFC8660</a>]</span> uses nested
1437 MPLS LSPs composing the source-routed label stack.<a href="#section-3-1" class="pilcrow">¶</a></p>
1438 <span id="name-traffic-engineering-use-cas"></span><div id="fig_TE_use_case">
1439 <figure id="figure-1">
1440 <div class="artwork art-text alignLeft" id="section-3-2.1">
1441 <pre>
1442 +------+
1443 | |
1444 +-------| P3 |-----+
1445 | +-----| |---+ |
1446 L3| |L4 +------+ L1| |L2 +----+
1447 | | | | +--| P4 |--+
1448 +-----+ +-----+ +-----+ | +----+ | +-----+
1449 | S |-----| P1 |------------| P2 |--+ +--| D |
1450 | | | | | |--+ +--| |
1451 +-----+ +-----+ +-----+ | +----+ | +-----+
1452 +--| P5 |--+
1453 +----+
1454 Key:
1455 S = Source LSR
1456 D = Destination LSR
1457 P1, P2, P3, P4, P5 = Transit LSRs
1458 L1, L2, L3, L4 = Links
1459 </pre>
1460 </div>
1461 <figcaption><a href="#figure-1" class="selfRef">Figure 1</a>:
1462 <a href="#name-traffic-engineering-use-cas" class="selfRef">Traffic-Engineering Use Case</a>
1463 </figcaption></figure>
1464 </div>
1465 <p id="section-3-3">
1466 An MPLS node may have limitations in the number of labels it can push. It may also have a limitation in the number of labels it can inspect when looking for hash keys during load-balancing.
1467 While the entropy label is normally inserted at the bottom of the transport tunnel, this may prevent an LSR from taking into account the EL in its load-balancing function if the EL is too deep in the stack.
1468 In a Segment Routing environment, it is important to define the considerations that need to be taken into account when inserting an EL.
1469 Multiple ways to apply entropy labels were considered and are
1470 documented in <a href="#other-options" class="xref">Section 10</a> along with their trade-offs. A recommended
1471 solution is described in <a href="#solution" class="xref">Section 7</a>.<a href="#section-3-3" class="pilcrow">¶</a></p>
1472 </section>
1473 </div>
1474 <div id="erld_definition">
1475 <section id="section-4">
1476 <h2 id="name-entropy-readable-label-dept">
1477 <a href="#section-4" class="section-number selfRef">4. </a><a href="#name-entropy-readable-label-dept" class="section-name selfRef">Entropy Readable Label Depth</a>
1478 </h2>
1479 <p id="section-4-1">
1480 The Entropy Readable Label Depth (ERLD) is defined as the number of labels a router can both:<a href="#section-4-1" class="pilcrow">¶</a></p>
1481 <ol start="1" type="a" class="normal" id="section-4-2">
1482 <li id="section-4-2.1">Read in an MPLS packet received on its incoming interface(s) (starting from the top of the stack).<a href="#section-4-2.1" class="pilcrow">¶</a>
1483 </li>
1484 <li id="section-4-2.2">Use in its load-balancing function.<a href="#section-4-2.2" class="pilcrow">¶</a>
1485 </li>
1486 </ol>
1487 <p id="section-4-3">The ERLD means that the router will perform load-balancing using the EL if the EL is placed within the first ERLD labels.<a href="#section-4-3" class="pilcrow">¶</a></p>
1488 <p id="section-4-4">A router capable of reading N labels but not using an EL located within those N labels <span class="bcp14">MUST</span> consider its ERLD to be 0.<a href="#section-4-4" class="pilcrow">¶</a></p>
1489 <p id="section-4-5">
1490 In a distributed switching architecture, each line card may have a
1491 different capability in terms of ERLD. For simplicity, an implementation
1492 <span class="bcp14">MAY</span> use the minimum ERLD of all line cards as the ERLD value for the system.<a href="#section-4-5" class="pilcrow">¶</a></p>
1493 <p id="section-4-6">There may also be a case where a router has a fast switching path
1494 (handled by an Application-Specific Integrated Circuit, or ASIC, or network processor) and a slow switching path (handled by a CPU) with a different ERLD for each switching path. Again, for simplicity's sake, an implementation <span class="bcp14">MAY</span> use the minimum ERLD as the ERLD value for the system.<a href="#section-4-6" class="pilcrow">¶</a></p>
1495 <p id="section-4-7">The drawback of using a single ERLD for a system lower than the capability of one or more specific components is that it may increase the number of ELI/ELs inserted. This leads to an increase of the label stack size and may have an impact on the capability of the ingress node to push this label stack.<a href="#section-4-7" class="pilcrow">¶</a></p>
1496 <p id="section-4-8">Examples:<a href="#section-4-8" class="pilcrow">¶</a></p>
1497 <span id="name-label-stacks-with-eli-el"></span><div id="fig_label_stacks">
1498 <figure id="figure-2">
1499 <div class="artwork art-text alignLeft" id="section-4-9.1">
1500 <pre>
1501 | Payload |
1502 +----------+
1503 | Payload | | EL | P7
1504 +----------+ +----------+
1505 | Payload | | EL | | ELI |
1506 +----------+ +----------+ +----------+
1507 | Payload | | EL | | ELI | | Label 50 |
1508 +----------+ +----------+ +----------+ +----------+
1509 | Payload | | EL | | ELI | | Label 40 | | Label 40 |
1510 +----------+ +----------+ +----------+ +----------+ +----------+
1511 | EL | | ELI | | Label 30 | | Label 30 | | Label 30 |
1512 +----------+ +----------+ +----------+ +----------+ +----------+
1513 | ELI | | Label 20 | | Label 20 | | Label 20 | | Label 20 |
1514 +----------+ +----------+ +----------+ +----------+ +----------+
1515 | Label 16 | | Label 16 | | Label 16 | | Label 16 | | Label 16 | P1
1516 +----------+ +----------+ +----------+ +----------+ +----------+
1517 Packet 1 Packet 2 Packet 3 Packet 4 Packet 5
1518 </pre>
1519 </div>
1520 <figcaption><a href="#figure-2" class="selfRef">Figure 2</a>:
1521 <a href="#name-label-stacks-with-eli-el" class="selfRef">Label Stacks with ELI/EL</a>
1522 </figcaption></figure>
1523 </div>
1524 <p id="section-4-10">
1525 In <a href="#fig_label_stacks" class="xref">Figure 2</a>, we consider the displayed packets received on a router interface. We consider also a single ERLD value for the router.<a href="#section-4-10" class="pilcrow">¶</a></p>
1526 <ul>
1527 <li id="section-4-11.1">If the router has an ERLD of 3, it will be able to load-balance Packet 1 displayed in <a href="#fig_label_stacks" class="xref">Figure 2</a> using the EL as part of the load-balancing keys. The ERLD value of 3 means that the router can read and take into account the entropy label for load-balancing if it is placed between position 1 (top of the MPLS label stack) and position 3.<a href="#section-4-11.1" class="pilcrow">¶</a>
1528 </li>
1529 <li id="section-4-11.2">If the router has an ERLD of 5, it will be able to load-balance Packets
1530 1 to 3 in <a href="#fig_label_stacks" class="xref">Figure 2</a> using the EL as part of the load-balancing keys. Packets
1531 4 and 5 have the EL placed at a position greater than 5, so the router is
1532 not able to read it and use it as part of the load-balancing keys.<a href="#section-4-11.2" class="pilcrow">¶</a>
1533 </li>
1534 <li id="section-4-11.3">If the router has an ERLD of 10, it will be able to load-balance all the packets displayed in <a href="#fig_label_stacks" class="xref">Figure 2</a> using the EL as part of the load-balancing keys.<a href="#section-4-11.3" class="pilcrow">¶</a>
1535 </li>
1536 </ul>
1537 <p id="section-4-12">To allow an efficient load-balancing based on entropy labels, a router running SPRING <span class="bcp14">SHOULD</span> advertise its ERLD (or ERLDs), so all the other SPRING routers in the network are aware of its capability. How this advertisement is done is outside the scope of this document (see <a href="#erld" class="xref">Section 7.2.1</a> for potential approaches).<a href="#section-4-12" class="pilcrow">¶</a></p>
1538 <p id="section-4-13">
1539 To advertise an ERLD value, a SPRING router:<a href="#section-4-13" class="pilcrow">¶</a></p>
1540 <ul>
1541 <li id="section-4-14.1">
1542 <span class="bcp14">MUST</span> be entropy label capable and, as a consequence, <span class="bcp14">MUST</span> apply the data-plane procedures defined in <span>[<a href="#RFC6790" class="xref">RFC6790</a>]</span>.<a href="#section-4-14.1" class="pilcrow">¶</a>
1543 </li>
1544 <li id="section-4-14.2">
1545 <span class="bcp14">MUST</span> be able to read an ELI/EL, which is located within its ERLD value.<a href="#section-4-14.2" class="pilcrow">¶</a>
1546 </li>
1547 <li id="section-4-14.3">
1548 <span class="bcp14">MUST</span> take into account an EL within the first ERLD labels in its load-balancing function.<a href="#section-4-14.3" class="pilcrow">¶</a>
1549 </li>
1550 </ul>
1551 </section>
1552 </div>
1553 <div id="msd">
1554 <section id="section-5">
1555 <h2 id="name-maximum-sid-depth">
1556 <a href="#section-5" class="section-number selfRef">5. </a><a href="#name-maximum-sid-depth" class="section-name selfRef">Maximum SID Depth</a>
1557 </h2>
1558 <p id="section-5-1">
1559 The Maximum SID Depth defines the maximum number of labels that a
1560 particular node can impose on a packet. This can include any kind of labels
1561 (service, entropy, transport, etc.). In an MPLS network, the MSD is a
1562 limit of the head-end of an SR tunnel or a Binding SID anchor node that
1563 performs imposition of additional labels on an existing label stack.<a href="#section-5-1" class="pilcrow">¶</a></p>
1564 <p id="section-5-2">
1565 Depending on the number of MPLS operations (POP, SWAP, etc.) to be performed before the PUSH, the MSD can vary due to hardware or software limitations.
1566 As for the ERLD, different MSD limits can exist within a single node based
1567 on the line-card types used in a distributed switching system. Thus, the MSD is a per link and/or per-node property.<a href="#section-5-2" class="pilcrow">¶</a></p>
1568 <p id="section-5-3">
1569 An external controller can be used to program a label stack on a particular
1570 node. This node <span class="bcp14">SHOULD</span> advertise its MSD to the controller
1571 in order to let the controller know the maximum label stack depth of the
1572 path computed that is supported on the head-end.
1573
1574 How this advertisement is done is outside the scope of this
1575 document. (<span>[<a href="#RFC8476" class="xref">RFC8476</a>]</span>, <span>[<a href="#RFC8491" class="xref">RFC8491</a>]</span>, and <span>[<a href="#I-D.ietf-idr-bgp-ls-segment-routing-msd" class="xref">MSD-BGP</a>]</span> provide
1576 examples of advertisement of the MSD.) As the controller does not have the
1577 knowledge of the entire label stack to be pushed by the node, in addition
1578 to the MSD value, the node <span class="bcp14">SHOULD</span> advertise the type of the
1579 MSD. For instance, the MSD value can represent the limit for pushing
1580 transport labels only while in reality the node can push an additional
1581 service label. As another example, the MSD value can represent the full
1582 limit of the node including all label types (transport, service, entropy,
1583 etc.). This gives the ability for the controller to program a label stack
1584 while leaving room for the local node to add more labels (e.g., service,
1585 entropy, etc.) without reaching the hardware/software limit. If the node
1586 does not provide the meaning of the MSD value, the controller could program
1587 an LSP using a number of labels equal to the full limit of the node. When
1588 receiving this label stack from the controller, the ingress node may not be
1589 able to add any service (L2VPN, L3VPN, EVPN, etc.) label on top of this
1590 label stack. The consequence could be for the ingress node to drop service
1591 packets that should have been forwarded over the LSP.<a href="#section-5-3" class="pilcrow">¶</a></p>
1592 <span id="name-topology-illustrating-label"></span><div id="fig_packet">
1593 <figure id="figure-3">
1594 <div class="artwork art-text alignLeft" id="section-5-4.1">
1595 <pre>
1596 P7 ---- P8 ---- P9
1597 / \
1598 PE1 --- P1 --- P2 --- P3 --- P4 --- P5 --- P6 --- PE2
1599 | \ |
1600 ----&gt; P10 \ |
1601 IP Pkt | \ |
1602 P11 --- P12 --- P13
1603 100 10000
1604 </pre>
1605 </div>
1606 <figcaption><a href="#figure-3" class="selfRef">Figure 3</a>:
1607 <a href="#name-topology-illustrating-label" class="selfRef">Topology Illustrating Label Stack Reduction</a>
1608 </figcaption></figure>
1609 </div>
1610 <p id="section-5-5">
1611 In <a href="#fig_packet" class="xref">Figure 3</a>, an IP packet comes into the MPLS network at PE1. All metrics
1612 are considered equal to 1 except P12-P13, which is 10000, and P11-P12,
1613 which is 100. PE1 wants to steer the traffic using a SPRING path to PE2
1614 along PE1 -&gt; P1 -&gt; P7 -&gt; P8 -&gt; P9 -&gt; P4 -&gt; P5 -&gt; P10 -&gt; P11 -&gt; P12 -&gt; P13
1615 -&gt; PE2. By using Adj-SIDs only, PE1 (acting as an ingress LSR, also known
1616 as an I-LSR) will be required to push 10 labels on the IP packet received
1617 and thus, requires an MSD of 10. If the IP packet should be carried over
1618 an MPLS service like a regular layer 3 VPN, an additional service label
1619 should be imposed requiring an MSD of 11 for PE1. In addition, if PE1
1620 wants to insert an ELI/EL for load-balancing purposes, PE1 will need to
1621 push 13 labels on the IP packet requiring an MSD of 13.<a href="#section-5-5" class="pilcrow">¶</a></p>
1622 <p id="section-5-6">
1623 In the SPRING architecture, Node SIDs or Binding SIDs can be used to reduce the label stack size. As an example, to steer the traffic on the same path as before, PE1 could use the following label stack: &lt;Node_P9, Node_P5, Binding_P5, Node_PE2&gt;.
1624 In this example, we consider a combination of Node SIDs and a Binding SID
1625 advertised by P5 that will stitch the traffic along the path P10 -&gt; P11
1626 -&gt; P12 -&gt; P13. The instruction associated with the Binding SID at P5 is thus to swap Binding_P5 to Adj_P12-P13 and then push &lt;Adj_P11-P12, Node_P11&gt;.
1627 P5 acts as a stitching node that pushes additional labels on an existing label stack; P5's MSD needs also to be taken into account and may limit the number of labels that can be imposed.<a href="#section-5-6" class="pilcrow">¶</a></p>
1628 </section>
1629 </div>
1630 <div id="stitching">
1631 <section id="section-6">
1632 <h2 id="name-lsp-stitching-using-the-bin">
1633 <a href="#section-6" class="section-number selfRef">6. </a><a href="#name-lsp-stitching-using-the-bin" class="section-name selfRef">LSP Stitching Using the Binding SID</a>
1634 </h2>
1635 <p id="section-6-1">
1636 The Binding SID allows binding a segment identifier to an existing LSP. As
1637 examples, the Binding SID can represent an RSVP-TE tunnel, an LDP path
1638 (through the Mapping Server Advertisement), or a SPRING path. Each
1639 tail-end router of an MPLS LSP associated with a Binding SID has its own
1640 entropy label capability. The entropy label capability of the associated
1641 LSP is advertised in the control-plane protocol used to signal the LSP.<a href="#section-6-1" class="pilcrow">¶</a></p>
1642 <p id="section-6-2">
1643 In <a href="#fig_stitching_example" class="xref">Figure 4</a>, we consider that:<a href="#section-6-2" class="pilcrow">¶</a></p>
1644 <ul>
1645 <li id="section-6-3.1">P6, PE2, P10, P11, P12, and P13 are pure LDP routers.<a href="#section-6-3.1" class="pilcrow">¶</a>
1646 </li>
1647 <li id="section-6-3.2">PE1, P1, P2, P3, P4, P7, P8, and P9 are pure SPRING routers.<a href="#section-6-3.2" class="pilcrow">¶</a>
1648 </li>
1649 <li id="section-6-3.3">P5 is running SPRING and LDP.<a href="#section-6-3.3" class="pilcrow">¶</a>
1650 </li>
1651 <li id="section-6-3.4">P5 acts as a Mapping Server and advertises Prefix-SIDs for the LDP FECs: an index value of 20 is used for PE2.<a href="#section-6-3.4" class="pilcrow">¶</a>
1652 </li>
1653 <li id="section-6-3.5">All SPRING routers use an SRGB of [1000, 1999].<a href="#section-6-3.5" class="pilcrow">¶</a>
1654 </li>
1655 <li id="section-6-3.6">P6 advertises label 20 for the PE2 FEC.<a href="#section-6-3.6" class="pilcrow">¶</a>
1656 </li>
1657 <li id="section-6-3.7">Traffic from PE1 to PE2 uses the shortest path.<a href="#section-6-3.7" class="pilcrow">¶</a>
1658 </li>
1659 </ul>
1660 <span id="name-example-illustrating-need-f"></span><div id="fig_stitching_example">
1661 <figure id="figure-4">
1662 <div class="artwork art-text alignLeft" id="section-6-4.1">
1663 <pre>
1664 PE1 ----- P1 -- P2 -- P3 -- P4 ---- P5 --- P6 --- PE2
1665 --&gt; +----+ +----+ +----+ +----+
1666 IP Pkt | IP | | IP | | IP | | IP |
1667 +----+ +----+ +----+ +----+
1668 |1020| |1020| | 20 |
1669 +----+ +----+ +----+
1670 SPRING LDP
1671 </pre>
1672 </div>
1673 <figcaption><a href="#figure-4" class="selfRef">Figure 4</a>:
1674 <a href="#name-example-illustrating-need-f" class="selfRef">Example Illustrating Need for ELC Propagation</a>
1675 </figcaption></figure>
1676 </div>
1677 <p id="section-6-5">In terms of packet forwarding, by learning the Mapping Server Advertisement from P5, PE1 imposes a label 1020 to an IP packet destined to PE2.
1678 SPRING routers along the shortest path to PE2 will switch the traffic
1679 until it reaches P5. P5 will perform the LSP stitching by swapping the
1680 SPRING label 1020 to the LDP label 20 advertised by the next hop P6.
1681 P6 will finally forward the packet using the LDP label towards PE2.<a href="#section-6-5" class="pilcrow">¶</a></p>
1682 <p id="section-6-6">
1683 PE1 cannot push an ELI/EL for the Binding SID without knowing that the
1684 tail end of the LSP associated with the binding (PE2) is entropy label capable.<a href="#section-6-6" class="pilcrow">¶</a></p>
1685 <p id="section-6-7">
1686 To accommodate the mix of signaling protocols involved during the stitching, the entropy label capability <span class="bcp14">SHOULD</span> be propagated between the signaling domains.
1687 Each Binding SID <span class="bcp14">SHOULD</span> have its own entropy label capability that <span class="bcp14">MUST</span> be inherited from the entropy label capability of the associated LSP.
1688 If the router advertising the Binding SID does not know the ELC state
1689 of the target FEC, it <span class="bcp14">MUST NOT</span> set the ELC for the
1690 Binding SID.
1691 An ingress node <span class="bcp14">MUST NOT</span> push an ELI/EL associated with
1692 a Binding SID unless this Binding SID has the entropy label capability.
1693 How the entropy label capability is advertised for a Binding SID is outside the scope of this document (see <a href="#erld" class="xref">Section 7.2.1</a> for potential approaches).<a href="#section-6-7" class="pilcrow">¶</a></p>
1694 <p id="section-6-8">
1695 In our example, if PE2 is LDP entropy label capable, it will add the
1696 entropy label capability in its LDP advertisement. When P5 receives
1697 the FEC/label binding for PE2, it learns about the ELC and can set the
1698 ELC in the Mapping Server Advertisement. Thus, PE1 learns about the
1699 ELC of PE2 and may push an ELI/EL associated with the Binding SID.<a href="#section-6-8" class="pilcrow">¶</a></p>
1700 <p id="section-6-9">
1701 The proposed solution only works if the SPRING router advertising the
1702 Binding SID is also performing the data-plane LSP stitching.
1703 In our example, if the Mapping Server function is hosted on P8 instead
1704 of P5, P8 does not know about the ELC state of PE2's LDP FEC. As a
1705 consequence, it does not set the ELC for the associated Binding SID.<a href="#section-6-9" class="pilcrow">¶</a></p>
1706 </section>
1707 </div>
1708 <div id="solution">
1709 <section id="section-7">
1710 <h2 id="name-insertion-of-entropy-labels">
1711 <a href="#section-7" class="section-number selfRef">7. </a><a href="#name-insertion-of-entropy-labels" class="section-name selfRef">Insertion of Entropy Labels for SPRING Path</a>
1712 </h2>
1713 <div id="overview">
1714 <section id="section-7.1">
1715 <h3 id="name-overview">
1716 <a href="#section-7.1" class="section-number selfRef">7.1. </a><a href="#name-overview" class="section-name selfRef">Overview</a>
1717 </h3>
1718 <p id="section-7.1-1">
1719 The solution described in this section follows the data-plane processing defined in <span>[<a href="#RFC6790" class="xref">RFC6790</a>]</span>. Within a SPRING path, a node may be ingress, egress, transit (regarding the entropy label processing described in <span>[<a href="#RFC6790" class="xref">RFC6790</a>]</span>), or it can be any combination of those.
1720 For example:<a href="#section-7.1-1" class="pilcrow">¶</a></p>
1721 <ul>
1722 <li id="section-7.1-2.1">The ingress node of a SPRING domain can be an ingress node from an entropy label perspective.<a href="#section-7.1-2.1" class="pilcrow">¶</a>
1723 </li>
1724 <li id="section-7.1-2.2">Any LSR terminating a segment of the SPRING path is an egress node (because it terminates the segment) but can also be a transit node if the SPRING path is not terminated because there is a subsequent SPRING MPLS label in the stack.<a href="#section-7.1-2.2" class="pilcrow">¶</a>
1725 </li>
1726 <li id="section-7.1-2.3">Any LSR processing a Binding SID may be a transit node and an
1727 ingress node (because it may push additional labels when processing
1728 the Binding SID).<a href="#section-7.1-2.3" class="pilcrow">¶</a>
1729 </li>
1730 </ul>
1731 <p id="section-7.1-3">
1732 As described earlier, an LSR may have a limitation (the ERLD) on the depth of the label stack that it
1733 can read and process in order to do multipath load-balancing based on entropy labels.<a href="#section-7.1-3" class="pilcrow">¶</a></p>
1734 <p id="section-7.1-4">If an EL does not occur within the ERLD of an
1735 LSR in the label stack of an MPLS packet that it receives, then it
1736 would lead to poor load-balancing at that LSR. Hence, an ELI/EL pair
1737 must be within the ERLD of the LSR in order for the LSR to use the EL
1738 during load-balancing.<a href="#section-7.1-4" class="pilcrow">¶</a></p>
1739 <p id="section-7.1-5">
1740 Adding a single ELI/EL pair for the entire SPRING path can also lead
1741 to poor load-balancing as well because the ELI/EL may not occur within
1742 the ERLD of some LSR on the path (if too deep) or may not be present
1743 in the stack when it reaches some LSRs (if it is too shallow).<a href="#section-7.1-5" class="pilcrow">¶</a></p>
1744 <p id="section-7.1-6">
1745 In order for the EL to occur within the ERLD of LSRs along the path
1746 corresponding to a SPRING label stack, multiple &lt;ELI, EL&gt; pairs <span class="bcp14">MAY</span> be
1747 inserted in this label stack.<a href="#section-7.1-6" class="pilcrow">¶</a></p>
1748 <p id="section-7.1-7">
1749 The insertion of an ELI/EL <span class="bcp14">MUST</span> occur only with a SPRING
1750 label advertised by an LSR that advertised an ERLD (the LSR is entropy
1751 label capable) or with a SPRING label associated with a Binding SID that has the ELC set.<a href="#section-7.1-7" class="pilcrow">¶</a></p>
1752 <p id="section-7.1-8">
1753 The ELs among multiple &lt;ELI, EL&gt; pairs inserted in the
1754 stack <span class="bcp14">MAY</span> be the same or different. The LSR that inserts &lt;ELI, EL&gt; pairs
1755 can have limitations on the number of such pairs that it can insert
1756 and also the depth at which it can insert them. If, due to
1757 limitations, the inserted ELs are at positions such that an LSR along
1758 the path receives an MPLS packet without an EL in the label stack
1759 within that LSR's ERLD, then the load-balancing performed by that LSR
1760 would be poor. An implementation <span class="bcp14">MAY</span> consider multiple criteria when inserting &lt;ELI, EL&gt; pairs.<a href="#section-7.1-8" class="pilcrow">¶</a></p>
1761 <div id="ex1">
1762 <section id="section-7.1.1">
1763 <h4 id="name-example-1-the-ingress-node-">
1764 <a href="#section-7.1.1" class="section-number selfRef">7.1.1. </a><a href="#name-example-1-the-ingress-node-" class="section-name selfRef">Example 1: The Ingress Node Has a Sufficient MSD</a>
1765 </h4>
1766 <span id="name-accommodating-msd-limitatio"></span><div id="fig_ex1">
1767 <figure id="figure-5">
1768 <div class="artwork art-text alignLeft" id="section-7.1.1-1.1">
1769 <pre>
1770 ECMP LAG LAG
1771 PE1 --- P1 --- P2 --- P3 --- P4 --- P5 --- P6 --- PE2
1772 </pre>
1773 </div>
1774 <figcaption><a href="#figure-5" class="selfRef">Figure 5</a>:
1775 <a href="#name-accommodating-msd-limitatio" class="selfRef">Accommodating MSD Limitations</a>
1776 </figcaption></figure>
1777 </div>
1778 <p id="section-7.1.1-2">
1779 In <a href="#fig_ex1" class="xref">Figure 5</a>, PE1 wants to forward some MPLS VPN traffic over an explicit path to PE2 resulting in the following label stack to be pushed onto the received IP header: &lt;Adj_P1P2, Adj_set_P2P3, Adj_P3P4, Adj_P4P5, Adj_P5P6, Adj_P6PE2, VPN_label&gt;.
1780 PE1 is limited to push a maximum of 11 labels (MSD=11). P2, P3, and P6 have an ERLD of 3 while others have an ERLD of 10.<a href="#section-7.1.1-2" class="pilcrow">¶</a></p>
1781 <p id="section-7.1.1-3">
1782 PE1 can only add two ELI/EL pairs in the label stack due to its MSD limitation. It should insert them strategically to benefit load-balancing along the longest part of the path.<a href="#section-7.1.1-3" class="pilcrow">¶</a></p>
1783 <p id="section-7.1.1-4">
1784 PE1 can take into account multiple parameters when inserting ELs; as examples:<a href="#section-7.1.1-4" class="pilcrow">¶</a></p>
1785 <ul>
1786 <li id="section-7.1.1-5.1">The ERLD value advertised by transit nodes.<a href="#section-7.1.1-5.1" class="pilcrow">¶</a>
1787 </li>
1788 <li id="section-7.1.1-5.2">The requirement of load-balancing for a particular label value.<a href="#section-7.1.1-5.2" class="pilcrow">¶</a>
1789 </li>
1790 <li id="section-7.1.1-5.3">Any service provider preference: favor beginning of the path or end of the path.<a href="#section-7.1.1-5.3" class="pilcrow">¶</a>
1791 </li>
1792 </ul>
1793 <p id="section-7.1.1-6">
1794 In <a href="#fig_ex1" class="xref">Figure 5</a>, a good strategy may be to use the following stack &lt;Adj_P1P2, Adj_set_P2P3, ELI1, EL1, Adj_P3P4, Adj_P4P5, Adj_P5P6, Adj_P6PE2, ELI2, EL2, VPN_label&gt;.
1795 The original stack requests P2 to forward based on an L3 adjacency-set that will require load-balancing. Therefore, it is important to ensure that P2 can load-balance correctly.
1796 As P2 has a limited ERLD of 3, an ELI/EL must be inserted just after the label that P2 will use to forward.
1797 On the path to PE2, P3 has also a limited ERLD, but P3 will forward based on a regular adjacency segment that may not require load-balancing.
1798 Therefore, it does not seem important to ensure that P3 can do load-balancing despite its limited ERLD.
1799 The next nodes along the forwarding path have a high ERLD that does not cause
1800 any issue, except P6. Moreover, P6 is using some LAGs to PE2 and so is
1801 expected to load-balance.
1802 It becomes important to insert a new ELI/EL just after the P6 forwarding label.<a href="#section-7.1.1-6" class="pilcrow">¶</a></p>
1803 <p id="section-7.1.1-7">
1804 In the case above, the ingress node was able to support a sufficient MSD to ensure
1805 end-to-end load-balancing while taking into account the path attributes.
1806 However, there might be cases where the ingress node may not have the necessary label imposition capacity.<a href="#section-7.1.1-7" class="pilcrow">¶</a></p>
1807 </section>
1808 </div>
1809 <div id="ex2">
1810 <section id="section-7.1.2">
1811 <h4 id="name-example-2-the-ingress-node-">
1812 <a href="#section-7.1.2" class="section-number selfRef">7.1.2. </a><a href="#name-example-2-the-ingress-node-" class="section-name selfRef">Example 2: The Ingress Node Does Not Have a Sufficient MSD</a>
1813 </h4>
1814 <span id="name-msd-considerations"></span><div id="fig_ex2">
1815 <figure id="figure-6">
1816 <div class="artwork art-text alignLeft" id="section-7.1.2-1.1">
1817 <pre>
1818 ECMP LAG ECMP ECMP
1819 PE1 --- P1 --- P2 --- P3 --- P4 --- P5 --- P6 --- P7 --- P8 --- PE2
1820 </pre>
1821 </div>
1822 <figcaption><a href="#figure-6" class="selfRef">Figure 6</a>:
1823 <a href="#name-msd-considerations" class="selfRef">MSD Considerations</a>
1824 </figcaption></figure>
1825 </div>
1826 <p id="section-7.1.2-2">
1827 In <a href="#fig_ex2" class="xref">Figure 6</a>, PE1 wants to forward MPLS VPN traffic over an explicit path to PE2 resulting in the following label stack to be pushed onto the IP header: &lt;Adj_P1P2, Adj_set_P2P3, Adj_P3P4, Adj_P4P5, Adj_P5P6, Adj_set_P6P7, Adj_P7P8; Adj_set_P8PE2, VPN_label&gt;.
1828 PE1 is limited to push a maximum of 11 labels. P2, P3, and P6 have an ERLD of 3 while others have an ERLD of 15.<a href="#section-7.1.2-2" class="pilcrow">¶</a></p>
1829 <p id="section-7.1.2-3">
1830 Using a similar strategy as the previous case may lead to a dilemma, as PE1 can only push a single ELI/EL while we may need a minimum of three to load-balance the end-to-end path.
1831 An optimized stack that would enable end-to-end load-balancing may be: &lt;Adj_P1P2, Adj_set_P2P3, ELI1, EL1, Adj_P3P4, Adj_P4P5, Adj_P5P6, Adj_set_P6P7, ELI2, EL2, Adj_P7P8, Adj_set_P8PE2, ELI3, EL3, VPN_label&gt;.<a href="#section-7.1.2-3" class="pilcrow">¶</a></p>
1832 <p id="section-7.1.2-4">
1833 A decision needs to be taken to favor some part of the path for load-balancing considering that load-balancing may not work on the other parts.
1834 A service provider may decide to place the ELI/EL after the P6 forwarding
1835 label as it will allow P4 and P6 to load-balance. Placing the ELI/EL at the bottom of the stack is also a possibility enabling load-balancing for P4 and P8.<a href="#section-7.1.2-4" class="pilcrow">¶</a></p>
1836 </section>
1837 </div>
1838 </section>
1839 </div>
1840 <div id="el_placement">
1841 <section id="section-7.2">
1842 <h3 id="name-considerations-for-the-plac">
1843 <a href="#section-7.2" class="section-number selfRef">7.2. </a><a href="#name-considerations-for-the-plac" class="section-name selfRef">Considerations for the Placement of Entropy Labels</a>
1844 </h3>
1845 <p id="section-7.2-1">
1846 The sample cases described in the previous section showed that ELI/EL placement when the maximum number of labels to be pushed is limited is not an easy decision, and multiple criteria may be taken into account.<a href="#section-7.2-1" class="pilcrow">¶</a></p>
1847 <p id="section-7.2-2">
1848 This section describes some considerations that an implementation <span class="bcp14">MAY</span> take into account when placing ELI/ELs. This list of criteria is not considered exhaustive and an implementation <span class="bcp14">MAY</span> take into account additional criteria or tiebreakers that are not documented here.
1849 As the insertion of ELI/ELs is performed by the ingress node, having ingress nodes that do not use the same criteria does not cause an interoperability issue. However, from a network design and operation perspective, it is better to have all ingress routers using the same criteria.<a href="#section-7.2-2" class="pilcrow">¶</a></p>
1850 <p id="section-7.2-3">
1851 An implementation <span class="bcp14">SHOULD</span> try to maximize the possibility of load-balancing along the path by inserting an ELI/EL where multiple equal-cost paths are available and minimize the number of ELI/ELs that need to be inserted.
1852 In case of a trade-off, an implementation <span class="bcp14">SHOULD</span> provide flexibility to the operator to select the criteria to be considered when placing ELI/ELs or specify a subobjective for optimization.<a href="#section-7.2-3" class="pilcrow">¶</a></p>
1853 <span id="name-msd-trade-offs"></span><div id="fig_consid_sample">
1854 <figure id="figure-7">
1855 <div class="artwork art-text alignLeft" id="section-7.2-4.1">
1856 <pre>
1857 2 2
1858 PE1 -- P1 -- P2 --P3 --- P4 --- P5 -- ... -- P8 -- P9 -- PE2
1859 | |
1860 P3'--- P4'--- P5'
1861 </pre>
1862 </div>
1863 <figcaption><a href="#figure-7" class="selfRef">Figure 7</a>:
1864 <a href="#name-msd-trade-offs" class="selfRef">MSD Trade-Offs</a>
1865 </figcaption></figure>
1866 </div>
1867 <p id="section-7.2-5"><a href="#fig_consid_sample" class="xref">Figure 7</a> will be used as reference in the following subsections. All
1868 metrics are equal to 1 except P3-P4 and P4-P5, which have a metric 2.
1869 We consider the MSD of nodes to be the full limit of label imposition
1870 (including service labels, entropy labels, and transport labels).<a href="#section-7.2-5" class="pilcrow">¶</a></p>
1871 <div id="erld">
1872 <section id="section-7.2.1">
1873 <h4 id="name-erld-value">
1874 <a href="#section-7.2.1" class="section-number selfRef">7.2.1. </a><a href="#name-erld-value" class="section-name selfRef">ERLD Value</a>
1875 </h4>
1876 <p id="section-7.2.1-1">
1877 As mentioned in <a href="#overview" class="xref">Section 7.1</a>, the ERLD value is an important parameter to consider when inserting an ELI/EL. If an ELI/EL does not fall within the ERLD of a node on the path, the node will not be able to load-balance the traffic efficiently.<a href="#section-7.2.1-1" class="pilcrow">¶</a></p>
1878 <p id="section-7.2.1-2">
1879 The ERLD value can be advertised via protocols, and those extensions are described in separate documents (for instance, <span>[<a href="#I-D.ietf-isis-mpls-elc" class="xref">ISIS-ELC</a>]</span> and <span>[<a href="#I-D.ietf-ospf-mpls-elc" class="xref">OSPF-ELC</a>]</span>).<a href="#section-7.2.1-2" class="pilcrow">¶</a></p>
1880 <p id="section-7.2.1-3">
1881 Let's consider a path from PE1 to PE2 using the following stack pushed by PE1: &lt;Adj_P1P2, Node_P9, Adj_P9PE2, Service_label&gt;.<a href="#section-7.2.1-3" class="pilcrow">¶</a></p>
1882 <p id="section-7.2.1-4">
1883 Using the ERLD as an input parameter can help to minimize the number of required ELI/EL pairs to be inserted.
1884 An ERLD value must be retrieved for each SPRING label in the label stack.<a href="#section-7.2.1-4" class="pilcrow">¶</a></p>
1885 <p id="section-7.2.1-5">
1886 For a label bound to an adjacency segment, the ERLD is the ERLD of the node that has advertised the adjacency segment. In the example above, the ERLD associated with Adj_P1P2 would be the ERLD of router P1, as P1 will perform the forwarding based on the Adj_P1P2 label.<a href="#section-7.2.1-5" class="pilcrow">¶</a></p>
1887 <p id="section-7.2.1-6">
1888 For a label bound to a node segment, multiple strategies <span class="bcp14">MAY</span> be implemented. An implementation <span class="bcp14">MAY</span> try to evaluate the minimum ERLD value along the node segment path.
1889 If an implementation cannot find the minimum ERLD along the path of the
1890 segment or does not support the computation of the minimum ERLD, it <span class="bcp14">SHOULD</span>
1891 instead use the ERLD of the tail-end node. Using the ERLD of the tail end of the node segment mimics the behavior of <span>[<a href="#RFC6790" class="xref">RFC6790</a>]</span> where the ingress takes only care of the egress of the LSP.
1892 In the example above, if the implementation supports computation of minimum ERLD along the path, the ERLD associated with label Node_P9 would be the minimum ERLD between nodes {P2,P3,P4 ..., P8}.
1893 If the implementation does not support the computation of minimum ERLD, it
1894 will consider the ERLD of P9 (tail-end node of Node_P9 SID). While providing
1895 the more optimal ELI/EL placement, evaluating the minimum ERLD increases the
1896 complexity of ELI/EL insertion. As the path to the Node SID may change over time, a recomputation of the minimum ERLD is required for each topology change. This recomputation may require the positions of the ELI/ELs to change.<a href="#section-7.2.1-6" class="pilcrow">¶</a></p>
1897 <p id="section-7.2.1-7">
1898 For a label bound to a Binding Segment, if the Binding Segment describes a
1899 path, an implementation <span class="bcp14">MAY</span> also try to evaluate the minimum ERLD along this
1900 path. If the implementation cannot find the minimum ERLD along the path of the
1901 segment or does not support this evaluation, it <span class="bcp14">SHOULD</span> instead use the ERLD of
1902 the node advertising the Binding SID. As for the node segment, evaluating the
1903 minimum ERLD adds complexity in the ELI/EL insertion process.<a href="#section-7.2.1-7" class="pilcrow">¶</a></p>
1904 </section>
1905 </div>
1906 <div id="sid-type">
1907 <section id="section-7.2.2">
1908 <h4 id="name-segment-type">
1909 <a href="#section-7.2.2" class="section-number selfRef">7.2.2. </a><a href="#name-segment-type" class="section-name selfRef">Segment Type</a>
1910 </h4>
1911 <p id="section-7.2.2-1">
1912 Depending on the type of segment a particular label is bound
1913 to, an implementation can deduce that this particular label
1914 will be subject to load-balancing on the path.<a href="#section-7.2.2-1" class="pilcrow">¶</a></p>
1915 <div id="node-sid">
1916 <section id="section-7.2.2.1">
1917 <h5 id="name-node-sid">
1918 <a href="#section-7.2.2.1" class="section-number selfRef">7.2.2.1. </a><a href="#name-node-sid" class="section-name selfRef">Node SID</a>
1919 </h5>
1920 <p id="section-7.2.2.1-1">
1921 An MPLS label bound to a Node SID represents a path
1922 that may cross multiple hops. Load-balancing may be
1923 needed on the node starting this path but also on any
1924 node along the path.<a href="#section-7.2.2.1-1" class="pilcrow">¶</a></p>
1925 <p id="section-7.2.2.1-2">
1926 In <a href="#fig_consid_sample" class="xref">Figure 7</a>, let's consider a path from PE1 to PE2 using the following stack pushed by PE1: &lt;Adj_P1P2, Node_P9, Adj_P9PE2, Service_label&gt;.<a href="#section-7.2.2.1-2" class="pilcrow">¶</a></p>
1927 <p id="section-7.2.2.1-3">
1928 If, for example, PE1 is limited to push 6 labels, it
1929 can add a single ELI/EL within the label stack. An
1930 operator may want to favor a placement that would
1931 allow load-balancing along the Node SID path. In
1932 <a href="#fig_consid_sample" class="xref">Figure 7</a>,
1933 P3, which is along the Node SID path,
1934 requires load-balancing between two equal-cost paths.<a href="#section-7.2.2.1-3" class="pilcrow">¶</a></p>
1935 <p id="section-7.2.2.1-4">
1936 An implementation <span class="bcp14">MAY</span> try to evaluate if load-balancing is really
1937 required within a node segment path. This could be done by running
1938 an additional SPT (Shortest Path Tree) computation and analyzing of the node segment path to
1939 prevent a node segment that does not really require load-balancing from
1940 being preferred when placing ELI/ELs. Such inspection may be time
1941 consuming for implementations and without a 100% guarantee, as a node
1942 segment path may use LAGs that are invisible to the IP
1943 topology. As a simpler approach, an implementation <span class="bcp14">MAY</span> consider that a label bound
1944 to a Node SID will be subject to load-balancing and require an
1945 ELI/⁠EL.<a href="#section-7.2.2.1-4" class="pilcrow">¶</a></p>
1946 </section>
1947 </div>
1948 <div id="adj-sid1">
1949 <section id="section-7.2.2.2">
1950 <h5 id="name-adjacency-set-sid">
1951 <a href="#section-7.2.2.2" class="section-number selfRef">7.2.2.2. </a><a href="#name-adjacency-set-sid" class="section-name selfRef">Adjacency-Set SID</a>
1952 </h5>
1953 <p id="section-7.2.2.2-1">
1954 An adjacency-set is an Adj-SID that refers to a set of
1955 adjacencies. When an adjacency-set segment is used
1956 within a label stack, an implementation can deduce
1957 that load-balancing is expected at the node that
1958 advertised this adjacency segment. An implementation
1959 <span class="bcp14">MAY</span> favor the insertion of an ELI/EL
1960 after the Adj-SID representing an adjacency-set.<a href="#section-7.2.2.2-1" class="pilcrow">¶</a></p>
1961 </section>
1962 </div>
1963 <div id="adj-sid2">
1964 <section id="section-7.2.2.3">
1965 <h5 id="name-adjacency-sid-representing-">
1966 <a href="#section-7.2.2.3" class="section-number selfRef">7.2.2.3. </a><a href="#name-adjacency-sid-representing-" class="section-name selfRef">Adjacency SID Representing a Single IP Link</a>
1967 </h5>
1968 <p id="section-7.2.2.3-1">
1969 When an adjacency segment representing a single IP link is used within a label stack, an implementation can deduce that load-balancing may not be expected at the node that advertised this adjacency segment.<a href="#section-7.2.2.3-1" class="pilcrow">¶</a></p>
1970 <p id="section-7.2.2.3-2">
1971 An implementation <span class="bcp14">MAY</span> NOT place an ELI/EL after a regular Adj-SID in order to favor the insertion of ELI/ELs following other segments.<a href="#section-7.2.2.3-2" class="pilcrow">¶</a></p>
1972 <p id="section-7.2.2.3-3">
1973 Readers should note that an adjacency segment representing a single IP link may require load-balancing. This is the case when a LAG (L2 bundle) is implemented between two IP nodes and the L2 bundle SR extensions <span>[<a href="#RFC8668" class="xref">RFC8668</a>]</span> are not implemented.
1974 In such a case, it could be useful to insert an ELI/EL in a readable position for the LSR advertising the label associated with the adjacency segment.
1975 To communicate the requirement for load-balancing for
1976 a particular Adjacency SID to ingress nodes, a user can enforce the use of the L2 bundle SR extensions defined in <span>[<a href="#RFC8668" class="xref">RFC8668</a>]</span> or can declare the single adjacency as an adjacency-set.<a href="#section-7.2.2.3-3" class="pilcrow">¶</a></p>
1977 </section>
1978 </div>
1979 <div id="adj-sid3">
1980 <section id="section-7.2.2.4">
1981 <h5 id="name-adjacency-sid-representing-a">
1982 <a href="#section-7.2.2.4" class="section-number selfRef">7.2.2.4. </a><a href="#name-adjacency-sid-representing-a" class="section-name selfRef">Adjacency SID Representing a Single Link within an L2 Bundle</a>
1983 </h5>
1984 <p id="section-7.2.2.4-1">
1985 When the L2 bundle SR extensions <span>[<a href="#RFC8668" class="xref">RFC8668</a>]</span> are used, adjacency segments may be advertised for each member of the bundle.
1986 In this case, an implementation can deduce that load-balancing is not expected on the LSR advertising this segment and <span class="bcp14">MAY</span> NOT insert an ELI/EL after the corresponding label.<a href="#section-7.2.2.4-1" class="pilcrow">¶</a></p>
1987 </section>
1988 </div>
1989 <div id="adj-sid4">
1990 <section id="section-7.2.2.5">
1991 <h5 id="name-adjacency-sid-representing-an">
1992 <a href="#section-7.2.2.5" class="section-number selfRef">7.2.2.5. </a><a href="#name-adjacency-sid-representing-an" class="section-name selfRef">Adjacency SID Representing an L2 Bundle</a>
1993 </h5>
1994 <p id="section-7.2.2.5-1">
1995 When the L2 bundle SR extensions <span>[<a href="#RFC8668" class="xref">RFC8668</a>]</span> are used, an adjacency segment may be advertised to represent the bundle.
1996 In this case, an implementation can deduce that load-balancing is expected on the LSR advertising this segment and <span class="bcp14">MAY</span> insert an ELI/EL after the corresponding label.<a href="#section-7.2.2.5-1" class="pilcrow">¶</a></p>
1997 </section>
1998 </div>
1999 </section>
2000 </div>
2001 <section id="section-7.2.3">
2002 <h4 id="name-maximizing-number-of-lsrs-t">
2003 <a href="#section-7.2.3" class="section-number selfRef">7.2.3. </a><a href="#name-maximizing-number-of-lsrs-t" class="section-name selfRef">Maximizing Number of LSRs That Will Load-Balance</a>
2004 </h4>
2005 <p id="section-7.2.3-1">
2006 When placing ELI/ELs, an implementation <span class="bcp14">MAY</span>
2007 optimize the number of LSRs that both need to load-balance
2008 (i.e., have ECMPs) and that will be able to perform
2009 load-balancing (i.e., the EL is within their ERLD).<a href="#section-7.2.3-1" class="pilcrow">¶</a></p>
2010 <p id="section-7.2.3-2">
2011 Let's consider a path from PE1 to PE2 using the following
2012 stack pushed by PE1: &lt;Adj_P1P2, Node_P9, Adj_P9PE2,
2013 Service_label&gt;. All routers have an ERLD of 10 except P1
2014 and P2, which have an ERLD of 4. PE1 is able to push 6 labels,
2015 so only a single ELI/EL can be added.<a href="#section-7.2.3-2" class="pilcrow">¶</a></p>
2016 <p id="section-7.2.3-3">
2017 In the example above, adding an ELI/EL after Adj_P1P2 will
2018 only allow load-balancing at P1, while inserting it after
2019 Adj_PE2P9 will allow load-balancing at P2, P3 ... P9 and
2020 maximize the number of LSRs that can perform load-balancing.<a href="#section-7.2.3-3" class="pilcrow">¶</a></p>
2021 </section>
2022 <section id="section-7.2.4">
2023 <h4 id="name-preference-for-a-part-of-th">
2024 <a href="#section-7.2.4" class="section-number selfRef">7.2.4. </a><a href="#name-preference-for-a-part-of-th" class="section-name selfRef">Preference for a Part of the Path</a>
2025 </h4>
2026 <p id="section-7.2.4-1">
2027 An implementation <span class="bcp14">MAY</span> allow the user to favor a part of the end-to-end path when the number of ELI/ELs that can be pushed is not enough to cover the entire path.
2028 As an example, a service provider may want to favor load-balancing at the
2029 beginning of the path or at the end of the path, so the implementation favors
2030 putting the ELI/ELs near the top or the bottom of the stack.<a href="#section-7.2.4-1" class="pilcrow">¶</a></p>
2031 </section>
2032 <section id="section-7.2.5">
2033 <h4 id="name-combining-criteria">
2034 <a href="#section-7.2.5" class="section-number selfRef">7.2.5. </a><a href="#name-combining-criteria" class="section-name selfRef">Combining Criteria</a>
2035 </h4>
2036 <p id="section-7.2.5-1">
2037 An implementation <span class="bcp14">MAY</span> combine multiple criteria to determine
2038 the best ELI/ELs placement. However, combining too many
2039 criteria could lead to implementation complexity and high
2040 resource consumption. Each time the network topology changes,
2041 a new evaluation of the ELI/EL placement will be necessary for
2042 each impacted LSP.<a href="#section-7.2.5-1" class="pilcrow">¶</a></p>
2043 </section>
2044 </section>
2045 </div>
2046 </section>
2047 </div>
2048 <div id="algo-example">
2049 <section id="section-8">
2050 <h2 id="name-a-simple-example-algorithm">
2051 <a href="#section-8" class="section-number selfRef">8. </a><a href="#name-a-simple-example-algorithm" class="section-name selfRef">A Simple Example Algorithm</a>
2052 </h2>
2053 <p id="section-8-1">
2054 A simple implementation might take into account the ERLD when placing ELI/EL
2055 while trying to minimize the number of ELI/ELs inserted and trying to
2056 maximize the number of LSRs that can load-balance.<a href="#section-8-1" class="pilcrow">¶</a></p>
2057 <p id="section-8-2">
2058 The example algorithm is based on the following considerations:<a href="#section-8-2" class="pilcrow">¶</a></p>
2059 <ul>
2060 <li id="section-8-3.1">An LSR that can insert a limited number of &lt;ELI, EL&gt; pairs should insert such pairs deeper in the stack.<a href="#section-8-3.1" class="pilcrow">¶</a>
2061 </li>
2062 <li id="section-8-3.2">An LSR should try to insert &lt;ELI, EL&gt; pairs at positions to maximize the number of transit LSRs for which the EL occurs within the ERLD of those LSRs.<a href="#section-8-3.2" class="pilcrow">¶</a>
2063 </li>
2064 <li id="section-8-3.3">An LSR should try to insert the minimum number of such pairs while trying to satisfy the above criteria.<a href="#section-8-3.3" class="pilcrow">¶</a>
2065 </li>
2066 </ul>
2067 <p id="section-8-4">
2068 The pseudocode of the example algorithm is shown below.<a href="#section-8-4" class="pilcrow">¶</a></p>
2069 <span id="name-example-algorithm-to-insert"></span><figure id="figure-8">
2070 <div id="section-8-5.1">
2071 <pre class="sourcecode lang-pseudocode">
2072 Initialize the current EL insertion point to the
2073 bottom-most label in the stack that is EL-capable
2074 while (local-node can push more &lt;ELI,EL&gt; pairs OR
2075 insertion point is not above label stack) {
2076 insert an &lt;ELI,EL&gt; pair below current insertion point
2077 move new insertion point up from current insertion point until
2078 ((last inserted EL is below the ERLD) AND (ERLD &gt; 2)
2079 AND
2080 (new insertion point is EL-capable))
2081 set current insertion point to new insertion point
2082 }
2083 </pre><a href="#section-8-5.1" class="pilcrow">¶</a>
2084 </div>
2085 <figcaption><a href="#figure-8" class="selfRef">Figure 8</a>:
2086 <a href="#name-example-algorithm-to-insert" class="selfRef">Example Algorithm to Insert &lt;ELI, EL&gt; Pairs in a Label Stack</a>
2087 </figcaption></figure>
2088 <p id="section-8-6">
2089 When this algorithm is applied to the example described in <a href="#usecase" class="xref">Section 3</a>,
2090 it will result in ELs being inserted in two positions; one after the
2091 label L_N-D and another after L_N-P3. Thus, the resulting label stack
2092 would be &lt;L_N-P3, ELI, EL, L_A-L1, L_N-D, ELI, EL&gt;.<a href="#section-8-6" class="pilcrow">¶</a></p>
2093 </section>
2094 </div>
2095 <div id="deployment">
2096 <section id="section-9">
2097 <h2 id="name-deployment-considerations">
2098 <a href="#section-9" class="section-number selfRef">9. </a><a href="#name-deployment-considerations" class="section-name selfRef">Deployment Considerations</a>
2099 </h2>
2100 <p id="section-9-1">
2101 As long as LSR node data-plane capabilities are limited (number of labels that can be pushed or number of labels that can be inspected), hop-by-hop load-balancing of SPRING-encapsulated flows will require trade-offs.<a href="#section-9-1" class="pilcrow">¶</a></p>
2102 <p id="section-9-2">
2103 The entropy label is still a good and usable solution as it allows load-balancing without having to perform deep packet inspection on each LSR: It does not seem reasonable to have an LSR inspecting UDP ports within a GRE tunnel carried over a 15-label SPRING tunnel.<a href="#section-9-2" class="pilcrow">¶</a></p>
2104 <p id="section-9-3">
2105 Due to the limited capacity of reading a deep stack of MPLS labels, multiple ELI/ELs may be required within the stack, which directly impacts the capacity of the head-end to push a deep stack: each ELI/EL inserted requires two additional labels to be pushed.<a href="#section-9-3" class="pilcrow">¶</a></p>
2106 <p id="section-9-4">
2107 Placement strategies of ELI/ELs are required to find the best trade-off. Multiple criteria could be taken into account, and some level of customization (by the user) is required to accommodate different deployments.
2108 Since analyzing the path of each destination to determine the best ELI/EL placement may be time consuming for the control plane, we encourage implementations to find the best trade-off between simplicity, resource consumption, and load-balancing efficiency.<a href="#section-9-4" class="pilcrow">¶</a></p>
2109 <p id="section-9-5">
2110 In the future, hardware and software capacity may increase data-plane capabilities and may remove some of these limitations, increasing load-balancing capability using entropy labels.<a href="#section-9-5" class="pilcrow">¶</a></p>
2111 </section>
2112 </div>
2113 <div id="other-options">
2114 <section id="section-10">
2115 <h2 id="name-options-considered">
2116 <a href="#section-10" class="section-number selfRef">10. </a><a href="#name-options-considered" class="section-name selfRef">Options Considered</a>
2117 </h2>
2118 <p id="section-10-1">Different options that were considered to arrive at the recommended
2119 solution are documented in this section.<a href="#section-10-1" class="pilcrow">¶</a></p>
2120 <p id="section-10-2">
2121 These options are detailed here only for historical purposes.<a href="#section-10-2" class="pilcrow">¶</a></p>
2122 <section id="section-10.1">
2123 <h3 id="name-single-el-at-the-bottom-of-">
2124 <a href="#section-10.1" class="section-number selfRef">10.1. </a><a href="#name-single-el-at-the-bottom-of-" class="section-name selfRef">Single EL at the Bottom of the Stack</a>
2125 </h3>
2126 <p id="section-10.1-1">
2127 In this option, a single EL is used for the entire label stack. The
2128 source LSR S encodes the entropy label at the bottom of the
2129 label stack. In the example described in <a href="#usecase" class="xref">Section 3</a>, it will result
2130 in the label stack at LSR S to look like &lt;L_N-P3, L_A-L1, L_N-D, ELI,
2131 EL&gt; &lt;remaining packet header&gt;. Note that the notation in <span>[<a href="#RFC6790" class="xref">RFC6790</a>]</span>
2132 is used to describe the label stack. An issue with this approach is
2133 that as the label stack grows due an increase in the number of SIDs,
2134 the EL goes correspondingly deeper in the label stack. Hence, transit
2135 LSRs have to access a larger number of bytes in the packet header
2136 when making forwarding decisions. In the example described in
2137 <a href="#usecase" class="xref">Section 3</a>, if we consider that the LSR P1 has an ERLD of 3, P1 would
2138 load-balance traffic poorly on the
2139 parallel links L3 and L4 since the EL is below the ERLD of P1.
2140 A load-balanced network design using this approach
2141 must ensure that all intermediate LSRs have the capability to
2142 read the maximum label stack depth as required for the
2143 application that uses source-routed stacking.<a href="#section-10.1-1" class="pilcrow">¶</a></p>
2144 <p id="section-10.1-2">
2145 This option was rejected since there exist a number of hardware
2146 implementations that have a low maximum readable label depth.
2147 Choosing this option can lead to a loss of load-balancing using EL in
2148 a significant part of the network when that is a critical requirement
2149 in a service-provider network.<a href="#section-10.1-2" class="pilcrow">¶</a></p>
2150 </section>
2151 <section id="section-10.2">
2152 <h3 id="name-an-el-per-segment-in-the-st">
2153 <a href="#section-10.2" class="section-number selfRef">10.2. </a><a href="#name-an-el-per-segment-in-the-st" class="section-name selfRef">An EL per Segment in the Stack</a>
2154 </h3>
2155 <p id="section-10.2-1">
2156 In this option, each segment/label in the stack can be given its own
2157 EL. When load-balancing is required to direct traffic on a segment,
2158 the source LSR pushes an &lt;ELI, EL&gt; before pushing the label
2159 associated to this segment. In the example described in <a href="#usecase" class="xref">Section 3</a>, the source label stack that is LSR S encoded would
2160 be &lt;L_N-P3, ELI, EL, L_A-L1, L_N-D, ELI, EL&gt;, where all the ELs
2161 can be the same. Accessing the EL at an intermediate LSR is
2162 independent of the depth of the label stack and hence, independent of
2163 the specific application that uses source-routed tunnels with label
2164 stacking. A drawback is that the depth of the label stack grows
2165 significantly, almost 3 times as the number of labels in the label
2166 stack. The network design should ensure that source LSRs have the
2167 capability to push such a deep label stack. Also, the bandwidth
2168 overhead and potential MTU issues of deep label stacks should be
2169 considered in the network design.<a href="#section-10.2-1" class="pilcrow">¶</a></p>
2170 <p id="section-10.2-2">
2171 This option was rejected due to the existence of hardware
2172 implementations that can push a limited number of labels on the label
2173 stack. Choosing this option would result in a hardware requirement
2174 to push two additional labels per tunnel label. Hence, it would
2175 restrict the number of tunnels that can be stacked in an LSP and hence,
2176 constrain the types of LSPs that can be created. This was considered
2177 unacceptable.<a href="#section-10.2-2" class="pilcrow">¶</a></p>
2178 </section>
2179 <section id="section-10.3">
2180 <h3 id="name-a-reusable-el-for-a-stack-o">
2181 <a href="#section-10.3" class="section-number selfRef">10.3. </a><a href="#name-a-reusable-el-for-a-stack-o" class="section-name selfRef">A Reusable EL for a Stack of Tunnels</a>
2182 </h3>
2183 <p id="section-10.3-1">
2184 In this option, an LSR that terminates a tunnel reuses the EL of the
2185 terminated tunnel for the next inner tunnel. It does this by storing
2186 the EL from the outer tunnel when that tunnel is terminated and
2187 reinserting it below the next inner tunnel label during the label-swap
2188 operation. The LSR that stacks tunnels should insert an EL below the
2189 outermost tunnel. It should not insert ELs for any inner tunnels.
2190 Also, the penultimate hop LSR of a segment must not pop the ELI and EL
2191 even though they are exposed as the top labels since the terminating
2192 LSR of that segment would reuse the EL for the next segment.<a href="#section-10.3-1" class="pilcrow">¶</a></p>
2193 <p id="section-10.3-2">
2194 In <a href="#usecase" class="xref">Section 3</a>, the source label stack that is LSR S
2195 encoded would be &lt;L_N-P3, ELI, EL, L_A-L1, L_N-⁠D&gt;. At P1, the
2196 outgoing label stack would be &lt;L_N-P3, ELI, EL, L_A-L1, L_N-D&gt;
2197 after it has load-balanced to one of the links L3 or L4. At P3, the
2198 outgoing label stack would be &lt;L_N-D, ELI, EL&gt;. At P2, the
2199 outgoing label stack would be &lt;L_N-D, ELI, EL&gt; and it would
2200 load-balance to one of the next-hop LSRs P4 or P5. Accessing the EL at
2201 an intermediate LSR (e.g., P1) is independent of the depth of the
2202 label stack and hence, independent of the specific use case to which
2203 the label stack is applied.<a href="#section-10.3-2" class="pilcrow">¶</a></p>
2204 <p id="section-10.3-3">
2205 This option was rejected due to the significant change in label-swap
2206 operations that would be required for existing hardware.<a href="#section-10.3-3" class="pilcrow">¶</a></p>
2207 </section>
2208 <section id="section-10.4">
2209 <h3 id="name-el-at-top-of-stack">
2210 <a href="#section-10.4" class="section-number selfRef">10.4. </a><a href="#name-el-at-top-of-stack" class="section-name selfRef">EL at Top of Stack</a>
2211 </h3>
2212 <p id="section-10.4-1">
2213 A slight variant of the reusable EL option is to keep the EL at the
2214 top of the stack rather than below the tunnel label. In this case,
2215 each LSR that is not terminating a segment should continue to keep
2216 the received EL at the top of the stack when forwarding the packet
2217 along the segment. An LSR that terminates a segment should use the
2218 EL from the terminated segment at the top of the stack when
2219 forwarding onto the next segment.<a href="#section-10.4-1" class="pilcrow">¶</a></p>
2220 <p id="section-10.4-2">
2221 This option was rejected due to the significant change in label swap
2222 operations that would be required for existing hardware.<a href="#section-10.4-2" class="pilcrow">¶</a></p>
2223 </section>
2224 <section id="section-10.5">
2225 <h3 id="name-els-at-readable-label-stack">
2226 <a href="#section-10.5" class="section-number selfRef">10.5. </a><a href="#name-els-at-readable-label-stack" class="section-name selfRef">ELs at Readable Label Stack Depths</a>
2227 </h3>
2228 <p id="section-10.5-1">
2229 In this option, the source LSR inserts ELs for tunnels in the label
2230 stack at depths such that each LSR along the path that must load-balance is able to access at least one EL. Note that the source LSR
2231 may have to insert multiple ELs in the label stack at different depths
2232 for this to work since intermediate LSRs may have differing
2233 capabilities in accessing the depth of a label stack. The label stack
2234 depth access value of intermediate LSRs must be known to create such a
2235 label stack. How this value is determined is outside the scope of
2236 this document. This value can be advertised using a protocol such as
2237 an IGP.<a href="#section-10.5-1" class="pilcrow">¶</a></p>
2238 <p id="section-10.5-2">
2239 Applying this method to the example in <a href="#usecase" class="xref">Section 3</a>, if LSR P1
2240 needs to have the EL within a depth of 4, then the source label stack that
2241 is LSR S encoded would be &lt;L_N-P3, ELI, EL, L_A-L1, L_N-D, ELI,
2242 EL&gt;, where all the ELs would typically have the same value.<a href="#section-10.5-2" class="pilcrow">¶</a></p>
2243 <p id="section-10.5-3">
2244 In the case where the ERLD has different values along the path and the
2245 LSR that is inserting &lt;ELI, EL&gt; pairs has no limit on how many pairs
2246 it can insert, and it knows the appropriate positions in the stack
2247 where they should be inserted, this option is the same as the
2248 recommended solution in <a href="#solution" class="xref">Section 7</a>.<a href="#section-10.5-3" class="pilcrow">¶</a></p>
2249 <p id="section-10.5-4">
2250 Note that a refinement of this solution, which balances the number of
2251 pushed labels against the desired entropy, is the solution described
2252 in <a href="#solution" class="xref">Section 7</a>.<a href="#section-10.5-4" class="pilcrow">¶</a></p>
2253 </section>
2254 </section>
2255 </div>
2256 <section id="section-11">
2257 <h2 id="name-iana-considerations">
2258 <a href="#section-11" class="section-number selfRef">11. </a><a href="#name-iana-considerations" class="section-name selfRef">IANA Considerations</a>
2259 </h2>
2260 <p id="section-11-1"> This document has no IANA actions.<a href="#section-11-1" class="pilcrow">¶</a></p>
2261 </section>
2262 <section id="section-12">
2263 <h2 id="name-security-considerations">
2264 <a href="#section-12" class="section-number selfRef">12. </a><a href="#name-security-considerations" class="section-name selfRef">Security Considerations</a>
2265 </h2>
2266 <p id="section-12-1">Compared to <span>[<a href="#RFC6790" class="xref">RFC6790</a>]</span>, this document introduces the notion
2267 of ERLD and MSD, and may require an ingress node to push multiple ELIs/ELs.
2268 These changes do not introduce any new security considerations beyond those
2269 already listed in <span>[<a href="#RFC6790" class="xref">RFC6790</a>]</span>.<a href="#section-12-1" class="pilcrow">¶</a></p>
2270 </section>
2271 <section id="section-13">
2272 <h2 id="name-references">
2273 <a href="#section-13" class="section-number selfRef">13. </a><a href="#name-references" class="section-name selfRef">References</a>
2274 </h2>
2275 <section id="section-13.1">
2276 <h3 id="name-normative-references">
2277 <a href="#section-13.1" class="section-number selfRef">13.1. </a><a href="#name-normative-references" class="section-name selfRef">Normative References</a>
2278 </h3>
2279 <dl class="references">
2280 <dt id="RFC6790">[RFC6790]</dt>
2281 <dd>
2282 <span class="refAuthor">Kompella, K.</span><span class="refAuthor">, Drake, J.</span><span class="refAuthor">, Amante, S.</span><span class="refAuthor">, Henderickx, W.</span><span class="refAuthor">, and L. Yong</span>, <span class="refTitle">"The Use of Entropy Labels in MPLS Forwarding"</span>, <span class="seriesInfo">RFC 6790</span>, <span class="seriesInfo">DOI 10.17487/RFC6790</span>, <time datetime="2012-11">November 2012</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc6790">https://www.rfc-editor.org/info/rfc6790</a>&gt;</span>. </dd>
2283 <dt id="RFC2119">[RFC2119]</dt>
2284 <dd>
2285 <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>&lt;<a href="https://www.rfc-editor.org/info/rfc2119">https://www.rfc-editor.org/info/rfc2119</a>&gt;</span>. </dd>
2286 <dt id="RFC8174">[RFC8174]</dt>
2287 <dd>
2288 <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>&lt;<a href="https://www.rfc-editor.org/info/rfc8174">https://www.rfc-editor.org/info/rfc8174</a>&gt;</span>. </dd>
2289 <dt id="RFC8402">[RFC8402]</dt>
2290 <dd>
2291 <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>&lt;<a href="https://www.rfc-editor.org/info/rfc8402">https://www.rfc-editor.org/info/rfc8402</a>&gt;</span>. </dd>
2292 <dt id="RFC8660">[RFC8660]</dt>
2293 <dd>
2294 <span class="refAuthor">Bashandy, A., Ed.</span><span class="refAuthor">, Filsfils, C., Ed.</span><span class="refAuthor">, Previdi, S.</span><span class="refAuthor">, Litkowski, S.</span><span class="refAuthor">, and R. Shakir</span>, <span class="refTitle">"Segment Routing with the 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>&lt;<a href="https://www.rfc-editor.org/info/rfc8660">https://www.rfc-editor.org/info/rfc8660</a>&gt;</span>. </dd>
2295 </dl>
2296 </section>
2297 <section id="section-13.2">
2298 <h3 id="name-informative-references">
2299 <a href="#section-13.2" class="section-number selfRef">13.2. </a><a href="#name-informative-references" class="section-name selfRef">Informative References</a>
2300 </h3>
2301 <dl class="references">
2302 <dt id="I-D.ietf-isis-mpls-elc">[ISIS-ELC]</dt>
2303 <dd>
2304 <span class="refAuthor">Xu, X.</span><span class="refAuthor">, Kini, S.</span><span class="refAuthor">, Psenak, P.</span><span class="refAuthor">, Filsfils, C.</span><span class="refAuthor">, Litkowski, S.</span><span class="refAuthor">, and M. Bocci</span>, <span class="refTitle">"Signaling Entropy Label Capability and Entropy Readable Label Depth Using IS-IS"</span>, <span class="refContent">Work in Progress</span>, <span class="seriesInfo">Internet-Draft, draft-ietf-isis-mpls-elc-10</span>, <time datetime="2019-10-21">21 October 2019</time>, <span>&lt;<a href="https://tools.ietf.org/html/draft-ietf-isis-mpls-elc-10">https://tools.ietf.org/html/draft-ietf-isis-mpls-elc-10</a>&gt;</span>. </dd>
2305 <dt id="I-D.ietf-ospf-mpls-elc">[OSPF-ELC]</dt>
2306 <dd>
2307 <span class="refAuthor">Xu, X.</span><span class="refAuthor">, Kini, S.</span><span class="refAuthor">, Psenak, P.</span><span class="refAuthor">, Filsfils, C.</span><span class="refAuthor">, Litkowski, S.</span><span class="refAuthor">, and M. Bocci</span>, <span class="refTitle">"Signaling Entropy Label Capability and Entropy Readable Label-stack Depth Using OSPF"</span>, <span class="refContent">Work in Progress</span>, <span class="seriesInfo">Internet-Draft, draft-ietf-ospf-mpls-elc-12</span>, <time datetime="2019-10-25">25 October 2019</time>, <span>&lt;<a href="https://tools.ietf.org/html/draft-ietf-ospf-mpls-elc-12">https://tools.ietf.org/html/draft-ietf-ospf-mpls-elc-12</a>&gt;</span>. </dd>
2308 <dt id="RFC8668">[RFC8668]</dt>
2309 <dd>
2310 <span class="refAuthor">Ginsberg, L.</span><span class="refAuthor">, Bashandy, A.</span><span class="refAuthor">, Filsfils, C.</span><span class="refAuthor">, Nanduri, M.</span><span class="refAuthor">, and E. Aries</span>, <span class="refTitle">"Advertising Layer 2 Bundle Member Link Attributes in IS-IS"</span>, <span class="seriesInfo">RFC 8668</span>, <span class="seriesInfo">DOI 10.17487/RFC8668</span>, <time datetime="2019-12">December 2019</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8668">https://www.rfc-editor.org/info/rfc8668</a>&gt;</span>. </dd>
2311 <dt id="RFC7855">[RFC7855]</dt>
2312 <dd>
2313 <span class="refAuthor">Previdi, S., Ed.</span><span class="refAuthor">, Filsfils, C., Ed.</span><span class="refAuthor">, Decraene, B.</span><span class="refAuthor">, Litkowski, S.</span><span class="refAuthor">, Horneffer, M.</span><span class="refAuthor">, and R. Shakir</span>, <span class="refTitle">"Source Packet Routing in Networking (SPRING) Problem Statement and Requirements"</span>, <span class="seriesInfo">RFC 7855</span>, <span class="seriesInfo">DOI 10.17487/RFC7855</span>, <time datetime="2016-05">May 2016</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc7855">https://www.rfc-editor.org/info/rfc7855</a>&gt;</span>. </dd>
2314 <dt id="RFC8476">[RFC8476]</dt>
2315 <dd>
2316 <span class="refAuthor">Tantsura, J.</span><span class="refAuthor">, Chunduri, U.</span><span class="refAuthor">, Aldrin, S.</span><span class="refAuthor">, and P. Psenak</span>, <span class="refTitle">"Signaling Maximum SID Depth (MSD) Using OSPF"</span>, <span class="seriesInfo">RFC 8476</span>, <span class="seriesInfo">DOI 10.17487/RFC8476</span>, <time datetime="2018-12">December 2018</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8476">https://www.rfc-editor.org/info/rfc8476</a>&gt;</span>. </dd>
2317 <dt id="RFC8491">[RFC8491]</dt>
2318 <dd>
2319 <span class="refAuthor">Tantsura, J.</span><span class="refAuthor">, Chunduri, U.</span><span class="refAuthor">, Aldrin, S.</span><span class="refAuthor">, and L. Ginsberg</span>, <span class="refTitle">"Signaling Maximum SID Depth (MSD) Using IS-IS"</span>, <span class="seriesInfo">RFC 8491</span>, <span class="seriesInfo">DOI 10.17487/RFC8491</span>, <time datetime="2018-11">November 2018</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8491">https://www.rfc-editor.org/info/rfc8491</a>&gt;</span>. </dd>
2320 <dt id="I-D.ietf-idr-bgp-ls-segment-routing-msd">[MSD-BGP]</dt>
2321 <dd>
2322 <span class="refAuthor">Tantsura, J.</span><span class="refAuthor">, Chunduri, U.</span><span class="refAuthor">, Talaulikar, K.</span><span class="refAuthor">, Mirsky, G.</span><span class="refAuthor">, and N. Triantafillis</span>, <span class="refTitle">"Signaling MSD (Maximum SID Depth) using Border Gateway Protocol Link-State"</span>, <span class="refContent">Work in Progress</span>, <span class="seriesInfo">Internet-Draft, draft-ietf-idr-bgp-ls-segment-routing-msd-09</span>, <time datetime="2019-10-15">15 October 2019</time>, <span>&lt;<a href="https://tools.ietf.org/html/draft-ietf-idr-bgp-ls-segment-routing-msd-09">https://tools.ietf.org/html/draft-ietf-idr-bgp-ls-segment-routing-msd-09</a>&gt;</span>. </dd>
2323 </dl>
2324 </section>
2325 </section>
2326 <section id="section-appendix.a">
2327 <h2 id="name-acknowledgements">
2328 <a href="#name-acknowledgements" class="section-name selfRef">Acknowledgements</a>
2329 </h2>
2330 <p id="section-appendix.a-1">The authors would like to thank John Drake, Loa Andersson, Curtis
2331 Villamizar, Greg Mirsky, Markus Jork, Kamran Raza, Carlos Pignataro, Bruno Decraene, Chris Bowers, Nobo Akiya, Daniele Ceccarelli, and Joe Clarke for
2332 their review, comments, and suggestions.<a href="#section-appendix.a-1" class="pilcrow">¶</a></p>
2333 </section>
2334 <section id="section-appendix.b">
2335 <h2 id="name-contributors">
2336 <a href="#name-contributors" class="section-name selfRef">Contributors</a>
2337 </h2>
2338 <div class="artwork art-text alignLeft" id="section-appendix.b-1">
2339 <pre>
2340 Xiaohu Xu
2341 Huawei
2342 Email: [email protected]
2343 </pre><a href="#section-appendix.b-1" class="pilcrow">¶</a>
2344 </div>
2345 <div class="artwork art-text alignLeft" id="section-appendix.b-2">
2346 <pre>
2347 Wim Hendrickx
2348 Nokia
2349 Email: [email protected]
2350 </pre><a href="#section-appendix.b-2" class="pilcrow">¶</a>
2351 </div>
2352 <div class="artwork art-text alignLeft" id="section-appendix.b-3">
2353 <pre>
2354 Gunter Van de Velde
2355 Nokia
2356 Email: [email protected]
2357 </pre><a href="#section-appendix.b-3" class="pilcrow">¶</a>
2358 </div>
2359 <div class="artwork art-text alignLeft" id="section-appendix.b-4">
2360 <pre>
2361 Acee Lindem
2362 Cisco
2363 Email: [email protected]
2364 </pre><a href="#section-appendix.b-4" class="pilcrow">¶</a>
2365 </div>
2366 </section>
2367 <div id="authors-addresses">
2368 <section id="section-appendix.c">
2369 <h2 id="name-authors-addresses">
2370 <a href="#name-authors-addresses" class="section-name selfRef">Authors' Addresses</a>
2371 </h2>
2372 <address class="vcard">
2373 <div dir="auto" class="left"><span class="fn nameRole">Sriganesh Kini</span></div>
2374 <div class="email">
2375 <span>Email:</span>
2376 <a href="mailto:[email protected]" class="email">[email protected]</a>
2377 </div>
2378 </address>
2379 <address class="vcard">
2380 <div dir="auto" class="left"><span class="fn nameRole">Kireeti Kompella</span></div>
2381 <div dir="auto" class="left"><span class="org">Juniper</span></div>
2382 <div class="email">
2383 <span>Email:</span>
2384 <a href="mailto:[email protected]" class="email">[email protected]</a>
2385 </div>
2386 </address>
2387 <address class="vcard">
2388 <div dir="auto" class="left"><span class="fn nameRole">Siva Sivabalan</span></div>
2389 <div dir="auto" class="left"><span class="org">Cisco</span></div>
2390 <div class="email">
2391 <span>Email:</span>
2392 <a href="mailto:[email protected]" class="email">[email protected]</a>
2393 </div>
2394 </address>
2395 <address class="vcard">
2396 <div dir="auto" class="left"><span class="fn nameRole">Stephane Litkowski</span></div>
2397 <div dir="auto" class="left"><span class="org">Orange</span></div>
2398 <div class="email">
2399 <span>Email:</span>
2400 <a href="mailto:[email protected]" class="email">[email protected]</a>
2401 </div>
2402 </address>
2403 <address class="vcard">
2404 <div dir="auto" class="left"><span class="fn nameRole">Rob Shakir</span></div>
2405 <div dir="auto" class="left"><span class="org">Google</span></div>
2406 <div class="email">
2407 <span>Email:</span>
2408 <a href="mailto:[email protected]" class="email">[email protected]</a>
2409 </div>
2410 </address>
2411 <address class="vcard">
2412 <div dir="auto" class="left"><span class="fn nameRole">Jeff Tantsura</span></div>
2413 <div dir="auto" class="left"><span class="org">Apstra, Inc.</span></div>
2414 <div class="email">
2415 <span>Email:</span>
2416 <a href="mailto:[email protected]" class="email">[email protected]</a>
2417 </div>
2418 </address>
2419 </section>
2420 </div>
2421 <script>var toc = document.getElementById("toc");
2422 var tocToggle = toc.querySelector("h2");
2423 var tocNav = toc.querySelector("nav");
2424
2425 // mobile menu toggle
2426 tocToggle.onclick = function(event) {
2427 if (window.innerWidth < 1024) {
2428 var tocNavDisplay = tocNav.currentStyle ? tocNav.currentStyle.display : getComputedStyle(tocNav, null).display;
2429 if (tocNavDisplay == "none") {
2430 tocNav.style.display = "block";
2431 } else {
2432 tocNav.style.display = "none";
2433 }
2434 }
2435 }
2436
2437 // toc anchor scroll to anchor
2438 tocNav.addEventListener("click", function (event) {
2439 event.preventDefault();
2440 if (event.target.nodeName == 'A') {
2441 if (window.innerWidth < 1024) {
2442 tocNav.style.display = "none";
2443 }
2444 var href = event.target.getAttribute("href");
2445 var anchorId = href.substr(1);
2446 var anchor = document.getElementById(anchorId);
2447 anchor.scrollIntoView(true);
2448 window.history.pushState("","",href);
2449 }
2450 });
2451
2452 // switch toc mode when window resized
2453 window.onresize = function () {
2454 if (window.innerWidth < 1024) {
2455 tocNav.style.display = "none";
2456 } else {
2457 tocNav.style.display = "block";
2458 }
2459 }
2460 </script>
2461 </body>
2462 </html>