Debian Codegraph @

rfc9085.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 9085: Border Gateway Protocol - Link State (BGP-LS) Extensions for Segment Routing</title>
8 <meta content="Stefano Previdi" name="author">
9 <meta content="Ketan Talaulikar" name="author">
10 <meta content="Clarence Filsfils" name="author">
11 <meta content="Hannes Gredler" name="author">
12 <meta content="Mach(Guoyi) Chen" name="author">
13 <meta content='
14 Segment Routing (SR) allows for a flexible definition of end-to-end
15 paths by encoding paths as sequences of topological subpaths, called
16 "segments". These segments are advertised by routing protocols, e.g., by
17 the link-state routing protocols (IS-IS, OSPFv2, and OSPFv3) within IGP
18 topologies.
19 This document defines extensions to the Border Gateway Protocol - Link State (BGP-LS) address family
20 in order to carry SR information via BGP.
21 ' name="description">
22 <meta content="xml2rfc 3.9.1" name="generator">
23 <meta content="BGP-LS" name="keyword">
24 <meta content="Segment Routing" name="keyword">
25 <meta content="SID" name="keyword">
26 <meta content="MPLS" name="keyword">
27 <meta content="Label advertisement" name="keyword">
28 <meta content="IS-IS" name="keyword">
29 <meta content="OSPF" name="keyword">
30 <meta content="OSPFv3" name="keyword">
31 <meta content="9085" name="rfc.number">
32 <!-- Generator version information:
33 xml2rfc 3.9.1
34 Python 3.6.10
35 appdirs 1.4.4
36 ConfigArgParse 1.2.3
37 google-i18n-address 2.3.5
38 html5lib 1.0.1
39 intervaltree 3.0.2
40 Jinja2 2.11.2
41 kitchen 1.2.6
42 lxml 4.4.2
43 pycairo 1.19.0
44 pycountry 19.8.18
45 pyflakes 2.1.1
46 PyYAML 5.3.1
47 requests 2.22.0
48 setuptools 40.6.2
49 six 1.14.0
50 WeasyPrint 51
51 -->
52 <link href="rfc9085.xml" rel="alternate" type="application/rfc+xml">
53 <link href="#copyright" rel="license">
54 <style type="text/css">/*
55
56 NOTE: Changes at the bottom of this file overrides some earlier settings.
57
58 Once the style has stabilized and has been adopted as an official RFC style,
59 this can be consolidated so that style settings occur only in one place, but
60 for now the contents of this file consists first of the initial CSS work as
61 provided to the RFC Formatter (xml2rfc) work, followed by itemized and
62 commented changes found necssary during the development of the v3
63 formatters.
64
65 */
66
67 /* fonts */
68 @import url('https://fonts.googleapis.com/css?family=Noto+Sans'); /* Sans-serif */
69 @import url('https://fonts.googleapis.com/css?family=Noto+Serif'); /* Serif (print) */
70 @import url('https://fonts.googleapis.com/css?family=Roboto+Mono'); /* Monospace */
71
72 @viewport {
73 zoom: 1.0;
74 width: extend-to-zoom;
75 }
76 @-ms-viewport {
77 width: extend-to-zoom;
78 zoom: 1.0;
79 }
80 /* general and mobile first */
81 html {
82 }
83 body {
84 max-width: 90%;
85 margin: 1.5em auto;
86 color: #222;
87 background-color: #fff;
88 font-size: 14px;
89 font-family: 'Noto Sans', Arial, Helvetica, sans-serif;
90 line-height: 1.6;
91 scroll-behavior: smooth;
92 }
93 .ears {
94 display: none;
95 }
96
97 /* headings */
98 #title, h1, h2, h3, h4, h5, h6 {
99 margin: 1em 0 0.5em;
100 font-weight: bold;
101 line-height: 1.3;
102 }
103 #title {
104 clear: both;
105 border-bottom: 1px solid #ddd;
106 margin: 0 0 0.5em 0;
107 padding: 1em 0 0.5em;
108 }
109 .author {
110 padding-bottom: 4px;
111 }
112 h1 {
113 font-size: 26px;
114 margin: 1em 0;
115 }
116 h2 {
117 font-size: 22px;
118 margin-top: -20px; /* provide offset for in-page anchors */
119 padding-top: 33px;
120 }
121 h3 {
122 font-size: 18px;
123 margin-top: -36px; /* provide offset for in-page anchors */
124 padding-top: 42px;
125 }
126 h4 {
127 font-size: 16px;
128 margin-top: -36px; /* provide offset for in-page anchors */
129 padding-top: 42px;
130 }
131 h5, h6 {
132 font-size: 14px;
133 }
134 #n-copyright-notice {
135 border-bottom: 1px solid #ddd;
136 padding-bottom: 1em;
137 margin-bottom: 1em;
138 }
139 /* general structure */
140 p {
141 padding: 0;
142 margin: 0 0 1em 0;
143 text-align: left;
144 }
145 div, span {
146 position: relative;
147 }
148 div {
149 margin: 0;
150 }
151 .alignRight.art-text {
152 background-color: #f9f9f9;
153 border: 1px solid #eee;
154 border-radius: 3px;
155 padding: 1em 1em 0;
156 margin-bottom: 1.5em;
157 }
158 .alignRight.art-text pre {
159 padding: 0;
160 }
161 .alignRight {
162 margin: 1em 0;
163 }
164 .alignRight > *:first-child {
165 border: none;
166 margin: 0;
167 float: right;
168 clear: both;
169 }
170 .alignRight > *:nth-child(2) {
171 clear: both;
172 display: block;
173 border: none;
174 }
175 svg {
176 display: block;
177 }
178 .alignCenter.art-text {
179 background-color: #f9f9f9;
180 border: 1px solid #eee;
181 border-radius: 3px;
182 padding: 1em 1em 0;
183 margin-bottom: 1.5em;
184 }
185 .alignCenter.art-text pre {
186 padding: 0;
187 }
188 .alignCenter {
189 margin: 1em 0;
190 }
191 .alignCenter > *:first-child {
192 border: none;
193 /* this isn't optimal, but it's an existence proof. PrinceXML doesn't
194 support flexbox yet.
195 */
196 display: table;
197 margin: 0 auto;
198 }
199
200 /* lists */
201 ol, ul {
202 padding: 0;
203 margin: 0 0 1em 2em;
204 }
205 ol ol, ul ul, ol ul, ul ol {
206 margin-left: 1em;
207 }
208 li {
209 margin: 0 0 0.25em 0;
210 }
211 .ulCompact li {
212 margin: 0;
213 }
214 ul.empty, .ulEmpty {
215 list-style-type: none;
216 }
217 ul.empty li, .ulEmpty li {
218 margin-top: 0.5em;
219 }
220 ul.ulBare, li.ulBare {
221 margin-left: 0em !important;
222 }
223 ul.compact, .ulCompact,
224 ol.compact, .olCompact {
225 line-height: 100%;
226 margin: 0 0 0 2em;
227 }
228
229 /* definition lists */
230 dl {
231 }
232 dl > dt {
233 float: left;
234 margin-right: 1em;
235 }
236 /*
237 dl.nohang > dt {
238 float: none;
239 }
240 */
241 dl > dd {
242 margin-bottom: .8em;
243 min-height: 1.3em;
244 }
245 dl.compact > dd, .dlCompact > dd {
246 margin-bottom: 0em;
247 }
248 dl > dd > dl {
249 margin-top: 0.5em;
250 margin-bottom: 0em;
251 }
252
253 /* links */
254 a {
255 text-decoration: none;
256 }
257 a[href] {
258 color: #22e; /* Arlen: WCAG 2019 */
259 }
260 a[href]:hover {
261 background-color: #f2f2f2;
262 }
263 figcaption a[href],
264 a[href].selfRef {
265 color: #222;
266 }
267 /* XXX probably not this:
268 a.selfRef:hover {
269 background-color: transparent;
270 cursor: default;
271 } */
272
273 /* Figures */
274 tt, code, pre, code {
275 background-color: #f9f9f9;
276 font-family: 'Roboto Mono', monospace;
277 }
278 pre {
279 border: 1px solid #eee;
280 margin: 0;
281 padding: 1em;
282 }
283 img {
284 max-width: 100%;
285 }
286 figure {
287 margin: 0;
288 }
289 figure blockquote {
290 margin: 0.8em 0.4em 0.4em;
291 }
292 figcaption {
293 font-style: italic;
294 margin: 0 0 1em 0;
295 }
296 @media screen {
297 pre {
298 overflow-x: auto;
299 max-width: 100%;
300 max-width: calc(100% - 22px);
301 }
302 }
303
304 /* aside, blockquote */
305 aside, blockquote {
306 margin-left: 0;
307 padding: 1.2em 2em;
308 }
309 blockquote {
310 background-color: #f9f9f9;
311 color: #111; /* Arlen: WCAG 2019 */
312 border: 1px solid #ddd;
313 border-radius: 3px;
314 margin: 1em 0;
315 }
316 cite {
317 display: block;
318 text-align: right;
319 font-style: italic;
320 }
321
322 /* tables */
323 table {
324 width: 100%;
325 margin: 0 0 1em;
326 border-collapse: collapse;
327 border: 1px solid #eee;
328 }
329 th, td {
330 text-align: left;
331 vertical-align: top;
332 padding: 0.5em 0.75em;
333 }
334 th {
335 text-align: left;
336 background-color: #e9e9e9;
337 }
338 tr:nth-child(2n+1) > td {
339 background-color: #f5f5f5;
340 }
341 table caption {
342 font-style: italic;
343 margin: 0;
344 padding: 0;
345 text-align: left;
346 }
347 table p {
348 /* XXX to avoid bottom margin on table row signifiers. If paragraphs should
349 be allowed within tables more generally, it would be far better to select on a class. */
350 margin: 0;
351 }
352
353 /* pilcrow */
354 a.pilcrow {
355 color: #666; /* Arlen: AHDJ 2019 */
356 text-decoration: none;
357 visibility: hidden;
358 user-select: none;
359 -ms-user-select: none;
360 -o-user-select:none;
361 -moz-user-select: none;
362 -khtml-user-select: none;
363 -webkit-user-select: none;
364 -webkit-touch-callout: none;
365 }
366 @media screen {
367 aside:hover > a.pilcrow,
368 p:hover > a.pilcrow,
369 blockquote:hover > a.pilcrow,
370 div:hover > a.pilcrow,
371 li:hover > a.pilcrow,
372 pre:hover > a.pilcrow {
373 visibility: visible;
374 }
375 a.pilcrow:hover {
376 background-color: transparent;
377 }
378 }
379
380 /* misc */
381 hr {
382 border: 0;
383 border-top: 1px solid #eee;
384 }
385 .bcp14 {
386 font-variant: small-caps;
387 }
388
389 .role {
390 font-variant: all-small-caps;
391 }
392
393 /* info block */
394 #identifiers {
395 margin: 0;
396 font-size: 0.9em;
397 }
398 #identifiers dt {
399 width: 3em;
400 clear: left;
401 }
402 #identifiers dd {
403 float: left;
404 margin-bottom: 0;
405 }
406 #identifiers .authors .author {
407 display: inline-block;
408 margin-right: 1.5em;
409 }
410 #identifiers .authors .org {
411 font-style: italic;
412 }
413
414 /* The prepared/rendered info at the very bottom of the page */
415 .docInfo {
416 color: #666; /* Arlen: WCAG 2019 */
417 font-size: 0.9em;
418 font-style: italic;
419 margin-top: 2em;
420 }
421 .docInfo .prepared {
422 float: left;
423 }
424 .docInfo .prepared {
425 float: right;
426 }
427
428 /* table of contents */
429 #toc {
430 padding: 0.75em 0 2em 0;
431 margin-bottom: 1em;
432 }
433 nav.toc ul {
434 margin: 0 0.5em 0 0;
435 padding: 0;
436 list-style: none;
437 }
438 nav.toc li {
439 line-height: 1.3em;
440 margin: 0.75em 0;
441 padding-left: 1.2em;
442 text-indent: -1.2em;
443 }
444 /* references */
445 .references dt {
446 text-align: right;
447 font-weight: bold;
448 min-width: 7em;
449 }
450 .references dd {
451 margin-left: 8em;
452 overflow: auto;
453 }
454
455 .refInstance {
456 margin-bottom: 1.25em;
457 }
458
459 .references .ascii {
460 margin-bottom: 0.25em;
461 }
462
463 /* index */
464 .index ul {
465 margin: 0 0 0 1em;
466 padding: 0;
467 list-style: none;
468 }
469 .index ul ul {
470 margin: 0;
471 }
472 .index li {
473 margin: 0;
474 text-indent: -2em;
475 padding-left: 2em;
476 padding-bottom: 5px;
477 }
478 .indexIndex {
479 margin: 0.5em 0 1em;
480 }
481 .index a {
482 font-weight: 700;
483 }
484 /* make the index two-column on all but the smallest screens */
485 @media (min-width: 600px) {
486 .index ul {
487 -moz-column-count: 2;
488 -moz-column-gap: 20px;
489 }
490 .index ul ul {
491 -moz-column-count: 1;
492 -moz-column-gap: 0;
493 }
494 }
495
496 /* authors */
497 address.vcard {
498 font-style: normal;
499 margin: 1em 0;
500 }
501
502 address.vcard .nameRole {
503 font-weight: 700;
504 margin-left: 0;
505 }
506 address.vcard .label {
507 font-family: "Noto Sans",Arial,Helvetica,sans-serif;
508 margin: 0.5em 0;
509 }
510 address.vcard .type {
511 display: none;
512 }
513 .alternative-contact {
514 margin: 1.5em 0 1em;
515 }
516 hr.addr {
517 border-top: 1px dashed;
518 margin: 0;
519 color: #ddd;
520 max-width: calc(100% - 16px);
521 }
522
523 /* temporary notes */
524 .rfcEditorRemove::before {
525 position: absolute;
526 top: 0.2em;
527 right: 0.2em;
528 padding: 0.2em;
529 content: "The RFC Editor will remove this note";
530 color: #9e2a00; /* Arlen: WCAG 2019 */
531 background-color: #ffd; /* Arlen: WCAG 2019 */
532 }
533 .rfcEditorRemove {
534 position: relative;
535 padding-top: 1.8em;
536 background-color: #ffd; /* Arlen: WCAG 2019 */
537 border-radius: 3px;
538 }
539 .cref {
540 background-color: #ffd; /* Arlen: WCAG 2019 */
541 padding: 2px 4px;
542 }
543 .crefSource {
544 font-style: italic;
545 }
546 /* alternative layout for smaller screens */
547 @media screen and (max-width: 1023px) {
548 body {
549 padding-top: 2em;
550 }
551 #title {
552 padding: 1em 0;
553 }
554 h1 {
555 font-size: 24px;
556 }
557 h2 {
558 font-size: 20px;
559 margin-top: -18px; /* provide offset for in-page anchors */
560 padding-top: 38px;
561 }
562 #identifiers dd {
563 max-width: 60%;
564 }
565 #toc {
566 position: fixed;
567 z-index: 2;
568 top: 0;
569 right: 0;
570 padding: 0;
571 margin: 0;
572 background-color: inherit;
573 border-bottom: 1px solid #ccc;
574 }
575 #toc h2 {
576 margin: -1px 0 0 0;
577 padding: 4px 0 4px 6px;
578 padding-right: 1em;
579 min-width: 190px;
580 font-size: 1.1em;
581 text-align: right;
582 background-color: #444;
583 color: white;
584 cursor: pointer;
585 }
586 #toc h2::before { /* css hamburger */
587 float: right;
588 position: relative;
589 width: 1em;
590 height: 1px;
591 left: -164px;
592 margin: 6px 0 0 0;
593 background: white none repeat scroll 0 0;
594 box-shadow: 0 4px 0 0 white, 0 8px 0 0 white;
595 content: "";
596 }
597 #toc nav {
598 display: none;
599 padding: 0.5em 1em 1em;
600 overflow: auto;
601 height: calc(100vh - 48px);
602 border-left: 1px solid #ddd;
603 }
604 }
605
606 /* alternative layout for wide screens */
607 @media screen and (min-width: 1024px) {
608 body {
609 max-width: 724px;
610 margin: 42px auto;
611 padding-left: 1.5em;
612 padding-right: 29em;
613 }
614 #toc {
615 position: fixed;
616 top: 42px;
617 right: 42px;
618 width: 25%;
619 margin: 0;
620 padding: 0 1em;
621 z-index: 1;
622 }
623 #toc h2 {
624 border-top: none;
625 border-bottom: 1px solid #ddd;
626 font-size: 1em;
627 font-weight: normal;
628 margin: 0;
629 padding: 0.25em 1em 1em 0;
630 }
631 #toc nav {
632 display: block;
633 height: calc(90vh - 84px);
634 bottom: 0;
635 padding: 0.5em 0 0;
636 overflow: auto;
637 }
638 img { /* future proofing */
639 max-width: 100%;
640 height: auto;
641 }
642 }
643
644 /* pagination */
645 @media print {
646 body {
647
648 width: 100%;
649 }
650 p {
651 orphans: 3;
652 widows: 3;
653 }
654 #n-copyright-notice {
655 border-bottom: none;
656 }
657 #toc, #n-introduction {
658 page-break-before: always;
659 }
660 #toc {
661 border-top: none;
662 padding-top: 0;
663 }
664 figure, pre {
665 page-break-inside: avoid;
666 }
667 figure {
668 overflow: scroll;
669 }
670 h1, h2, h3, h4, h5, h6 {
671 page-break-after: avoid;
672 }
673 h2+*, h3+*, h4+*, h5+*, h6+* {
674 page-break-before: avoid;
675 }
676 pre {
677 white-space: pre-wrap;
678 word-wrap: break-word;
679 font-size: 10pt;
680 }
681 table {
682 border: 1px solid #ddd;
683 }
684 td {
685 border-top: 1px solid #ddd;
686 }
687 }
688
689 /* This is commented out here, as the string-set: doesn't
690 pass W3C validation currently */
691 /*
692 .ears thead .left {
693 string-set: ears-top-left content();
694 }
695
696 .ears thead .center {
697 string-set: ears-top-center content();
698 }
699
700 .ears thead .right {
701 string-set: ears-top-right content();
702 }
703
704 .ears tfoot .left {
705 string-set: ears-bottom-left content();
706 }
707
708 .ears tfoot .center {
709 string-set: ears-bottom-center content();
710 }
711
712 .ears tfoot .right {
713 string-set: ears-bottom-right content();
714 }
715 */
716
717 @page :first {
718 padding-top: 0;
719 @top-left {
720 content: normal;
721 border: none;
722 }
723 @top-center {
724 content: normal;
725 border: none;
726 }
727 @top-right {
728 content: normal;
729 border: none;
730 }
731 }
732
733 @page {
734 size: A4;
735 margin-bottom: 45mm;
736 padding-top: 20px;
737 /* The follwing is commented out here, but set appropriately by in code, as
738 the content depends on the document */
739 /*
740 @top-left {
741 content: 'Internet-Draft';
742 vertical-align: bottom;
743 border-bottom: solid 1px #ccc;
744 }
745 @top-left {
746 content: string(ears-top-left);
747 vertical-align: bottom;
748 border-bottom: solid 1px #ccc;
749 }
750 @top-center {
751 content: string(ears-top-center);
752 vertical-align: bottom;
753 border-bottom: solid 1px #ccc;
754 }
755 @top-right {
756 content: string(ears-top-right);
757 vertical-align: bottom;
758 border-bottom: solid 1px #ccc;
759 }
760 @bottom-left {
761 content: string(ears-bottom-left);
762 vertical-align: top;
763 border-top: solid 1px #ccc;
764 }
765 @bottom-center {
766 content: string(ears-bottom-center);
767 vertical-align: top;
768 border-top: solid 1px #ccc;
769 }
770 @bottom-right {
771 content: '[Page ' counter(page) ']';
772 vertical-align: top;
773 border-top: solid 1px #ccc;
774 }
775 */
776
777 }
778
779 /* Changes introduced to fix issues found during implementation */
780 /* Make sure links are clickable even if overlapped by following H* */
781 a {
782 z-index: 2;
783 }
784 /* Separate body from document info even without intervening H1 */
785 section {
786 clear: both;
787 }
788
789
790 /* Top align author divs, to avoid names without organization dropping level with org names */
791 .author {
792 vertical-align: top;
793 }
794
795 /* Leave room in document info to show Internet-Draft on one line */
796 #identifiers dt {
797 width: 8em;
798 }
799
800 /* Don't waste quite as much whitespace between label and value in doc info */
801 #identifiers dd {
802 margin-left: 1em;
803 }
804
805 /* Give floating toc a background color (needed when it's a div inside section */
806 #toc {
807 background-color: white;
808 }
809
810 /* Make the collapsed ToC header render white on gray also when it's a link */
811 @media screen and (max-width: 1023px) {
812 #toc h2 a,
813 #toc h2 a:link,
814 #toc h2 a:focus,
815 #toc h2 a:hover,
816 #toc a.toplink,
817 #toc a.toplink:hover {
818 color: white;
819 background-color: #444;
820 text-decoration: none;
821 }
822 }
823
824 /* Give the bottom of the ToC some whitespace */
825 @media screen and (min-width: 1024px) {
826 #toc {
827 padding: 0 0 1em 1em;
828 }
829 }
830
831 /* Style section numbers with more space between number and title */
832 .section-number {
833 padding-right: 0.5em;
834 }
835
836 /* prevent monospace from becoming overly large */
837 tt, code, pre, code {
838 font-size: 95%;
839 }
840
841 /* Fix the height/width aspect for ascii art*/
842 pre.sourcecode,
843 .art-text pre {
844 line-height: 1.12;
845 }
846
847
848 /* Add styling for a link in the ToC that points to the top of the document */
849 a.toplink {
850 float: right;
851 margin-right: 0.5em;
852 }
853
854 /* Fix the dl styling to match the RFC 7992 attributes */
855 dl > dt,
856 dl.dlParallel > dt {
857 float: left;
858 margin-right: 1em;
859 }
860 dl.dlNewline > dt {
861 float: none;
862 }
863
864 /* Provide styling for table cell text alignment */
865 table td.text-left,
866 table th.text-left {
867 text-align: left;
868 }
869 table td.text-center,
870 table th.text-center {
871 text-align: center;
872 }
873 table td.text-right,
874 table th.text-right {
875 text-align: right;
876 }
877
878 /* Make the alternative author contact informatio look less like just another
879 author, and group it closer with the primary author contact information */
880 .alternative-contact {
881 margin: 0.5em 0 0.25em 0;
882 }
883 address .non-ascii {
884 margin: 0 0 0 2em;
885 }
886
887 /* With it being possible to set tables with alignment
888 left, center, and right, { width: 100%; } does not make sense */
889 table {
890 width: auto;
891 }
892
893 /* Avoid reference text that sits in a block with very wide left margin,
894 because of a long floating dt label.*/
895 .references dd {
896 overflow: visible;
897 }
898
899 /* Control caption placement */
900 caption {
901 caption-side: bottom;
902 }
903
904 /* Limit the width of the author address vcard, so names in right-to-left
905 script don't end up on the other side of the page. */
906
907 address.vcard {
908 max-width: 30em;
909 margin-right: auto;
910 }
911
912 /* For address alignment dependent on LTR or RTL scripts */
913 address div.left {
914 text-align: left;
915 }
916 address div.right {
917 text-align: right;
918 }
919
920 /* Provide table alignment support. We can't use the alignX classes above
921 since they do unwanted things with caption and other styling. */
922 table.right {
923 margin-left: auto;
924 margin-right: 0;
925 }
926 table.center {
927 margin-left: auto;
928 margin-right: auto;
929 }
930 table.left {
931 margin-left: 0;
932 margin-right: auto;
933 }
934
935 /* Give the table caption label the same styling as the figcaption */
936 caption a[href] {
937 color: #222;
938 }
939
940 @media print {
941 .toplink {
942 display: none;
943 }
944
945 /* avoid overwriting the top border line with the ToC header */
946 #toc {
947 padding-top: 1px;
948 }
949
950 /* Avoid page breaks inside dl and author address entries */
951 .vcard {
952 page-break-inside: avoid;
953 }
954
955 }
956 /* Tweak the bcp14 keyword presentation */
957 .bcp14 {
958 font-variant: small-caps;
959 font-weight: bold;
960 font-size: 0.9em;
961 }
962 /* Tweak the invisible space above H* in order not to overlay links in text above */
963 h2 {
964 margin-top: -18px; /* provide offset for in-page anchors */
965 padding-top: 31px;
966 }
967 h3 {
968 margin-top: -18px; /* provide offset for in-page anchors */
969 padding-top: 24px;
970 }
971 h4 {
972 margin-top: -18px; /* provide offset for in-page anchors */
973 padding-top: 24px;
974 }
975 /* Float artwork pilcrow to the right */
976 @media screen {
977 .artwork a.pilcrow {
978 display: block;
979 line-height: 0.7;
980 margin-top: 0.15em;
981 }
982 }
983 /* Make pilcrows on dd visible */
984 @media screen {
985 dd:hover > a.pilcrow {
986 visibility: visible;
987 }
988 }
989 /* Make the placement of figcaption match that of a table's caption
990 by removing the figure's added bottom margin */
991 .alignLeft.art-text,
992 .alignCenter.art-text,
993 .alignRight.art-text {
994 margin-bottom: 0;
995 }
996 .alignLeft,
997 .alignCenter,
998 .alignRight {
999 margin: 1em 0 0 0;
1000 }
1001 /* In print, the pilcrow won't show on hover, so prevent it from taking up space,
1002 possibly even requiring a new line */
1003 @media print {
1004 a.pilcrow {
1005 display: none;
1006 }
1007 }
1008 /* Styling for the external metadata */
1009 div#external-metadata {
1010 background-color: #eee;
1011 padding: 0.5em;
1012 margin-bottom: 0.5em;
1013 display: none;
1014 }
1015 div#internal-metadata {
1016 padding: 0.5em; /* to match the external-metadata padding */
1017 }
1018 /* Styling for title RFC Number */
1019 h1#rfcnum {
1020 clear: both;
1021 margin: 0 0 -1em;
1022 padding: 1em 0 0 0;
1023 }
1024 /* Make .olPercent look the same as <ol><li> */
1025 dl.olPercent > dd {
1026 margin-bottom: 0.25em;
1027 min-height: initial;
1028 }
1029 /* Give aside some styling to set it apart */
1030 aside {
1031 border-left: 1px solid #ddd;
1032 margin: 1em 0 1em 2em;
1033 padding: 0.2em 2em;
1034 }
1035 aside > dl,
1036 aside > ol,
1037 aside > ul,
1038 aside > table,
1039 aside > p {
1040 margin-bottom: 0.5em;
1041 }
1042 /* Additional page break settings */
1043 @media print {
1044 figcaption, table caption {
1045 page-break-before: avoid;
1046 }
1047 }
1048 /* Font size adjustments for print */
1049 @media print {
1050 body { font-size: 10pt; line-height: normal; max-width: 96%; }
1051 h1 { font-size: 1.72em; padding-top: 1.5em; } /* 1*1.2*1.2*1.2 */
1052 h2 { font-size: 1.44em; padding-top: 1.5em; } /* 1*1.2*1.2 */
1053 h3 { font-size: 1.2em; padding-top: 1.5em; } /* 1*1.2 */
1054 h4 { font-size: 1em; padding-top: 1.5em; }
1055 h5, h6 { font-size: 1em; margin: initial; padding: 0.5em 0 0.3em; }
1056 }
1057 /* Sourcecode margin in print, when there's no pilcrow */
1058 @media print {
1059 .artwork,
1060 .sourcecode {
1061 margin-bottom: 1em;
1062 }
1063 }
1064 /* Avoid narrow tables forcing too narrow table captions, which may render badly */
1065 table {
1066 min-width: 20em;
1067 }
1068 /* ol type a */
1069 ol.type-a { list-style-type: lower-alpha; }
1070 ol.type-A { list-style-type: upper-alpha; }
1071 ol.type-i { list-style-type: lower-roman; }
1072 ol.type-I { list-style-type: lower-roman; }
1073 /* Apply the print table and row borders in general, on request from the RPC,
1074 and increase the contrast between border and odd row background sligthtly */
1075 table {
1076 border: 1px solid #ddd;
1077 }
1078 td {
1079 border-top: 1px solid #ddd;
1080 }
1081 tr:nth-child(2n+1) > td {
1082 background-color: #f8f8f8;
1083 }
1084 /* Use style rules to govern display of the TOC. */
1085 @media screen and (max-width: 1023px) {
1086 #toc nav { display: none; }
1087 #toc.active nav { display: block; }
1088 }
1089 /* Add support for keepWithNext */
1090 .keepWithNext {
1091 break-after: avoid-page;
1092 break-after: avoid-page;
1093 }
1094 /* Add support for keepWithPrevious */
1095 .keepWithPrevious {
1096 break-before: avoid-page;
1097 }
1098 /* Change the approach to avoiding breaks inside artwork etc. */
1099 figure, pre, table, .artwork, .sourcecode {
1100 break-before: avoid-page;
1101 break-after: auto;
1102 }
1103 /* Avoid breaks between <dt> and <dd> */
1104 dl {
1105 break-before: auto;
1106 break-inside: auto;
1107 }
1108 dt {
1109 break-before: auto;
1110 break-after: avoid-page;
1111 }
1112 dd {
1113 break-before: avoid-page;
1114 break-after: auto;
1115 orphans: 3;
1116 widows: 3
1117 }
1118 span.break, dd.break {
1119 margin-bottom: 0;
1120 min-height: 0;
1121 break-before: auto;
1122 break-inside: auto;
1123 break-after: auto;
1124 }
1125 /* Undo break-before ToC */
1126 @media print {
1127 #toc {
1128 break-before: auto;
1129 }
1130 }
1131 /* Text in compact lists should not get extra bottim margin space,
1132 since that would makes the list not compact */
1133 ul.compact p, .ulCompact p,
1134 ol.compact p, .olCompact p {
1135 margin: 0;
1136 }
1137 /* But the list as a whole needs the extra space at the end */
1138 section ul.compact,
1139 section .ulCompact,
1140 section ol.compact,
1141 section .olCompact {
1142 margin-bottom: 1em; /* same as p not within ul.compact etc. */
1143 }
1144 /* The tt and code background above interferes with for instance table cell
1145 backgrounds. Changed to something a bit more selective. */
1146 tt, code {
1147 background-color: transparent;
1148 }
1149 p tt, p code, li tt, li code {
1150 background-color: #f8f8f8;
1151 }
1152 /* Tweak the pre margin -- 0px doesn't come out well */
1153 pre {
1154 margin-top: 0.5px;
1155 }
1156 /* Tweak the comact list text */
1157 ul.compact, .ulCompact,
1158 ol.compact, .olCompact,
1159 dl.compact, .dlCompact {
1160 line-height: normal;
1161 }
1162 /* Don't add top margin for nested lists */
1163 li > ul, li > ol, li > dl,
1164 dd > ul, dd > ol, dd > dl,
1165 dl > dd > dl {
1166 margin-top: initial;
1167 }
1168 /* Elements that should not be rendered on the same line as a <dt> */
1169 /* This should match the element list in writer.text.TextWriter.render_dl() */
1170 dd > div.artwork:first-child,
1171 dd > aside:first-child,
1172 dd > figure:first-child,
1173 dd > ol:first-child,
1174 dd > div:first-child > pre.sourcecode,
1175 dd > table:first-child,
1176 dd > ul:first-child {
1177 clear: left;
1178 }
1179 /* fix for weird browser behaviour when <dd/> is empty */
1180 dt+dd:empty::before{
1181 content: "\00a0";
1182 }
1183 /* Make paragraph spacing inside <li> smaller than in body text, to fit better within the list */
1184 li > p {
1185 margin-bottom: 0.5em
1186 }
1187 /* Don't let p margin spill out from inside list items */
1188 li > p:last-of-type {
1189 margin-bottom: 0;
1190 }
1191 </style>
1192 <link href="rfc-local.css" rel="stylesheet" type="text/css">
1193 <link href="https://dx.doi.org/10.17487/rfc9085" rel="alternate">
1194 <link href="urn:issn:2070-1721" rel="alternate">
1195 <link href="https://datatracker.ietf.org/doc/draft-ietf-idr-bgp-ls-segment-routing-ext-18" rel="prev">
1196 </head>
1197 <body>
1198 <script src="https://www.rfc-editor.org/js/metadata.min.js"></script>
1199 <table class="ears">
1200 <thead><tr>
1201 <td class="left">RFC 9085</td>
1202 <td class="center">BGP-LS Extensions for Segment Routing</td>
1203 <td class="right">August 2021</td>
1204 </tr></thead>
1205 <tfoot><tr>
1206 <td class="left">Previdi, et al.</td>
1207 <td class="center">Standards Track</td>
1208 <td class="right">[Page]</td>
1209 </tr></tfoot>
1210 </table>
1211 <div id="external-metadata" class="document-information"></div>
1212 <div id="internal-metadata" class="document-information">
1213 <dl id="identifiers">
1214 <dt class="label-stream">Stream:</dt>
1215 <dd class="stream">Internet Engineering Task Force (IETF)</dd>
1216 <dt class="label-rfc">RFC:</dt>
1217 <dd class="rfc"><a href="https://www.rfc-editor.org/rfc/rfc9085" class="eref">9085</a></dd>
1218 <dt class="label-category">Category:</dt>
1219 <dd class="category">Standards Track</dd>
1220 <dt class="label-published">Published:</dt>
1221 <dd class="published">
1222 <time datetime="2021-08" class="published">August 2021</time>
1223 </dd>
1224 <dt class="label-issn">ISSN:</dt>
1225 <dd class="issn">2070-1721</dd>
1226 <dt class="label-authors">Authors:</dt>
1227 <dd class="authors">
1228 <div class="author">
1229 <div class="author-name">S. Previdi</div>
1230 <div class="org">Huawei Technologies</div>
1231 </div>
1232 <div class="author">
1233 <div class="author-name">K. Talaulikar, <span class="editor">Ed.</span>
1234 </div>
1235 <div class="org">Cisco Systems, Inc.</div>
1236 </div>
1237 <div class="author">
1238 <div class="author-name">C. Filsfils</div>
1239 <div class="org">Cisco Systems, Inc.</div>
1240 </div>
1241 <div class="author">
1242 <div class="author-name">H. Gredler</div>
1243 <div class="org">RtBrick Inc.</div>
1244 </div>
1245 <div class="author">
1246 <div class="author-name">M. Chen</div>
1247 <div class="org">Huawei Technologies</div>
1248 </div>
1249 </dd>
1250 </dl>
1251 </div>
1252 <h1 id="rfcnum">RFC 9085</h1>
1253 <h1 id="title">Border Gateway Protocol - Link State (BGP-LS) Extensions for Segment Routing</h1>
1254 <section id="section-abstract">
1255 <h2 id="abstract"><a href="#abstract" class="selfRef">Abstract</a></h2>
1256 <p id="section-abstract-1">Segment Routing (SR) allows for a flexible definition of end-to-end
1257 paths by encoding paths as sequences of topological subpaths, called
1258 "segments". These segments are advertised by routing protocols, e.g., by
1259 the link-state routing protocols (IS-IS, OSPFv2, and OSPFv3) within IGP
1260 topologies.<a href="#section-abstract-1" class="pilcrow">¶</a></p>
1261 <p id="section-abstract-2">This document defines extensions to the Border Gateway Protocol - Link State (BGP-LS) address family
1262 in order to carry SR information via BGP.<a href="#section-abstract-2" class="pilcrow">¶</a></p>
1263 </section>
1264 <div id="status-of-memo">
1265 <section id="section-boilerplate.1">
1266 <h2 id="name-status-of-this-memo">
1267 <a href="#name-status-of-this-memo" class="section-name selfRef">Status of This Memo</a>
1268 </h2>
1269 <p id="section-boilerplate.1-1">
1270 This is an Internet Standards Track document.<a href="#section-boilerplate.1-1" class="pilcrow">¶</a></p>
1271 <p id="section-boilerplate.1-2">
1272 This document is a product of the Internet Engineering Task Force
1273 (IETF). It represents the consensus of the IETF community. It has
1274 received public review and has been approved for publication by
1275 the Internet Engineering Steering Group (IESG). Further
1276 information on Internet Standards is available in Section 2 of
1277 RFC 7841.<a href="#section-boilerplate.1-2" class="pilcrow">¶</a></p>
1278 <p id="section-boilerplate.1-3">
1279 Information about the current status of this document, any
1280 errata, and how to provide feedback on it may be obtained at
1281 <span><a href="https://www.rfc-editor.org/info/rfc9085">https://www.rfc-editor.org/info/rfc9085</a></span>.<a href="#section-boilerplate.1-3" class="pilcrow">¶</a></p>
1282 </section>
1283 </div>
1284 <div id="copyright">
1285 <section id="section-boilerplate.2">
1286 <h2 id="name-copyright-notice">
1287 <a href="#name-copyright-notice" class="section-name selfRef">Copyright Notice</a>
1288 </h2>
1289 <p id="section-boilerplate.2-1">
1290 Copyright (c) 2021 IETF Trust and the persons identified as the
1291 document authors. All rights reserved.<a href="#section-boilerplate.2-1" class="pilcrow">¶</a></p>
1292 <p id="section-boilerplate.2-2">
1293 This document is subject to BCP 78 and the IETF Trust's Legal
1294 Provisions Relating to IETF Documents
1295 (<span><a href="https://trustee.ietf.org/license-info">https://trustee.ietf.org/license-info</a></span>) in effect on the date of
1296 publication of this document. Please review these documents
1297 carefully, as they describe your rights and restrictions with
1298 respect to this document. Code Components extracted from this
1299 document must include Simplified BSD License text as described in
1300 Section 4.e of the Trust Legal Provisions and are provided without
1301 warranty as described in the Simplified BSD License.<a href="#section-boilerplate.2-2" class="pilcrow">¶</a></p>
1302 </section>
1303 </div>
1304 <div id="toc">
1305 <section id="section-toc.1">
1306 <a href="#" onclick="scroll(0,0)" class="toplink">▲</a><h2 id="name-table-of-contents">
1307 <a href="#name-table-of-contents" class="section-name selfRef">Table of Contents</a>
1308 </h2>
1309 <nav class="toc"><ul class="compact ulBare toc ulEmpty">
1310 <li class="compact ulBare toc ulEmpty" id="section-toc.1-1.1">
1311 <p id="section-toc.1-1.1.1" class="keepWithNext"><a href="#section-1" class="xref">1</a>.  <a href="#name-introduction" class="xref">Introduction</a></p>
1312 <ul class="toc ulEmpty compact ulBare">
1313 <li class="toc ulEmpty compact ulBare" id="section-toc.1-1.1.2.1">
1314 <p id="section-toc.1-1.1.2.1.1" class="keepWithNext"><a href="#section-1.1" class="xref">1.1</a>.  <a href="#name-requirements-language" class="xref">Requirements Language</a></p>
1315 </li>
1316 </ul>
1317 </li>
1318 <li class="compact ulBare toc ulEmpty" id="section-toc.1-1.2">
1319 <p id="section-toc.1-1.2.1"><a href="#section-2" class="xref">2</a>.  <a href="#name-bgp-ls-extensions-for-segme" class="xref">BGP-LS Extensions for Segment Routing</a></p>
1320 <ul class="toc ulEmpty compact ulBare">
1321 <li class="toc ulEmpty compact ulBare" id="section-toc.1-1.2.2.1">
1322 <p id="section-toc.1-1.2.2.1.1"><a href="#section-2.1" class="xref">2.1</a>.  <a href="#name-node-attribute-tlvs" class="xref">Node Attribute TLVs</a></p>
1323 <ul class="toc ulEmpty compact ulBare">
1324 <li class="toc ulEmpty compact ulBare" id="section-toc.1-1.2.2.1.2.1">
1325 <p id="section-toc.1-1.2.2.1.2.1.1" class="keepWithNext"><a href="#section-2.1.1" class="xref">2.1.1</a>.  <a href="#name-sid-label-tlv" class="xref">SID/Label TLV</a></p>
1326 </li>
1327 <li class="toc ulEmpty compact ulBare" id="section-toc.1-1.2.2.1.2.2">
1328 <p id="section-toc.1-1.2.2.1.2.2.1"><a href="#section-2.1.2" class="xref">2.1.2</a>.  <a href="#name-sr-capabilities-tlv" class="xref">SR Capabilities TLV</a></p>
1329 </li>
1330 <li class="toc ulEmpty compact ulBare" id="section-toc.1-1.2.2.1.2.3">
1331 <p id="section-toc.1-1.2.2.1.2.3.1"><a href="#section-2.1.3" class="xref">2.1.3</a>.  <a href="#name-sr-algorithm-tlv" class="xref">SR-Algorithm TLV</a></p>
1332 </li>
1333 <li class="toc ulEmpty compact ulBare" id="section-toc.1-1.2.2.1.2.4">
1334 <p id="section-toc.1-1.2.2.1.2.4.1"><a href="#section-2.1.4" class="xref">2.1.4</a>.  <a href="#name-sr-local-block-tlv" class="xref">SR Local Block TLV</a></p>
1335 </li>
1336 <li class="toc ulEmpty compact ulBare" id="section-toc.1-1.2.2.1.2.5">
1337 <p id="section-toc.1-1.2.2.1.2.5.1"><a href="#section-2.1.5" class="xref">2.1.5</a>.  <a href="#name-srms-preference-tlv" class="xref">SRMS Preference TLV</a></p>
1338 </li>
1339 </ul>
1340 </li>
1341 <li class="toc ulEmpty compact ulBare" id="section-toc.1-1.2.2.2">
1342 <p id="section-toc.1-1.2.2.2.1"><a href="#section-2.2" class="xref">2.2</a>.  <a href="#name-link-attribute-tlvs" class="xref">Link Attribute TLVs</a></p>
1343 <ul class="toc ulEmpty compact ulBare">
1344 <li class="toc ulEmpty compact ulBare" id="section-toc.1-1.2.2.2.2.1">
1345 <p id="section-toc.1-1.2.2.2.2.1.1"><a href="#section-2.2.1" class="xref">2.2.1</a>.  <a href="#name-adjacency-sid-tlv" class="xref">Adjacency SID TLV</a></p>
1346 </li>
1347 <li class="toc ulEmpty compact ulBare" id="section-toc.1-1.2.2.2.2.2">
1348 <p id="section-toc.1-1.2.2.2.2.2.1"><a href="#section-2.2.2" class="xref">2.2.2</a>.  <a href="#name-lan-adjacency-sid-tlv" class="xref">LAN Adjacency SID TLV</a></p>
1349 </li>
1350 <li class="toc ulEmpty compact ulBare" id="section-toc.1-1.2.2.2.2.3">
1351 <p id="section-toc.1-1.2.2.2.2.3.1"><a href="#section-2.2.3" class="xref">2.2.3</a>.  <a href="#name-l2-bundle-member-attributes" class="xref">L2 Bundle Member Attributes TLV</a></p>
1352 </li>
1353 </ul>
1354 </li>
1355 <li class="toc ulEmpty compact ulBare" id="section-toc.1-1.2.2.3">
1356 <p id="section-toc.1-1.2.2.3.1"><a href="#section-2.3" class="xref">2.3</a>.  <a href="#name-prefix-attribute-tlvs" class="xref">Prefix Attribute TLVs</a></p>
1357 <ul class="toc ulEmpty compact ulBare">
1358 <li class="toc ulEmpty compact ulBare" id="section-toc.1-1.2.2.3.2.1">
1359 <p id="section-toc.1-1.2.2.3.2.1.1"><a href="#section-2.3.1" class="xref">2.3.1</a>.  <a href="#name-prefix-sid-tlv" class="xref">Prefix-SID TLV</a></p>
1360 </li>
1361 <li class="toc ulEmpty compact ulBare" id="section-toc.1-1.2.2.3.2.2">
1362 <p id="section-toc.1-1.2.2.3.2.2.1"><a href="#section-2.3.2" class="xref">2.3.2</a>.  <a href="#name-prefix-attribute-flags-tlv" class="xref">Prefix Attribute Flags TLV</a></p>
1363 </li>
1364 <li class="toc ulEmpty compact ulBare" id="section-toc.1-1.2.2.3.2.3">
1365 <p id="section-toc.1-1.2.2.3.2.3.1"><a href="#section-2.3.3" class="xref">2.3.3</a>.  <a href="#name-source-router-identifier-tl" class="xref">Source Router Identifier TLV</a></p>
1366 </li>
1367 <li class="toc ulEmpty compact ulBare" id="section-toc.1-1.2.2.3.2.4">
1368 <p id="section-toc.1-1.2.2.3.2.4.1"><a href="#section-2.3.4" class="xref">2.3.4</a>.  <a href="#name-source-ospf-router-id-tlv" class="xref">Source OSPF Router-ID TLV</a></p>
1369 </li>
1370 <li class="toc ulEmpty compact ulBare" id="section-toc.1-1.2.2.3.2.5">
1371 <p id="section-toc.1-1.2.2.3.2.5.1"><a href="#section-2.3.5" class="xref">2.3.5</a>.  <a href="#name-range-tlv" class="xref">Range TLV</a></p>
1372 </li>
1373 </ul>
1374 </li>
1375 <li class="toc ulEmpty compact ulBare" id="section-toc.1-1.2.2.4">
1376 <p id="section-toc.1-1.2.2.4.1"><a href="#section-2.4" class="xref">2.4</a>.  <a href="#name-equivalent-is-is-segment-ro" class="xref">Equivalent IS-IS Segment Routing TLVs/Sub-TLVs</a></p>
1377 </li>
1378 <li class="toc ulEmpty compact ulBare" id="section-toc.1-1.2.2.5">
1379 <p id="section-toc.1-1.2.2.5.1"><a href="#section-2.5" class="xref">2.5</a>.  <a href="#name-equivalent-ospfv2-ospfv3-se" class="xref">Equivalent OSPFv2/OSPFv3 Segment Routing TLVs/Sub-TLVs</a></p>
1380 </li>
1381 </ul>
1382 </li>
1383 <li class="compact ulBare toc ulEmpty" id="section-toc.1-1.3">
1384 <p id="section-toc.1-1.3.1"><a href="#section-3" class="xref">3</a>.  <a href="#name-iana-considerations" class="xref">IANA Considerations</a></p>
1385 <ul class="toc ulEmpty compact ulBare">
1386 <li class="toc ulEmpty compact ulBare" id="section-toc.1-1.3.2.1">
1387 <p id="section-toc.1-1.3.2.1.1"><a href="#section-3.1" class="xref">3.1</a>.  <a href="#name-tlv-sub-tlv-code-points-sum" class="xref">TLV/Sub-TLV Code Points Summary</a></p>
1388 </li>
1389 </ul>
1390 </li>
1391 <li class="compact ulBare toc ulEmpty" id="section-toc.1-1.4">
1392 <p id="section-toc.1-1.4.1"><a href="#section-4" class="xref">4</a>.  <a href="#name-manageability-consideration" class="xref">Manageability Considerations</a></p>
1393 </li>
1394 <li class="compact ulBare toc ulEmpty" id="section-toc.1-1.5">
1395 <p id="section-toc.1-1.5.1"><a href="#section-5" class="xref">5</a>.  <a href="#name-security-considerations" class="xref">Security Considerations</a></p>
1396 </li>
1397 <li class="compact ulBare toc ulEmpty" id="section-toc.1-1.6">
1398 <p id="section-toc.1-1.6.1"><a href="#section-6" class="xref">6</a>.  <a href="#name-references" class="xref">References</a></p>
1399 <ul class="toc ulEmpty compact ulBare">
1400 <li class="toc ulEmpty compact ulBare" id="section-toc.1-1.6.2.1">
1401 <p id="section-toc.1-1.6.2.1.1"><a href="#section-6.1" class="xref">6.1</a>.  <a href="#name-normative-references" class="xref">Normative References</a></p>
1402 </li>
1403 <li class="toc ulEmpty compact ulBare" id="section-toc.1-1.6.2.2">
1404 <p id="section-toc.1-1.6.2.2.1"><a href="#section-6.2" class="xref">6.2</a>.  <a href="#name-informative-references" class="xref">Informative References</a></p>
1405 </li>
1406 </ul>
1407 </li>
1408 <li class="compact ulBare toc ulEmpty" id="section-toc.1-1.7">
1409 <p id="section-toc.1-1.7.1"><a href="#appendix-A" class="xref"></a><a href="#name-acknowledgements" class="xref">Acknowledgements</a></p>
1410 </li>
1411 <li class="compact ulBare toc ulEmpty" id="section-toc.1-1.8">
1412 <p id="section-toc.1-1.8.1"><a href="#appendix-B" class="xref"></a><a href="#name-contributors" class="xref">Contributors</a></p>
1413 </li>
1414 <li class="compact ulBare toc ulEmpty" id="section-toc.1-1.9">
1415 <p id="section-toc.1-1.9.1"><a href="#appendix-C" class="xref"></a><a href="#name-authors-addresses" class="xref">Authors' Addresses</a></p>
1416 </li>
1417 </ul>
1418 </nav>
1419 </section>
1420 </div>
1421 <section id="section-1">
1422 <h2 id="name-introduction">
1423 <a href="#section-1" class="section-number selfRef">1. </a><a href="#name-introduction" class="section-name selfRef">Introduction</a>
1424 </h2>
1425 <p id="section-1-1">Segment Routing (SR) allows for a flexible definition of end-to-end
1426 paths by combining subpaths called "segments". A segment can represent
1427 any instruction: topological or service based. A segment can have a
1428 local semantic to an SR node or global semantic within a domain. Within
1429 IGP topologies, an SR path is encoded as a sequence of topological
1430 subpaths, called "IGP segments". These segments are advertised by the
1431 link-state routing protocols (IS-IS, OSPFv2, and OSPFv3).<a href="#section-1-1" class="pilcrow">¶</a></p>
1432 <p id="section-1-2"><span>[<a href="#RFC8402" class="xref">RFC8402</a>]</span> defines the link-state IGP segments --
1433 prefix, node, anycast, and adjacency segments. Prefix segments, by
1434 default, represent an ECMP-aware shortest-path to a prefix, as per the
1435 state of the IGP topology. Adjacency segments represent a hop over a
1436 specific adjacency between two nodes in the IGP. A prefix segment is
1437 typically a multi-hop path while an adjacency segment, in most of the
1438 cases, is a one-hop path. Node and anycast segments are variations of
1439 the prefix segment with their specific characteristics.<a href="#section-1-2" class="pilcrow">¶</a></p>
1440 <p id="section-1-3">When SR is enabled in an IGP domain, segments are
1441 advertised in the form of Segment Identifiers (SIDs). The IGP link-state
1442 routing protocols have been extended to advertise SIDs and other
1443 SR-related information. IGP extensions are described for: <span><a href="#RFC8667" class="xref">IS-IS</a> [<a href="#RFC8667" class="xref">RFC8667</a>]</span>, <span><a href="#RFC8665" class="xref">OSPFv2</a> [<a href="#RFC8665" class="xref">RFC8665</a>]</span>, and
1444 <span><a href="#RFC8666" class="xref">OSPFv3</a> [<a href="#RFC8666" class="xref">RFC8666</a>]</span>.
1445 Using these extensions, SR can be enabled within an IGP
1446 domain.<a href="#section-1-3" class="pilcrow">¶</a></p>
1447 <p id="section-1-4">SR allows advertisement of single or multi-hop
1448 paths. The flooding scope for the IGP extensions for SR is
1449 IGP area-wide. Consequently, the contents of a Link-State Database
1450 (LSDB) or a Traffic Engineering Database (TED) has the scope of an IGP
1451 area; therefore, by using the IGP alone, it is not enough to construct
1452 segments across multiple IGP area or Autonomous
1453 System (AS) boundaries.<a href="#section-1-4" class="pilcrow">¶</a></p>
1454 <p id="section-1-5">In order to address the need for applications that require
1455 topological visibility across IGP areas, or even across ASes,
1456 the BGP-LS address family / subaddress family have been
1457 defined to allow BGP to carry link-state information.
1458 The BGP Network
1459 Layer Reachability Information (NLRI) encoding format for BGP-LS and a
1460 new BGP Path Attribute called the "BGP-LS Attribute" are defined in <span>[<a href="#RFC7752" class="xref">RFC7752</a>]</span>. The identifying key of each link-state object,
1461 namely a node, link, or prefix, is encoded in the NLRI, and the
1462 properties of the object are encoded in the BGP-LS Attribute.<a href="#section-1-5" class="pilcrow">¶</a></p>
1463 <span id="name-link-state-information-coll"></span><div id="MECHANISM-CONSUMER-PRODUCER">
1464 <figure id="figure-1">
1465 <div class="artwork art-text alignLeft" id="section-1-6.1">
1466 <pre>
1467 +------------+
1468 | Consumer |
1469 +------------+
1470 ^
1471 |
1472 v
1473 +-------------------+
1474 | BGP Speaker | +-----------+
1475 | (Route Reflector) | | Consumer |
1476 +-------------------+ +-----------+
1477 ^ ^ ^ ^
1478 | | | |
1479 +---------------+ | +-------------------+ |
1480 | | | |
1481 v v v v
1482 +-----------+ +-----------+ +-----------+
1483 | BGP | | BGP | | BGP |
1484 | Speaker | | Speaker | . . . | Speaker |
1485 +-----------+ +-----------+ +-----------+
1486 ^ ^ ^
1487 | | |
1488 IGP IGP IGP
1489 </pre>
1490 </div>
1491 <figcaption><a href="#figure-1" class="selfRef">Figure 1</a>:
1492 <a href="#name-link-state-information-coll" class="selfRef">Link-State Information Collection</a>
1493 </figcaption></figure>
1494 </div>
1495 <p id="section-1-7"><a href="#MECHANISM-CONSUMER-PRODUCER" class="xref">Figure 1</a> denotes a typical
1496 deployment scenario. In each IGP area, one or more nodes are configured
1497 with BGP-LS. These BGP speakers form an Internal BGP (IBGP) mesh by connecting to one
1498 or more route reflectors. This way, all BGP speakers (specifically the
1499 route reflectors) obtain link-state information from all IGP areas (and
1500 from other ASes from External BGP (EBGP) peers). An external component connects to the
1501 route reflector to obtain this information (perhaps moderated by a
1502 policy regarding what information is or isn't advertised to the external
1503 component) as described in <span>[<a href="#RFC7752" class="xref">RFC7752</a>]</span>.<a href="#section-1-7" class="pilcrow">¶</a></p>
1504 <p id="section-1-8">This document describes extensions to BGP-LS to advertise the SR
1505 information. An external component (e.g., a controller) can collect SR
1506 information from across an SR domain (as described in <span>[<a href="#RFC8402" class="xref">RFC8402</a>]</span>) and construct the end-to-end path (with its
1507 associated SIDs) that needs to be applied to an incoming packet to
1508 achieve the desired end-to-end forwarding. SR operates within a trusted
1509 domain consisting of a single AS or multiple ASes managed by the same
1510 administrative entity, e.g., within a single provider network.<a href="#section-1-8" class="pilcrow">¶</a></p>
1511 <section id="section-1.1">
1512 <h3 id="name-requirements-language">
1513 <a href="#section-1.1" class="section-number selfRef">1.1. </a><a href="#name-requirements-language" class="section-name selfRef">Requirements Language</a>
1514 </h3>
1515 <p id="section-1.1-1">The key words "<span class="bcp14">MUST</span>", "<span class="bcp14">MUST NOT</span>", "<span class="bcp14">REQUIRED</span>", "<span class="bcp14">SHALL</span>", "<span class="bcp14">SHALL NOT</span>",
1516 "<span class="bcp14">SHOULD</span>", "<span class="bcp14">SHOULD NOT</span>", "<span class="bcp14">RECOMMENDED</span>", "<span class="bcp14">NOT RECOMMENDED</span>", "<span class="bcp14">MAY</span>", and
1517 "<span class="bcp14">OPTIONAL</span>" in this document are to be interpreted as described in BCP 14
1518 <span>[<a href="#RFC2119" class="xref">RFC2119</a>]</span> <span>[<a href="#RFC8174" class="xref">RFC8174</a>]</span> when, and only when,
1519 they appear in all capitals, as shown here.<a href="#section-1.1-1" class="pilcrow">¶</a></p>
1520 </section>
1521 </section>
1522 <section id="section-2">
1523 <h2 id="name-bgp-ls-extensions-for-segme">
1524 <a href="#section-2" class="section-number selfRef">2. </a><a href="#name-bgp-ls-extensions-for-segme" class="section-name selfRef">BGP-LS Extensions for Segment Routing</a>
1525 </h2>
1526 <p id="section-2-1">This document defines SR extensions to BGP-LS and specifies the TLVs
1527 and sub-TLVs for advertising SR information within the BGP-LS Attribute.
1528 Sections <a href="#ISISTLV" class="xref">2.4</a> and <a href="#OSPFTLV" class="xref">2.5</a> list the
1529 equivalent TLVs and sub-TLVs in the IS-IS, OSPFv2, and OSPFv3 protocols.<a href="#section-2-1" class="pilcrow">¶</a></p>
1530 <p id="section-2-2"><span><a href="#RFC7752" class="xref">BGP-LS</a> [<a href="#RFC7752" class="xref">RFC7752</a>]</span> defines the BGP-LS NLRI that can
1531 be a Node NLRI, a Link NLRI, or a Prefix NLRI, and it defines the TLVs that map link-state
1532 information to BGP-LS NLRI within the BGP-LS Attribute. This document
1533 adds additional BGP-LS Attribute TLVs in order to encode SR information.
1534 It does not introduce any changes to the encoding of the BGP-LS
1535 NLRIs.<a href="#section-2-2" class="pilcrow">¶</a></p>
1536 <div id="NODE">
1537 <section id="section-2.1">
1538 <h3 id="name-node-attribute-tlvs">
1539 <a href="#section-2.1" class="section-number selfRef">2.1. </a><a href="#name-node-attribute-tlvs" class="section-name selfRef">Node Attribute TLVs</a>
1540 </h3>
1541 <p id="section-2.1-1">The following Node Attribute TLVs are defined:<a href="#section-2.1-1" class="pilcrow">¶</a></p>
1542 <span id="name-node-attribute-tlvs-2"></span><div id="node-attribute_tlv">
1543 <table class="center" id="table-1">
1544 <caption>
1545 <a href="#table-1" class="selfRef">Table 1</a>:
1546 <a href="#name-node-attribute-tlvs-2" class="selfRef">Node Attribute TLVs</a>
1547 </caption>
1548 <thead>
1549 <tr>
1550 <th class="text-left" rowspan="1" colspan="1">Type</th>
1551 <th class="text-left" rowspan="1" colspan="1">Description</th>
1552 <th class="text-left" rowspan="1" colspan="1">Section</th>
1553 </tr>
1554 </thead>
1555 <tbody>
1556 <tr>
1557 <td class="text-center" rowspan="1" colspan="1">1161</td>
1558 <td class="text-left" rowspan="1" colspan="1">SID/Label</td>
1559 <td class="text-right" rowspan="1" colspan="1">
1560 <a href="#SIDLABELTLV" class="xref">Section 2.1.1</a>
1561 </td>
1562 </tr>
1563 <tr>
1564 <td class="text-center" rowspan="1" colspan="1">1034</td>
1565 <td class="text-left" rowspan="1" colspan="1">SR Capabilities</td>
1566 <td class="text-right" rowspan="1" colspan="1">
1567 <a href="#SRCAPTLV" class="xref">Section 2.1.2</a>
1568 </td>
1569 </tr>
1570 <tr>
1571 <td class="text-center" rowspan="1" colspan="1">1035</td>
1572 <td class="text-left" rowspan="1" colspan="1">SR Algorithm</td>
1573 <td class="text-right" rowspan="1" colspan="1">
1574 <a href="#SRALGOTLV" class="xref">Section 2.1.3</a>
1575 </td>
1576 </tr>
1577 <tr>
1578 <td class="text-center" rowspan="1" colspan="1">1036</td>
1579 <td class="text-left" rowspan="1" colspan="1">SR Local Block</td>
1580 <td class="text-right" rowspan="1" colspan="1">
1581 <a href="#SRLB" class="xref">Section 2.1.4</a>
1582 </td>
1583 </tr>
1584 <tr>
1585 <td class="text-center" rowspan="1" colspan="1">1037</td>
1586 <td class="text-left" rowspan="1" colspan="1">SRMS Preference</td>
1587 <td class="text-right" rowspan="1" colspan="1">
1588 <a href="#SRMSPREF" class="xref">Section 2.1.5</a>
1589 </td>
1590 </tr>
1591 </tbody>
1592 </table>
1593 </div>
1594 <p id="section-2.1-3">These TLVs should only be added to the BGP-LS Attribute associated
1595 with the Node NLRI that describes the IGP node that is originating the
1596 corresponding IGP TLV/sub-TLV described below.<a href="#section-2.1-3" class="pilcrow">¶</a></p>
1597 <div id="SIDLABELTLV">
1598 <section id="section-2.1.1">
1599 <h4 id="name-sid-label-tlv">
1600 <a href="#section-2.1.1" class="section-number selfRef">2.1.1. </a><a href="#name-sid-label-tlv" class="section-name selfRef">SID/Label TLV</a>
1601 </h4>
1602 <p id="section-2.1.1-1">The SID/Label TLV is used as a sub-TLV by the SR Capabilities
1603 (<a href="#SRCAPTLV" class="xref">Section 2.1.2</a>) and Segment Routing Local Block (SRLB)
1604 (<a href="#SRLB" class="xref">Section 2.1.4</a>) TLVs. This information is derived from the
1605 protocol-specific advertisements.<a href="#section-2.1.1-1" class="pilcrow">¶</a></p>
1606 <ul class="normal">
1607 <li class="normal" id="section-2.1.1-2.1">IS-IS, as defined by the SID/Label Sub-TLV in
1608 <span><a href="https://www.rfc-editor.org/rfc/rfc8667#section-2.3" class="relref">Section 2.3</a> of [<a href="#RFC8667" class="xref">RFC8667</a>]</span>.<a href="#section-2.1.1-2.1" class="pilcrow">¶</a>
1609 </li>
1610 <li class="normal" id="section-2.1.1-2.2">OSPFv2/OSPFv3, as defined by the SID/Label Sub-TLV in <span><a href="https://www.rfc-editor.org/rfc/rfc8665#section-2.1" class="relref">Section 2.1</a> of [<a href="#RFC8665" class="xref">RFC8665</a>]</span>
1611 and <span><a href="https://www.rfc-editor.org/rfc/rfc8666#section-3.1" class="relref">Section 3.1</a> of [<a href="#RFC8666" class="xref">RFC8666</a>]</span>.<a href="#section-2.1.1-2.2" class="pilcrow">¶</a>
1612 </li>
1613 </ul>
1614 <p id="section-2.1.1-3">The TLV has the following format:<a href="#section-2.1.1-3" class="pilcrow">¶</a></p>
1615 <span id="name-sid-label-tlv-format"></span><div id="SIDLTLVFIG">
1616 <figure id="figure-2">
1617 <div class="artwork art-text alignLeft" id="section-2.1.1-4.1">
1618 <pre>
1619 0 1 2 3
1620 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
1621 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1622 | Type | Length |
1623 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1624 | SID/Label (variable) //
1625 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1626 </pre>
1627 </div>
1628 <figcaption><a href="#figure-2" class="selfRef">Figure 2</a>:
1629 <a href="#name-sid-label-tlv-format" class="selfRef">SID/Label TLV Format</a>
1630 </figcaption></figure>
1631 </div>
1632 <p id="section-2.1.1-5">Where:<a href="#section-2.1.1-5" class="pilcrow">¶</a></p>
1633 <span class="break"></span><dl class="dlParallel" id="section-2.1.1-6">
1634 <dt id="section-2.1.1-6.1">Type:</dt>
1635 <dd style="margin-left: 1.5em" id="section-2.1.1-6.2"> 1161<a href="#section-2.1.1-6.2" class="pilcrow">¶</a>
1636 </dd>
1637 <dd class="break"></dd>
1638 <dt id="section-2.1.1-6.3">Length:</dt>
1639 <dd style="margin-left: 1.5em" id="section-2.1.1-6.4"> Variable. Either 3 or 4 octets depending on whether the value
1640 is encoded as a label or as an index/SID.<a href="#section-2.1.1-6.4" class="pilcrow">¶</a>
1641 </dd>
1642 <dd class="break"></dd>
1643 <dt id="section-2.1.1-6.5">SID/Label:</dt>
1644 <dd style="margin-left: 1.5em" id="section-2.1.1-6.6"> If the length is set to 3, then the 20 rightmost bits
1645 represent a label (the total TLV size is 7), and the 4 leftmost
1646 bits are set to 0. If the length is set to 4, then the value
1647 represents a 32-bit SID (the total TLV size is 8).<a href="#section-2.1.1-6.6" class="pilcrow">¶</a>
1648 </dd>
1649 <dd class="break"></dd>
1650 </dl>
1651 </section>
1652 </div>
1653 <div id="SRCAPTLV">
1654 <section id="section-2.1.2">
1655 <h4 id="name-sr-capabilities-tlv">
1656 <a href="#section-2.1.2" class="section-number selfRef">2.1.2. </a><a href="#name-sr-capabilities-tlv" class="section-name selfRef">SR Capabilities TLV</a>
1657 </h4>
1658 <p id="section-2.1.2-1">The SR Capabilities TLV is used in order to advertise the node's
1659 SR capabilities including its Segment Routing Global Base (SRGB)
1660 range(s). In the case of IS-IS, the capabilities also include the
1661 IPv4 and IPv6 support for the SR-MPLS forwarding plane. This
1662 information is derived from the protocol-specific advertisements.<a href="#section-2.1.2-1" class="pilcrow">¶</a></p>
1663 <ul class="normal">
1664 <li class="normal" id="section-2.1.2-2.1">IS-IS, as defined by the SR-Capabilities Sub-TLV in <span><a href="https://www.rfc-editor.org/rfc/rfc8667#section-3.1" class="relref">Section 3.1</a> of [<a href="#RFC8667" class="xref">RFC8667</a>]</span>.<a href="#section-2.1.2-2.1" class="pilcrow">¶</a>
1665 </li>
1666 <li class="normal" id="section-2.1.2-2.2">OSPFv2/OSPFv3, as defined by the SID/Label Range TLV in
1667 <span><a href="https://www.rfc-editor.org/rfc/rfc8665#section-3.2" class="relref">Section 3.2</a> of [<a href="#RFC8665" class="xref">RFC8665</a>]</span>. OSPFv3
1668 leverages the same TLV as defined for OSPFv2.<a href="#section-2.1.2-2.2" class="pilcrow">¶</a>
1669 </li>
1670 </ul>
1671 <p id="section-2.1.2-3">The SR Capabilities TLV has the following format:<a href="#section-2.1.2-3" class="pilcrow">¶</a></p>
1672 <span id="name-sr-capabilities-tlv-format"></span><div id="SRCAPTLVFIG">
1673 <figure id="figure-3">
1674 <div class="artwork art-text alignLeft" id="section-2.1.2-4.1">
1675 <pre>
1676 0 1 2 3
1677 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
1678 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1679 | Type | Length |
1680 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1681 | Flags | Reserved |
1682 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1683
1684 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1685 | Range Size 1 |
1686 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1687 | SID/Label Sub-TLV 1 //
1688 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1689
1690 ...
1691
1692 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1693 | Range Size N |
1694 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1695 | SID/Label Sub-TLV N //
1696 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1697 </pre>
1698 </div>
1699 <figcaption><a href="#figure-3" class="selfRef">Figure 3</a>:
1700 <a href="#name-sr-capabilities-tlv-format" class="selfRef">SR Capabilities TLV Format</a>
1701 </figcaption></figure>
1702 </div>
1703 <p id="section-2.1.2-5">Where:<a href="#section-2.1.2-5" class="pilcrow">¶</a></p>
1704 <span class="break"></span><dl class="dlParallel" id="section-2.1.2-6">
1705 <dt id="section-2.1.2-6.1">Type:</dt>
1706 <dd style="margin-left: 1.5em" id="section-2.1.2-6.2">1034<a href="#section-2.1.2-6.2" class="pilcrow">¶</a>
1707 </dd>
1708 <dd class="break"></dd>
1709 <dt id="section-2.1.2-6.3">Length:</dt>
1710 <dd style="margin-left: 1.5em" id="section-2.1.2-6.4">Variable. The minimum length is 12 octets.<a href="#section-2.1.2-6.4" class="pilcrow">¶</a>
1711 </dd>
1712 <dd class="break"></dd>
1713 <dt id="section-2.1.2-6.5">Flags:</dt>
1714 <dd style="margin-left: 1.5em" id="section-2.1.2-6.6"> 1 octet of flags as defined in
1715 <span><a href="https://www.rfc-editor.org/rfc/rfc8667#section-3.1" class="relref">Section 3.1</a> of [<a href="#RFC8667" class="xref">RFC8667</a>]</span> for IS-IS. The flags are not currently
1716 defined for OSPFv2 and OSPFv3 and <span class="bcp14">MUST</span> be
1717 set to 0 and ignored on receipt.<a href="#section-2.1.2-6.6" class="pilcrow">¶</a>
1718 </dd>
1719 <dd class="break"></dd>
1720 <dt id="section-2.1.2-6.7">Reserved:</dt>
1721 <dd style="margin-left: 1.5em" id="section-2.1.2-6.8"> 1 octet that <span class="bcp14">MUST</span> be set to 0 and ignored on
1722 receipt.<a href="#section-2.1.2-6.8" class="pilcrow">¶</a>
1723 </dd>
1724 <dd class="break"></dd>
1725 <dt id="section-2.1.2-6.9">One or more entries, each of which have the following
1726 format:</dt>
1727 <dd style="margin-left: 1.5em" id="section-2.1.2-6.10">
1728 <p id="section-2.1.2-6.10.1"><br></p>
1729 <span class="break"></span><dl class="dlParallel" id="section-2.1.2-6.10.2">
1730 <dt id="section-2.1.2-6.10.2.1">Range Size:</dt>
1731 <dd style="margin-left: 1.5em" id="section-2.1.2-6.10.2.2"> 3 octets with a non-zero value
1732 indicating the number of labels in the range.<a href="#section-2.1.2-6.10.2.2" class="pilcrow">¶</a>
1733 </dd>
1734 <dd class="break"></dd>
1735 <dt id="section-2.1.2-6.10.2.3">SID/Label TLV:</dt>
1736 <dd style="margin-left: 1.5em" id="section-2.1.2-6.10.2.4">(as defined in <a href="#SIDLABELTLV" class="xref">Section 2.1.1</a>) used as a sub-TLV, which encodes the
1737 first label in the range. Since the SID/Label TLV is used to
1738 indicate the first label of the SRGB range, only label
1739 encoding is valid under the SR Capabilities TLV.<a href="#section-2.1.2-6.10.2.4" class="pilcrow">¶</a>
1740 </dd>
1741 <dd class="break"></dd>
1742 </dl>
1743 </dd>
1744 <dd class="break"></dd>
1745 </dl>
1746 </section>
1747 </div>
1748 <div id="SRALGOTLV">
1749 <section id="section-2.1.3">
1750 <h4 id="name-sr-algorithm-tlv">
1751 <a href="#section-2.1.3" class="section-number selfRef">2.1.3. </a><a href="#name-sr-algorithm-tlv" class="section-name selfRef">SR-Algorithm TLV</a>
1752 </h4>
1753 <p id="section-2.1.3-1">The SR-Algorithm TLV is used in order to advertise the SR algorithms
1754 supported by the node. This information is derived from
1755 the protocol-specific advertisements.<a href="#section-2.1.3-1" class="pilcrow">¶</a></p>
1756 <ul class="normal">
1757 <li class="normal" id="section-2.1.3-2.1">IS-IS, as defined by the SR-Algorithm Sub-TLV in
1758 <span><a href="https://www.rfc-editor.org/rfc/rfc8667#section-3.2" class="relref">Section 3.2</a> of [<a href="#RFC8667" class="xref">RFC8667</a>]</span>.<a href="#section-2.1.3-2.1" class="pilcrow">¶</a>
1759 </li>
1760 <li class="normal" id="section-2.1.3-2.2">OSPFv2/OSPFv3, as defined by the SR-Algorithm TLV in
1761 <span><a href="https://www.rfc-editor.org/rfc/rfc8665#section-3.1" class="relref">Section 3.1</a> of [<a href="#RFC8665" class="xref">RFC8665</a>]</span>. OSPFv3
1762 leverages the same TLV as defined for OSPFv2.<a href="#section-2.1.3-2.2" class="pilcrow">¶</a>
1763 </li>
1764 </ul>
1765 <p id="section-2.1.3-3">The SR-Algorithm TLV has the following format:<a href="#section-2.1.3-3" class="pilcrow">¶</a></p>
1766 <span id="name-sr-algorithm-tlv-format"></span><div id="SRALGTLVFIG">
1767 <figure id="figure-4">
1768 <div class="artwork art-text alignLeft" id="section-2.1.3-4.1">
1769 <pre>
1770 0 1 2 3
1771 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
1772 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1773 | Type | Length |
1774 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1775 | Algorithm 1 | Algorithm... | Algorithm N |
1776 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1777 </pre>
1778 </div>
1779 <figcaption><a href="#figure-4" class="selfRef">Figure 4</a>:
1780 <a href="#name-sr-algorithm-tlv-format" class="selfRef">SR-Algorithm TLV Format</a>
1781 </figcaption></figure>
1782 </div>
1783 <p id="section-2.1.3-5">Where:<a href="#section-2.1.3-5" class="pilcrow">¶</a></p>
1784 <span class="break"></span><dl class="dlParallel" id="section-2.1.3-6">
1785 <dt id="section-2.1.3-6.1">Type:</dt>
1786 <dd style="margin-left: 1.5em" id="section-2.1.3-6.2"> 1035<a href="#section-2.1.3-6.2" class="pilcrow">¶</a>
1787 </dd>
1788 <dd class="break"></dd>
1789 <dt id="section-2.1.3-6.3">Length:</dt>
1790 <dd style="margin-left: 1.5em" id="section-2.1.3-6.4"> Variable. The minimum length is 1 octet and the maximum can be
1791 256.<a href="#section-2.1.3-6.4" class="pilcrow">¶</a>
1792 </dd>
1793 <dd class="break"></dd>
1794 <dt id="section-2.1.3-6.5">Algorithm:</dt>
1795 <dd style="margin-left: 1.5em" id="section-2.1.3-6.6"> One or more fields of 1 octet each that identifies the
1796 algorithm.<a href="#section-2.1.3-6.6" class="pilcrow">¶</a>
1797 </dd>
1798 <dd class="break"></dd>
1799 </dl>
1800 </section>
1801 </div>
1802 <div id="SRLB">
1803 <section id="section-2.1.4">
1804 <h4 id="name-sr-local-block-tlv">
1805 <a href="#section-2.1.4" class="section-number selfRef">2.1.4. </a><a href="#name-sr-local-block-tlv" class="section-name selfRef">SR Local Block TLV</a>
1806 </h4>
1807 <p id="section-2.1.4-1">The SRLB TLV contains the range(s) of labels the
1808 node has reserved for local SIDs. Local SIDs are used, e.g., in IGP
1809 (IS-IS, OSPF) for Adjacency SIDs and may also be allocated by
1810 components other than IGP protocols. As an example, an application
1811 or a controller may instruct a node to allocate a specific local
1812 SID. Therefore, in order for such applications or controllers to
1813 know the range of local SIDs available, the node is required to
1814 advertise its SRLB.<a href="#section-2.1.4-1" class="pilcrow">¶</a></p>
1815 <p id="section-2.1.4-2">This information is derived from the protocol-specific
1816 advertisements.<a href="#section-2.1.4-2" class="pilcrow">¶</a></p>
1817 <ul class="normal">
1818 <li class="normal" id="section-2.1.4-3.1">IS-IS, as defined by the SRLB Sub-TLV in
1819 <span><a href="https://www.rfc-editor.org/rfc/rfc8667#section-3.3" class="relref">Section 3.3</a> of [<a href="#RFC8667" class="xref">RFC8667</a>]</span>.<a href="#section-2.1.4-3.1" class="pilcrow">¶</a>
1820 </li>
1821 <li class="normal" id="section-2.1.4-3.2">OSPFv2/OSPFv3, as defined by the SR Local Block TLV in
1822 <span><a href="https://www.rfc-editor.org/rfc/rfc8665#section-3.3" class="relref">Section 3.3</a> of [<a href="#RFC8665" class="xref">RFC8665</a>]</span>. OSPFv3
1823 leverages the same TLV as defined for OSPFv2.<a href="#section-2.1.4-3.2" class="pilcrow">¶</a>
1824 </li>
1825 </ul>
1826 <p id="section-2.1.4-4">The SRLB TLV has the following format:<a href="#section-2.1.4-4" class="pilcrow">¶</a></p>
1827 <span id="name-srlb-tlv-format"></span><div id="SRLBTLVFIG">
1828 <figure id="figure-5">
1829 <div class="artwork art-text alignLeft" id="section-2.1.4-5.1">
1830 <pre> 0 1 2 3
1831 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
1832 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1833 | Type | Length |
1834 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1835 | Flags | Reserved |
1836 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1837
1838 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1839 | Sub-Range Size 1 |
1840 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1841 | SID/Label Sub-TLV 1 //
1842 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1843
1844 ...
1845
1846 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1847 | Sub-Range Size N |
1848 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1849 | SID/Label Sub-TLV N //
1850 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1851 </pre>
1852 </div>
1853 <figcaption><a href="#figure-5" class="selfRef">Figure 5</a>:
1854 <a href="#name-srlb-tlv-format" class="selfRef">SRLB TLV Format</a>
1855 </figcaption></figure>
1856 </div>
1857 <p id="section-2.1.4-6">Where:<a href="#section-2.1.4-6" class="pilcrow">¶</a></p>
1858 <span class="break"></span><dl class="dlParallel" id="section-2.1.4-7">
1859 <dt id="section-2.1.4-7.1">Type:</dt>
1860 <dd style="margin-left: 1.5em" id="section-2.1.4-7.2"> 1036<a href="#section-2.1.4-7.2" class="pilcrow">¶</a>
1861 </dd>
1862 <dd class="break"></dd>
1863 <dt id="section-2.1.4-7.3">Length:</dt>
1864 <dd style="margin-left: 1.5em" id="section-2.1.4-7.4"> Variable. The minimum length is 12 octets.<a href="#section-2.1.4-7.4" class="pilcrow">¶</a>
1865 </dd>
1866 <dd class="break"></dd>
1867 <dt id="section-2.1.4-7.5">Flags:</dt>
1868 <dd style="margin-left: 1.5em" id="section-2.1.4-7.6"> 1 octet of flags. The flags are as defined in
1869 <span><a href="https://www.rfc-editor.org/rfc/rfc8667#section-3.3" class="relref">Section 3.3</a> of [<a href="#RFC8667" class="xref">RFC8667</a>]</span>
1870 for IS-IS. The flags are not currently defined for OSPFv2 and
1871 OSPFv3 and <span class="bcp14">MUST</span> be set to 0 and ignored on receipt.<a href="#section-2.1.4-7.6" class="pilcrow">¶</a>
1872 </dd>
1873 <dd class="break"></dd>
1874 <dt id="section-2.1.4-7.7">Reserved:</dt>
1875 <dd style="margin-left: 1.5em" id="section-2.1.4-7.8"> 1 octet that <span class="bcp14">MUST</span> be set to 0 and ignored on
1876 receipt.<a href="#section-2.1.4-7.8" class="pilcrow">¶</a>
1877 </dd>
1878 <dd class="break"></dd>
1879 <dt id="section-2.1.4-7.9">One or more entries corresponding to a sub-range(s), each of
1880 which have the following format:</dt>
1881 <dd style="margin-left: 1.5em" id="section-2.1.4-7.10">
1882 <p id="section-2.1.4-7.10.1"><br></p>
1883 <span class="break"></span><dl class="dlParallel" id="section-2.1.4-7.10.2">
1884 <dt id="section-2.1.4-7.10.2.1">Range Size:</dt>
1885 <dd style="margin-left: 1.5em" id="section-2.1.4-7.10.2.2"> 3-octet value indicating the number of labels
1886 in the range.<a href="#section-2.1.4-7.10.2.2" class="pilcrow">¶</a>
1887 </dd>
1888 <dd class="break"></dd>
1889 <dt id="section-2.1.4-7.10.2.3">SID/Label TLV:</dt>
1890 <dd style="margin-left: 1.5em" id="section-2.1.4-7.10.2.4">(as defined in <a href="#SIDLABELTLV" class="xref">Section 2.1.1</a>) used as a sub-TLV, which encodes the
1891 first label in the sub-range. Since the SID/Label TLV is
1892 used to indicate the first label of the SRLB sub-range, only
1893 label encoding is valid under the SR Local Block TLV.<a href="#section-2.1.4-7.10.2.4" class="pilcrow">¶</a>
1894 </dd>
1895 <dd class="break"></dd>
1896 </dl>
1897 </dd>
1898 <dd class="break"></dd>
1899 </dl>
1900 </section>
1901 </div>
1902 <div id="SRMSPREF">
1903 <section id="section-2.1.5">
1904 <h4 id="name-srms-preference-tlv">
1905 <a href="#section-2.1.5" class="section-number selfRef">2.1.5. </a><a href="#name-srms-preference-tlv" class="section-name selfRef">SRMS Preference TLV</a>
1906 </h4>
1907 <p id="section-2.1.5-1">The Segment Routing Mapping Server (SRMS) Preference TLV is used
1908 in order to associate a preference with SRMS advertisements from a
1909 particular source. <span>[<a href="#RFC8661" class="xref">RFC8661</a>]</span> specifies the
1910 SRMS functionality along with the SRMS preference of the node
1911 advertising the SRMS Prefix-to-SID mapping ranges.<a href="#section-2.1.5-1" class="pilcrow">¶</a></p>
1912 <p id="section-2.1.5-2">This information is derived from the protocol-specific
1913 advertisements.<a href="#section-2.1.5-2" class="pilcrow">¶</a></p>
1914 <ul class="normal">
1915 <li class="normal" id="section-2.1.5-3.1">IS-IS, as defined by the SRMS Preference Sub-TLV in
1916 <span><a href="https://www.rfc-editor.org/rfc/rfc8667#section-3.4" class="relref">Section 3.4</a> of [<a href="#RFC8667" class="xref">RFC8667</a>]</span>.<a href="#section-2.1.5-3.1" class="pilcrow">¶</a>
1917 </li>
1918 <li class="normal" id="section-2.1.5-3.2">OSPFv2/OSPFv3, as defined by the SRMS Preference TLV in
1919 <span><a href="https://www.rfc-editor.org/rfc/rfc8665#section-3.4" class="relref">Section 3.4</a> of [<a href="#RFC8665" class="xref">RFC8665</a>]</span>. OSPFv3
1920 leverages the same TLV as defined for OSPFv2.<a href="#section-2.1.5-3.2" class="pilcrow">¶</a>
1921 </li>
1922 </ul>
1923 <p id="section-2.1.5-4">The SRMS Preference TLV has the following format:<a href="#section-2.1.5-4" class="pilcrow">¶</a></p>
1924 <span id="name-srms-preference-tlv-format"></span><div id="SRMSTLVFIG">
1925 <figure id="figure-6">
1926 <div class="artwork art-text alignLeft" id="section-2.1.5-5.1">
1927 <pre> 0 1 2 3
1928 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
1929 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1930 | Type | Length |
1931 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1932 | Preference |
1933 +-+-+-+-+-+-+-+-+
1934 </pre>
1935 </div>
1936 <figcaption><a href="#figure-6" class="selfRef">Figure 6</a>:
1937 <a href="#name-srms-preference-tlv-format" class="selfRef">SRMS Preference TLV Format</a>
1938 </figcaption></figure>
1939 </div>
1940 <p id="section-2.1.5-6">Where:<a href="#section-2.1.5-6" class="pilcrow">¶</a></p>
1941 <span class="break"></span><dl class="dlParallel" id="section-2.1.5-7">
1942 <dt id="section-2.1.5-7.1">Type:</dt>
1943 <dd style="margin-left: 1.5em" id="section-2.1.5-7.2"> 1037<a href="#section-2.1.5-7.2" class="pilcrow">¶</a>
1944 </dd>
1945 <dd class="break"></dd>
1946 <dt id="section-2.1.5-7.3">Length:</dt>
1947 <dd style="margin-left: 1.5em" id="section-2.1.5-7.4"> 1 octet<a href="#section-2.1.5-7.4" class="pilcrow">¶</a>
1948 </dd>
1949 <dd class="break"></dd>
1950 <dt id="section-2.1.5-7.5">Preference:</dt>
1951 <dd style="margin-left: 1.5em" id="section-2.1.5-7.6"> 1 octet carrying an unsigned 8-bit SRMS
1952 preference.<a href="#section-2.1.5-7.6" class="pilcrow">¶</a>
1953 </dd>
1954 <dd class="break"></dd>
1955 </dl>
1956 </section>
1957 </div>
1958 </section>
1959 </div>
1960 <div id="LINK">
1961 <section id="section-2.2">
1962 <h3 id="name-link-attribute-tlvs">
1963 <a href="#section-2.2" class="section-number selfRef">2.2. </a><a href="#name-link-attribute-tlvs" class="section-name selfRef">Link Attribute TLVs</a>
1964 </h3>
1965 <p id="section-2.2-1">The following Link Attribute TLVs are defined:<a href="#section-2.2-1" class="pilcrow">¶</a></p>
1966 <span id="name-link-attribute-tlvs-2"></span><div id="link-attribute_tlv">
1967 <table class="center" id="table-2">
1968 <caption>
1969 <a href="#table-2" class="selfRef">Table 2</a>:
1970 <a href="#name-link-attribute-tlvs-2" class="selfRef">Link Attribute TLVs</a>
1971 </caption>
1972 <thead>
1973 <tr>
1974 <th class="text-left" rowspan="1" colspan="1">Type</th>
1975 <th class="text-left" rowspan="1" colspan="1">Description</th>
1976 <th class="text-left" rowspan="1" colspan="1">Section</th>
1977 </tr>
1978 </thead>
1979 <tbody>
1980 <tr>
1981 <td class="text-center" rowspan="1" colspan="1">1099</td>
1982 <td class="text-left" rowspan="1" colspan="1">Adjacency SID TLV</td>
1983 <td class="text-right" rowspan="1" colspan="1">
1984 <a href="#ADJSIDTLV" class="xref">Section 2.2.1</a>
1985 </td>
1986 </tr>
1987 <tr>
1988 <td class="text-center" rowspan="1" colspan="1">1100</td>
1989 <td class="text-left" rowspan="1" colspan="1">LAN Adjacency SID TLV</td>
1990 <td class="text-right" rowspan="1" colspan="1">
1991 <a href="#LANADJSIDTLV" class="xref">Section 2.2.2</a>
1992 </td>
1993 </tr>
1994 <tr>
1995 <td class="text-center" rowspan="1" colspan="1">1172</td>
1996 <td class="text-left" rowspan="1" colspan="1">L2 Bundle Member Attributes TLV</td>
1997 <td class="text-right" rowspan="1" colspan="1">
1998 <a href="#L2BUNDLETLV" class="xref">Section 2.2.3</a>
1999 </td>
2000 </tr>
2001 </tbody>
2002 </table>
2003 </div>
2004 <p id="section-2.2-3">These TLVs should only be added to the BGP-LS Attribute associated
2005 with the Link NLRI that describes the link of the IGP node that is
2006 originating the corresponding IGP TLV/sub-TLV described below.<a href="#section-2.2-3" class="pilcrow">¶</a></p>
2007 <div id="ADJSIDTLV">
2008 <section id="section-2.2.1">
2009 <h4 id="name-adjacency-sid-tlv">
2010 <a href="#section-2.2.1" class="section-number selfRef">2.2.1. </a><a href="#name-adjacency-sid-tlv" class="section-name selfRef">Adjacency SID TLV</a>
2011 </h4>
2012 <p id="section-2.2.1-1">The Adjacency SID TLV is used in order to advertise information
2013 related to an Adjacency SID. This information is derived from
2014 the Adj-SID Sub-TLV of IS-IS (<span><a href="https://www.rfc-editor.org/rfc/rfc8667#section-2.2.1" class="relref">Section 2.2.1</a> of [<a href="#RFC8667" class="xref">RFC8667</a>]</span>), OSPFv2
2015 (<span><a href="https://www.rfc-editor.org/rfc/rfc8665#section-6.1" class="relref">Section 6.1</a> of [<a href="#RFC8665" class="xref">RFC8665</a>]</span>), and OSPFv3
2016 (<span><a href="https://www.rfc-editor.org/rfc/rfc8666#section-7.1" class="relref">Section 7.1</a> of [<a href="#RFC8666" class="xref">RFC8666</a>]</span>).<a href="#section-2.2.1-1" class="pilcrow">¶</a></p>
2017 <p id="section-2.2.1-2">The Adjacency SID TLV has the following format:<a href="#section-2.2.1-2" class="pilcrow">¶</a></p>
2018 <span id="name-adjacency-sid-tlv-format"></span><div id="ADJSIDTLVFIG">
2019 <figure id="figure-7">
2020 <div class="artwork art-text alignLeft" id="section-2.2.1-3.1">
2021 <pre>
2022 0 1 2 3
2023 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
2024 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2025 | Type | Length |
2026 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2027 | Flags | Weight | Reserved |
2028 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2029 | SID/Label/Index (variable) //
2030 +---------------------------------------------------------------+
2031 </pre>
2032 </div>
2033 <figcaption><a href="#figure-7" class="selfRef">Figure 7</a>:
2034 <a href="#name-adjacency-sid-tlv-format" class="selfRef">Adjacency SID TLV Format</a>
2035 </figcaption></figure>
2036 </div>
2037 <p id="section-2.2.1-4">Where:<a href="#section-2.2.1-4" class="pilcrow">¶</a></p>
2038 <span class="break"></span><dl class="dlParallel" id="section-2.2.1-5">
2039 <dt id="section-2.2.1-5.1">Type:</dt>
2040 <dd style="margin-left: 1.5em" id="section-2.2.1-5.2">1099<a href="#section-2.2.1-5.2" class="pilcrow">¶</a>
2041 </dd>
2042 <dd class="break"></dd>
2043 <dt id="section-2.2.1-5.3">Length:</dt>
2044 <dd style="margin-left: 1.5em" id="section-2.2.1-5.4"> Variable. Either 7 or 8 octets depending on the label or index
2045 encoding of the SID.<a href="#section-2.2.1-5.4" class="pilcrow">¶</a>
2046 </dd>
2047 <dd class="break"></dd>
2048 <dt id="section-2.2.1-5.5">Flags:</dt>
2049 <dd style="margin-left: 1.5em" id="section-2.2.1-5.6">
2050 <p id="section-2.2.1-5.6.1"> 1-octet value that should be set as:<a href="#section-2.2.1-5.6.1" class="pilcrow">¶</a></p>
2051 <ul class="normal">
2052 <li class="normal" id="section-2.2.1-5.6.2.1">IS-IS Adj-SID flags as defined in <span><a href="https://www.rfc-editor.org/rfc/rfc8667#section-2.2.1" class="relref">Section 2.2.1</a> of [<a href="#RFC8667" class="xref">RFC8667</a>]</span>.<a href="#section-2.2.1-5.6.2.1" class="pilcrow">¶</a>
2053 </li>
2054 <li class="normal" id="section-2.2.1-5.6.2.2">OSPFv2 Adj-SID flags as defined in <span><a href="https://www.rfc-editor.org/rfc/rfc8665#section-6.1" class="relref">Section 6.1</a> of [<a href="#RFC8665" class="xref">RFC8665</a>]</span>.<a href="#section-2.2.1-5.6.2.2" class="pilcrow">¶</a>
2055 </li>
2056 <li class="normal" id="section-2.2.1-5.6.2.3">OSPFv3 Adj-SID flags as defined in <span><a href="https://www.rfc-editor.org/rfc/rfc8666#section-7.1" class="relref">Section 7.1</a> of [<a href="#RFC8666" class="xref">RFC8666</a>]</span>.<a href="#section-2.2.1-5.6.2.3" class="pilcrow">¶</a>
2057 </li>
2058 </ul>
2059 </dd>
2060 <dd class="break"></dd>
2061 <dt id="section-2.2.1-5.7">Weight:</dt>
2062 <dd style="margin-left: 1.5em" id="section-2.2.1-5.8"> 1 octet carrying the weight used for load-balancing
2063 purposes. The use of weight is described in <span><a href="https://www.rfc-editor.org/rfc/rfc8402#section-3.4" class="relref">Section 3.4</a> of [<a href="#RFC8402" class="xref">RFC8402</a>]</span>.<a href="#section-2.2.1-5.8" class="pilcrow">¶</a>
2064 </dd>
2065 <dd class="break"></dd>
2066 <dt id="section-2.2.1-5.9">Reserved:</dt>
2067 <dd style="margin-left: 1.5em" id="section-2.2.1-5.10"> 2 octets that <span class="bcp14">MUST</span> be set to 0 and ignored on
2068 receipt.<a href="#section-2.2.1-5.10" class="pilcrow">¶</a>
2069 </dd>
2070 <dd class="break"></dd>
2071 <dt id="section-2.2.1-5.11">SID/Index/Label: </dt>
2072 <dd style="margin-left: 1.5em" id="section-2.2.1-5.12">
2073 <p id="section-2.2.1-5.12.1"><br></p>
2074 <span class="break"></span><dl class="dlParallel" id="section-2.2.1-5.12.2">
2075 <dt id="section-2.2.1-5.12.2.1">IS-IS:</dt>
2076 <dd style="margin-left: 1.5em" id="section-2.2.1-5.12.2.2"> Label or index value as defined in
2077 <span><a href="https://www.rfc-editor.org/rfc/rfc8667#section-2.2.1" class="relref">Section 2.2.1</a> of [<a href="#RFC8667" class="xref">RFC8667</a>]</span>.<a href="#section-2.2.1-5.12.2.2" class="pilcrow">¶</a>
2078 </dd>
2079 <dd class="break"></dd>
2080 <dt id="section-2.2.1-5.12.2.3">OSPFv2:</dt>
2081 <dd style="margin-left: 1.5em" id="section-2.2.1-5.12.2.4"> Label or index value as defined in
2082 <span><a href="https://www.rfc-editor.org/rfc/rfc8665#section-6.1" class="relref">Section 6.1</a> of [<a href="#RFC8665" class="xref">RFC8665</a>]</span>.<a href="#section-2.2.1-5.12.2.4" class="pilcrow">¶</a>
2083 </dd>
2084 <dd class="break"></dd>
2085 <dt id="section-2.2.1-5.12.2.5">OSPFv3:</dt>
2086 <dd style="margin-left: 1.5em" id="section-2.2.1-5.12.2.6"> Label or index value as defined in
2087 <span><a href="https://www.rfc-editor.org/rfc/rfc8666#section-7.1" class="relref">Section 7.1</a> of [<a href="#RFC8666" class="xref">RFC8666</a>]</span>.<a href="#section-2.2.1-5.12.2.6" class="pilcrow">¶</a>
2088 </dd>
2089 <dd class="break"></dd>
2090 </dl>
2091 </dd>
2092 <dd class="break"></dd>
2093 </dl>
2094 <p id="section-2.2.1-6">The Flags and, as an extension, the SID/Index/Label fields of
2095 this TLV are interpreted according to the respective underlying
2096 IS-IS, OSPFv2, or OSPFv3 protocol. The Protocol-ID of the BGP-LS Link
2097 NLRI is used to determine the underlying protocol specification for
2098 parsing these fields.<a href="#section-2.2.1-6" class="pilcrow">¶</a></p>
2099 </section>
2100 </div>
2101 <div id="LANADJSIDTLV">
2102 <section id="section-2.2.2">
2103 <h4 id="name-lan-adjacency-sid-tlv">
2104 <a href="#section-2.2.2" class="section-number selfRef">2.2.2. </a><a href="#name-lan-adjacency-sid-tlv" class="section-name selfRef">LAN Adjacency SID TLV</a>
2105 </h4>
2106 <p id="section-2.2.2-1">For a LAN, normally a node only announces its adjacency to the
2107 IS-IS pseudonode (or the equivalent OSPF Designated and Backup
2108 Designated Routers). The LAN Adjacency SID TLV allows a node to
2109 announce adjacencies to all other nodes attached to the LAN in a
2110 single instance of the BGP-LS Link NLRI. Without this TLV, the
2111 corresponding BGP-LS Link NLRI would need to be originated for each
2112 additional adjacency in order to advertise the SR TLVs for these
2113 neighbor adjacencies.<a href="#section-2.2.2-1" class="pilcrow">¶</a></p>
2114 <p id="section-2.2.2-2">This information is derived from the LAN-Adj-SID Sub-TLV of
2115 IS-IS (<span><a href="https://www.rfc-editor.org/rfc/rfc8667#section-2.2.2" class="relref">Section 2.2.2</a> of [<a href="#RFC8667" class="xref">RFC8667</a>]</span>), the LAN Adj-SID Sub-TLV of OSPFv2
2116 (<span><a href="https://www.rfc-editor.org/rfc/rfc8665#section-6.2" class="relref">Section 6.2</a> of [<a href="#RFC8665" class="xref">RFC8665</a>]</span>), and the LAN Adj-SID Sub-TLV of OSPFv3 (<span><a href="https://www.rfc-editor.org/rfc/rfc8666#section-7.2" class="relref">Section 7.2</a> of [<a href="#RFC8666" class="xref">RFC8666</a>]</span>).<a href="#section-2.2.2-2" class="pilcrow">¶</a></p>
2117 <p id="section-2.2.2-3">The LAN Adjacency SID TLV has the following format:<a href="#section-2.2.2-3" class="pilcrow">¶</a></p>
2118 <span id="name-lan-adjacency-sid-tlv-forma"></span><div id="LADJSIDTLVFIG">
2119 <figure id="figure-8">
2120 <div class="artwork art-text alignLeft" id="section-2.2.2-4.1">
2121 <pre>
2122 0 1 2 3
2123 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
2124 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2125 | Type | Length |
2126 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2127 | Flags | Weight | Reserved |
2128 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2129
2130 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2131 | OSPF Neighbor ID / IS-IS System ID |
2132 + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2133 | |
2134 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2135
2136 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2137 | SID/Label/Index (variable) //
2138 +---------------------------------------------------------------+
2139 </pre>
2140 </div>
2141 <figcaption><a href="#figure-8" class="selfRef">Figure 8</a>:
2142 <a href="#name-lan-adjacency-sid-tlv-forma" class="selfRef">LAN Adjacency SID TLV Format</a>
2143 </figcaption></figure>
2144 </div>
2145 <p id="section-2.2.2-5">Where:<a href="#section-2.2.2-5" class="pilcrow">¶</a></p>
2146 <span class="break"></span><dl class="dlParallel" id="section-2.2.2-6">
2147 <dt id="section-2.2.2-6.1">Type:</dt>
2148 <dd style="margin-left: 1.5em" id="section-2.2.2-6.2">1100<a href="#section-2.2.2-6.2" class="pilcrow">¶</a>
2149 </dd>
2150 <dd class="break"></dd>
2151 <dt id="section-2.2.2-6.3">Length:</dt>
2152 <dd style="margin-left: 1.5em" id="section-2.2.2-6.4"> Variable. For IS-IS, it would be 13 or 14 octets depending on
2153 the label or index encoding of the SID. For OSPF, it would be 11 or
2154 12 octets depending on the label or index encoding of the SID.<a href="#section-2.2.2-6.4" class="pilcrow">¶</a>
2155 </dd>
2156 <dd class="break"></dd>
2157 <dt id="section-2.2.2-6.5">Flags:</dt>
2158 <dd style="margin-left: 1.5em" id="section-2.2.2-6.6">
2159 <p id="section-2.2.2-6.6.1"> 1-octet value that should be set as:<a href="#section-2.2.2-6.6.1" class="pilcrow">¶</a></p>
2160 <ul class="normal">
2161 <li class="normal" id="section-2.2.2-6.6.2.1">IS-IS LAN Adj-SID flags as defined in
2162 <span><a href="https://www.rfc-editor.org/rfc/rfc8667#section-2.2.2" class="relref">Section 2.2.2</a> of [<a href="#RFC8667" class="xref">RFC8667</a>]</span>.<a href="#section-2.2.2-6.6.2.1" class="pilcrow">¶</a>
2163 </li>
2164 <li class="normal" id="section-2.2.2-6.6.2.2">OSPFv2 LAN Adj-SID flags as defined in
2165 <span><a href="https://www.rfc-editor.org/rfc/rfc8665#section-6.2" class="relref">Section 6.2</a> of [<a href="#RFC8665" class="xref">RFC8665</a>]</span>.<a href="#section-2.2.2-6.6.2.2" class="pilcrow">¶</a>
2166 </li>
2167 <li class="normal" id="section-2.2.2-6.6.2.3">OSPFv3 LAN Adj-SID flags as defined in
2168 <span><a href="https://www.rfc-editor.org/rfc/rfc8666#section-7.2" class="relref">Section 7.2</a> of [<a href="#RFC8666" class="xref">RFC8666</a>]</span>.<a href="#section-2.2.2-6.6.2.3" class="pilcrow">¶</a>
2169 </li>
2170 </ul>
2171 </dd>
2172 <dd class="break"></dd>
2173 <dt id="section-2.2.2-6.7">Weight:</dt>
2174 <dd style="margin-left: 1.5em" id="section-2.2.2-6.8"> 1 octet carrying the weight used for load-balancing
2175 purposes. The use of weight is described in <span><a href="https://www.rfc-editor.org/rfc/rfc8402#section-3.4" class="relref">Section 3.4</a> of [<a href="#RFC8402" class="xref">RFC8402</a>]</span>.<a href="#section-2.2.2-6.8" class="pilcrow">¶</a>
2176 </dd>
2177 <dd class="break"></dd>
2178 <dt id="section-2.2.2-6.9">Reserved:</dt>
2179 <dd style="margin-left: 1.5em" id="section-2.2.2-6.10"> 2 octets that <span class="bcp14">MUST</span> be set to 0 and ignored on
2180 receipt.<a href="#section-2.2.2-6.10" class="pilcrow">¶</a>
2181 </dd>
2182 <dd class="break"></dd>
2183 <dt id="section-2.2.2-6.11">Neighbor ID:</dt>
2184 <dd style="margin-left: 1.5em" id="section-2.2.2-6.12"> 6 octets for IS-IS for the System ID, and 4
2185 octets for OSPF for the OSPF Router-ID of the neighbor.<a href="#section-2.2.2-6.12" class="pilcrow">¶</a>
2186 </dd>
2187 <dd class="break"></dd>
2188 <dt id="section-2.2.2-6.13">SID/Index/Label: </dt>
2189 <dd style="margin-left: 1.5em" id="section-2.2.2-6.14">
2190 <p id="section-2.2.2-6.14.1"><br></p>
2191 <span class="break"></span><dl class="dlParallel" id="section-2.2.2-6.14.2">
2192 <dt id="section-2.2.2-6.14.2.1">IS-IS:</dt>
2193 <dd style="margin-left: 1.5em" id="section-2.2.2-6.14.2.2"> Label or index value as defined in
2194 <span><a href="https://www.rfc-editor.org/rfc/rfc8667#section-2.2.2" class="relref">Section 2.2.2</a> of [<a href="#RFC8667" class="xref">RFC8667</a>]</span>.<a href="#section-2.2.2-6.14.2.2" class="pilcrow">¶</a>
2195 </dd>
2196 <dd class="break"></dd>
2197 <dt id="section-2.2.2-6.14.2.3">OSPFv2:</dt>
2198 <dd style="margin-left: 1.5em" id="section-2.2.2-6.14.2.4"> Label or index value as defined in
2199 <span><a href="https://www.rfc-editor.org/rfc/rfc8665#section-6.2" class="relref">Section 6.2</a> of [<a href="#RFC8665" class="xref">RFC8665</a>]</span>.<a href="#section-2.2.2-6.14.2.4" class="pilcrow">¶</a>
2200 </dd>
2201 <dd class="break"></dd>
2202 <dt id="section-2.2.2-6.14.2.5">OSPFv3:</dt>
2203 <dd style="margin-left: 1.5em" id="section-2.2.2-6.14.2.6"> Label or index value as defined in
2204 <span><a href="https://www.rfc-editor.org/rfc/rfc8666#section-7.2" class="relref">Section 7.2</a> of [<a href="#RFC8666" class="xref">RFC8666</a>]</span>.<a href="#section-2.2.2-6.14.2.6" class="pilcrow">¶</a>
2205 </dd>
2206 <dd class="break"></dd>
2207 </dl>
2208 </dd>
2209 <dd class="break"></dd>
2210 </dl>
2211 <p id="section-2.2.2-7">The Neighbor ID, Flags, and, as an extension, the SID/Index/Label
2212 fields of this TLV are interpreted according to the respective
2213 underlying IS-IS, OSPFv2, or OSPFv3 protocol. The Protocol-ID of the
2214 BGP-LS Link NLRI is used to determine the underlying protocol
2215 specification for parsing these fields.<a href="#section-2.2.2-7" class="pilcrow">¶</a></p>
2216 </section>
2217 </div>
2218 <div id="L2BUNDLETLV">
2219 <section id="section-2.2.3">
2220 <h4 id="name-l2-bundle-member-attributes">
2221 <a href="#section-2.2.3" class="section-number selfRef">2.2.3. </a><a href="#name-l2-bundle-member-attributes" class="section-name selfRef">L2 Bundle Member Attributes TLV</a>
2222 </h4>
2223 <p id="section-2.2.3-1">The L2 Bundle Member Attributes TLV identifies an L2 Bundle Member
2224 link, which in turn is associated with a parent L3 link. The L3 link
2225 is described by the Link NLRI defined in <span>[<a href="#RFC7752" class="xref">RFC7752</a>]</span>,
2226 and the L2 Bundle Member Attributes TLV is associated with the Link
2227 NLRI. The TLV <span class="bcp14">MAY</span> include sub-TLVs that describe attributes
2228 associated with the bundle member. The identified bundle member
2229 represents a unidirectional path from the originating router to the
2230 neighbor specified in the parent L3 link. Multiple L2 Bundle Member
2231 Attributes TLVs <span class="bcp14">MAY</span> be associated with a Link NLRI.<a href="#section-2.2.3-1" class="pilcrow">¶</a></p>
2232 <p id="section-2.2.3-2">This information is derived from L2 Bundle Member Attributes TLV
2233 of IS-IS (<span><a href="https://www.rfc-editor.org/rfc/rfc8668#section-2" class="relref">Section 2</a> of [<a href="#RFC8668" class="xref">RFC8668</a>]</span>).
2234 The equivalent functionality has not been specified as yet for
2235 OSPF.<a href="#section-2.2.3-2" class="pilcrow">¶</a></p>
2236 <p id="section-2.2.3-3">The L2 Bundle Member Attributes TLV has the following format:<a href="#section-2.2.3-3" class="pilcrow">¶</a></p>
2237 <span id="name-l2-bundle-member-attributes-"></span><div id="L2BTLVFIG">
2238 <figure id="figure-9">
2239 <div class="artwork art-text alignLeft" id="section-2.2.3-4.1">
2240 <pre> 0 1 2 3
2241 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
2242 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2243 | Type | Length |
2244 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2245 | L2 Bundle Member Descriptor |
2246 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2247 | Link Attribute Sub-TLVs(variable) //
2248 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2249 </pre>
2250 </div>
2251 <figcaption><a href="#figure-9" class="selfRef">Figure 9</a>:
2252 <a href="#name-l2-bundle-member-attributes-" class="selfRef">L2 Bundle Member Attributes TLV Format</a>
2253 </figcaption></figure>
2254 </div>
2255 <p id="section-2.2.3-5">Where:<a href="#section-2.2.3-5" class="pilcrow">¶</a></p>
2256 <span class="break"></span><dl class="dlParallel" id="section-2.2.3-6">
2257 <dt id="section-2.2.3-6.1">Type:</dt>
2258 <dd style="margin-left: 1.5em" id="section-2.2.3-6.2"> 1172<a href="#section-2.2.3-6.2" class="pilcrow">¶</a>
2259 </dd>
2260 <dd class="break"></dd>
2261 <dt id="section-2.2.3-6.3">Length:</dt>
2262 <dd style="margin-left: 1.5em" id="section-2.2.3-6.4"> Variable.<a href="#section-2.2.3-6.4" class="pilcrow">¶</a>
2263 </dd>
2264 <dd class="break"></dd>
2265 <dt id="section-2.2.3-6.5">L2 Bundle Member Descriptor:</dt>
2266 <dd style="margin-left: 1.5em" id="section-2.2.3-6.6"> 4-octet field that carries a
2267 link-local identifier as defined in <span>[<a href="#RFC4202" class="xref">RFC4202</a>]</span>.<a href="#section-2.2.3-6.6" class="pilcrow">¶</a>
2268 </dd>
2269 <dd class="break"></dd>
2270 </dl>
2271 <p id="section-2.2.3-7">Link attributes for L2 Bundle Member links are advertised as
2272 sub-TLVs of the L2 Bundle Member Attributes TLV. The sub-TLVs are
2273 identical to existing BGP-LS TLVs as identified in the table
2274 below.<a href="#section-2.2.3-7" class="pilcrow">¶</a></p>
2275 <span id="name-bgp-ls-attribute-tlvs-are-a"></span><div id="l2subtlvs">
2276 <table class="center" id="table-3">
2277 <caption>
2278 <a href="#table-3" class="selfRef">Table 3</a>:
2279 <a href="#name-bgp-ls-attribute-tlvs-are-a" class="selfRef">BGP-LS Attribute TLVs are also used as sub-TLVs of the L2 Bundle Member Attributes TLV</a>
2280 </caption>
2281 <thead>
2282 <tr>
2283 <th class="text-center" rowspan="1" colspan="1">TLV Code Point</th>
2284 <th class="text-left" rowspan="1" colspan="1">Description</th>
2285 <th class="text-left" rowspan="1" colspan="1">Reference Document</th>
2286 </tr>
2287 </thead>
2288 <tbody>
2289 <tr>
2290 <td class="text-center" rowspan="1" colspan="1">1088</td>
2291 <td class="text-left" rowspan="1" colspan="1">Administrative group (color)</td>
2292 <td class="text-left" rowspan="1" colspan="1">
2293 <span>[<a href="#RFC7752" class="xref">RFC7752</a>]</span>
2294 </td>
2295 </tr>
2296 <tr>
2297 <td class="text-center" rowspan="1" colspan="1">1089</td>
2298 <td class="text-left" rowspan="1" colspan="1">Maximum link bandwidth</td>
2299 <td class="text-left" rowspan="1" colspan="1">
2300 <span>[<a href="#RFC7752" class="xref">RFC7752</a>]</span>
2301 </td>
2302 </tr>
2303 <tr>
2304 <td class="text-center" rowspan="1" colspan="1">1090</td>
2305 <td class="text-left" rowspan="1" colspan="1">Max. reservable link bandwidth</td>
2306 <td class="text-left" rowspan="1" colspan="1">
2307 <span>[<a href="#RFC7752" class="xref">RFC7752</a>]</span>
2308 </td>
2309 </tr>
2310 <tr>
2311 <td class="text-center" rowspan="1" colspan="1">1091</td>
2312 <td class="text-left" rowspan="1" colspan="1">Unreserved bandwidth</td>
2313 <td class="text-left" rowspan="1" colspan="1">
2314 <span>[<a href="#RFC7752" class="xref">RFC7752</a>]</span>
2315 </td>
2316 </tr>
2317 <tr>
2318 <td class="text-center" rowspan="1" colspan="1">1092</td>
2319 <td class="text-left" rowspan="1" colspan="1">TE default metric</td>
2320 <td class="text-left" rowspan="1" colspan="1">
2321 <span>[<a href="#RFC7752" class="xref">RFC7752</a>]</span>
2322 </td>
2323 </tr>
2324 <tr>
2325 <td class="text-center" rowspan="1" colspan="1">1093</td>
2326 <td class="text-left" rowspan="1" colspan="1">Link protection type</td>
2327 <td class="text-left" rowspan="1" colspan="1">
2328 <span>[<a href="#RFC7752" class="xref">RFC7752</a>]</span>
2329 </td>
2330 </tr>
2331 <tr>
2332 <td class="text-center" rowspan="1" colspan="1">1099</td>
2333 <td class="text-left" rowspan="1" colspan="1">Adjacency Segment Identifier (Adj-SID) TLV</td>
2334 <td class="text-left" rowspan="1" colspan="1">
2335 <a href="#ADJSIDTLV" class="xref">Section 2.2.1</a>
2336 </td>
2337 </tr>
2338 <tr>
2339 <td class="text-center" rowspan="1" colspan="1">1100</td>
2340 <td class="text-left" rowspan="1" colspan="1">LAN Adjacency Segment Identifier (Adj-SID) TLV</td>
2341 <td class="text-left" rowspan="1" colspan="1">
2342 <a href="#LANADJSIDTLV" class="xref">Section 2.2.2</a>
2343 </td>
2344 </tr>
2345 <tr>
2346 <td class="text-center" rowspan="1" colspan="1">1114</td>
2347 <td class="text-left" rowspan="1" colspan="1">Unidirectional link delay</td>
2348 <td class="text-left" rowspan="1" colspan="1">
2349 <span>[<a href="#RFC8571" class="xref">RFC8571</a>]</span>
2350 </td>
2351 </tr>
2352 <tr>
2353 <td class="text-center" rowspan="1" colspan="1">1115</td>
2354 <td class="text-left" rowspan="1" colspan="1">Min/Max Unidirectional link delay</td>
2355 <td class="text-left" rowspan="1" colspan="1">
2356 <span>[<a href="#RFC8571" class="xref">RFC8571</a>]</span>
2357 </td>
2358 </tr>
2359 <tr>
2360 <td class="text-center" rowspan="1" colspan="1">1116</td>
2361 <td class="text-left" rowspan="1" colspan="1">Unidirectional Delay Variation</td>
2362 <td class="text-left" rowspan="1" colspan="1">
2363 <span>[<a href="#RFC8571" class="xref">RFC8571</a>]</span>
2364 </td>
2365 </tr>
2366 <tr>
2367 <td class="text-center" rowspan="1" colspan="1">1117</td>
2368 <td class="text-left" rowspan="1" colspan="1">Unidirectional Link Loss</td>
2369 <td class="text-left" rowspan="1" colspan="1">
2370 <span>[<a href="#RFC8571" class="xref">RFC8571</a>]</span>
2371 </td>
2372 </tr>
2373 <tr>
2374 <td class="text-center" rowspan="1" colspan="1">1118</td>
2375 <td class="text-left" rowspan="1" colspan="1">Unidirectional residual bandwidth</td>
2376 <td class="text-left" rowspan="1" colspan="1">
2377 <span>[<a href="#RFC8571" class="xref">RFC8571</a>]</span>
2378 </td>
2379 </tr>
2380 <tr>
2381 <td class="text-center" rowspan="1" colspan="1">1119</td>
2382 <td class="text-left" rowspan="1" colspan="1">Unidirectional available bandwidth</td>
2383 <td class="text-left" rowspan="1" colspan="1">
2384 <span>[<a href="#RFC8571" class="xref">RFC8571</a>]</span>
2385 </td>
2386 </tr>
2387 <tr>
2388 <td class="text-center" rowspan="1" colspan="1">1120</td>
2389 <td class="text-left" rowspan="1" colspan="1">Unidirectional Utilized Bandwidth</td>
2390 <td class="text-left" rowspan="1" colspan="1">
2391 <span>[<a href="#RFC8571" class="xref">RFC8571</a>]</span>
2392 </td>
2393 </tr>
2394 </tbody>
2395 </table>
2396 </div>
2397 </section>
2398 </div>
2399 </section>
2400 </div>
2401 <div id="PREFIX">
2402 <section id="section-2.3">
2403 <h3 id="name-prefix-attribute-tlvs">
2404 <a href="#section-2.3" class="section-number selfRef">2.3. </a><a href="#name-prefix-attribute-tlvs" class="section-name selfRef">Prefix Attribute TLVs</a>
2405 </h3>
2406 <p id="section-2.3-1">The following Prefix Attribute TLVs are defined:<a href="#section-2.3-1" class="pilcrow">¶</a></p>
2407 <span id="name-prefix-attribute-tlvs-2"></span><div id="prefix-attribute_tlv">
2408 <table class="center" id="table-4">
2409 <caption>
2410 <a href="#table-4" class="selfRef">Table 4</a>:
2411 <a href="#name-prefix-attribute-tlvs-2" class="selfRef">Prefix Attribute TLVs</a>
2412 </caption>
2413 <thead>
2414 <tr>
2415 <th class="text-center" rowspan="1" colspan="1">Type</th>
2416 <th class="text-left" rowspan="1" colspan="1">Description</th>
2417 <th class="text-left" rowspan="1" colspan="1">Section</th>
2418 </tr>
2419 </thead>
2420 <tbody>
2421 <tr>
2422 <td class="text-center" rowspan="1" colspan="1">1158</td>
2423 <td class="text-left" rowspan="1" colspan="1">Prefix-SID</td>
2424 <td class="text-left" rowspan="1" colspan="1">
2425 <a href="#PREFIXSIDTLV" class="xref">Section 2.3.1</a>
2426 </td>
2427 </tr>
2428 <tr>
2429 <td class="text-center" rowspan="1" colspan="1">1159</td>
2430 <td class="text-left" rowspan="1" colspan="1">Range</td>
2431 <td class="text-left" rowspan="1" colspan="1">
2432 <a href="#RANGETLV" class="xref">Section 2.3.5</a>
2433 </td>
2434 </tr>
2435 <tr>
2436 <td class="text-center" rowspan="1" colspan="1">1170</td>
2437 <td class="text-left" rowspan="1" colspan="1">Prefix Attribute Flags</td>
2438 <td class="text-left" rowspan="1" colspan="1">
2439 <a href="#PREFIXATTRFLAGTLV" class="xref">Section 2.3.2</a>
2440 </td>
2441 </tr>
2442 <tr>
2443 <td class="text-center" rowspan="1" colspan="1">1171</td>
2444 <td class="text-left" rowspan="1" colspan="1">Source Router Identifier</td>
2445 <td class="text-left" rowspan="1" colspan="1">
2446 <a href="#SOURCEIDTLV" class="xref">Section 2.3.3</a>
2447 </td>
2448 </tr>
2449 <tr>
2450 <td class="text-center" rowspan="1" colspan="1">1174</td>
2451 <td class="text-left" rowspan="1" colspan="1">Source OSPF Router-ID</td>
2452 <td class="text-left" rowspan="1" colspan="1">
2453 <a href="#SOURCEOSPFRIDTLV" class="xref">Section 2.3.4</a>
2454 </td>
2455 </tr>
2456 </tbody>
2457 </table>
2458 </div>
2459 <p id="section-2.3-3">These TLVs should only be added to the BGP-LS Attribute associated
2460 with the Prefix NLRI that describes the prefix of the IGP node that is
2461 originating the corresponding IGP TLV/sub-TLV described below.<a href="#section-2.3-3" class="pilcrow">¶</a></p>
2462 <div id="PREFIXSIDTLV">
2463 <section id="section-2.3.1">
2464 <h4 id="name-prefix-sid-tlv">
2465 <a href="#section-2.3.1" class="section-number selfRef">2.3.1. </a><a href="#name-prefix-sid-tlv" class="section-name selfRef">Prefix-SID TLV</a>
2466 </h4>
2467 <p id="section-2.3.1-1">The Prefix-SID TLV is used in order to advertise information
2468 related to a Prefix-SID. This information is derived from the Prefix-SID
2469 Sub-TLV of IS-IS (<span><a href="https://www.rfc-editor.org/rfc/rfc8667#section-2.1" class="relref">Section 2.1</a> of [<a href="#RFC8667" class="xref">RFC8667</a>]</span>), the Prefix-SID
2470 Sub-TLV of OSPFv2 (<span><a href="https://www.rfc-editor.org/rfc/rfc8665#section-5" class="relref">Section 5</a> of [<a href="#RFC8665" class="xref">RFC8665</a>]</span>), and the Prefix-SID
2471 Sub-TLV of OSPFv3
2472 (<span><a href="https://www.rfc-editor.org/rfc/rfc8666#section-6" class="relref">Section 6</a> of [<a href="#RFC8666" class="xref">RFC8666</a>]</span>).<a href="#section-2.3.1-1" class="pilcrow">¶</a></p>
2473 <p id="section-2.3.1-2">The Prefix-SID TLV has the following format:<a href="#section-2.3.1-2" class="pilcrow">¶</a></p>
2474 <span id="name-prefix-sid-tlv-format"></span><div id="PFXSIDTLVFIG">
2475 <figure id="figure-10">
2476 <div class="artwork art-text alignLeft" id="section-2.3.1-3.1">
2477 <pre>
2478 0 1 2 3
2479 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
2480 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2481 | Type | Length |
2482 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2483 | Flags | Algorithm | Reserved |
2484 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2485 | SID/Index/Label (variable) //
2486 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2487 </pre>
2488 </div>
2489 <figcaption><a href="#figure-10" class="selfRef">Figure 10</a>:
2490 <a href="#name-prefix-sid-tlv-format" class="selfRef">Prefix-SID TLV Format</a>
2491 </figcaption></figure>
2492 </div>
2493 <p id="section-2.3.1-4">Where:<a href="#section-2.3.1-4" class="pilcrow">¶</a></p>
2494 <span class="break"></span><dl class="dlParallel" id="section-2.3.1-5">
2495 <dt id="section-2.3.1-5.1">Type:</dt>
2496 <dd style="margin-left: 1.5em" id="section-2.3.1-5.2"> 1158<a href="#section-2.3.1-5.2" class="pilcrow">¶</a>
2497 </dd>
2498 <dd class="break"></dd>
2499 <dt id="section-2.3.1-5.3">Length:</dt>
2500 <dd style="margin-left: 1.5em" id="section-2.3.1-5.4"> Variable. 7 or 8 octets depending on the label or index encoding
2501 of the SID.<a href="#section-2.3.1-5.4" class="pilcrow">¶</a>
2502 </dd>
2503 <dd class="break"></dd>
2504 <dt id="section-2.3.1-5.5">Flags:</dt>
2505 <dd style="margin-left: 1.5em" id="section-2.3.1-5.6">
2506 <p id="section-2.3.1-5.6.1"> 1-octet value that should be set as:<a href="#section-2.3.1-5.6.1" class="pilcrow">¶</a></p>
2507 <ul class="normal">
2508 <li class="normal" id="section-2.3.1-5.6.2.1">IS-IS Prefix-SID flags as defined in
2509 <span><a href="https://www.rfc-editor.org/rfc/rfc8667#section-2.1.1" class="relref">Section 2.1.1</a> of [<a href="#RFC8667" class="xref">RFC8667</a>]</span>.<a href="#section-2.3.1-5.6.2.1" class="pilcrow">¶</a>
2510 </li>
2511 <li class="normal" id="section-2.3.1-5.6.2.2">OSPFv2 Prefix-SID flags as defined in <span><a href="https://www.rfc-editor.org/rfc/rfc8665#section-5" class="relref">Section 5</a> of [<a href="#RFC8665" class="xref">RFC8665</a>]</span>.<a href="#section-2.3.1-5.6.2.2" class="pilcrow">¶</a>
2512 </li>
2513 <li class="normal" id="section-2.3.1-5.6.2.3">OSPFv3 Prefix-SID flags as defined in <span><a href="https://www.rfc-editor.org/rfc/rfc8665#section-6" class="relref">Section 6</a> of [<a href="#RFC8665" class="xref">RFC8665</a>]</span>.<a href="#section-2.3.1-5.6.2.3" class="pilcrow">¶</a>
2514 </li>
2515 </ul>
2516 </dd>
2517 <dd class="break"></dd>
2518 <dt id="section-2.3.1-5.7">Algorithm:</dt>
2519 <dd style="margin-left: 1.5em" id="section-2.3.1-5.8"> 1-octet value identifies the algorithm. The
2520 semantics of the algorithm are described in <span><a href="https://www.rfc-editor.org/rfc/rfc8402#section-3.1.1" class="relref">Section 3.1.1</a> of [<a href="#RFC8402" class="xref">RFC8402</a>]</span>.<a href="#section-2.3.1-5.8" class="pilcrow">¶</a>
2521 </dd>
2522 <dd class="break"></dd>
2523 <dt id="section-2.3.1-5.9">Reserved:</dt>
2524 <dd style="margin-left: 1.5em" id="section-2.3.1-5.10"> 2 octets that <span class="bcp14">MUST</span> be set to 0 and ignored on
2525 receipt.<a href="#section-2.3.1-5.10" class="pilcrow">¶</a>
2526 </dd>
2527 <dd class="break"></dd>
2528 <dt id="section-2.3.1-5.11">SID/Index/Label:</dt>
2529 <dd style="margin-left: 1.5em" id="section-2.3.1-5.12">
2530 <p id="section-2.3.1-5.12.1"><br></p>
2531 <span class="break"></span><dl class="dlParallel" id="section-2.3.1-5.12.2">
2532 <dt id="section-2.3.1-5.12.2.1">IS-IS:</dt>
2533 <dd style="margin-left: 1.5em" id="section-2.3.1-5.12.2.2"> Label or index value as defined in
2534 <span><a href="https://www.rfc-editor.org/rfc/rfc8667#section-2.1" class="relref">Section 2.1</a> of [<a href="#RFC8667" class="xref">RFC8667</a>]</span>.<a href="#section-2.3.1-5.12.2.2" class="pilcrow">¶</a>
2535 </dd>
2536 <dd class="break"></dd>
2537 <dt id="section-2.3.1-5.12.2.3">OSPFv2:</dt>
2538 <dd style="margin-left: 1.5em" id="section-2.3.1-5.12.2.4"> Label or index value as defined in
2539 <span><a href="https://www.rfc-editor.org/rfc/rfc8665#section-5" class="relref">Section 5</a> of [<a href="#RFC8665" class="xref">RFC8665</a>]</span>.<a href="#section-2.3.1-5.12.2.4" class="pilcrow">¶</a>
2540 </dd>
2541 <dd class="break"></dd>
2542 <dt id="section-2.3.1-5.12.2.5">OSPFv3:</dt>
2543 <dd style="margin-left: 1.5em" id="section-2.3.1-5.12.2.6"> Label or index value as defined in
2544 <span><a href="https://www.rfc-editor.org/rfc/rfc8666#section-6" class="relref">Section 6</a> of [<a href="#RFC8666" class="xref">RFC8666</a>]</span>.<a href="#section-2.3.1-5.12.2.6" class="pilcrow">¶</a>
2545 </dd>
2546 <dd class="break"></dd>
2547 </dl>
2548 </dd>
2549 <dd class="break"></dd>
2550 </dl>
2551 <p id="section-2.3.1-6">The Flags and, as an extension, the SID/Index/Label fields of
2552 this TLV are interpreted according to the respective underlying
2553 IS-IS, OSPFv2, or OSPFv3 protocol. The Protocol-ID of the BGP-LS
2554 Prefix NLRI is used to determine the underlying protocol
2555 specification for parsing these fields.<a href="#section-2.3.1-6" class="pilcrow">¶</a></p>
2556 </section>
2557 </div>
2558 <div id="PREFIXATTRFLAGTLV">
2559 <section id="section-2.3.2">
2560 <h4 id="name-prefix-attribute-flags-tlv">
2561 <a href="#section-2.3.2" class="section-number selfRef">2.3.2. </a><a href="#name-prefix-attribute-flags-tlv" class="section-name selfRef">Prefix Attribute Flags TLV</a>
2562 </h4>
2563 <p id="section-2.3.2-1">The Prefix Attribute Flags TLV carries IPv4/IPv6 prefix attribute
2564 flags information. These flags are defined for OSPFv2 in
2565 <span><a href="https://www.rfc-editor.org/rfc/rfc7684#section-2.1" class="relref">Section 2.1</a> of [<a href="#RFC7684" class="xref">RFC7684</a>]</span>, OSPFv3 in <span><a href="https://www.rfc-editor.org/rfc/rfc5340#appendix-A.4.1.1" class="relref">Appendix A.4.1.1</a> of [<a href="#RFC5340" class="xref">RFC5340</a>]</span>, and IS-IS in <span><a href="https://www.rfc-editor.org/rfc/rfc7794#section-2.1" class="relref">Section 2.1</a> of [<a href="#RFC7794" class="xref">RFC7794</a>]</span>.<a href="#section-2.3.2-1" class="pilcrow">¶</a></p>
2566 <p id="section-2.3.2-2">The Prefix Attribute Flags TLV has the following format:<a href="#section-2.3.2-2" class="pilcrow">¶</a></p>
2567 <span id="name-prefix-attribute-flags-tlv-"></span><div id="PFXATRTLVFIG">
2568 <figure id="figure-11">
2569 <div class="artwork art-text alignLeft" id="section-2.3.2-3.1">
2570 <pre> 0 1 2 3
2571 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
2572 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2573 | Type | Length |
2574 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2575 | Flags (variable) //
2576 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2577 </pre>
2578 </div>
2579 <figcaption><a href="#figure-11" class="selfRef">Figure 11</a>:
2580 <a href="#name-prefix-attribute-flags-tlv-" class="selfRef">Prefix Attribute Flags TLV Format</a>
2581 </figcaption></figure>
2582 </div>
2583 <p id="section-2.3.2-4">Where:<a href="#section-2.3.2-4" class="pilcrow">¶</a></p>
2584 <span class="break"></span><dl class="dlParallel" id="section-2.3.2-5">
2585 <dt id="section-2.3.2-5.1">Type:</dt>
2586 <dd style="margin-left: 1.5em" id="section-2.3.2-5.2"> 1170<a href="#section-2.3.2-5.2" class="pilcrow">¶</a>
2587 </dd>
2588 <dd class="break"></dd>
2589 <dt id="section-2.3.2-5.3">Length:</dt>
2590 <dd style="margin-left: 1.5em" id="section-2.3.2-5.4"> Variable.<a href="#section-2.3.2-5.4" class="pilcrow">¶</a>
2591 </dd>
2592 <dd class="break"></dd>
2593 <dt id="section-2.3.2-5.5">Flags:</dt>
2594 <dd style="margin-left: 1.5em" id="section-2.3.2-5.6">
2595 <p id="section-2.3.2-5.6.1"> a variable-length Flag field (according to the Length
2596 field). Flags are routing protocol specific and are to be set as
2597 below:<a href="#section-2.3.2-5.6.1" class="pilcrow">¶</a></p>
2598 <ul class="normal">
2599 <li class="normal" id="section-2.3.2-5.6.2.1">IS-IS flags correspond to the IPv4/IPv6 Extended
2600 Reachability Attribute Flags defined in <span><a href="https://www.rfc-editor.org/rfc/rfc7794#section-2.1" class="relref">Section 2.1</a> of [<a href="#RFC7794" class="xref">RFC7794</a>]</span>.
2601 In the case of the X-flag when associated with IPv6 prefix
2602 reachability, the setting corresponds to the setting of the
2603 X-flag in the fixed format of IS-IS TLVs 236 <span>[<a href="#RFC5308" class="xref">RFC5308</a>]</span> and 237
2604 <span>[<a href="#RFC5120" class="xref">RFC5120</a>]</span>.<a href="#section-2.3.2-5.6.2.1" class="pilcrow">¶</a>
2605 </li>
2606 <li class="normal" id="section-2.3.2-5.6.2.2">OSPFv2 flags correspond to the Flags field of the
2607 OSPFv2 Extended Prefix TLV defined in
2608 <span><a href="https://www.rfc-editor.org/rfc/rfc7684#section-2.1" class="relref">Section 2.1</a> of [<a href="#RFC7684" class="xref">RFC7684</a>]</span>.<a href="#section-2.3.2-5.6.2.2" class="pilcrow">¶</a>
2609 </li>
2610 <li class="normal" id="section-2.3.2-5.6.2.3">OSPFv3 flags map to the Prefix Options field defined in
2611 <span><a href="https://www.rfc-editor.org/rfc/rfc5340#appendix-A.4.1.1" class="relref">Appendix A.4.1.1</a> of [<a href="#RFC5340" class="xref">RFC5340</a>]</span> and extended in
2612 <span><a href="https://www.rfc-editor.org/rfc/rfc8362#section-3.1" class="relref">Section 3.1</a> of [<a href="#RFC8362" class="xref">RFC8362</a>]</span>.<a href="#section-2.3.2-5.6.2.3" class="pilcrow">¶</a>
2613 </li>
2614 </ul>
2615 </dd>
2616 <dd class="break"></dd>
2617 </dl>
2618 <p id="section-2.3.2-6">The Flags field of this TLV is interpreted according to the
2619 respective underlying IS-IS, OSPFv2, or OSPFv3 protocol. The
2620 Protocol-ID of the BGP-LS Prefix NLRI is used to determine the
2621 underlying protocol specification for parsing this field.<a href="#section-2.3.2-6" class="pilcrow">¶</a></p>
2622 </section>
2623 </div>
2624 <div id="SOURCEIDTLV">
2625 <section id="section-2.3.3">
2626 <h4 id="name-source-router-identifier-tl">
2627 <a href="#section-2.3.3" class="section-number selfRef">2.3.3. </a><a href="#name-source-router-identifier-tl" class="section-name selfRef">Source Router Identifier TLV</a>
2628 </h4>
2629 <p id="section-2.3.3-1">The Source Router Identifier TLV contains the IPv4 or IPv6 Router Identifier of
2630 the originator of the prefix. For the IS-IS protocol, this is derived
2631 from the IPv4/IPv6 Source Router ID Sub-TLV as defined in
2632 <span><a href="https://www.rfc-editor.org/rfc/rfc7794#section-2.2" class="relref">Section 2.2</a> of [<a href="#RFC7794" class="xref">RFC7794</a>]</span>. For the OSPF protocol, this is
2633 derived from the Prefix Source Router Address Sub-TLV as defined in
2634 <span><a href="https://www.rfc-editor.org/rfc/rfc9084#section-2.2" class="relref">Section 2.2</a> of [<a href="#RFC9084" class="xref">RFC9084</a>]</span>.<a href="#section-2.3.3-1" class="pilcrow">¶</a></p>
2635 <p id="section-2.3.3-2">The Source Router Identifier TLV has the following format:<a href="#section-2.3.3-2" class="pilcrow">¶</a></p>
2636 <span id="name-source-router-identifier-tlv"></span><div id="SRCRIDTLVFIG">
2637 <figure id="figure-12">
2638 <div class="artwork art-text alignLeft" id="section-2.3.3-3.1">
2639 <pre> 0 1 2 3
2640 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
2641 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2642 | Type | Length |
2643 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2644 | 4- or 16-octet Router Identifier //
2645 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2646 </pre>
2647 </div>
2648 <figcaption><a href="#figure-12" class="selfRef">Figure 12</a>:
2649 <a href="#name-source-router-identifier-tlv" class="selfRef">Source Router Identifier TLV Format</a>
2650 </figcaption></figure>
2651 </div>
2652 <p id="section-2.3.3-4">Where:<a href="#section-2.3.3-4" class="pilcrow">¶</a></p>
2653 <span class="break"></span><dl class="dlParallel" id="section-2.3.3-5">
2654 <dt id="section-2.3.3-5.1">Type:</dt>
2655 <dd style="margin-left: 1.5em" id="section-2.3.3-5.2"> 1171<a href="#section-2.3.3-5.2" class="pilcrow">¶</a>
2656 </dd>
2657 <dd class="break"></dd>
2658 <dt id="section-2.3.3-5.3">Length:</dt>
2659 <dd style="margin-left: 1.5em" id="section-2.3.3-5.4"> Variable. 4 or 16 octets for the IPv4 or IPv6 prefix, respectively.<a href="#section-2.3.3-5.4" class="pilcrow">¶</a>
2660 </dd>
2661 <dd class="break"></dd>
2662 <dt id="section-2.3.3-5.5">Router-ID:</dt>
2663 <dd style="margin-left: 1.5em" id="section-2.3.3-5.6"> the IPv4 or IPv6 Router-ID in the case of IS-IS, and
2664 the IPv4 or IPv6 Router Address in the case of OSPF.<a href="#section-2.3.3-5.6" class="pilcrow">¶</a>
2665 </dd>
2666 <dd class="break"></dd>
2667 </dl>
2668 </section>
2669 </div>
2670 <div id="SOURCEOSPFRIDTLV">
2671 <section id="section-2.3.4">
2672 <h4 id="name-source-ospf-router-id-tlv">
2673 <a href="#section-2.3.4" class="section-number selfRef">2.3.4. </a><a href="#name-source-ospf-router-id-tlv" class="section-name selfRef">Source OSPF Router-ID TLV</a>
2674 </h4>
2675 <p id="section-2.3.4-1">The Source OSPF Router-ID TLV is applicable only for the OSPF
2676 protocol and contains the OSPF Router-ID of the originator of the
2677 prefix. It is derived from the Prefix Source OSPF Router-ID Sub-TLV
2678 as defined in <span><a href="https://www.rfc-editor.org/rfc/rfc9084#section-2.1" class="relref">Section 2.1</a> of [<a href="#RFC9084" class="xref">RFC9084</a>]</span>.<a href="#section-2.3.4-1" class="pilcrow">¶</a></p>
2679 <p id="section-2.3.4-2">The Source OSPF Router-ID TLV has the following format:<a href="#section-2.3.4-2" class="pilcrow">¶</a></p>
2680 <span id="name-source-ospf-router-id-tlv-f"></span><div id="SRCOSPFRIDTLVFIG">
2681 <figure id="figure-13">
2682 <div class="artwork art-text alignLeft" id="section-2.3.4-3.1">
2683 <pre>
2684 0 1 2 3
2685 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
2686 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2687 | Type | Length |
2688 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2689 | 4-octet OSPF Router-ID //
2690 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2691 </pre>
2692 </div>
2693 <figcaption><a href="#figure-13" class="selfRef">Figure 13</a>:
2694 <a href="#name-source-ospf-router-id-tlv-f" class="selfRef">Source OSPF Router-ID TLV Format</a>
2695 </figcaption></figure>
2696 </div>
2697 <p id="section-2.3.4-4">Where:<a href="#section-2.3.4-4" class="pilcrow">¶</a></p>
2698 <span class="break"></span><dl class="dlParallel" id="section-2.3.4-5">
2699 <dt id="section-2.3.4-5.1">Type:</dt>
2700 <dd style="margin-left: 1.5em" id="section-2.3.4-5.2">1174<a href="#section-2.3.4-5.2" class="pilcrow">¶</a>
2701 </dd>
2702 <dd class="break"></dd>
2703 <dt id="section-2.3.4-5.3">Length:</dt>
2704 <dd style="margin-left: 1.5em" id="section-2.3.4-5.4">4 octets<a href="#section-2.3.4-5.4" class="pilcrow">¶</a>
2705 </dd>
2706 <dd class="break"></dd>
2707 <dt id="section-2.3.4-5.5">OSPF Router-ID:</dt>
2708 <dd style="margin-left: 1.5em" id="section-2.3.4-5.6">the OSPF Router-ID of the node originating
2709 the prefix.<a href="#section-2.3.4-5.6" class="pilcrow">¶</a>
2710 </dd>
2711 <dd class="break"></dd>
2712 </dl>
2713 </section>
2714 </div>
2715 <div id="RANGETLV">
2716 <section id="section-2.3.5">
2717 <h4 id="name-range-tlv">
2718 <a href="#section-2.3.5" class="section-number selfRef">2.3.5. </a><a href="#name-range-tlv" class="section-name selfRef">Range TLV</a>
2719 </h4>
2720 <p id="section-2.3.5-1">The Range TLV is used in order to advertise a range of
2721 prefix-to-SID mappings as part of the
2722 SRMS functionality <span>[<a href="#RFC8661" class="xref">RFC8661</a>]</span>, as defined
2723 in the respective underlying IGP SR extensions: <span><a href="https://www.rfc-editor.org/rfc/rfc8665#section-4" class="relref">Section 4</a> of [<a href="#RFC8665" class="xref">RFC8665</a>]</span>,
2724 <span><a href="https://www.rfc-editor.org/rfc/rfc8666#section-5" class="relref">Section 5</a> of [<a href="#RFC8666" class="xref">RFC8666</a>]</span>,
2725 and <span><a href="https://www.rfc-editor.org/rfc/rfc8667#section-2.4" class="relref">Section 2.4</a> of [<a href="#RFC8667" class="xref">RFC8667</a>]</span>.
2726 The information advertised in the Range TLV is derived from the
2727 SID/Label Binding TLV in the case of IS-IS and the OSPFv2/OSPFv3
2728 Extended Prefix Range TLV in the case of OSPFv2/OSPFv3.<a href="#section-2.3.5-1" class="pilcrow">¶</a></p>
2729 <p id="section-2.3.5-2">A Prefix NLRI, that has been advertised with a Range TLV, is
2730 considered a normal routing prefix (i.e., prefix reachability) only
2731 when there is also an IGP metric TLV (TLV 1095) associated it.
2732 Otherwise, it is considered only as the first prefix in the range
2733 for prefix-to-SID mapping advertisement.<a href="#section-2.3.5-2" class="pilcrow">¶</a></p>
2734 <p id="section-2.3.5-3">The format of the Range TLV is as follows:<a href="#section-2.3.5-3" class="pilcrow">¶</a></p>
2735 <span id="name-range-tlv-format"></span><div id="RANGETLVFIG">
2736 <figure id="figure-14">
2737 <div class="artwork art-text alignLeft" id="section-2.3.5-4.1">
2738 <pre> 0 1 2 3
2739 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
2740 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2741 | Type | Length |
2742 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2743 | Flags | Reserved | Range Size |
2744 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2745 | sub-TLVs //
2746 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2747 </pre>
2748 </div>
2749 <figcaption><a href="#figure-14" class="selfRef">Figure 14</a>:
2750 <a href="#name-range-tlv-format" class="selfRef">Range TLV Format</a>
2751 </figcaption></figure>
2752 </div>
2753 <p id="section-2.3.5-5">Where:<a href="#section-2.3.5-5" class="pilcrow">¶</a></p>
2754 <span class="break"></span><dl class="dlParallel" id="section-2.3.5-6">
2755 <dt id="section-2.3.5-6.1">Type:</dt>
2756 <dd style="margin-left: 1.5em" id="section-2.3.5-6.2"> 1159<a href="#section-2.3.5-6.2" class="pilcrow">¶</a>
2757 </dd>
2758 <dd class="break"></dd>
2759 <dt id="section-2.3.5-6.3">Length:</dt>
2760 <dd style="margin-left: 1.5em" id="section-2.3.5-6.4"> Variable. 11 or 12 octets depending on the label or index
2761 encoding of the SID.<a href="#section-2.3.5-6.4" class="pilcrow">¶</a>
2762 </dd>
2763 <dd class="break"></dd>
2764 <dt id="section-2.3.5-6.5">Flags:</dt>
2765 <dd style="margin-left: 1.5em" id="section-2.3.5-6.6">
2766 <p id="section-2.3.5-6.6.1"> 1-octet value that should be set as:<a href="#section-2.3.5-6.6.1" class="pilcrow">¶</a></p>
2767 <ul class="normal">
2768 <li class="normal" id="section-2.3.5-6.6.2.1">IS-IS SID/Label Binding TLV flags as defined in
2769 <span><a href="https://www.rfc-editor.org/rfc/rfc8667#section-2.4.1" class="relref">Section 2.4.1</a> of [<a href="#RFC8667" class="xref">RFC8667</a>]</span>.<a href="#section-2.3.5-6.6.2.1" class="pilcrow">¶</a>
2770 </li>
2771 <li class="normal" id="section-2.3.5-6.6.2.2">OSPFv2 OSPF Extended Prefix Range TLV flags as defined
2772 in <span><a href="https://www.rfc-editor.org/rfc/rfc8665#section-4" class="relref">Section 4</a> of [<a href="#RFC8665" class="xref">RFC8665</a>]</span>.<a href="#section-2.3.5-6.6.2.2" class="pilcrow">¶</a>
2773 </li>
2774 <li class="normal" id="section-2.3.5-6.6.2.3">OSPFv3 Extended Prefix Range TLV flags as defined in
2775 <span><a href="https://www.rfc-editor.org/rfc/rfc8666#section-5" class="relref">Section 5</a> of [<a href="#RFC8666" class="xref">RFC8666</a>]</span>.<a href="#section-2.3.5-6.6.2.3" class="pilcrow">¶</a>
2776 </li>
2777 </ul>
2778 </dd>
2779 <dd class="break"></dd>
2780 <dt id="section-2.3.5-6.7">Reserved:</dt>
2781 <dd style="margin-left: 1.5em" id="section-2.3.5-6.8"> 1 octet that <span class="bcp14">MUST</span> be set to 0 and ignored on
2782 receipt.<a href="#section-2.3.5-6.8" class="pilcrow">¶</a>
2783 </dd>
2784 <dd class="break"></dd>
2785 <dt id="section-2.3.5-6.9">Range Size:</dt>
2786 <dd style="margin-left: 1.5em" id="section-2.3.5-6.10"> 2 octets that carry the number of prefixes that
2787 are covered by the advertisement.<a href="#section-2.3.5-6.10" class="pilcrow">¶</a>
2788 </dd>
2789 <dd class="break"></dd>
2790 </dl>
2791 <p id="section-2.3.5-7">The Flags field of this TLV is interpreted according to the
2792 respective underlying IS-IS, OSPFv2, or OSPFv3 protocol. The
2793 Protocol-ID of the BGP-LS Prefix NLRI is used to determine the
2794 underlying protocol specification for parsing this field.<a href="#section-2.3.5-7" class="pilcrow">¶</a></p>
2795 <p id="section-2.3.5-8">The prefix-to-SID mappings are advertised using sub-TLVs as
2796 below:<a href="#section-2.3.5-8" class="pilcrow">¶</a></p>
2797 <span class="break"></span><dl class="dlNewline" id="section-2.3.5-9">
2798 <dt id="section-2.3.5-9.1">IS-IS:</dt>
2799 <dd style="margin-left: 1.5em" id="section-2.3.5-9.2">
2800 <span class="break"></span><dl class="dlNewline dlCompact" id="section-2.3.5-9.2.1">
2801 <dt id="section-2.3.5-9.2.1.1">SID/Label Range TLV</dt>
2802 <dd style="margin-left: 1.5em" id="section-2.3.5-9.2.1.2">Prefix-SID Sub-TLV<a href="#section-2.3.5-9.2.1.2" class="pilcrow">¶</a>
2803 </dd>
2804 <dd class="break"></dd>
2805 </dl>
2806 </dd>
2807 <dd class="break"></dd>
2808 <dt id="section-2.3.5-9.3">OSPFv2/OSPFv3:</dt>
2809 <dd style="margin-left: 1.5em" id="section-2.3.5-9.4">
2810 <span class="break"></span><dl class="dlNewline dlCompact" id="section-2.3.5-9.4.1">
2811 <dt id="section-2.3.5-9.4.1.1">
2812 OSPFv2/OSPFv3 Extended Prefix Range TLV
2813 </dt>
2814 <dd style="margin-left: 1.5em" id="section-2.3.5-9.4.1.2">
2815 Prefix-SID Sub-TLV<a href="#section-2.3.5-9.4.1.2" class="pilcrow">¶</a>
2816 </dd>
2817 <dd class="break"></dd>
2818 </dl>
2819 </dd>
2820 <dd class="break"></dd>
2821 <dt id="section-2.3.5-9.5">BGP-LS:</dt>
2822 <dd style="margin-left: 1.5em" id="section-2.3.5-9.6">
2823 <span class="break"></span><dl class="dlNewline dlCompact" id="section-2.3.5-9.6.1">
2824 <dt id="section-2.3.5-9.6.1.1">Range TLV</dt>
2825 <dd style="margin-left: 1.5em" id="section-2.3.5-9.6.1.2">Prefix-SID TLV (used as a sub-TLV in this context)<a href="#section-2.3.5-9.6.1.2" class="pilcrow">¶</a>
2826 </dd>
2827 <dd class="break"></dd>
2828 </dl>
2829 </dd>
2830 <dd class="break"></dd>
2831 </dl>
2832 <p id="section-2.3.5-10">The prefix-to-SID mapping information for the BGP-LS Prefix-SID
2833 TLV (used as a sub-TLV in this context) is encoded as described in
2834 <a href="#PREFIXSIDTLV" class="xref">Section 2.3.1</a>.<a href="#section-2.3.5-10" class="pilcrow">¶</a></p>
2835 </section>
2836 </div>
2837 </section>
2838 </div>
2839 <div id="ISISTLV">
2840 <section id="section-2.4">
2841 <h3 id="name-equivalent-is-is-segment-ro">
2842 <a href="#section-2.4" class="section-number selfRef">2.4. </a><a href="#name-equivalent-is-is-segment-ro" class="section-name selfRef">Equivalent IS-IS Segment Routing TLVs/Sub-TLVs</a>
2843 </h3>
2844 <p id="section-2.4-1">This section illustrates the IS-IS Segment Routing Extensions TLVs
2845 and sub-TLVs mapped to the ones defined in this document.<a href="#section-2.4-1" class="pilcrow">¶</a></p>
2846 <p id="section-2.4-2">For each BGP-LS TLV, the following table illustrates its
2847 equivalence in IS-IS.<a href="#section-2.4-2" class="pilcrow">¶</a></p>
2848 <span id="name-is-is-segment-routing-exten"></span><div id="ISISTLVTAB">
2849 <table class="center" id="table-5">
2850 <caption>
2851 <a href="#table-5" class="selfRef">Table 5</a>:
2852 <a href="#name-is-is-segment-routing-exten" class="selfRef">IS-IS Segment Routing Extensions TLVs/Sub-TLVs</a>
2853 </caption>
2854 <thead>
2855 <tr>
2856 <th class="text-left" rowspan="1" colspan="1">Description</th>
2857 <th class="text-left" rowspan="1" colspan="1">IS-IS TLV/sub-TLV</th>
2858 <th class="text-left" rowspan="1" colspan="1">Reference</th>
2859 </tr>
2860 </thead>
2861 <tbody>
2862 <tr>
2863 <td class="text-left" rowspan="1" colspan="1">SR Capabilities</td>
2864 <td class="text-left" rowspan="1" colspan="1">SR-Capabilities Sub-TLV (2)</td>
2865 <td class="text-left" rowspan="1" colspan="1">
2866 <span>[<a href="#RFC8667" class="xref">RFC8667</a>]</span>
2867 </td>
2868 </tr>
2869 <tr>
2870 <td class="text-left" rowspan="1" colspan="1">SR Algorithm</td>
2871 <td class="text-left" rowspan="1" colspan="1">SR-Algorithm Sub-TLV (19)</td>
2872 <td class="text-left" rowspan="1" colspan="1">
2873 <span>[<a href="#RFC8667" class="xref">RFC8667</a>]</span>
2874 </td>
2875 </tr>
2876 <tr>
2877 <td class="text-left" rowspan="1" colspan="1">SR Local Block</td>
2878 <td class="text-left" rowspan="1" colspan="1">SR Local Block Sub-TLV (22)</td>
2879 <td class="text-left" rowspan="1" colspan="1">
2880 <span>[<a href="#RFC8667" class="xref">RFC8667</a>]</span>
2881 </td>
2882 </tr>
2883 <tr>
2884 <td class="text-left" rowspan="1" colspan="1">SRMS Preference</td>
2885 <td class="text-left" rowspan="1" colspan="1">SRMS Preference Sub-TLV (19)</td>
2886 <td class="text-left" rowspan="1" colspan="1">
2887 <span>[<a href="#RFC8667" class="xref">RFC8667</a>]</span>
2888 </td>
2889 </tr>
2890 <tr>
2891 <td class="text-left" rowspan="1" colspan="1">Adjacency SID</td>
2892 <td class="text-left" rowspan="1" colspan="1">Adj-SID Sub-TLV (31)</td>
2893 <td class="text-left" rowspan="1" colspan="1">
2894 <span>[<a href="#RFC8667" class="xref">RFC8667</a>]</span>
2895 </td>
2896 </tr>
2897 <tr>
2898 <td class="text-left" rowspan="1" colspan="1">LAN Adjacency SID</td>
2899 <td class="text-left" rowspan="1" colspan="1">LAN-Adj-SID Sub-TLV (32)</td>
2900 <td class="text-left" rowspan="1" colspan="1">
2901 <span>[<a href="#RFC8667" class="xref">RFC8667</a>]</span>
2902 </td>
2903 </tr>
2904 <tr>
2905 <td class="text-left" rowspan="1" colspan="1">Prefix-SID</td>
2906 <td class="text-left" rowspan="1" colspan="1">Prefix-SID Sub-TLV (3)</td>
2907 <td class="text-left" rowspan="1" colspan="1">
2908 <span>[<a href="#RFC8667" class="xref">RFC8667</a>]</span>
2909 </td>
2910 </tr>
2911 <tr>
2912 <td class="text-left" rowspan="1" colspan="1">Range</td>
2913 <td class="text-left" rowspan="1" colspan="1">SID/Label Binding TLV (149)</td>
2914 <td class="text-left" rowspan="1" colspan="1">
2915 <span>[<a href="#RFC8667" class="xref">RFC8667</a>]</span>
2916 </td>
2917 </tr>
2918 <tr>
2919 <td class="text-left" rowspan="1" colspan="1">SID/Label</td>
2920 <td class="text-left" rowspan="1" colspan="1">SID/Label Sub-TLV (1)</td>
2921 <td class="text-left" rowspan="1" colspan="1">
2922 <span>[<a href="#RFC8667" class="xref">RFC8667</a>]</span>
2923 </td>
2924 </tr>
2925 <tr>
2926 <td class="text-left" rowspan="1" colspan="1">Prefix Attribute Flags</td>
2927 <td class="text-left" rowspan="1" colspan="1">Prefix Attribute Flags Sub-TLV (4)</td>
2928 <td class="text-left" rowspan="1" colspan="1">
2929 <span>[<a href="#RFC7794" class="xref">RFC7794</a>]</span>
2930 </td>
2931 </tr>
2932 <tr>
2933 <td class="text-left" rowspan="1" colspan="1">Source Router Identifier</td>
2934 <td class="text-left" rowspan="1" colspan="1">IPv4/IPv6 Source Router ID Sub-TLV (11/12)</td>
2935 <td class="text-left" rowspan="1" colspan="1">
2936 <span>[<a href="#RFC7794" class="xref">RFC7794</a>]</span>
2937 </td>
2938 </tr>
2939 <tr>
2940 <td class="text-left" rowspan="1" colspan="1">L2 Bundle Member Attributes</td>
2941 <td class="text-left" rowspan="1" colspan="1">L2 Bundle Member Attributes TLV (25)</td>
2942 <td class="text-left" rowspan="1" colspan="1">
2943 <span>[<a href="#RFC8668" class="xref">RFC8668</a>]</span>
2944 </td>
2945 </tr>
2946 </tbody>
2947 </table>
2948 </div>
2949 </section>
2950 </div>
2951 <div id="OSPFTLV">
2952 <section id="section-2.5">
2953 <h3 id="name-equivalent-ospfv2-ospfv3-se">
2954 <a href="#section-2.5" class="section-number selfRef">2.5. </a><a href="#name-equivalent-ospfv2-ospfv3-se" class="section-name selfRef">Equivalent OSPFv2/OSPFv3 Segment Routing TLVs/Sub-TLVs</a>
2955 </h3>
2956 <p id="section-2.5-1">This section illustrates the OSPFv2 and OSPFv3 Segment Routing
2957 Extensions TLVs and sub-TLVs mapped to the ones defined in this
2958 document.<a href="#section-2.5-1" class="pilcrow">¶</a></p>
2959 <p id="section-2.5-2">For each BGP-LS TLV, the following tables illustrate its
2960 equivalence in OSPFv2 and OSPFv3.<a href="#section-2.5-2" class="pilcrow">¶</a></p>
2961 <span id="name-ospfv2-segment-routing-exte"></span><div id="OSPFTVLTAB">
2962 <table class="center" id="table-6">
2963 <caption>
2964 <a href="#table-6" class="selfRef">Table 6</a>:
2965 <a href="#name-ospfv2-segment-routing-exte" class="selfRef">OSPFv2 Segment Routing Extensions TLVs/Sub-TLVs</a>
2966 </caption>
2967 <thead>
2968 <tr>
2969 <th class="text-left" rowspan="1" colspan="1">Description</th>
2970 <th class="text-left" rowspan="1" colspan="1">OSPFv2 TLV/sub-TLV</th>
2971 <th class="text-left" rowspan="1" colspan="1">Reference</th>
2972 </tr>
2973 </thead>
2974 <tbody>
2975 <tr>
2976 <td class="text-left" rowspan="1" colspan="1">SR Capabilities</td>
2977 <td class="text-left" rowspan="1" colspan="1">SID/Label Range TLV (9)</td>
2978 <td class="text-left" rowspan="1" colspan="1">
2979 <span>[<a href="#RFC8665" class="xref">RFC8665</a>]</span>
2980 </td>
2981 </tr>
2982 <tr>
2983 <td class="text-left" rowspan="1" colspan="1">SR Algorithm</td>
2984 <td class="text-left" rowspan="1" colspan="1">SR-Algorithm TLV (8)</td>
2985 <td class="text-left" rowspan="1" colspan="1">
2986 <span>[<a href="#RFC8665" class="xref">RFC8665</a>]</span>
2987 </td>
2988 </tr>
2989 <tr>
2990 <td class="text-left" rowspan="1" colspan="1">SR Local Block</td>
2991 <td class="text-left" rowspan="1" colspan="1">SR Local Block TLV (14)</td>
2992 <td class="text-left" rowspan="1" colspan="1">
2993 <span>[<a href="#RFC8665" class="xref">RFC8665</a>]</span>
2994 </td>
2995 </tr>
2996 <tr>
2997 <td class="text-left" rowspan="1" colspan="1">SRMS Preference</td>
2998 <td class="text-left" rowspan="1" colspan="1">SRMS Preference TLV (15)</td>
2999 <td class="text-left" rowspan="1" colspan="1">
3000 <span>[<a href="#RFC8665" class="xref">RFC8665</a>]</span>
3001 </td>
3002 </tr>
3003 <tr>
3004 <td class="text-left" rowspan="1" colspan="1">Adjacency SID</td>
3005 <td class="text-left" rowspan="1" colspan="1">Adj-SID Sub-TLV (2)</td>
3006 <td class="text-left" rowspan="1" colspan="1">
3007 <span>[<a href="#RFC8665" class="xref">RFC8665</a>]</span>
3008 </td>
3009 </tr>
3010 <tr>
3011 <td class="text-left" rowspan="1" colspan="1">LAN Adjacency SID</td>
3012 <td class="text-left" rowspan="1" colspan="1">LAN Adj-SID Sub-TLV (3)</td>
3013 <td class="text-left" rowspan="1" colspan="1">
3014 <span>[<a href="#RFC8665" class="xref">RFC8665</a>]</span>
3015 </td>
3016 </tr>
3017 <tr>
3018 <td class="text-left" rowspan="1" colspan="1">Prefix-SID</td>
3019 <td class="text-left" rowspan="1" colspan="1">Prefix-SID Sub-TLV (2)</td>
3020 <td class="text-left" rowspan="1" colspan="1">
3021 <span>[<a href="#RFC8665" class="xref">RFC8665</a>]</span>
3022 </td>
3023 </tr>
3024 <tr>
3025 <td class="text-left" rowspan="1" colspan="1">Range</td>
3026 <td class="text-left" rowspan="1" colspan="1">OSPF Extended Prefix Range TLV (2)</td>
3027 <td class="text-left" rowspan="1" colspan="1">
3028 <span>[<a href="#RFC8665" class="xref">RFC8665</a>]</span>
3029 </td>
3030 </tr>
3031 <tr>
3032 <td class="text-left" rowspan="1" colspan="1">SID/Label</td>
3033 <td class="text-left" rowspan="1" colspan="1">SID/Label Sub-TLV (1)</td>
3034 <td class="text-left" rowspan="1" colspan="1">
3035 <span>[<a href="#RFC8665" class="xref">RFC8665</a>]</span>
3036 </td>
3037 </tr>
3038 <tr>
3039 <td class="text-left" rowspan="1" colspan="1">Prefix Attribute Flags</td>
3040 <td class="text-left" rowspan="1" colspan="1">Flags of OSPFv2 Extended Prefix TLV (1)</td>
3041 <td class="text-left" rowspan="1" colspan="1">
3042 <span>[<a href="#RFC7684" class="xref">RFC7684</a>]</span>
3043 </td>
3044 </tr>
3045 <tr>
3046 <td class="text-left" rowspan="1" colspan="1">Source Router Identifier</td>
3047 <td class="text-left" rowspan="1" colspan="1">Prefix Source Router Address Sub-TLV (5)</td>
3048 <td class="text-left" rowspan="1" colspan="1">
3049 <span>[<a href="#RFC9084" class="xref">RFC9084</a>]</span>
3050 </td>
3051 </tr>
3052 <tr>
3053 <td class="text-left" rowspan="1" colspan="1">Source OSPF Router-ID</td>
3054 <td class="text-left" rowspan="1" colspan="1">Prefix Source OSPF Router-ID Sub-TLV (4)</td>
3055 <td class="text-left" rowspan="1" colspan="1">
3056 <span>[<a href="#RFC9084" class="xref">RFC9084</a>]</span>
3057 </td>
3058 </tr>
3059 </tbody>
3060 </table>
3061 </div>
3062 <span id="name-ospfv3-segment-routing-exte"></span><div id="OSPFV3TVLTAB">
3063 <table class="center" id="table-7">
3064 <caption>
3065 <a href="#table-7" class="selfRef">Table 7</a>:
3066 <a href="#name-ospfv3-segment-routing-exte" class="selfRef">OSPFv3 Segment Routing Extensions TLVs/Sub-TLVs</a>
3067 </caption>
3068 <thead>
3069 <tr>
3070 <th class="text-left" rowspan="1" colspan="1">Description</th>
3071 <th class="text-left" rowspan="1" colspan="1">OSPFv3 TLV/sub-TLV</th>
3072 <th class="text-left" rowspan="1" colspan="1">Reference</th>
3073 </tr>
3074 </thead>
3075 <tbody>
3076 <tr>
3077 <td class="text-left" rowspan="1" colspan="1">SR Capabilities</td>
3078 <td class="text-left" rowspan="1" colspan="1">SID/Label Range TLV (9)</td>
3079 <td class="text-left" rowspan="1" colspan="1">
3080 <span>[<a href="#RFC8665" class="xref">RFC8665</a>]</span>
3081 </td>
3082 </tr>
3083 <tr>
3084 <td class="text-left" rowspan="1" colspan="1">SR Algorithm</td>
3085 <td class="text-left" rowspan="1" colspan="1">SR-Algorithm TLV (8)</td>
3086 <td class="text-left" rowspan="1" colspan="1">
3087 <span>[<a href="#RFC8665" class="xref">RFC8665</a>]</span>
3088 </td>
3089 </tr>
3090 <tr>
3091 <td class="text-left" rowspan="1" colspan="1">SR Local Block</td>
3092 <td class="text-left" rowspan="1" colspan="1">SR Local Block TLV (14)</td>
3093 <td class="text-left" rowspan="1" colspan="1">
3094 <span>[<a href="#RFC8665" class="xref">RFC8665</a>]</span>
3095 </td>
3096 </tr>
3097 <tr>
3098 <td class="text-left" rowspan="1" colspan="1">SRMS Preference</td>
3099 <td class="text-left" rowspan="1" colspan="1">SRMS Preference TLV (15)</td>
3100 <td class="text-left" rowspan="1" colspan="1">
3101 <span>[<a href="#RFC8665" class="xref">RFC8665</a>]</span>
3102 </td>
3103 </tr>
3104 <tr>
3105 <td class="text-left" rowspan="1" colspan="1">Adjacency SID</td>
3106 <td class="text-left" rowspan="1" colspan="1">Adj-SID Sub-TLV (5)</td>
3107 <td class="text-left" rowspan="1" colspan="1">
3108 <span>[<a href="#RFC8666" class="xref">RFC8666</a>]</span>
3109 </td>
3110 </tr>
3111 <tr>
3112 <td class="text-left" rowspan="1" colspan="1">LAN Adjacency SID</td>
3113 <td class="text-left" rowspan="1" colspan="1">LAN Adj-SID Sub-TLV (6)</td>
3114 <td class="text-left" rowspan="1" colspan="1">
3115 <span>[<a href="#RFC8666" class="xref">RFC8666</a>]</span>
3116 </td>
3117 </tr>
3118 <tr>
3119 <td class="text-left" rowspan="1" colspan="1">Prefix-SID</td>
3120 <td class="text-left" rowspan="1" colspan="1">Prefix-SID Sub-TLV (4)</td>
3121 <td class="text-left" rowspan="1" colspan="1">
3122 <span>[<a href="#RFC8666" class="xref">RFC8666</a>]</span>
3123 </td>
3124 </tr>
3125 <tr>
3126 <td class="text-left" rowspan="1" colspan="1">Range</td>
3127 <td class="text-left" rowspan="1" colspan="1">OSPFv3 Extended Prefix Range TLV (9)</td>
3128 <td class="text-left" rowspan="1" colspan="1">
3129 <span>[<a href="#RFC8666" class="xref">RFC8666</a>]</span>
3130 </td>
3131 </tr>
3132 <tr>
3133 <td class="text-left" rowspan="1" colspan="1">SID/Label</td>
3134 <td class="text-left" rowspan="1" colspan="1">SID/Label Sub-TLV (7)</td>
3135 <td class="text-left" rowspan="1" colspan="1">
3136 <span>[<a href="#RFC8666" class="xref">RFC8666</a>]</span>
3137 </td>
3138 </tr>
3139 <tr>
3140 <td class="text-left" rowspan="1" colspan="1">Prefix Attribute Flags</td>
3141 <td class="text-left" rowspan="1" colspan="1">Prefix Option Fields of Prefix TLV types 3,5,6</td>
3142 <td class="text-left" rowspan="1" colspan="1">
3143 <span>[<a href="#RFC8362" class="xref">RFC8362</a>]</span>
3144 </td>
3145 </tr>
3146 <tr>
3147 <td class="text-left" rowspan="1" colspan="1">Source OSPF Router Identifier</td>
3148 <td class="text-left" rowspan="1" colspan="1">Prefix Source Router Address Sub-TLV (28)</td>
3149 <td class="text-left" rowspan="1" colspan="1">
3150 <span>[<a href="#RFC9084" class="xref">RFC9084</a>]</span>
3151 </td>
3152 </tr>
3153 <tr>
3154 <td class="text-left" rowspan="1" colspan="1">Source OSPF Router-ID</td>
3155 <td class="text-left" rowspan="1" colspan="1">Prefix Source OSPF Router-ID Sub-TLV (27)</td>
3156 <td class="text-left" rowspan="1" colspan="1">
3157 <span>[<a href="#RFC9084" class="xref">RFC9084</a>]</span>
3158 </td>
3159 </tr>
3160 </tbody>
3161 </table>
3162 </div>
3163 </section>
3164 </div>
3165 </section>
3166 <div id="IANA">
3167 <section id="section-3">
3168 <h2 id="name-iana-considerations">
3169 <a href="#section-3" class="section-number selfRef">3. </a><a href="#name-iana-considerations" class="section-name selfRef">IANA Considerations</a>
3170 </h2>
3171 <p id="section-3-1">IANA has registered the following code points in the "BGP-LS Node
3172 Descriptor, Link Descriptor, Prefix Descriptor, and Attribute TLVs"
3173 registry under the "Border Gateway Protocol - Link State (BGP-LS)
3174 Parameter" registry based on <a href="#BGPLSCODEPOINTS" class="xref">Table 8</a>. The column "IS-IS
3175 TLV/Sub-TLV" defined in the registry does not require any value and
3176 should be left empty.<a href="#section-3-1" class="pilcrow">¶</a></p>
3177 <div id="TLVSUMMARY">
3178 <section id="section-3.1">
3179 <h3 id="name-tlv-sub-tlv-code-points-sum">
3180 <a href="#section-3.1" class="section-number selfRef">3.1. </a><a href="#name-tlv-sub-tlv-code-points-sum" class="section-name selfRef">TLV/Sub-TLV Code Points Summary</a>
3181 </h3>
3182 <p id="section-3.1-1">This section contains the global table of all TLVs/sub-TLVs defined
3183 in this document.<a href="#section-3.1-1" class="pilcrow">¶</a></p>
3184 <span id="name-summary-of-tlv-sub-tlv-code"></span><div id="BGPLSCODEPOINTS">
3185 <table class="center" id="table-8">
3186 <caption>
3187 <a href="#table-8" class="selfRef">Table 8</a>:
3188 <a href="#name-summary-of-tlv-sub-tlv-code" class="selfRef">Summary of TLV/Sub-TLV Code Points</a>
3189 </caption>
3190 <thead>
3191 <tr>
3192 <th class="text-center" rowspan="1" colspan="1">TLV Code Point</th>
3193 <th class="text-left" rowspan="1" colspan="1">Description</th>
3194 <th class="text-left" rowspan="1" colspan="1">Reference</th>
3195 </tr>
3196 </thead>
3197 <tbody>
3198 <tr>
3199 <td class="text-center" rowspan="1" colspan="1">1034</td>
3200 <td class="text-left" rowspan="1" colspan="1">SR Capabilities</td>
3201 <td class="text-right" rowspan="1" colspan="1">
3202 <a href="#SRCAPTLV" class="xref">Section 2.1.2</a>
3203 </td>
3204 </tr>
3205 <tr>
3206 <td class="text-center" rowspan="1" colspan="1">1035</td>
3207 <td class="text-left" rowspan="1" colspan="1">SR Algorithm</td>
3208 <td class="text-right" rowspan="1" colspan="1">
3209 <a href="#SRALGOTLV" class="xref">Section 2.1.3</a>
3210 </td>
3211 </tr>
3212 <tr>
3213 <td class="text-center" rowspan="1" colspan="1">1036</td>
3214 <td class="text-left" rowspan="1" colspan="1">SR Local Block</td>
3215 <td class="text-right" rowspan="1" colspan="1">
3216 <a href="#SRLB" class="xref">Section 2.1.4</a>
3217 </td>
3218 </tr>
3219 <tr>
3220 <td class="text-center" rowspan="1" colspan="1">1037</td>
3221 <td class="text-left" rowspan="1" colspan="1">SRMS Preference</td>
3222 <td class="text-right" rowspan="1" colspan="1">
3223 <a href="#SRMSPREF" class="xref">Section 2.1.5</a>
3224 </td>
3225 </tr>
3226 <tr>
3227 <td class="text-center" rowspan="1" colspan="1">1099</td>
3228 <td class="text-left" rowspan="1" colspan="1">Adjacency SID</td>
3229 <td class="text-right" rowspan="1" colspan="1">
3230 <a href="#ADJSIDTLV" class="xref">Section 2.2.1</a>
3231 </td>
3232 </tr>
3233 <tr>
3234 <td class="text-center" rowspan="1" colspan="1">1100</td>
3235 <td class="text-left" rowspan="1" colspan="1">LAN Adjacency SID</td>
3236 <td class="text-right" rowspan="1" colspan="1">
3237 <a href="#LANADJSIDTLV" class="xref">Section 2.2.2</a>
3238 </td>
3239 </tr>
3240 <tr>
3241 <td class="text-center" rowspan="1" colspan="1">1158</td>
3242 <td class="text-left" rowspan="1" colspan="1">Prefix-SID</td>
3243 <td class="text-right" rowspan="1" colspan="1">
3244 <a href="#PREFIXSIDTLV" class="xref">Section 2.3.1</a>
3245 </td>
3246 </tr>
3247 <tr>
3248 <td class="text-center" rowspan="1" colspan="1">1159</td>
3249 <td class="text-left" rowspan="1" colspan="1">Range</td>
3250 <td class="text-right" rowspan="1" colspan="1">
3251 <a href="#RANGETLV" class="xref">Section 2.3.5</a>
3252 </td>
3253 </tr>
3254 <tr>
3255 <td class="text-center" rowspan="1" colspan="1">1161</td>
3256 <td class="text-left" rowspan="1" colspan="1">SID/Label</td>
3257 <td class="text-right" rowspan="1" colspan="1">
3258 <a href="#SIDLABELTLV" class="xref">Section 2.1.1</a>
3259 </td>
3260 </tr>
3261 <tr>
3262 <td class="text-center" rowspan="1" colspan="1">1170</td>
3263 <td class="text-left" rowspan="1" colspan="1">Prefix Attribute Flags</td>
3264 <td class="text-right" rowspan="1" colspan="1">
3265 <a href="#PREFIXATTRFLAGTLV" class="xref">Section 2.3.2</a>
3266 </td>
3267 </tr>
3268 <tr>
3269 <td class="text-center" rowspan="1" colspan="1">1171</td>
3270 <td class="text-left" rowspan="1" colspan="1">Source Router Identifier</td>
3271 <td class="text-right" rowspan="1" colspan="1">
3272 <a href="#SOURCEIDTLV" class="xref">Section 2.3.3</a>
3273 </td>
3274 </tr>
3275 <tr>
3276 <td class="text-center" rowspan="1" colspan="1">1172</td>
3277 <td class="text-left" rowspan="1" colspan="1">L2 Bundle Member Attributes</td>
3278 <td class="text-right" rowspan="1" colspan="1">
3279 <a href="#L2BUNDLETLV" class="xref">Section 2.2.3</a>
3280 </td>
3281 </tr>
3282 <tr>
3283 <td class="text-center" rowspan="1" colspan="1">1174</td>
3284 <td class="text-left" rowspan="1" colspan="1">Source OSPF Router-ID</td>
3285 <td class="text-right" rowspan="1" colspan="1">
3286 <a href="#SOURCEOSPFRIDTLV" class="xref">Section 2.3.4</a>
3287 </td>
3288 </tr>
3289 </tbody>
3290 </table>
3291 </div>
3292 </section>
3293 </div>
3294 </section>
3295 </div>
3296 <div id="Manageability">
3297 <section id="section-4">
3298 <h2 id="name-manageability-consideration">
3299 <a href="#section-4" class="section-number selfRef">4. </a><a href="#name-manageability-consideration" class="section-name selfRef">Manageability Considerations</a>
3300 </h2>
3301 <p id="section-4-1">This section is structured as recommended in <span>[<a href="#RFC5706" class="xref">RFC5706</a>]</span>.<a href="#section-4-1" class="pilcrow">¶</a></p>
3302 <p id="section-4-2">The new protocol extensions introduced in this document augment the
3303 existing IGP topology information that is distributed via <span>[<a href="#RFC7752" class="xref">RFC7752</a>]</span>. Procedures and protocol extensions defined in this
3304 document do not affect the BGP protocol operations and management other
3305 than as discussed in the Manageability Considerations section of <span>[<a href="#RFC7752" class="xref">RFC7752</a>]</span>. Specifically, the malformed attribute tests for
3306 syntactic checks in the Fault Management section of <span>[<a href="#RFC7752" class="xref">RFC7752</a>]</span> now encompass the new BGP-LS Attribute TLVs defined
3307 in this document. The semantic or content checking for the TLVs
3308 specified in this document and their association with the BGP-LS NLRI
3309 types or their BGP-LS Attribute is left to the consumer of the BGP-LS
3310 information (e.g., an application or a controller) and not the BGP
3311 protocol.<a href="#section-4-2" class="pilcrow">¶</a></p>
3312 <p id="section-4-3">A consumer of the BGP-LS information retrieves this information over
3313 a BGP-LS session (refer to Sections <a href="https://www.rfc-editor.org/rfc/rfc7752#section-1" class="relref">1</a> and <a href="https://www.rfc-editor.org/rfc/rfc7752#section-2" class="relref">2</a> of <span>[<a href="#RFC7752" class="xref">RFC7752</a>]</span>).
3314 The handling of semantic or content errors by the consumer would be
3315 dictated by the nature of its application usage and hence is beyond the
3316 scope of this document.<a href="#section-4-3" class="pilcrow">¶</a></p>
3317 <p id="section-4-4">This document only introduces new Attribute TLVs, and any syntactic
3318 error in them would result in the BGP-LS Attribute being
3319 discarded with an error log.
3320 The SR information introduced in BGP-LS by
3321 this specification may be used by BGP-LS consumer applications like an
3322 SR Path Computation Engine (PCE) to learn the SR capabilities of the
3323 nodes in the topology and the mapping of SR segments to those nodes.
3324 This can enable the SR PCE to perform path computations based on SR for
3325 traffic engineering use cases and to steer traffic on paths different
3326 from the underlying IGP-based distributed best-path computation. Errors
3327 in the encoding or decoding of the SR information may result in the
3328 unavailability of such information to the SR PCE or incorrect
3329 information being made available to it. This may result in the SR PCE
3330 not being able to perform the desired SR-based optimization
3331 functionality or to perform it in an unexpected or inconsistent manner.
3332 The handling of such errors by applications like SR PCE may be
3333 implementation specific and out of scope of this document.<a href="#section-4-4" class="pilcrow">¶</a></p>
3334 <p id="section-4-5">The extensions, specified in this document, do not introduce any new
3335 configuration or monitoring aspects in BGP or BGP-LS other than as
3336 discussed in <span>[<a href="#RFC7752" class="xref">RFC7752</a>]</span>. The manageability aspects of the
3337 underlying SR features are covered by <span>[<a href="#RFC9020" class="xref">RFC9020</a>]</span>, <span>[<a href="#I-D.ietf-isis-sr-yang" class="xref">ISIS-SR-YANG</a>]</span>, and <span>[<a href="#I-D.ietf-ospf-sr-yang" class="xref">OSPF-SR-YANG</a>]</span>.<a href="#section-4-5" class="pilcrow">¶</a></p>
3338 </section>
3339 </div>
3340 <div id="Security">
3341 <section id="section-5">
3342 <h2 id="name-security-considerations">
3343 <a href="#section-5" class="section-number selfRef">5. </a><a href="#name-security-considerations" class="section-name selfRef">Security Considerations</a>
3344 </h2>
3345 <p id="section-5-1">The new protocol extensions introduced in this document augment the
3346 existing IGP topology information that is distributed via <span>[<a href="#RFC7752" class="xref">RFC7752</a>]</span>. The advertisement of the SR link attribute
3347 information defined in this document presents similar risk as associated
3348 with the existing set of link attribute information as described in
3349 <span>[<a href="#RFC7752" class="xref">RFC7752</a>]</span>. The Security Considerations section of <span>[<a href="#RFC7752" class="xref">RFC7752</a>]</span> also applies to these extensions. The procedures and
3350 new TLVs defined in this document, by themselves, do not affect the
3351 BGP-LS security model discussed in <span>[<a href="#RFC7752" class="xref">RFC7752</a>]</span>.<a href="#section-5-1" class="pilcrow">¶</a></p>
3352 <p id="section-5-2">The TLVs introduced in this document are used to propagate IGP-defined
3353 information (see <span>[<a href="#RFC8665" class="xref">RFC8665</a>]</span>, <span>[<a href="#RFC8666" class="xref">RFC8666</a>]</span>, and <span>[<a href="#RFC8667" class="xref">RFC8667</a>]</span>). These TLVs
3354 represent the SR information associated with the IGP node, link, and
3355 prefix. The IGP instances originating these TLVs are assumed to support
3356 all the required security and authentication mechanisms (as described in
3357 <span>[<a href="#RFC8665" class="xref">RFC8665</a>]</span>, <span>[<a href="#RFC8666" class="xref">RFC8666</a>]</span>, and <span>[<a href="#RFC8667" class="xref">RFC8667</a>]</span>) in order to
3358 prevent any security issue when propagating the TLVs into BGP-LS.<a href="#section-5-2" class="pilcrow">¶</a></p>
3359 <p id="section-5-3">BGP-LS SR extensions enable traffic engineering use cases within the
3360 SR domain. SR operates within a trusted domain <span>[<a href="#RFC8402" class="xref">RFC8402</a>]</span>, and its security considerations also apply to BGP-LS
3361 sessions when carrying SR information. The SR traffic engineering
3362 policies using the SIDs advertised via BGP-LS are expected to be used
3363 entirely within this trusted SR domain (e.g., between multiple ASes/domains
3364 within a single provider network). Therefore, precaution is necessary to
3365 ensure that the link-state information (including SR information)
3366 advertised via BGP-LS sessions is limited to consumers in a secure
3367 manner within this trusted SR domain. BGP peering sessions for
3368 address families other than link state may be set up to routers outside
3369 the SR domain. The isolation of BGP-LS peering sessions is recommended
3370 to ensure that BGP-LS topology information (including the newly added SR
3371 information) is not advertised to an external BGP peering session
3372 outside the SR domain.<a href="#section-5-3" class="pilcrow">¶</a></p>
3373 </section>
3374 </div>
3375 <section id="section-6">
3376 <h2 id="name-references">
3377 <a href="#section-6" class="section-number selfRef">6. </a><a href="#name-references" class="section-name selfRef">References</a>
3378 </h2>
3379 <section id="section-6.1">
3380 <h3 id="name-normative-references">
3381 <a href="#section-6.1" class="section-number selfRef">6.1. </a><a href="#name-normative-references" class="section-name selfRef">Normative References</a>
3382 </h3>
3383 <dl class="references">
3384 <dt id="RFC2119">[RFC2119]</dt>
3385 <dd>
3386 <span class="refAuthor">Bradner, S.</span>, <span class="refTitle">"Key words for use in RFCs to Indicate Requirement Levels"</span>, <span class="seriesInfo">BCP 14</span>, <span class="seriesInfo">RFC 2119</span>, <span class="seriesInfo">DOI 10.17487/RFC2119</span>, <time datetime="1997-03" class="refDate">March 1997</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc2119">https://www.rfc-editor.org/info/rfc2119</a>&gt;</span>. </dd>
3387 <dd class="break"></dd>
3388 <dt id="RFC4202">[RFC4202]</dt>
3389 <dd>
3390 <span class="refAuthor">Kompella, K., Ed.</span> and <span class="refAuthor">Y. Rekhter, Ed.</span>, <span class="refTitle">"Routing Extensions in Support of Generalized Multi-Protocol Label Switching (GMPLS)"</span>, <span class="seriesInfo">RFC 4202</span>, <span class="seriesInfo">DOI 10.17487/RFC4202</span>, <time datetime="2005-10" class="refDate">October 2005</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc4202">https://www.rfc-editor.org/info/rfc4202</a>&gt;</span>. </dd>
3391 <dd class="break"></dd>
3392 <dt id="RFC5120">[RFC5120]</dt>
3393 <dd>
3394 <span class="refAuthor">Przygienda, T.</span>, <span class="refAuthor">Shen, N.</span>, and <span class="refAuthor">N. Sheth</span>, <span class="refTitle">"M-ISIS: Multi Topology (MT) Routing in Intermediate System to Intermediate Systems (IS-ISs)"</span>, <span class="seriesInfo">RFC 5120</span>, <span class="seriesInfo">DOI 10.17487/RFC5120</span>, <time datetime="2008-02" class="refDate">February 2008</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc5120">https://www.rfc-editor.org/info/rfc5120</a>&gt;</span>. </dd>
3395 <dd class="break"></dd>
3396 <dt id="RFC5308">[RFC5308]</dt>
3397 <dd>
3398 <span class="refAuthor">Hopps, C.</span>, <span class="refTitle">"Routing IPv6 with IS-IS"</span>, <span class="seriesInfo">RFC 5308</span>, <span class="seriesInfo">DOI 10.17487/RFC5308</span>, <time datetime="2008-10" class="refDate">October 2008</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc5308">https://www.rfc-editor.org/info/rfc5308</a>&gt;</span>. </dd>
3399 <dd class="break"></dd>
3400 <dt id="RFC5340">[RFC5340]</dt>
3401 <dd>
3402 <span class="refAuthor">Coltun, R.</span>, <span class="refAuthor">Ferguson, D.</span>, <span class="refAuthor">Moy, J.</span>, and <span class="refAuthor">A. Lindem</span>, <span class="refTitle">"OSPF for IPv6"</span>, <span class="seriesInfo">RFC 5340</span>, <span class="seriesInfo">DOI 10.17487/RFC5340</span>, <time datetime="2008-07" class="refDate">July 2008</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc5340">https://www.rfc-editor.org/info/rfc5340</a>&gt;</span>. </dd>
3403 <dd class="break"></dd>
3404 <dt id="RFC7684">[RFC7684]</dt>
3405 <dd>
3406 <span class="refAuthor">Psenak, P.</span>, <span class="refAuthor">Gredler, H.</span>, <span class="refAuthor">Shakir, R.</span>, <span class="refAuthor">Henderickx, W.</span>, <span class="refAuthor">Tantsura, J.</span>, and <span class="refAuthor">A. Lindem</span>, <span class="refTitle">"OSPFv2 Prefix/Link Attribute Advertisement"</span>, <span class="seriesInfo">RFC 7684</span>, <span class="seriesInfo">DOI 10.17487/RFC7684</span>, <time datetime="2015-11" class="refDate">November 2015</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc7684">https://www.rfc-editor.org/info/rfc7684</a>&gt;</span>. </dd>
3407 <dd class="break"></dd>
3408 <dt id="RFC7752">[RFC7752]</dt>
3409 <dd>
3410 <span class="refAuthor">Gredler, H., Ed.</span>, <span class="refAuthor">Medved, J.</span>, <span class="refAuthor">Previdi, S.</span>, <span class="refAuthor">Farrel, A.</span>, and <span class="refAuthor">S. Ray</span>, <span class="refTitle">"North-Bound Distribution of Link-State and Traffic Engineering (TE) Information Using BGP"</span>, <span class="seriesInfo">RFC 7752</span>, <span class="seriesInfo">DOI 10.17487/RFC7752</span>, <time datetime="2016-03" class="refDate">March 2016</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc7752">https://www.rfc-editor.org/info/rfc7752</a>&gt;</span>. </dd>
3411 <dd class="break"></dd>
3412 <dt id="RFC7794">[RFC7794]</dt>
3413 <dd>
3414 <span class="refAuthor">Ginsberg, L., Ed.</span>, <span class="refAuthor">Decraene, B.</span>, <span class="refAuthor">Previdi, S.</span>, <span class="refAuthor">Xu, X.</span>, and <span class="refAuthor">U. Chunduri</span>, <span class="refTitle">"IS-IS Prefix Attributes for Extended IPv4 and IPv6 Reachability"</span>, <span class="seriesInfo">RFC 7794</span>, <span class="seriesInfo">DOI 10.17487/RFC7794</span>, <time datetime="2016-03" class="refDate">March 2016</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc7794">https://www.rfc-editor.org/info/rfc7794</a>&gt;</span>. </dd>
3415 <dd class="break"></dd>
3416 <dt id="RFC8174">[RFC8174]</dt>
3417 <dd>
3418 <span class="refAuthor">Leiba, B.</span>, <span class="refTitle">"Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words"</span>, <span class="seriesInfo">BCP 14</span>, <span class="seriesInfo">RFC 8174</span>, <span class="seriesInfo">DOI 10.17487/RFC8174</span>, <time datetime="2017-05" class="refDate">May 2017</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8174">https://www.rfc-editor.org/info/rfc8174</a>&gt;</span>. </dd>
3419 <dd class="break"></dd>
3420 <dt id="RFC8362">[RFC8362]</dt>
3421 <dd>
3422 <span class="refAuthor">Lindem, A.</span>, <span class="refAuthor">Roy, A.</span>, <span class="refAuthor">Goethals, D.</span>, <span class="refAuthor">Reddy Vallem, V.</span>, and <span class="refAuthor">F. Baker</span>, <span class="refTitle">"OSPFv3 Link State Advertisement (LSA) Extensibility"</span>, <span class="seriesInfo">RFC 8362</span>, <span class="seriesInfo">DOI 10.17487/RFC8362</span>, <time datetime="2018-04" class="refDate">April 2018</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8362">https://www.rfc-editor.org/info/rfc8362</a>&gt;</span>. </dd>
3423 <dd class="break"></dd>
3424 <dt id="RFC8402">[RFC8402]</dt>
3425 <dd>
3426 <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>, and <span class="refAuthor">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" class="refDate">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>
3427 <dd class="break"></dd>
3428 <dt id="RFC8571">[RFC8571]</dt>
3429 <dd>
3430 <span class="refAuthor">Ginsberg, L., Ed.</span>, <span class="refAuthor">Previdi, S.</span>, <span class="refAuthor">Wu, Q.</span>, <span class="refAuthor">Tantsura, J.</span>, and <span class="refAuthor">C. Filsfils</span>, <span class="refTitle">"BGP - Link State (BGP-LS) Advertisement of IGP Traffic Engineering Performance Metric Extensions"</span>, <span class="seriesInfo">RFC 8571</span>, <span class="seriesInfo">DOI 10.17487/RFC8571</span>, <time datetime="2019-03" class="refDate">March 2019</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8571">https://www.rfc-editor.org/info/rfc8571</a>&gt;</span>. </dd>
3431 <dd class="break"></dd>
3432 <dt id="RFC8665">[RFC8665]</dt>
3433 <dd>
3434 <span class="refAuthor">Psenak, P., Ed.</span>, <span class="refAuthor">Previdi, S., Ed.</span>, <span class="refAuthor">Filsfils, C.</span>, <span class="refAuthor">Gredler, H.</span>, <span class="refAuthor">Shakir, R.</span>, <span class="refAuthor">Henderickx, W.</span>, and <span class="refAuthor">J. Tantsura</span>, <span class="refTitle">"OSPF Extensions for Segment Routing"</span>, <span class="seriesInfo">RFC 8665</span>, <span class="seriesInfo">DOI 10.17487/RFC8665</span>, <time datetime="2019-12" class="refDate">December 2019</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8665">https://www.rfc-editor.org/info/rfc8665</a>&gt;</span>. </dd>
3435 <dd class="break"></dd>
3436 <dt id="RFC8666">[RFC8666]</dt>
3437 <dd>
3438 <span class="refAuthor">Psenak, P., Ed.</span> and <span class="refAuthor">S. Previdi, Ed.</span>, <span class="refTitle">"OSPFv3 Extensions for Segment Routing"</span>, <span class="seriesInfo">RFC 8666</span>, <span class="seriesInfo">DOI 10.17487/RFC8666</span>, <time datetime="2019-12" class="refDate">December 2019</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8666">https://www.rfc-editor.org/info/rfc8666</a>&gt;</span>. </dd>
3439 <dd class="break"></dd>
3440 <dt id="RFC8667">[RFC8667]</dt>
3441 <dd>
3442 <span class="refAuthor">Previdi, S., Ed.</span>, <span class="refAuthor">Ginsberg, L., Ed.</span>, <span class="refAuthor">Filsfils, C.</span>, <span class="refAuthor">Bashandy, A.</span>, <span class="refAuthor">Gredler, H.</span>, and <span class="refAuthor">B. Decraene</span>, <span class="refTitle">"IS-IS Extensions for Segment Routing"</span>, <span class="seriesInfo">RFC 8667</span>, <span class="seriesInfo">DOI 10.17487/RFC8667</span>, <time datetime="2019-12" class="refDate">December 2019</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8667">https://www.rfc-editor.org/info/rfc8667</a>&gt;</span>. </dd>
3443 <dd class="break"></dd>
3444 <dt id="RFC8668">[RFC8668]</dt>
3445 <dd>
3446 <span class="refAuthor">Ginsberg, L., Ed.</span>, <span class="refAuthor">Bashandy, A.</span>, <span class="refAuthor">Filsfils, C.</span>, <span class="refAuthor">Nanduri, M.</span>, and <span class="refAuthor">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" class="refDate">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>
3447 <dd class="break"></dd>
3448 <dt id="RFC9084">[RFC9084]</dt>
3449 <dd>
3450 <span class="refAuthor">Wang, A.</span>, <span class="refAuthor">Lindem, A.</span>, <span class="refAuthor">Dong, J.</span>, <span class="refAuthor">Psenak, P.</span>, and <span class="refAuthor">K. Talaulikar, Ed.</span>, <span class="refTitle">"OSPF Prefix Originator Extensions"</span>, <span class="seriesInfo">RFC 9084</span>, <span class="seriesInfo">DOI 10.17487/RFC9084</span>, <time datetime="2021-08" class="refDate">August 2021</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc9084">https://www.rfc-editor.org/info/rfc9084</a>&gt;</span>. </dd>
3451 <dd class="break"></dd>
3452 </dl>
3453 </section>
3454 <section id="section-6.2">
3455 <h3 id="name-informative-references">
3456 <a href="#section-6.2" class="section-number selfRef">6.2. </a><a href="#name-informative-references" class="section-name selfRef">Informative References</a>
3457 </h3>
3458 <dl class="references">
3459 <dt id="I-D.ietf-isis-sr-yang">[ISIS-SR-YANG]</dt>
3460 <dd>
3461 <span class="refAuthor">Litkowski, S.</span>, <span class="refAuthor">Qu, Y.</span>, <span class="refAuthor">Sarkar, P.</span>, <span class="refAuthor">Chen, I.</span>, and <span class="refAuthor">J. Tantsura</span>, <span class="refTitle">"YANG Data Model for IS-IS Segment Routing"</span>, <span class="refContent">Work in Progress</span>, <span class="seriesInfo">Internet-Draft, draft-ietf-isis-sr-yang-10</span>, <time datetime="2021-02-21" class="refDate">21 February 2021</time>, <span>&lt;<a href="https://datatracker.ietf.org/doc/html/draft-ietf-isis-sr-yang-10">https://datatracker.ietf.org/doc/html/draft-ietf-isis-sr-yang-10</a>&gt;</span>. </dd>
3462 <dd class="break"></dd>
3463 <dt id="I-D.ietf-ospf-sr-yang">[OSPF-SR-YANG]</dt>
3464 <dd>
3465 <span class="refAuthor">Yeung, D.</span>, <span class="refAuthor">Qu, Y.</span>, <span class="refAuthor">Zhang, J.</span>, <span class="refAuthor">Chen, I.</span>, and <span class="refAuthor">A. Lindem</span>, <span class="refTitle">"YANG Data Model for OSPF SR (Segment Routing) Protocol"</span>, <span class="refContent">Work in Progress</span>, <span class="seriesInfo">Internet-Draft, draft-ietf-ospf-sr-yang-15</span>, <time datetime="2021-07-02" class="refDate">2 July 2021</time>, <span>&lt;<a href="https://datatracker.ietf.org/doc/html/draft-ietf-ospf-sr-yang-15">https://datatracker.ietf.org/doc/html/draft-ietf-ospf-sr-yang-15</a>&gt;</span>. </dd>
3466 <dd class="break"></dd>
3467 <dt id="RFC5706">[RFC5706]</dt>
3468 <dd>
3469 <span class="refAuthor">Harrington, D.</span>, <span class="refTitle">"Guidelines for Considering Operations and Management of New Protocols and Protocol Extensions"</span>, <span class="seriesInfo">RFC 5706</span>, <span class="seriesInfo">DOI 10.17487/RFC5706</span>, <time datetime="2009-11" class="refDate">November 2009</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc5706">https://www.rfc-editor.org/info/rfc5706</a>&gt;</span>. </dd>
3470 <dd class="break"></dd>
3471 <dt id="RFC8661">[RFC8661]</dt>
3472 <dd>
3473 <span class="refAuthor">Bashandy, A., Ed.</span>, <span class="refAuthor">Filsfils, C., Ed.</span>, <span class="refAuthor">Previdi, S.</span>, <span class="refAuthor">Decraene, B.</span>, and <span class="refAuthor">S. Litkowski</span>, <span class="refTitle">"Segment Routing MPLS Interworking with LDP"</span>, <span class="seriesInfo">RFC 8661</span>, <span class="seriesInfo">DOI 10.17487/RFC8661</span>, <time datetime="2019-12" class="refDate">December 2019</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8661">https://www.rfc-editor.org/info/rfc8661</a>&gt;</span>. </dd>
3474 <dd class="break"></dd>
3475 <dt id="RFC9020">[RFC9020]</dt>
3476 <dd>
3477 <span class="refAuthor">Litkowski, S.</span>, <span class="refAuthor">Qu, Y.</span>, <span class="refAuthor">Lindem, A.</span>, <span class="refAuthor">Sarkar, P.</span>, and <span class="refAuthor">J. Tantsura</span>, <span class="refTitle">"YANG Data Model for Segment Routing"</span>, <span class="seriesInfo">RFC 9020</span>, <span class="seriesInfo">DOI 10.17487/RFC9020</span>, <time datetime="2021-05" class="refDate">May 2021</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc9020">https://www.rfc-editor.org/info/rfc9020</a>&gt;</span>. </dd>
3478 <dd class="break"></dd>
3479 </dl>
3480 </section>
3481 </section>
3482 <div id="Acknowledgements">
3483 <section id="appendix-A">
3484 <h2 id="name-acknowledgements">
3485 <a href="#name-acknowledgements" class="section-name selfRef">Acknowledgements</a>
3486 </h2>
3487 <p id="appendix-A-1">The authors would like to thank <span class="contact-name">Jeffrey Haas</span>, <span class="contact-name">Aijun Wang</span>, <span class="contact-name">Robert Raszuk</span>, and <span class="contact-name">Susan Hares</span>
3488 for their review of this document and their comments. The
3489 authors would also like to thank <span class="contact-name">Alvaro Retana</span> for his extensive
3490 review and comments, which helped correct issues and improve the
3491 document.<a href="#appendix-A-1" class="pilcrow">¶</a></p>
3492 </section>
3493 </div>
3494 <div id="Contributors">
3495 <section id="appendix-B">
3496 <h2 id="name-contributors">
3497 <a href="#name-contributors" class="section-name selfRef">Contributors</a>
3498 </h2>
3499 <p id="appendix-B-1">The following people have substantially contributed to the editing of
3500 this document:<a href="#appendix-B-1" class="pilcrow">¶</a></p>
3501 <address class="vcard">
3502 <div dir="auto" class="left"><span class="fn nameRole">Peter Psenak</span></div>
3503 <div dir="auto" class="left"><span class="org">Cisco Systems</span></div>
3504 <div class="email">
3505 <span>Email:</span>
3506 <a href="mailto:[email protected]" class="email">[email protected]</a>
3507 </div>
3508 </address>
3509 <address class="vcard">
3510 <div dir="auto" class="left"><span class="fn nameRole">Les Ginsberg</span></div>
3511 <div dir="auto" class="left"><span class="org">Cisco Systems</span></div>
3512 <div class="email">
3513 <span>Email:</span>
3514 <a href="mailto:[email protected]" class="email">[email protected]</a>
3515 </div>
3516 </address>
3517 <address class="vcard">
3518 <div dir="auto" class="left"><span class="fn nameRole">Acee Lindem</span></div>
3519 <div dir="auto" class="left"><span class="org">Cisco Systems</span></div>
3520 <div class="email">
3521 <span>Email:</span>
3522 <a href="mailto:[email protected]" class="email">[email protected]</a>
3523 </div>
3524 </address>
3525 <address class="vcard">
3526 <div dir="auto" class="left"><span class="fn nameRole">Saikat Ray</span></div>
3527 <div dir="auto" class="left"><span class="org">Individual</span></div>
3528 <div class="email">
3529 <span>Email:</span>
3530 <a href="mailto:[email protected]" class="email">[email protected]</a>
3531 </div>
3532 </address>
3533 <address class="vcard">
3534 <div dir="auto" class="left"><span class="fn nameRole">Jeff Tantsura</span></div>
3535 <div dir="auto" class="left"><span class="org">Apstra Inc.</span></div>
3536 <div class="email">
3537 <span>Email:</span>
3538 <a href="mailto:[email protected]" class="email">[email protected]</a>
3539 </div>
3540 </address>
3541 </section>
3542 </div>
3543 <div id="authors-addresses">
3544 <section id="appendix-C">
3545 <h2 id="name-authors-addresses">
3546 <a href="#name-authors-addresses" class="section-name selfRef">Authors' Addresses</a>
3547 </h2>
3548 <address class="vcard">
3549 <div dir="auto" class="left"><span class="fn nameRole">Stefano Previdi</span></div>
3550 <div dir="auto" class="left"><span class="org">Huawei Technologies</span></div>
3551 <div dir="auto" class="left">
3552 <span class="locality">Rome</span> </div>
3553 <div dir="auto" class="left"><span class="country-name">Italy</span></div>
3554 <div class="email">
3555 <span>Email:</span>
3556 <a href="mailto:[email protected]" class="email">[email protected]</a>
3557 </div>
3558 </address>
3559 <address class="vcard">
3560 <div dir="auto" class="left"><span class="fn nameRole">Ketan Talaulikar (<span class="role">editor</span>)</span></div>
3561 <div dir="auto" class="left"><span class="org">Cisco Systems, Inc.</span></div>
3562 <div dir="auto" class="left"><span class="country-name">India</span></div>
3563 <div class="email">
3564 <span>Email:</span>
3565 <a href="mailto:[email protected]" class="email">[email protected]</a>
3566 </div>
3567 </address>
3568 <address class="vcard">
3569 <div dir="auto" class="left"><span class="fn nameRole">Clarence Filsfils</span></div>
3570 <div dir="auto" class="left"><span class="org">Cisco Systems, Inc.</span></div>
3571 <div dir="auto" class="left"><span class="locality">Brussels</span></div>
3572 <div dir="auto" class="left"><span class="country-name">Belgium</span></div>
3573 <div class="email">
3574 <span>Email:</span>
3575 <a href="mailto:[email protected]" class="email">[email protected]</a>
3576 </div>
3577 </address>
3578 <address class="vcard">
3579 <div dir="auto" class="left"><span class="fn nameRole">Hannes Gredler</span></div>
3580 <div dir="auto" class="left"><span class="org">RtBrick Inc.</span></div>
3581 <div class="email">
3582 <span>Email:</span>
3583 <a href="mailto:[email protected]" class="email">[email protected]</a>
3584 </div>
3585 </address>
3586 <address class="vcard">
3587 <div dir="auto" class="left"><span class="fn nameRole">Mach(Guoyi) Chen</span></div>
3588 <div dir="auto" class="left"><span class="org">Huawei Technologies</span></div>
3589 <div dir="auto" class="left"><span class="street-address">Huawei Building, No. 156 Beiqing Rd.</span></div>
3590 <div dir="auto" class="left"><span class="locality">Beijing</span></div>
3591 <div dir="auto" class="left"><span class="postal-code">100095</span></div>
3592 <div dir="auto" class="left"><span class="country-name">China</span></div>
3593 <div class="email">
3594 <span>Email:</span>
3595 <a href="mailto:[email protected]" class="email">[email protected]</a>
3596 </div>
3597 </address>
3598 </section>
3599 </div>
3600 <script>const toc = document.getElementById("toc");
3601 toc.querySelector("h2").addEventListener("click", e => {
3602 toc.classList.toggle("active");
3603 });
3604 toc.querySelector("nav").addEventListener("click", e => {
3605 toc.classList.remove("active");
3606 });
3607 </script>
3608 </body>
3609 </html>