Debian Codegraph @

rfc9070.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 9070: YANG Data Model for MPLS LDP</title>
8 <meta content="Kamran Raza" name="author">
9 <meta content="Rajiv Asati" name="author">
10 <meta content="Xufeng Liu" name="author">
11 <meta content="Santosh Easale" name="author">
12 <meta content="Xia Chen" name="author">
13 <meta content="Himanshu Shah" name="author">
14 <meta content="
15 This document describes a YANG data model for the Multiprotocol Label Switching (MPLS)
16 Label Distribution Protocol (LDP). The model also serves as the base model
17 to define the Multipoint LDP (mLDP) model.
18 The YANG modules in this document conform to the Network Management
19 Datastore Architecture (NMDA).
20
21 " name="description">
22 <meta content="xml2rfc 3.12.2" name="generator">
23 <meta content="MPLS" name="keyword">
24 <meta content="LDP" name="keyword">
25 <meta content="YANG" name="keyword">
26 <meta content="9070" name="rfc.number">
27 <!-- Generator version information:
28 xml2rfc 3.12.2
29 Python 3.6.15
30 appdirs 1.4.4
31 ConfigArgParse 1.4.1
32 google-i18n-address 2.4.0
33 html5lib 1.0.1
34 intervaltree 3.0.2
35 Jinja2 2.11.3
36 kitchen 1.2.6
37 lxml 4.4.2
38 pycairo 1.15.1
39 pycountry 19.8.18
40 pyflakes 2.1.1
41 PyYAML 5.4.1
42 requests 2.24.0
43 setuptools 40.5.0
44 six 1.14.0
45 WeasyPrint 52.5
46 -->
47 <link href="rfc9070.xml" rel="alternate" type="application/rfc+xml">
48 <link href="#copyright" rel="license">
49 <style type="text/css">/*
50
51 NOTE: Changes at the bottom of this file overrides some earlier settings.
52
53 Once the style has stabilized and has been adopted as an official RFC style,
54 this can be consolidated so that style settings occur only in one place, but
55 for now the contents of this file consists first of the initial CSS work as
56 provided to the RFC Formatter (xml2rfc) work, followed by itemized and
57 commented changes found necssary during the development of the v3
58 formatters.
59
60 */
61
62 /* fonts */
63 @import url('https://fonts.googleapis.com/css?family=Noto+Sans'); /* Sans-serif */
64 @import url('https://fonts.googleapis.com/css?family=Noto+Serif'); /* Serif (print) */
65 @import url('https://fonts.googleapis.com/css?family=Roboto+Mono'); /* Monospace */
66
67 @viewport {
68 zoom: 1.0;
69 width: extend-to-zoom;
70 }
71 @-ms-viewport {
72 width: extend-to-zoom;
73 zoom: 1.0;
74 }
75 /* general and mobile first */
76 html {
77 }
78 body {
79 max-width: 90%;
80 margin: 1.5em auto;
81 color: #222;
82 background-color: #fff;
83 font-size: 14px;
84 font-family: 'Noto Sans', Arial, Helvetica, sans-serif;
85 line-height: 1.6;
86 scroll-behavior: smooth;
87 }
88 .ears {
89 display: none;
90 }
91
92 /* headings */
93 #title, h1, h2, h3, h4, h5, h6 {
94 margin: 1em 0 0.5em;
95 font-weight: bold;
96 line-height: 1.3;
97 }
98 #title {
99 clear: both;
100 border-bottom: 1px solid #ddd;
101 margin: 0 0 0.5em 0;
102 padding: 1em 0 0.5em;
103 }
104 .author {
105 padding-bottom: 4px;
106 }
107 h1 {
108 font-size: 26px;
109 margin: 1em 0;
110 }
111 h2 {
112 font-size: 22px;
113 margin-top: -20px; /* provide offset for in-page anchors */
114 padding-top: 33px;
115 }
116 h3 {
117 font-size: 18px;
118 margin-top: -36px; /* provide offset for in-page anchors */
119 padding-top: 42px;
120 }
121 h4 {
122 font-size: 16px;
123 margin-top: -36px; /* provide offset for in-page anchors */
124 padding-top: 42px;
125 }
126 h5, h6 {
127 font-size: 14px;
128 }
129 #n-copyright-notice {
130 border-bottom: 1px solid #ddd;
131 padding-bottom: 1em;
132 margin-bottom: 1em;
133 }
134 /* general structure */
135 p {
136 padding: 0;
137 margin: 0 0 1em 0;
138 text-align: left;
139 }
140 div, span {
141 position: relative;
142 }
143 div {
144 margin: 0;
145 }
146 .alignRight.art-text {
147 background-color: #f9f9f9;
148 border: 1px solid #eee;
149 border-radius: 3px;
150 padding: 1em 1em 0;
151 margin-bottom: 1.5em;
152 }
153 .alignRight.art-text pre {
154 padding: 0;
155 }
156 .alignRight {
157 margin: 1em 0;
158 }
159 .alignRight > *:first-child {
160 border: none;
161 margin: 0;
162 float: right;
163 clear: both;
164 }
165 .alignRight > *:nth-child(2) {
166 clear: both;
167 display: block;
168 border: none;
169 }
170 svg {
171 display: block;
172 }
173 .alignCenter.art-text {
174 background-color: #f9f9f9;
175 border: 1px solid #eee;
176 border-radius: 3px;
177 padding: 1em 1em 0;
178 margin-bottom: 1.5em;
179 }
180 .alignCenter.art-text pre {
181 padding: 0;
182 }
183 .alignCenter {
184 margin: 1em 0;
185 }
186 .alignCenter > *:first-child {
187 border: none;
188 /* this isn't optimal, but it's an existence proof. PrinceXML doesn't
189 support flexbox yet.
190 */
191 display: table;
192 margin: 0 auto;
193 }
194
195 /* lists */
196 ol, ul {
197 padding: 0;
198 margin: 0 0 1em 2em;
199 }
200 ol ol, ul ul, ol ul, ul ol {
201 margin-left: 1em;
202 }
203 li {
204 margin: 0 0 0.25em 0;
205 }
206 .ulCompact li {
207 margin: 0;
208 }
209 ul.empty, .ulEmpty {
210 list-style-type: none;
211 }
212 ul.empty li, .ulEmpty li {
213 margin-top: 0.5em;
214 }
215 ul.ulBare, li.ulBare {
216 margin-left: 0em !important;
217 }
218 ul.compact, .ulCompact,
219 ol.compact, .olCompact {
220 line-height: 100%;
221 margin: 0 0 0 2em;
222 }
223
224 /* definition lists */
225 dl {
226 }
227 dl > dt {
228 float: left;
229 margin-right: 1em;
230 }
231 /*
232 dl.nohang > dt {
233 float: none;
234 }
235 */
236 dl > dd {
237 margin-bottom: .8em;
238 min-height: 1.3em;
239 }
240 dl.compact > dd, .dlCompact > dd {
241 margin-bottom: 0em;
242 }
243 dl > dd > dl {
244 margin-top: 0.5em;
245 margin-bottom: 0em;
246 }
247
248 /* links */
249 a {
250 text-decoration: none;
251 }
252 a[href] {
253 color: #22e; /* Arlen: WCAG 2019 */
254 }
255 a[href]:hover {
256 background-color: #f2f2f2;
257 }
258 figcaption a[href],
259 a[href].selfRef {
260 color: #222;
261 }
262 /* XXX probably not this:
263 a.selfRef:hover {
264 background-color: transparent;
265 cursor: default;
266 } */
267
268 /* Figures */
269 tt, code, pre, code {
270 background-color: #f9f9f9;
271 font-family: 'Roboto Mono', monospace;
272 }
273 pre {
274 border: 1px solid #eee;
275 margin: 0;
276 padding: 1em;
277 }
278 img {
279 max-width: 100%;
280 }
281 figure {
282 margin: 0;
283 }
284 figure blockquote {
285 margin: 0.8em 0.4em 0.4em;
286 }
287 figcaption {
288 font-style: italic;
289 margin: 0 0 1em 0;
290 }
291 @media screen {
292 pre {
293 overflow-x: auto;
294 max-width: 100%;
295 max-width: calc(100% - 22px);
296 }
297 }
298
299 /* aside, blockquote */
300 aside, blockquote {
301 margin-left: 0;
302 padding: 1.2em 2em;
303 }
304 blockquote {
305 background-color: #f9f9f9;
306 color: #111; /* Arlen: WCAG 2019 */
307 border: 1px solid #ddd;
308 border-radius: 3px;
309 margin: 1em 0;
310 }
311 cite {
312 display: block;
313 text-align: right;
314 font-style: italic;
315 }
316
317 /* tables */
318 table {
319 width: 100%;
320 margin: 0 0 1em;
321 border-collapse: collapse;
322 border: 1px solid #eee;
323 }
324 th, td {
325 text-align: left;
326 vertical-align: top;
327 padding: 0.5em 0.75em;
328 }
329 th {
330 text-align: left;
331 background-color: #e9e9e9;
332 }
333 tr:nth-child(2n+1) > td {
334 background-color: #f5f5f5;
335 }
336 table caption {
337 font-style: italic;
338 margin: 0;
339 padding: 0;
340 text-align: left;
341 }
342 table p {
343 /* XXX to avoid bottom margin on table row signifiers. If paragraphs should
344 be allowed within tables more generally, it would be far better to select on a class. */
345 margin: 0;
346 }
347
348 /* pilcrow */
349 a.pilcrow {
350 color: #666; /* Arlen: AHDJ 2019 */
351 text-decoration: none;
352 visibility: hidden;
353 user-select: none;
354 -ms-user-select: none;
355 -o-user-select:none;
356 -moz-user-select: none;
357 -khtml-user-select: none;
358 -webkit-user-select: none;
359 -webkit-touch-callout: none;
360 }
361 @media screen {
362 aside:hover > a.pilcrow,
363 p:hover > a.pilcrow,
364 blockquote:hover > a.pilcrow,
365 div:hover > a.pilcrow,
366 li:hover > a.pilcrow,
367 pre:hover > a.pilcrow {
368 visibility: visible;
369 }
370 a.pilcrow:hover {
371 background-color: transparent;
372 }
373 }
374
375 /* misc */
376 hr {
377 border: 0;
378 border-top: 1px solid #eee;
379 }
380 .bcp14 {
381 font-variant: small-caps;
382 }
383
384 .role {
385 font-variant: all-small-caps;
386 }
387
388 /* info block */
389 #identifiers {
390 margin: 0;
391 font-size: 0.9em;
392 }
393 #identifiers dt {
394 width: 3em;
395 clear: left;
396 }
397 #identifiers dd {
398 float: left;
399 margin-bottom: 0;
400 }
401 /* Fix PDF info block run off issue */
402 @media print {
403 #identifiers dd {
404 float: none;
405 }
406 }
407 #identifiers .authors .author {
408 display: inline-block;
409 margin-right: 1.5em;
410 }
411 #identifiers .authors .org {
412 font-style: italic;
413 }
414
415 /* The prepared/rendered info at the very bottom of the page */
416 .docInfo {
417 color: #666; /* Arlen: WCAG 2019 */
418 font-size: 0.9em;
419 font-style: italic;
420 margin-top: 2em;
421 }
422 .docInfo .prepared {
423 float: left;
424 }
425 .docInfo .prepared {
426 float: right;
427 }
428
429 /* table of contents */
430 #toc {
431 padding: 0.75em 0 2em 0;
432 margin-bottom: 1em;
433 }
434 nav.toc ul {
435 margin: 0 0.5em 0 0;
436 padding: 0;
437 list-style: none;
438 }
439 nav.toc li {
440 line-height: 1.3em;
441 margin: 0.75em 0;
442 padding-left: 1.2em;
443 text-indent: -1.2em;
444 }
445 /* references */
446 .references dt {
447 text-align: right;
448 font-weight: bold;
449 min-width: 7em;
450 }
451 .references dd {
452 margin-left: 8em;
453 overflow: auto;
454 }
455
456 .refInstance {
457 margin-bottom: 1.25em;
458 }
459
460 .references .ascii {
461 margin-bottom: 0.25em;
462 }
463
464 /* index */
465 .index ul {
466 margin: 0 0 0 1em;
467 padding: 0;
468 list-style: none;
469 }
470 .index ul ul {
471 margin: 0;
472 }
473 .index li {
474 margin: 0;
475 text-indent: -2em;
476 padding-left: 2em;
477 padding-bottom: 5px;
478 }
479 .indexIndex {
480 margin: 0.5em 0 1em;
481 }
482 .index a {
483 font-weight: 700;
484 }
485 /* make the index two-column on all but the smallest screens */
486 @media (min-width: 600px) {
487 .index ul {
488 -moz-column-count: 2;
489 -moz-column-gap: 20px;
490 }
491 .index ul ul {
492 -moz-column-count: 1;
493 -moz-column-gap: 0;
494 }
495 }
496
497 /* authors */
498 address.vcard {
499 font-style: normal;
500 margin: 1em 0;
501 }
502
503 address.vcard .nameRole {
504 font-weight: 700;
505 margin-left: 0;
506 }
507 address.vcard .label {
508 font-family: "Noto Sans",Arial,Helvetica,sans-serif;
509 margin: 0.5em 0;
510 }
511 address.vcard .type {
512 display: none;
513 }
514 .alternative-contact {
515 margin: 1.5em 0 1em;
516 }
517 hr.addr {
518 border-top: 1px dashed;
519 margin: 0;
520 color: #ddd;
521 max-width: calc(100% - 16px);
522 }
523
524 /* temporary notes */
525 .rfcEditorRemove::before {
526 position: absolute;
527 top: 0.2em;
528 right: 0.2em;
529 padding: 0.2em;
530 content: "The RFC Editor will remove this note";
531 color: #9e2a00; /* Arlen: WCAG 2019 */
532 background-color: #ffd; /* Arlen: WCAG 2019 */
533 }
534 .rfcEditorRemove {
535 position: relative;
536 padding-top: 1.8em;
537 background-color: #ffd; /* Arlen: WCAG 2019 */
538 border-radius: 3px;
539 }
540 .cref {
541 background-color: #ffd; /* Arlen: WCAG 2019 */
542 padding: 2px 4px;
543 }
544 .crefSource {
545 font-style: italic;
546 }
547 /* alternative layout for smaller screens */
548 @media screen and (max-width: 1023px) {
549 body {
550 padding-top: 2em;
551 }
552 #title {
553 padding: 1em 0;
554 }
555 h1 {
556 font-size: 24px;
557 }
558 h2 {
559 font-size: 20px;
560 margin-top: -18px; /* provide offset for in-page anchors */
561 padding-top: 38px;
562 }
563 #identifiers dd {
564 max-width: 60%;
565 }
566 #toc {
567 position: fixed;
568 z-index: 2;
569 top: 0;
570 right: 0;
571 padding: 0;
572 margin: 0;
573 background-color: inherit;
574 border-bottom: 1px solid #ccc;
575 }
576 #toc h2 {
577 margin: -1px 0 0 0;
578 padding: 4px 0 4px 6px;
579 padding-right: 1em;
580 min-width: 190px;
581 font-size: 1.1em;
582 text-align: right;
583 background-color: #444;
584 color: white;
585 cursor: pointer;
586 }
587 #toc h2::before { /* css hamburger */
588 float: right;
589 position: relative;
590 width: 1em;
591 height: 1px;
592 left: -164px;
593 margin: 6px 0 0 0;
594 background: white none repeat scroll 0 0;
595 box-shadow: 0 4px 0 0 white, 0 8px 0 0 white;
596 content: "";
597 }
598 #toc nav {
599 display: none;
600 padding: 0.5em 1em 1em;
601 overflow: auto;
602 height: calc(100vh - 48px);
603 border-left: 1px solid #ddd;
604 }
605 }
606
607 /* alternative layout for wide screens */
608 @media screen and (min-width: 1024px) {
609 body {
610 max-width: 724px;
611 margin: 42px auto;
612 padding-left: 1.5em;
613 padding-right: 29em;
614 }
615 #toc {
616 position: fixed;
617 top: 42px;
618 right: 42px;
619 width: 25%;
620 margin: 0;
621 padding: 0 1em;
622 z-index: 1;
623 }
624 #toc h2 {
625 border-top: none;
626 border-bottom: 1px solid #ddd;
627 font-size: 1em;
628 font-weight: normal;
629 margin: 0;
630 padding: 0.25em 1em 1em 0;
631 }
632 #toc nav {
633 display: block;
634 height: calc(90vh - 84px);
635 bottom: 0;
636 padding: 0.5em 0 0;
637 overflow: auto;
638 }
639 img { /* future proofing */
640 max-width: 100%;
641 height: auto;
642 }
643 }
644
645 /* pagination */
646 @media print {
647 body {
648
649 width: 100%;
650 }
651 p {
652 orphans: 3;
653 widows: 3;
654 }
655 #n-copyright-notice {
656 border-bottom: none;
657 }
658 #toc, #n-introduction {
659 page-break-before: always;
660 }
661 #toc {
662 border-top: none;
663 padding-top: 0;
664 }
665 figure, pre {
666 page-break-inside: avoid;
667 }
668 figure {
669 overflow: scroll;
670 }
671 h1, h2, h3, h4, h5, h6 {
672 page-break-after: avoid;
673 }
674 h2+*, h3+*, h4+*, h5+*, h6+* {
675 page-break-before: avoid;
676 }
677 pre {
678 white-space: pre-wrap;
679 word-wrap: break-word;
680 font-size: 10pt;
681 }
682 table {
683 border: 1px solid #ddd;
684 }
685 td {
686 border-top: 1px solid #ddd;
687 }
688 }
689
690 /* This is commented out here, as the string-set: doesn't
691 pass W3C validation currently */
692 /*
693 .ears thead .left {
694 string-set: ears-top-left content();
695 }
696
697 .ears thead .center {
698 string-set: ears-top-center content();
699 }
700
701 .ears thead .right {
702 string-set: ears-top-right content();
703 }
704
705 .ears tfoot .left {
706 string-set: ears-bottom-left content();
707 }
708
709 .ears tfoot .center {
710 string-set: ears-bottom-center content();
711 }
712
713 .ears tfoot .right {
714 string-set: ears-bottom-right content();
715 }
716 */
717
718 @page :first {
719 padding-top: 0;
720 @top-left {
721 content: normal;
722 border: none;
723 }
724 @top-center {
725 content: normal;
726 border: none;
727 }
728 @top-right {
729 content: normal;
730 border: none;
731 }
732 }
733
734 @page {
735 size: A4;
736 margin-bottom: 45mm;
737 padding-top: 20px;
738 /* The follwing is commented out here, but set appropriately by in code, as
739 the content depends on the document */
740 /*
741 @top-left {
742 content: 'Internet-Draft';
743 vertical-align: bottom;
744 border-bottom: solid 1px #ccc;
745 }
746 @top-left {
747 content: string(ears-top-left);
748 vertical-align: bottom;
749 border-bottom: solid 1px #ccc;
750 }
751 @top-center {
752 content: string(ears-top-center);
753 vertical-align: bottom;
754 border-bottom: solid 1px #ccc;
755 }
756 @top-right {
757 content: string(ears-top-right);
758 vertical-align: bottom;
759 border-bottom: solid 1px #ccc;
760 }
761 @bottom-left {
762 content: string(ears-bottom-left);
763 vertical-align: top;
764 border-top: solid 1px #ccc;
765 }
766 @bottom-center {
767 content: string(ears-bottom-center);
768 vertical-align: top;
769 border-top: solid 1px #ccc;
770 }
771 @bottom-right {
772 content: '[Page ' counter(page) ']';
773 vertical-align: top;
774 border-top: solid 1px #ccc;
775 }
776 */
777
778 }
779
780 /* Changes introduced to fix issues found during implementation */
781 /* Make sure links are clickable even if overlapped by following H* */
782 a {
783 z-index: 2;
784 }
785 /* Separate body from document info even without intervening H1 */
786 section {
787 clear: both;
788 }
789
790
791 /* Top align author divs, to avoid names without organization dropping level with org names */
792 .author {
793 vertical-align: top;
794 }
795
796 /* Leave room in document info to show Internet-Draft on one line */
797 #identifiers dt {
798 width: 8em;
799 }
800
801 /* Don't waste quite as much whitespace between label and value in doc info */
802 #identifiers dd {
803 margin-left: 1em;
804 }
805
806 /* Give floating toc a background color (needed when it's a div inside section */
807 #toc {
808 background-color: white;
809 }
810
811 /* Make the collapsed ToC header render white on gray also when it's a link */
812 @media screen and (max-width: 1023px) {
813 #toc h2 a,
814 #toc h2 a:link,
815 #toc h2 a:focus,
816 #toc h2 a:hover,
817 #toc a.toplink,
818 #toc a.toplink:hover {
819 color: white;
820 background-color: #444;
821 text-decoration: none;
822 }
823 }
824
825 /* Give the bottom of the ToC some whitespace */
826 @media screen and (min-width: 1024px) {
827 #toc {
828 padding: 0 0 1em 1em;
829 }
830 }
831
832 /* Style section numbers with more space between number and title */
833 .section-number {
834 padding-right: 0.5em;
835 }
836
837 /* prevent monospace from becoming overly large */
838 tt, code, pre, code {
839 font-size: 95%;
840 }
841
842 /* Fix the height/width aspect for ascii art*/
843 pre.sourcecode,
844 .art-text pre {
845 line-height: 1.12;
846 }
847
848
849 /* Add styling for a link in the ToC that points to the top of the document */
850 a.toplink {
851 float: right;
852 margin-right: 0.5em;
853 }
854
855 /* Fix the dl styling to match the RFC 7992 attributes */
856 dl > dt,
857 dl.dlParallel > dt {
858 float: left;
859 margin-right: 1em;
860 }
861 dl.dlNewline > dt {
862 float: none;
863 }
864
865 /* Provide styling for table cell text alignment */
866 table td.text-left,
867 table th.text-left {
868 text-align: left;
869 }
870 table td.text-center,
871 table th.text-center {
872 text-align: center;
873 }
874 table td.text-right,
875 table th.text-right {
876 text-align: right;
877 }
878
879 /* Make the alternative author contact informatio look less like just another
880 author, and group it closer with the primary author contact information */
881 .alternative-contact {
882 margin: 0.5em 0 0.25em 0;
883 }
884 address .non-ascii {
885 margin: 0 0 0 2em;
886 }
887
888 /* With it being possible to set tables with alignment
889 left, center, and right, { width: 100%; } does not make sense */
890 table {
891 width: auto;
892 }
893
894 /* Avoid reference text that sits in a block with very wide left margin,
895 because of a long floating dt label.*/
896 .references dd {
897 overflow: visible;
898 }
899
900 /* Control caption placement */
901 caption {
902 caption-side: bottom;
903 }
904
905 /* Limit the width of the author address vcard, so names in right-to-left
906 script don't end up on the other side of the page. */
907
908 address.vcard {
909 max-width: 30em;
910 margin-right: auto;
911 }
912
913 /* For address alignment dependent on LTR or RTL scripts */
914 address div.left {
915 text-align: left;
916 }
917 address div.right {
918 text-align: right;
919 }
920
921 /* Provide table alignment support. We can't use the alignX classes above
922 since they do unwanted things with caption and other styling. */
923 table.right {
924 margin-left: auto;
925 margin-right: 0;
926 }
927 table.center {
928 margin-left: auto;
929 margin-right: auto;
930 }
931 table.left {
932 margin-left: 0;
933 margin-right: auto;
934 }
935
936 /* Give the table caption label the same styling as the figcaption */
937 caption a[href] {
938 color: #222;
939 }
940
941 @media print {
942 .toplink {
943 display: none;
944 }
945
946 /* avoid overwriting the top border line with the ToC header */
947 #toc {
948 padding-top: 1px;
949 }
950
951 /* Avoid page breaks inside dl and author address entries */
952 .vcard {
953 page-break-inside: avoid;
954 }
955
956 }
957 /* Tweak the bcp14 keyword presentation */
958 .bcp14 {
959 font-variant: small-caps;
960 font-weight: bold;
961 font-size: 0.9em;
962 }
963 /* Tweak the invisible space above H* in order not to overlay links in text above */
964 h2 {
965 margin-top: -18px; /* provide offset for in-page anchors */
966 padding-top: 31px;
967 }
968 h3 {
969 margin-top: -18px; /* provide offset for in-page anchors */
970 padding-top: 24px;
971 }
972 h4 {
973 margin-top: -18px; /* provide offset for in-page anchors */
974 padding-top: 24px;
975 }
976 /* Float artwork pilcrow to the right */
977 @media screen {
978 .artwork a.pilcrow {
979 display: block;
980 line-height: 0.7;
981 margin-top: 0.15em;
982 }
983 }
984 /* Make pilcrows on dd visible */
985 @media screen {
986 dd:hover > a.pilcrow {
987 visibility: visible;
988 }
989 }
990 /* Make the placement of figcaption match that of a table's caption
991 by removing the figure's added bottom margin */
992 .alignLeft.art-text,
993 .alignCenter.art-text,
994 .alignRight.art-text {
995 margin-bottom: 0;
996 }
997 .alignLeft,
998 .alignCenter,
999 .alignRight {
1000 margin: 1em 0 0 0;
1001 }
1002 /* In print, the pilcrow won't show on hover, so prevent it from taking up space,
1003 possibly even requiring a new line */
1004 @media print {
1005 a.pilcrow {
1006 display: none;
1007 }
1008 }
1009 /* Styling for the external metadata */
1010 div#external-metadata {
1011 background-color: #eee;
1012 padding: 0.5em;
1013 margin-bottom: 0.5em;
1014 display: none;
1015 }
1016 div#internal-metadata {
1017 padding: 0.5em; /* to match the external-metadata padding */
1018 }
1019 /* Styling for title RFC Number */
1020 h1#rfcnum {
1021 clear: both;
1022 margin: 0 0 -1em;
1023 padding: 1em 0 0 0;
1024 }
1025 /* Make .olPercent look the same as <ol><li> */
1026 dl.olPercent > dd {
1027 margin-bottom: 0.25em;
1028 min-height: initial;
1029 }
1030 /* Give aside some styling to set it apart */
1031 aside {
1032 border-left: 1px solid #ddd;
1033 margin: 1em 0 1em 2em;
1034 padding: 0.2em 2em;
1035 }
1036 aside > dl,
1037 aside > ol,
1038 aside > ul,
1039 aside > table,
1040 aside > p {
1041 margin-bottom: 0.5em;
1042 }
1043 /* Additional page break settings */
1044 @media print {
1045 figcaption, table caption {
1046 page-break-before: avoid;
1047 }
1048 }
1049 /* Font size adjustments for print */
1050 @media print {
1051 body { font-size: 10pt; line-height: normal; max-width: 96%; }
1052 h1 { font-size: 1.72em; padding-top: 1.5em; } /* 1*1.2*1.2*1.2 */
1053 h2 { font-size: 1.44em; padding-top: 1.5em; } /* 1*1.2*1.2 */
1054 h3 { font-size: 1.2em; padding-top: 1.5em; } /* 1*1.2 */
1055 h4 { font-size: 1em; padding-top: 1.5em; }
1056 h5, h6 { font-size: 1em; margin: initial; padding: 0.5em 0 0.3em; }
1057 }
1058 /* Sourcecode margin in print, when there's no pilcrow */
1059 @media print {
1060 .artwork,
1061 .sourcecode {
1062 margin-bottom: 1em;
1063 }
1064 }
1065 /* Avoid narrow tables forcing too narrow table captions, which may render badly */
1066 table {
1067 min-width: 20em;
1068 }
1069 /* ol type a */
1070 ol.type-a { list-style-type: lower-alpha; }
1071 ol.type-A { list-style-type: upper-alpha; }
1072 ol.type-i { list-style-type: lower-roman; }
1073 ol.type-I { list-style-type: lower-roman; }
1074 /* Apply the print table and row borders in general, on request from the RPC,
1075 and increase the contrast between border and odd row background sligthtly */
1076 table {
1077 border: 1px solid #ddd;
1078 }
1079 td {
1080 border-top: 1px solid #ddd;
1081 }
1082 tr:nth-child(2n+1) > td {
1083 background-color: #f8f8f8;
1084 }
1085 /* Use style rules to govern display of the TOC. */
1086 @media screen and (max-width: 1023px) {
1087 #toc nav { display: none; }
1088 #toc.active nav { display: block; }
1089 }
1090 /* Add support for keepWithNext */
1091 .keepWithNext {
1092 break-after: avoid-page;
1093 break-after: avoid-page;
1094 }
1095 /* Add support for keepWithPrevious */
1096 .keepWithPrevious {
1097 break-before: avoid-page;
1098 }
1099 /* Change the approach to avoiding breaks inside artwork etc. */
1100 figure, pre, table, .artwork, .sourcecode {
1101 break-before: auto;
1102 break-after: auto;
1103 }
1104 /* Avoid breaks between <dt> and <dd> */
1105 dl {
1106 break-before: auto;
1107 break-inside: auto;
1108 }
1109 dt {
1110 break-before: auto;
1111 break-after: avoid-page;
1112 }
1113 dd {
1114 break-before: avoid-page;
1115 break-after: auto;
1116 orphans: 3;
1117 widows: 3
1118 }
1119 span.break, dd.break {
1120 margin-bottom: 0;
1121 min-height: 0;
1122 break-before: auto;
1123 break-inside: auto;
1124 break-after: auto;
1125 }
1126 /* Undo break-before ToC */
1127 @media print {
1128 #toc {
1129 break-before: auto;
1130 }
1131 }
1132 /* Text in compact lists should not get extra bottim margin space,
1133 since that would makes the list not compact */
1134 ul.compact p, .ulCompact p,
1135 ol.compact p, .olCompact p {
1136 margin: 0;
1137 }
1138 /* But the list as a whole needs the extra space at the end */
1139 section ul.compact,
1140 section .ulCompact,
1141 section ol.compact,
1142 section .olCompact {
1143 margin-bottom: 1em; /* same as p not within ul.compact etc. */
1144 }
1145 /* The tt and code background above interferes with for instance table cell
1146 backgrounds. Changed to something a bit more selective. */
1147 tt, code {
1148 background-color: transparent;
1149 }
1150 p tt, p code, li tt, li code {
1151 background-color: #f8f8f8;
1152 }
1153 /* Tweak the pre margin -- 0px doesn't come out well */
1154 pre {
1155 margin-top: 0.5px;
1156 }
1157 /* Tweak the comact list text */
1158 ul.compact, .ulCompact,
1159 ol.compact, .olCompact,
1160 dl.compact, .dlCompact {
1161 line-height: normal;
1162 }
1163 /* Don't add top margin for nested lists */
1164 li > ul, li > ol, li > dl,
1165 dd > ul, dd > ol, dd > dl,
1166 dl > dd > dl {
1167 margin-top: initial;
1168 }
1169 /* Elements that should not be rendered on the same line as a <dt> */
1170 /* This should match the element list in writer.text.TextWriter.render_dl() */
1171 dd > div.artwork:first-child,
1172 dd > aside:first-child,
1173 dd > figure:first-child,
1174 dd > ol:first-child,
1175 dd > div:first-child > pre.sourcecode,
1176 dd > table:first-child,
1177 dd > ul:first-child {
1178 clear: left;
1179 }
1180 /* fix for weird browser behaviour when <dd/> is empty */
1181 dt+dd:empty::before{
1182 content: "\00a0";
1183 }
1184 /* Make paragraph spacing inside <li> smaller than in body text, to fit better within the list */
1185 li > p {
1186 margin-bottom: 0.5em
1187 }
1188 /* Don't let p margin spill out from inside list items */
1189 li > p:last-of-type {
1190 margin-bottom: 0;
1191 }
1192 </style>
1193 <link href="rfc-local.css" rel="stylesheet" type="text/css">
1194 <link href="https://dx.doi.org/10.17487/rfc9070" rel="alternate">
1195 <link href="urn:issn:2070-1721" rel="alternate">
1196 <link href="https://datatracker.ietf.org/doc/draft-ietf-mpls-ldp-yang-09" rel="prev">
1197 </head>
1198 <body>
1199 <script src="https://www.rfc-editor.org/js/metadata.min.js"></script>
1200 <table class="ears">
1201 <thead><tr>
1202 <td class="left">RFC 9070</td>
1203 <td class="center">YANG Data Model for MPLS LDP</td>
1204 <td class="right">March 2022</td>
1205 </tr></thead>
1206 <tfoot><tr>
1207 <td class="left">Raza, et al.</td>
1208 <td class="center">Standards Track</td>
1209 <td class="right">[Page]</td>
1210 </tr></tfoot>
1211 </table>
1212 <div id="external-metadata" class="document-information"></div>
1213 <div id="internal-metadata" class="document-information">
1214 <dl id="identifiers">
1215 <dt class="label-stream">Stream:</dt>
1216 <dd class="stream">Internet Engineering Task Force (IETF)</dd>
1217 <dt class="label-rfc">RFC:</dt>
1218 <dd class="rfc"><a href="https://www.rfc-editor.org/rfc/rfc9070" class="eref">9070</a></dd>
1219 <dt class="label-category">Category:</dt>
1220 <dd class="category">Standards Track</dd>
1221 <dt class="label-published">Published:</dt>
1222 <dd class="published">
1223 <time datetime="2022-03" class="published">March 2022</time>
1224 </dd>
1225 <dt class="label-issn">ISSN:</dt>
1226 <dd class="issn">2070-1721</dd>
1227 <dt class="label-authors">Authors:</dt>
1228 <dd class="authors">
1229 <div class="author">
1230 <div class="author-name">K. Raza, <span class="editor">Ed.</span>
1231 </div>
1232 <div class="org">Cisco Systems</div>
1233 </div>
1234 <div class="author">
1235 <div class="author-name">R. Asati</div>
1236 <div class="org">Cisco Systems</div>
1237 </div>
1238 <div class="author">
1239 <div class="author-name">X. Liu</div>
1240 <div class="org">IBM Corporation</div>
1241 </div>
1242 <div class="author">
1243 <div class="author-name">S. Easale</div>
1244 <div class="org">Juniper Networks</div>
1245 </div>
1246 <div class="author">
1247 <div class="author-name">X. Chen</div>
1248 <div class="org">Huawei Technologies</div>
1249 </div>
1250 <div class="author">
1251 <div class="author-name">H. Shah</div>
1252 <div class="org">Ciena Corporation</div>
1253 </div>
1254 </dd>
1255 </dl>
1256 </div>
1257 <h1 id="rfcnum">RFC 9070</h1>
1258 <h1 id="title">YANG Data Model for MPLS LDP</h1>
1259 <section id="section-abstract">
1260 <h2 id="abstract"><a href="#abstract" class="selfRef">Abstract</a></h2>
1261 <p id="section-abstract-1">This document describes a YANG data model for the Multiprotocol Label Switching (MPLS)
1262 Label Distribution Protocol (LDP). The model also serves as the base model
1263 to define the Multipoint LDP (mLDP) model.<a href="#section-abstract-1" class="pilcrow">¶</a></p>
1264 <p id="section-abstract-2"> The YANG modules in this document conform to the Network Management
1265 Datastore Architecture (NMDA).<a href="#section-abstract-2" class="pilcrow">¶</a></p>
1266 </section>
1267 <div id="status-of-memo">
1268 <section id="section-boilerplate.1">
1269 <h2 id="name-status-of-this-memo">
1270 <a href="#name-status-of-this-memo" class="section-name selfRef">Status of This Memo</a>
1271 </h2>
1272 <p id="section-boilerplate.1-1">
1273 This is an Internet Standards Track document.<a href="#section-boilerplate.1-1" class="pilcrow">¶</a></p>
1274 <p id="section-boilerplate.1-2">
1275 This document is a product of the Internet Engineering Task Force
1276 (IETF). It represents the consensus of the IETF community. It has
1277 received public review and has been approved for publication by
1278 the Internet Engineering Steering Group (IESG). Further
1279 information on Internet Standards is available in Section 2 of
1280 RFC 7841.<a href="#section-boilerplate.1-2" class="pilcrow">¶</a></p>
1281 <p id="section-boilerplate.1-3">
1282 Information about the current status of this document, any
1283 errata, and how to provide feedback on it may be obtained at
1284 <span><a href="https://www.rfc-editor.org/info/rfc9070">https://www.rfc-editor.org/info/rfc9070</a></span>.<a href="#section-boilerplate.1-3" class="pilcrow">¶</a></p>
1285 </section>
1286 </div>
1287 <div id="copyright">
1288 <section id="section-boilerplate.2">
1289 <h2 id="name-copyright-notice">
1290 <a href="#name-copyright-notice" class="section-name selfRef">Copyright Notice</a>
1291 </h2>
1292 <p id="section-boilerplate.2-1">
1293 Copyright (c) 2022 IETF Trust and the persons identified as the
1294 document authors. All rights reserved.<a href="#section-boilerplate.2-1" class="pilcrow">¶</a></p>
1295 <p id="section-boilerplate.2-2">
1296 This document is subject to BCP 78 and the IETF Trust's Legal
1297 Provisions Relating to IETF Documents
1298 (<span><a href="https://trustee.ietf.org/license-info">https://trustee.ietf.org/license-info</a></span>) in effect on the date of
1299 publication of this document. Please review these documents
1300 carefully, as they describe your rights and restrictions with
1301 respect to this document. Code Components extracted from this
1302 document must include Revised BSD License text as described in
1303 Section 4.e of the Trust Legal Provisions and are provided without
1304 warranty as described in the Revised BSD License.<a href="#section-boilerplate.2-2" class="pilcrow">¶</a></p>
1305 </section>
1306 </div>
1307 <div id="toc">
1308 <section id="section-toc.1">
1309 <a href="#" onclick="scroll(0,0)" class="toplink">▲</a><h2 id="name-table-of-contents">
1310 <a href="#name-table-of-contents" class="section-name selfRef">Table of Contents</a>
1311 </h2>
1312 <nav class="toc"><ul class="compact toc ulBare ulEmpty">
1313 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.1">
1314 <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>
1315 <ul class="compact toc ulBare ulEmpty">
1316 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.1.2.1">
1317 <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-base-and-extended" class="xref">Base and Extended</a></p>
1318 </li>
1319 </ul>
1320 </li>
1321 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.2">
1322 <p id="section-toc.1-1.2.1" class="keepWithNext"><a href="#section-2" class="xref">2</a>.  <a href="#name-specification-of-requiremen" class="xref">Specification of Requirements</a></p>
1323 </li>
1324 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.3">
1325 <p id="section-toc.1-1.3.1"><a href="#section-3" class="xref">3</a>.  <a href="#name-overview" class="xref">Overview</a></p>
1326 </li>
1327 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.4">
1328 <p id="section-toc.1-1.4.1"><a href="#section-4" class="xref">4</a>.  <a href="#name-the-complete-tree" class="xref">The Complete Tree</a></p>
1329 </li>
1330 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.5">
1331 <p id="section-toc.1-1.5.1"><a href="#section-5" class="xref">5</a>.  <a href="#name-configuration" class="xref">Configuration</a></p>
1332 <ul class="compact toc ulBare ulEmpty">
1333 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.5.2.1">
1334 <p id="section-toc.1-1.5.2.1.1"><a href="#section-5.1" class="xref">5.1</a>.  <a href="#name-configuration-hierarchy" class="xref">Configuration Hierarchy</a></p>
1335 <ul class="compact toc ulBare ulEmpty">
1336 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.5.2.1.2.1">
1337 <p id="section-toc.1-1.5.2.1.2.1.1"><a href="#section-5.1.1" class="xref">5.1.1</a>.  <a href="#name-global-parameters" class="xref">Global Parameters</a></p>
1338 </li>
1339 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.5.2.1.2.2">
1340 <p id="section-toc.1-1.5.2.1.2.2.1"><a href="#section-5.1.2" class="xref">5.1.2</a>.  <a href="#name-capabilities-parameters" class="xref">Capabilities Parameters</a></p>
1341 </li>
1342 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.5.2.1.2.3">
1343 <p id="section-toc.1-1.5.2.1.2.3.1"><a href="#section-5.1.3" class="xref">5.1.3</a>.  <a href="#name-per-address-family-paramete" class="xref">Per-Address-Family Parameters</a></p>
1344 </li>
1345 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.5.2.1.2.4">
1346 <p id="section-toc.1-1.5.2.1.2.4.1"><a href="#section-5.1.4" class="xref">5.1.4</a>.  <a href="#name-hello-discovery-parameters" class="xref">Hello Discovery Parameters</a></p>
1347 </li>
1348 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.5.2.1.2.5">
1349 <p id="section-toc.1-1.5.2.1.2.5.1"><a href="#section-5.1.5" class="xref">5.1.5</a>.  <a href="#name-peer-parameters" class="xref">Peer Parameters</a></p>
1350 </li>
1351 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.5.2.1.2.6">
1352 <p id="section-toc.1-1.5.2.1.2.6.1"><a href="#section-5.1.6" class="xref">5.1.6</a>.  <a href="#name-forwarding-parameters" class="xref">Forwarding Parameters</a></p>
1353 </li>
1354 </ul>
1355 </li>
1356 </ul>
1357 </li>
1358 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.6">
1359 <p id="section-toc.1-1.6.1"><a href="#section-6" class="xref">6</a>.  <a href="#name-operational-state" class="xref">Operational State</a></p>
1360 <ul class="compact toc ulBare ulEmpty">
1361 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.6.2.1">
1362 <p id="section-toc.1-1.6.2.1.1"><a href="#section-6.1" class="xref">6.1</a>.  <a href="#name-adjacency-state" class="xref">Adjacency State</a></p>
1363 </li>
1364 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.6.2.2">
1365 <p id="section-toc.1-1.6.2.2.1"><a href="#section-6.2" class="xref">6.2</a>.  <a href="#name-peer-state" class="xref">Peer State</a></p>
1366 </li>
1367 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.6.2.3">
1368 <p id="section-toc.1-1.6.2.3.1"><a href="#section-6.3" class="xref">6.3</a>.  <a href="#name-bindings-state" class="xref">Bindings State</a></p>
1369 </li>
1370 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.6.2.4">
1371 <p id="section-toc.1-1.6.2.4.1"><a href="#section-6.4" class="xref">6.4</a>.  <a href="#name-capabilities-state" class="xref">Capabilities State</a></p>
1372 </li>
1373 </ul>
1374 </li>
1375 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.7">
1376 <p id="section-toc.1-1.7.1"><a href="#section-7" class="xref">7</a>.  <a href="#name-notifications" class="xref">Notifications</a></p>
1377 </li>
1378 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.8">
1379 <p id="section-toc.1-1.8.1"><a href="#section-8" class="xref">8</a>.  <a href="#name-action" class="xref">Action</a></p>
1380 </li>
1381 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.9">
1382 <p id="section-toc.1-1.9.1"><a href="#section-9" class="xref">9</a>.  <a href="#name-yang-specification" class="xref">YANG Specification</a></p>
1383 <ul class="compact toc ulBare ulEmpty">
1384 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.9.2.1">
1385 <p id="section-toc.1-1.9.2.1.1"><a href="#section-9.1" class="xref">9.1</a>.  <a href="#name-base" class="xref">Base</a></p>
1386 </li>
1387 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.9.2.2">
1388 <p id="section-toc.1-1.9.2.2.1"><a href="#section-9.2" class="xref">9.2</a>.  <a href="#name-extended" class="xref">Extended</a></p>
1389 </li>
1390 </ul>
1391 </li>
1392 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.10">
1393 <p id="section-toc.1-1.10.1"><a href="#section-10" class="xref">10</a>. <a href="#name-security-considerations" class="xref">Security Considerations</a></p>
1394 <ul class="compact toc ulBare ulEmpty">
1395 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.10.2.1">
1396 <p id="section-toc.1-1.10.2.1.1"><a href="#section-10.1" class="xref">10.1</a>.  <a href="#name-yang-data-model" class="xref">YANG Data Model</a></p>
1397 <ul class="compact toc ulBare ulEmpty">
1398 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.10.2.1.2.1">
1399 <p id="section-toc.1-1.10.2.1.2.1.1"><a href="#section-10.1.1" class="xref">10.1.1</a>.  <a href="#name-writable-nodes" class="xref">Writable Nodes</a></p>
1400 </li>
1401 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.10.2.1.2.2">
1402 <p id="section-toc.1-1.10.2.1.2.2.1"><a href="#section-10.1.2" class="xref">10.1.2</a>.  <a href="#name-readable-nodes" class="xref">Readable Nodes</a></p>
1403 </li>
1404 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.10.2.1.2.3">
1405 <p id="section-toc.1-1.10.2.1.2.3.1"><a href="#section-10.1.3" class="xref">10.1.3</a>.  <a href="#name-rpc-operations" class="xref">RPC Operations</a></p>
1406 </li>
1407 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.10.2.1.2.4">
1408 <p id="section-toc.1-1.10.2.1.2.4.1"><a href="#section-10.1.4" class="xref">10.1.4</a>.  <a href="#name-notifications-2" class="xref">Notifications</a></p>
1409 </li>
1410 </ul>
1411 </li>
1412 </ul>
1413 </li>
1414 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.11">
1415 <p id="section-toc.1-1.11.1"><a href="#section-11" class="xref">11</a>. <a href="#name-iana-considerations" class="xref">IANA Considerations</a></p>
1416 </li>
1417 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.12">
1418 <p id="section-toc.1-1.12.1"><a href="#section-12" class="xref">12</a>. <a href="#name-normative-references" class="xref">Normative References</a></p>
1419 </li>
1420 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.13">
1421 <p id="section-toc.1-1.13.1"><a href="#section-13" class="xref">13</a>. <a href="#name-informative-references" class="xref">Informative References</a></p>
1422 </li>
1423 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.14">
1424 <p id="section-toc.1-1.14.1"><a href="#appendix-A" class="xref">Appendix A</a>.  <a href="#name-data-tree-example" class="xref">Data Tree Example</a></p>
1425 </li>
1426 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.15">
1427 <p id="section-toc.1-1.15.1"><a href="#appendix-B" class="xref"></a><a href="#name-acknowledgments" class="xref">Acknowledgments</a></p>
1428 </li>
1429 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.16">
1430 <p id="section-toc.1-1.16.1"><a href="#appendix-C" class="xref"></a><a href="#name-contributors" class="xref">Contributors</a></p>
1431 </li>
1432 <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.17">
1433 <p id="section-toc.1-1.17.1"><a href="#appendix-D" class="xref"></a><a href="#name-authors-addresses" class="xref">Authors' Addresses</a></p>
1434 </li>
1435 </ul>
1436 </nav>
1437 </section>
1438 </div>
1439 <section id="section-1">
1440 <h2 id="name-introduction">
1441 <a href="#section-1" class="section-number selfRef">1. </a><a href="#name-introduction" class="section-name selfRef">Introduction</a>
1442 </h2>
1443 <p id="section-1-1">The Network Configuration Protocol (NETCONF) <span>[<a href="#RFC6241" class="xref">RFC6241</a>]</span>
1444 is one of the network management protocols that defines mechanisms to
1445 manage network devices. YANG <span>[<a href="#RFC6020" class="xref">RFC6020</a>]</span> <span>[<a href="#RFC7950" class="xref">RFC7950</a>]</span> is a modular language that represents data structures
1446 in an XML tree format and is used as a data modeling language for
1447 NETCONF.<a href="#section-1-1" class="pilcrow">¶</a></p>
1448 <p id="section-1-2"> This document introduces a YANG data model for the MPLS Label
1449 Distribution Protocol (LDP) <span>[<a href="#RFC5036" class="xref">RFC5036</a>]</span>. This model also
1450 covers LDP IPv6 <span>[<a href="#RFC7552" class="xref">RFC7552</a>]</span> and LDP capability <span>[<a href="#RFC5561" class="xref">RFC5561</a>]</span> specifications.<a href="#section-1-2" class="pilcrow">¶</a></p>
1451 <p id="section-1-3"> The data model is defined for the following constructs that are used for managing the protocol:<a href="#section-1-3" class="pilcrow">¶</a></p>
1452 <ul class="normal">
1453 <li class="normal" id="section-1-4.1"> Configuration<a href="#section-1-4.1" class="pilcrow">¶</a>
1454 </li>
1455 <li class="normal" id="section-1-4.2"> Operational State<a href="#section-1-4.2" class="pilcrow">¶</a>
1456 </li>
1457 <li class="normal" id="section-1-4.3"> Executables (Actions)<a href="#section-1-4.3" class="pilcrow">¶</a>
1458 </li>
1459 <li class="normal" id="section-1-4.4"> Notifications<a href="#section-1-4.4" class="pilcrow">¶</a>
1460 </li>
1461 </ul>
1462 <p id="section-1-5"> This document is organized to define the data model for each of the above constructs
1463 in the sequence as listed above.<a href="#section-1-5" class="pilcrow">¶</a></p>
1464 <section id="section-1.1">
1465 <h3 id="name-base-and-extended">
1466 <a href="#section-1.1" class="section-number selfRef">1.1. </a><a href="#name-base-and-extended" class="section-name selfRef">Base and Extended</a>
1467 </h3>
1468 <p id="section-1.1-1"> The configuration and state items are divided into the following two broad categories:<a href="#section-1.1-1" class="pilcrow">¶</a></p>
1469 <ul class="normal">
1470 <li class="normal" id="section-1.1-2.1"> Base<a href="#section-1.1-2.1" class="pilcrow">¶</a>
1471 </li>
1472 <li class="normal" id="section-1.1-2.2"> Extended<a href="#section-1.1-2.2" class="pilcrow">¶</a>
1473 </li>
1474 </ul>
1475 <p id="section-1.1-3"> The "base" category contains the basic and fundamental features that are
1476 covered in LDP base specification <span>[<a href="#RFC5036" class="xref">RFC5036</a>]</span> and constitute the
1477 minimum requirements for a typical base LDP deployment, whereas the "extended"
1478 category contains other non-base features. All the items in a base category
1479 are mandatory and, hence, no "if-feature" is allowed under the "base" category.
1480 The base and extended categories are defined in their own modules as described
1481 later.<a href="#section-1.1-3" class="pilcrow">¶</a></p>
1482 <p id="section-1.1-4"> The examples of a base feature include the configuration of LDP lsr-id,
1483 enabling LDP interfaces, setting passwords for LDP sessions, etc., whereas the
1484 examples of an extended feature include inbound/outbound label policies, IGP
1485 Sync <span>[<a href="#RFC5443" class="xref">RFC5443</a>]</span>, downstream on demand, etc. It is worth
1486 highlighting that LDP IPv6 <span>[<a href="#RFC7552" class="xref">RFC7552</a>]</span> is also categorized as an
1487 extended feature.<a href="#section-1.1-4" class="pilcrow">¶</a></p>
1488 <p id="section-1.1-5"> While "base" model support will suffice for small deployments, it is expected that large deployments will require both "base" and "extended" model support from the vendors.<a href="#section-1.1-5" class="pilcrow">¶</a></p>
1489 </section>
1490 </section>
1491 <section id="section-2">
1492 <h2 id="name-specification-of-requiremen">
1493 <a href="#section-2" class="section-number selfRef">2. </a><a href="#name-specification-of-requiremen" class="section-name selfRef">Specification of Requirements</a>
1494 </h2>
1495 <p id="section-2-1"> In this document, the word "IP" is used to refer to both IPv4 and
1496 IPv6 unless otherwise explicitly stated. For example, "IP address
1497 family" should be read as "IPv4 and/or IPv6 address family".<a href="#section-2-1" class="pilcrow">¶</a></p>
1498 </section>
1499 <section id="section-3">
1500 <h2 id="name-overview">
1501 <a href="#section-3" class="section-number selfRef">3. </a><a href="#name-overview" class="section-name selfRef">Overview</a>
1502 </h2>
1503 <p id="section-3-1"> This document defines two new modules for LDP YANG support:<a href="#section-3-1" class="pilcrow">¶</a></p>
1504 <span class="break"></span><dl class="dlNewline" id="section-3-2">
1505 <dt id="section-3-2.1">"ietf-mpls-ldp"
1506 </dt>
1507 <dd style="margin-left: 1.5em" id="section-3-2.2">A module that specifies the base LDP features and augments
1508 /rt:routing/rt:control-plane-protocols/rt:control-plane-protocol defined in
1509 <span>[<a href="#RFC8349" class="xref">RFC8349</a>]</span>. We define the new identity 'mpls-ldp' for LDP; the
1510 model allows only a single instance of 'mpls-ldp'.<a href="#section-3-2.2" class="pilcrow">¶</a>
1511 </dd>
1512 <dd class="break"></dd>
1513 <dt id="section-3-2.3">"ietf-mpls-ldp-extended"
1514 </dt>
1515 <dd style="margin-left: 1.5em" id="section-3-2.4">A module that specifies the extended LDP features and augments the base
1516 LDP module.<a href="#section-3-2.4" class="pilcrow">¶</a>
1517 </dd>
1518 <dd class="break"></dd>
1519 </dl>
1520 <p id="section-3-3"> It is to be noted that the mLDP YANG data model <span>[<a href="#I-D.ietf-mpls-mldp-yang" class="xref">MPLS-MLDP-YANG</a>]</span> augments LDP base and extended
1521 modules to specify the mLDP-specific base and extended features.<a href="#section-3-3" class="pilcrow">¶</a></p>
1522 <p id="section-3-4">
1523 There are four types of containers in our module(s):<a href="#section-3-4" class="pilcrow">¶</a></p>
1524 <ul class="normal">
1525 <li class="normal" id="section-3-5.1"> Read-write parameters for configuration (<a href="#section_ldp_cfg" class="xref">Section 5</a>)<a href="#section-3-5.1" class="pilcrow">¶</a>
1526 </li>
1527 <li class="normal" id="section-3-5.2"> Read-only parameters for operational state (<a href="#section_ldp_oper" class="xref">Section 6</a>)<a href="#section-3-5.2" class="pilcrow">¶</a>
1528 </li>
1529 <li class="normal" id="section-3-5.3"> Notifications for events (<a href="#section_ldp_notif" class="xref">Section 7</a>)<a href="#section-3-5.3" class="pilcrow">¶</a>
1530 </li>
1531 <li class="normal" id="section-3-5.4"> RPCs for executing commands to perform some action (<a href="#section_ldp_action" class="xref">Section 8</a>)<a href="#section-3-5.4" class="pilcrow">¶</a>
1532 </li>
1533 </ul>
1534 <p id="section-3-6">
1535 The modules in this document conform to the Network Management
1536 Datastore Architecture (NMDA) defined in <span>[<a href="#RFC8342" class="xref">RFC8342</a>]</span>.
1537 The operational state data is combined with the associated
1538 configuration data in the same hierarchy <span>[<a href="#RFC8407" class="xref">RFC8407</a>]</span>.
1539 When protocol states are retrieved from the NMDA operational state
1540 datastore, the returned states cover all "config true" (rw) and
1541 "config false" (ro) nodes defined in the schema.<a href="#section-3-6" class="pilcrow">¶</a></p>
1542 <p id="section-3-7">The following diagram depicts high-level LDP YANG tree organization and hierarchy:<a href="#section-3-7" class="pilcrow">¶</a></p>
1543 <span id="name-ldp-yang-tree-organization"></span><div id="LDPYangTreeHL">
1544 <figure id="figure-1">
1545 <div id="section-3-8.1">
1546 <pre class="lang-yangtree sourcecode">
1547 +-- rw routing
1548 +-- rw control-plane-protocols
1549 +-- rw control-plane-protocol
1550 +-- rw mpls-ldp
1551 +-- rw ...
1552 +-- rw ... // base
1553 | +-- rw ...
1554 | +-- ro ...
1555 | +--
1556 +-- ro ...
1557 | +-- ro ...
1558 | +-- ro ...
1559 | +--
1560 +-- rw ldp-ext: .... // extended
1561 | +-- rw ...
1562 | +-- ro ...
1563 | +--
1564 +-- ro ...
1565 +-- ro ...
1566 +-- ro ...
1567
1568
1569 rpcs:
1570 +-- x mpls-ldp-some_action
1571 +-- x . . . . .
1572
1573 notifications:
1574 +--- n mpls-ldp-some_event
1575 +--- n ...
1576 </pre>
1577 </div>
1578 <figcaption><a href="#figure-1" class="selfRef">Figure 1</a>:
1579 <a href="#name-ldp-yang-tree-organization" class="selfRef">LDP YANG Tree Organization</a>
1580 </figcaption></figure>
1581 </div>
1582 <p id="section-3-9"> Before going into data model details, it is important to take
1583 note of the following points:<a href="#section-3-9" class="pilcrow">¶</a></p>
1584 <ul class="normal">
1585 <li class="normal" id="section-3-10.1"> This model aims to address only the core LDP parameters as
1586 per RFC specification, as well as well-known and widely deployed
1587 manageability controls (such as label filtering policies to apply
1588 filtering rules on the assignment, advertisement, and acceptance
1589 for label bindings). Any vendor-specific feature should be
1590 defined in a vendor-specific augmentation of this model.<a href="#section-3-10.1" class="pilcrow">¶</a>
1591 </li>
1592 <li class="normal" id="section-3-10.2"> Multi-topology LDP <span>[<a href="#RFC7307" class="xref">RFC7307</a>]</span> is beyond the scope of this document.<a href="#section-3-10.2" class="pilcrow">¶</a>
1593 </li>
1594 <li class="normal" id="section-3-10.3"> This model does not cover any applications running on top of
1595 LDP, nor does it cover any Operations, Administration, and
1596 Maintenance (OAM) procedures for LDP.<a href="#section-3-10.3" class="pilcrow">¶</a>
1597 </li>
1598 <li class="normal" id="section-3-10.4">This model is a VRF-centric model. It is important to note
1599 that <span>[<a href="#RFC4364" class="xref">RFC4364</a>]</span> defines VPN Routing and Forwarding
1600 (VRF) tables and default forwarding tables as different; however,
1601 from a YANG modeling perspective, this introduces unnecessary
1602 complications; hence, we are treating the default forwarding table
1603 as just another VRF.<a href="#section-3-10.4" class="pilcrow">¶</a>
1604 </li>
1605 <li class="normal" id="section-3-10.5"> A "network-instance", as defined in <span>[<a href="#RFC8529" class="xref">RFC8529</a>]</span>,
1606 refers to a VRF instance (both default and non-default) within the
1607 scope of this model.<a href="#section-3-10.5" class="pilcrow">¶</a>
1608 </li>
1609 <li class="normal" id="section-3-10.6"> This model supports two address families, namely, "ipv4" and "ipv6".<a href="#section-3-10.6" class="pilcrow">¶</a>
1610 </li>
1611 <li class="normal" id="section-3-10.7"> This model assumes platform-wide label space (i.e., label
1612 space Id of zero). However, when upstream label assignment <span>[<a href="#RFC6389" class="xref">RFC6389</a>]</span> is in use, an upstream assigned label is looked
1613 up in a Context-Specific Label Space as defined in <span>[<a href="#RFC5331" class="xref">RFC5331</a>]</span>.<a href="#section-3-10.7" class="pilcrow">¶</a>
1614 </li>
1615 <li class="normal" id="section-3-10.8"> The label and peer policies (including filters) are defined
1616 using prefix-set and neighbor-set, respectively, as defined in the
1617 routing-policy model <span>[<a href="#RFC9067" class="xref">RFC9067</a>]</span>.<a href="#section-3-10.8" class="pilcrow">¶</a>
1618 </li>
1619 <li class="normal" id="section-3-10.9">
1620 <p id="section-3-10.9.1"> This model uses the terms LDP "neighbor/adjacency",
1621 "session", and "peer" with the following semantics:<a href="#section-3-10.9.1" class="pilcrow">¶</a></p>
1622 <span class="break"></span><dl class="dlParallel" id="section-3-10.9.2">
1623 <dt id="section-3-10.9.2.1">Neighbor/Adjacency:
1624 </dt>
1625 <dd style="margin-left: 1.5em" id="section-3-10.9.2.2">An LDP-enabled Label Switching Router (LSR) that is discovered through LDP
1626 discovery mechanisms.<a href="#section-3-10.9.2.2" class="pilcrow">¶</a>
1627 </dd>
1628 <dd class="break"></dd>
1629 <dt id="section-3-10.9.2.3">Session:
1630 </dt>
1631 <dd style="margin-left: 1.5em" id="section-3-10.9.2.4">An LDP neighbor with whom a TCP connection has been established.<a href="#section-3-10.9.2.4" class="pilcrow">¶</a>
1632 </dd>
1633 <dd class="break"></dd>
1634 <dt id="section-3-10.9.2.5">Peer:
1635 </dt>
1636 <dd style="margin-left: 1.5em" id="section-3-10.9.2.6">An LDP session that has successfully progressed beyond its initialization
1637 phase and is either already exchanging the bindings or is ready to do so.<a href="#section-3-10.9.2.6" class="pilcrow">¶</a>
1638 </dd>
1639 <dd class="break"></dd>
1640 </dl>
1641 <p id="section-3-10.9.3">
1642 It is to be noted that LDP Graceful Restart (GR) mechanisms
1643 defined in <span>[<a href="#RFC3478" class="xref">RFC3478</a>]</span> allow keeping the exchanged
1644 bindings for some time after a session goes down with a peer. We
1645 refer to such a state as belonging to a "stale" peer, i.e., keeping peer
1646 bindings from a peer with whom currently there is either no
1647 connection established or connection is established but the GR session
1648 is in recovery state.
1649
1650 When used in this document, the above terms will refer strictly to
1651 the semantics and definitions defined for them.<a href="#section-3-10.9.3" class="pilcrow">¶</a></p>
1652 </li>
1653 </ul>
1654 <p id="section-3-11">
1655 A simplified graphical tree representation of base and extended LDP
1656 YANG data models is presented in <a href="#ConsolidatedTree" class="xref">Figure 2</a>.
1657 The meaning of the symbols in these tree diagrams is defined in
1658 <span>[<a href="#RFC8340" class="xref">RFC8340</a>]</span>.<a href="#section-3-11" class="pilcrow">¶</a></p>
1659 <p id="section-3-12">
1660 The actual YANG specification for base and extended modules is
1661 captured in <a href="#YANG" class="xref">Section 9</a>.<a href="#section-3-12" class="pilcrow">¶</a></p>
1662 <p id="section-3-13">
1663 While presenting the YANG tree view and actual specification, this
1664 document assumes readers are familiar with the concepts of YANG
1665 modeling, its presentation, and its compilation.<a href="#section-3-13" class="pilcrow">¶</a></p>
1666 </section>
1667 <section id="section-4">
1668 <h2 id="name-the-complete-tree">
1669 <a href="#section-4" class="section-number selfRef">4. </a><a href="#name-the-complete-tree" class="section-name selfRef">The Complete Tree</a>
1670 </h2>
1671 <p id="section-4-1">The following is a complete tree representation of configuration,
1672 state, notification, and RPC items under LDP base and extended
1673 modules.<a href="#section-4-1" class="pilcrow">¶</a></p>
1674 <span id="name-complete-tree"></span><div id="ConsolidatedTree">
1675 <figure id="figure-2">
1676 <div id="section-4-2.1">
1677 <pre class="lang-yangtree sourcecode">
1678 module: ietf-mpls-ldp
1679 augment /rt:routing/rt:control-plane-protocols
1680 /rt:control-plane-protocol:
1681 +--rw mpls-ldp
1682 +--rw global
1683 | +--rw capability
1684 | | +--rw ldp-ext:end-of-lib {capability-end-of-lib}?
1685 | | | +--rw ldp-ext:enabled? boolean
1686 | | +--rw ldp-ext:typed-wildcard-fec
1687 | | | {capability-typed-wildcard-fec}?
1688 | | | +--rw ldp-ext:enabled? boolean
1689 | | +--rw ldp-ext:upstream-label-assignment
1690 | | {capability-upstream-label-assignment}?
1691 | | +--rw ldp-ext:enabled? boolean
1692 | +--rw graceful-restart
1693 | | +--rw enabled? boolean
1694 | | +--rw reconnect-time? uint16
1695 | | +--rw recovery-time? uint16
1696 | | +--rw forwarding-holdtime? uint16
1697 | | +--rw ldp-ext:helper-enabled? boolean
1698 | | {graceful-restart-helper-mode}?
1699 | +--rw lsr-id?
1700 | | rt-types:router-id
1701 | +--rw address-families
1702 | | +--rw ipv4!
1703 | | | +--rw enabled? boolean
1704 | | | +--ro label-distribution-control-mode? enumeration
1705 | | | +--ro bindings
1706 | | | | +--ro address* [address]
1707 | | | | | +--ro address inet:ipv4-address
1708 | | | | | +--ro advertisement-type? advertised-received
1709 | | | | | +--ro peer
1710 | | | | | +--ro lsr-id? leafref
1711 | | | | | +--ro label-space-id? leafref
1712 | | | | +--ro fec-label* [fec]
1713 | | | | +--ro fec inet:ipv4-prefix
1714 | | | | +--ro peer*
1715 | | | | [lsr-id label-space-id advertisement-type]
1716 | | | | +--ro lsr-id leafref
1717 | | | | +--ro label-space-id leafref
1718 | | | | +--ro advertisement-type
1719 | | | | | advertised-received
1720 | | | | +--ro label?
1721 | | | | | rt-types:mpls-label
1722 | | | | +--ro used-in-forwarding? boolean
1723 | | | +--rw ldp-ext:label-policy
1724 | | | | +--rw ldp-ext:advertise
1725 | | | | | +--rw ldp-ext:egress-explicit-null
1726 | | | | | | +--rw ldp-ext:enabled? boolean
1727 | | | | | +--rw ldp-ext:prefix-list?
1728 | | | | | prefix-list-ref
1729 | | | | +--rw ldp-ext:accept
1730 | | | | | +--rw ldp-ext:prefix-list? prefix-list-ref
1731 | | | | +--rw ldp-ext:assign
1732 | | | | {policy-label-assignment-config}?
1733 | | | | +--rw ldp-ext:independent-mode
1734 | | | | | +--rw ldp-ext:prefix-list? prefix-list-ref
1735 | | | | +--rw ldp-ext:ordered-mode
1736 | | | | {policy-ordered-label-config}?
1737 | | | | +--rw ldp-ext:egress-prefix-list?
1738 | | | | prefix-list-ref
1739 | | | +--rw ldp-ext:transport-address?
1740 | | | inet:ipv4-address
1741 | | +--rw ldp-ext:ipv6!
1742 | | +--rw ldp-ext:enabled?
1743 | | | boolean
1744 | | +--rw ldp-ext:label-policy
1745 | | | +--rw ldp-ext:advertise
1746 | | | | +--rw ldp-ext:egress-explicit-null
1747 | | | | | +--rw ldp-ext:enabled? boolean
1748 | | | | +--rw ldp-ext:prefix-list?
1749 | | | | prefix-list-ref
1750 | | | +--rw ldp-ext:accept
1751 | | | | +--rw ldp-ext:prefix-list? prefix-list-ref
1752 | | | +--rw ldp-ext:assign
1753 | | | {policy-label-assignment-config}?
1754 | | | +--rw ldp-ext:independent-mode
1755 | | | | +--rw ldp-ext:prefix-list? prefix-list-ref
1756 | | | +--rw ldp-ext:ordered-mode
1757 | | | {policy-ordered-label-config}?
1758 | | | +--rw ldp-ext:egress-prefix-list?
1759 | | | prefix-list-ref
1760 | | +--rw ldp-ext:transport-address
1761 | | | inet:ipv6-address
1762 | | +--ro ldp-ext:label-distribution-control-mode?
1763 | | | enumeration
1764 | | +--ro ldp-ext:bindings
1765 | | +--ro ldp-ext:address* [address]
1766 | | | +--ro ldp-ext:address
1767 | | | | inet:ipv6-address
1768 | | | +--ro ldp-ext:advertisement-type?
1769 | | | | advertised-received
1770 | | | +--ro ldp-ext:peer
1771 | | | +--ro ldp-ext:lsr-id? leafref
1772 | | | +--ro ldp-ext:label-space-id? leafref
1773 | | +--ro ldp-ext:fec-label* [fec]
1774 | | +--ro ldp-ext:fec inet:ipv6-prefix
1775 | | +--ro ldp-ext:peer*
1776 | | [lsr-id label-space-id advertisement-type]
1777 | | +--ro ldp-ext:lsr-id leafref
1778 | | +--ro ldp-ext:label-space-id leafref
1779 | | +--ro ldp-ext:advertisement-type
1780 | | | advertised-received
1781 | | +--ro ldp-ext:label?
1782 | | | rt-types:mpls-label
1783 | | +--ro ldp-ext:used-in-forwarding? boolean
1784 | +--rw ldp-ext:forwarding-nexthop
1785 | | {forwarding-nexthop-config}?
1786 | | +--rw ldp-ext:interfaces
1787 | | +--rw ldp-ext:interface* [name]
1788 | | +--rw ldp-ext:name if:interface-ref
1789 | | +--rw ldp-ext:address-family* [afi]
1790 | | +--rw ldp-ext:afi identityref
1791 | | +--rw ldp-ext:ldp-disable? boolean
1792 | +--rw ldp-ext:igp-synchronization-delay? uint16
1793 +--rw discovery
1794 | +--rw interfaces
1795 | | +--rw hello-holdtime? uint16
1796 | | +--rw hello-interval? uint16
1797 | | +--rw interface* [name]
1798 | | +--rw name
1799 | | | if:interface-ref
1800 | | +--ro next-hello? uint16
1801 | | +--rw address-families
1802 | | | +--rw ipv4!
1803 | | | | +--rw enabled? boolean
1804 | | | | +--ro hello-adjacencies
1805 | | | | | +--ro hello-adjacency* [adjacent-address]
1806 | | | | | +--ro adjacent-address
1807 | | | | | | inet:ipv4-address
1808 | | | | | +--ro flag* identityref
1809 | | | | | +--ro hello-holdtime
1810 | | | | | | +--ro adjacent? uint16
1811 | | | | | | +--ro negotiated? uint16
1812 | | | | | | +--ro remaining? uint16
1813 | | | | | +--ro next-hello? uint16
1814 | | | | | +--ro statistics
1815 | | | | | | +--ro discontinuity-time
1816 | | | | | | | yang:date-and-time
1817 | | | | | | +--ro hello-received?
1818 | | | | | | | yang:counter64
1819 | | | | | | +--ro hello-dropped?
1820 | | | | | | yang:counter64
1821 | | | | | +--ro peer
1822 | | | | | +--ro lsr-id? leafref
1823 | | | | | +--ro label-space-id? leafref
1824 | | | | +--rw ldp-ext:transport-address? union
1825 | | | +--rw ldp-ext:ipv6!
1826 | | | +--rw ldp-ext:enabled? boolean
1827 | | | +--ro ldp-ext:hello-adjacencies
1828 | | | | +--ro ldp-ext:hello-adjacency*
1829 | | | | [adjacent-address]
1830 | | | | +--ro ldp-ext:adjacent-address
1831 | | | | | inet:ipv6-address
1832 | | | | +--ro ldp-ext:flag*
1833 | | | | | identityref
1834 | | | | +--ro ldp-ext:hello-holdtime
1835 | | | | | +--ro ldp-ext:adjacent? uint16
1836 | | | | | +--ro ldp-ext:negotiated? uint16
1837 | | | | | +--ro ldp-ext:remaining? uint16
1838 | | | | +--ro ldp-ext:next-hello? uint16
1839 | | | | +--ro ldp-ext:statistics
1840 | | | | | +--ro ldp-ext:discontinuity-time
1841 | | | | | | yang:date-and-time
1842 | | | | | +--ro ldp-ext:hello-received?
1843 | | | | | | yang:counter64
1844 | | | | | +--ro ldp-ext:hello-dropped?
1845 | | | | | yang:counter64
1846 | | | | +--ro ldp-ext:peer
1847 | | | | +--ro ldp-ext:lsr-id? leafref
1848 | | | | +--ro ldp-ext:label-space-id? leafref
1849 | | | +--rw ldp-ext:transport-address? union
1850 | | +--rw ldp-ext:hello-holdtime? uint16
1851 | | | {per-interface-timer-config}?
1852 | | +--rw ldp-ext:hello-interval? uint16
1853 | | | {per-interface-timer-config}?
1854 | | +--rw ldp-ext:igp-synchronization-delay? uint16
1855 | | {per-interface-timer-config}?
1856 | +--rw targeted
1857 | +--rw hello-holdtime? uint16
1858 | +--rw hello-interval? uint16
1859 | +--rw hello-accept
1860 | | +--rw enabled? boolean
1861 | | +--rw ldp-ext:neighbor-list? neighbor-list-ref
1862 | | {policy-targeted-discovery-config}?
1863 | +--rw address-families
1864 | +--rw ipv4!
1865 | | +--ro hello-adjacencies
1866 | | | +--ro hello-adjacency*
1867 | | | [local-address adjacent-address]
1868 | | | +--ro local-address inet:ipv4-address
1869 | | | +--ro adjacent-address inet:ipv4-address
1870 | | | +--ro flag* identityref
1871 | | | +--ro hello-holdtime
1872 | | | | +--ro adjacent? uint16
1873 | | | | +--ro negotiated? uint16
1874 | | | | +--ro remaining? uint16
1875 | | | +--ro next-hello? uint16
1876 | | | +--ro statistics
1877 | | | | +--ro discontinuity-time
1878 | | | | | yang:date-and-time
1879 | | | | +--ro hello-received?
1880 | | | | | yang:counter64
1881 | | | | +--ro hello-dropped?
1882 | | | | yang:counter64
1883 | | | +--ro peer
1884 | | | +--ro lsr-id? leafref
1885 | | | +--ro label-space-id? leafref
1886 | | +--rw target* [adjacent-address]
1887 | | +--rw adjacent-address inet:ipv4-address
1888 | | +--rw enabled? boolean
1889 | | +--rw local-address? inet:ipv4-address
1890 | +--rw ldp-ext:ipv6!
1891 | +--ro ldp-ext:hello-adjacencies
1892 | | +--ro ldp-ext:hello-adjacency*
1893 | | [local-address adjacent-address]
1894 | | +--ro ldp-ext:local-address
1895 | | | inet:ipv6-address
1896 | | +--ro ldp-ext:adjacent-address
1897 | | | inet:ipv6-address
1898 | | +--ro ldp-ext:flag*
1899 | | | identityref
1900 | | +--ro ldp-ext:hello-holdtime
1901 | | | +--ro ldp-ext:adjacent? uint16
1902 | | | +--ro ldp-ext:negotiated? uint16
1903 | | | +--ro ldp-ext:remaining? uint16
1904 | | +--ro ldp-ext:next-hello? uint16
1905 | | +--ro ldp-ext:statistics
1906 | | | +--ro ldp-ext:discontinuity-time
1907 | | | | yang:date-and-time
1908 | | | +--ro ldp-ext:hello-received?
1909 | | | | yang:counter64
1910 | | | +--ro ldp-ext:hello-dropped?
1911 | | | yang:counter64
1912 | | +--ro ldp-ext:peer
1913 | | +--ro ldp-ext:lsr-id? leafref
1914 | | +--ro ldp-ext:label-space-id? leafref
1915 | +--rw ldp-ext:target* [adjacent-address]
1916 | +--rw ldp-ext:adjacent-address
1917 | | inet:ipv6-address
1918 | +--rw ldp-ext:enabled? boolean
1919 | +--rw ldp-ext:local-address?
1920 | inet:ipv6-address
1921 +--rw peers
1922 +--rw authentication
1923 | +--rw (authentication-type)?
1924 | +--:(password)
1925 | | +--rw key? string
1926 | | +--rw crypto-algorithm? identityref
1927 | +--:(ldp-ext:key-chain) {key-chain}?
1928 | +--rw ldp-ext:key-chain? key-chain:key-chain-ref
1929 +--rw session-ka-holdtime? uint16
1930 +--rw session-ka-interval? uint16
1931 +--rw peer* [lsr-id label-space-id]
1932 | +--rw lsr-id rt-types:router-id
1933 | +--rw label-space-id uint16
1934 | +--rw authentication
1935 | | +--rw (authentication-type)?
1936 | | +--:(password)
1937 | | | +--rw key? string
1938 | | | +--rw crypto-algorithm? identityref
1939 | | +--:(ldp-ext:key-chain) {key-chain}?
1940 | | +--rw ldp-ext:key-chain?
1941 | | key-chain:key-chain-ref
1942 | +--rw address-families
1943 | | +--rw ipv4!
1944 | | | +--ro hello-adjacencies
1945 | | | | +--ro hello-adjacency*
1946 | | | | [local-address adjacent-address]
1947 | | | | +--ro local-address inet:ipv4-address
1948 | | | | +--ro adjacent-address inet:ipv4-address
1949 | | | | +--ro flag* identityref
1950 | | | | +--ro hello-holdtime
1951 | | | | | +--ro adjacent? uint16
1952 | | | | | +--ro negotiated? uint16
1953 | | | | | +--ro remaining? uint16
1954 | | | | +--ro next-hello? uint16
1955 | | | | +--ro statistics
1956 | | | | | +--ro discontinuity-time
1957 | | | | | | yang:date-and-time
1958 | | | | | +--ro hello-received?
1959 | | | | | | yang:counter64
1960 | | | | | +--ro hello-dropped?
1961 | | | | | yang:counter64
1962 | | | | +--ro interface? if:interface-ref
1963 | | | +--rw ldp-ext:label-policy
1964 | | | +--rw ldp-ext:advertise
1965 | | | | +--rw ldp-ext:prefix-list? prefix-list-ref
1966 | | | +--rw ldp-ext:accept
1967 | | | +--rw ldp-ext:prefix-list? prefix-list-ref
1968 | | +--rw ldp-ext:ipv6!
1969 | | +--ro ldp-ext:hello-adjacencies
1970 | | | +--ro ldp-ext:hello-adjacency*
1971 | | | [local-address adjacent-address]
1972 | | | +--ro ldp-ext:local-address
1973 | | | | inet:ipv6-address
1974 | | | +--ro ldp-ext:adjacent-address
1975 | | | | inet:ipv6-address
1976 | | | +--ro ldp-ext:flag*
1977 | | | | identityref
1978 | | | +--ro ldp-ext:hello-holdtime
1979 | | | | +--ro ldp-ext:adjacent? uint16
1980 | | | | +--ro ldp-ext:negotiated? uint16
1981 | | | | +--ro ldp-ext:remaining? uint16
1982 | | | +--ro ldp-ext:next-hello? uint16
1983 | | | +--ro ldp-ext:statistics
1984 | | | | +--ro ldp-ext:discontinuity-time
1985 | | | | | yang:date-and-time
1986 | | | | +--ro ldp-ext:hello-received?
1987 | | | | | yang:counter64
1988 | | | | +--ro ldp-ext:hello-dropped?
1989 | | | | yang:counter64
1990 | | | +--ro ldp-ext:interface?
1991 | | | if:interface-ref
1992 | | +--rw ldp-ext:label-policy
1993 | | +--rw ldp-ext:advertise
1994 | | | +--rw ldp-ext:prefix-list? prefix-list-ref
1995 | | +--rw ldp-ext:accept
1996 | | +--rw ldp-ext:prefix-list? prefix-list-ref
1997 | +--ro label-advertisement-mode
1998 | | +--ro local? label-adv-mode
1999 | | +--ro peer? label-adv-mode
2000 | | +--ro negotiated? label-adv-mode
2001 | +--ro next-keep-alive? uint16
2002 | +--ro received-peer-state
2003 | | +--ro graceful-restart
2004 | | | +--ro enabled? boolean
2005 | | | +--ro reconnect-time? uint16
2006 | | | +--ro recovery-time? uint16
2007 | | +--ro capability
2008 | | +--ro end-of-lib
2009 | | | +--ro enabled? boolean
2010 | | +--ro typed-wildcard-fec
2011 | | | +--ro enabled? boolean
2012 | | +--ro upstream-label-assignment
2013 | | +--ro enabled? boolean
2014 | +--ro session-holdtime
2015 | | +--ro peer? uint16
2016 | | +--ro negotiated? uint16
2017 | | +--ro remaining? uint16
2018 | +--ro session-state? enumeration
2019 | +--ro tcp-connection
2020 | | +--ro local-address? inet:ip-address
2021 | | +--ro local-port? inet:port-number
2022 | | +--ro remote-address? inet:ip-address
2023 | | +--ro remote-port? inet:port-number
2024 | +--ro up-time?
2025 | | rt-types:timeticks64
2026 | +--ro statistics
2027 | | +--ro discontinuity-time yang:date-and-time
2028 | | +--ro received
2029 | | | +--ro total-octets? yang:counter64
2030 | | | +--ro total-messages? yang:counter64
2031 | | | +--ro address? yang:counter64
2032 | | | +--ro address-withdraw? yang:counter64
2033 | | | +--ro initialization? yang:counter64
2034 | | | +--ro keepalive? yang:counter64
2035 | | | +--ro label-abort-request? yang:counter64
2036 | | | +--ro label-mapping? yang:counter64
2037 | | | +--ro label-release? yang:counter64
2038 | | | +--ro label-request? yang:counter64
2039 | | | +--ro label-withdraw? yang:counter64
2040 | | | +--ro notification? yang:counter64
2041 | | +--ro sent
2042 | | | +--ro total-octets? yang:counter64
2043 | | | +--ro total-messages? yang:counter64
2044 | | | +--ro address? yang:counter64
2045 | | | +--ro address-withdraw? yang:counter64
2046 | | | +--ro initialization? yang:counter64
2047 | | | +--ro keepalive? yang:counter64
2048 | | | +--ro label-abort-request? yang:counter64
2049 | | | +--ro label-mapping? yang:counter64
2050 | | | +--ro label-release? yang:counter64
2051 | | | +--ro label-request? yang:counter64
2052 | | | +--ro label-withdraw? yang:counter64
2053 | | | +--ro notification? yang:counter64
2054 | | +--ro total-addresses? uint32
2055 | | +--ro total-labels? uint32
2056 | | +--ro total-fec-label-bindings? uint32
2057 | +--rw ldp-ext:admin-down? boolean
2058 | | {per-peer-admin-down}?
2059 | +--rw ldp-ext:graceful-restart
2060 | | {per-peer-graceful-restart-config}?
2061 | | +--rw ldp-ext:enabled? boolean
2062 | | +--rw ldp-ext:reconnect-time? uint16
2063 | | +--rw ldp-ext:recovery-time? uint16
2064 | +--rw ldp-ext:session-ka-holdtime? uint16
2065 | | {per-peer-session-attributes-config}?
2066 | +--rw ldp-ext:session-ka-interval? uint16
2067 | {per-peer-session-attributes-config}?
2068 +--rw ldp-ext:session-downstream-on-demand
2069 | {session-downstream-on-demand-config}?
2070 | +--rw ldp-ext:enabled? boolean
2071 | +--rw ldp-ext:peer-list? peer-list-ref
2072 +--rw ldp-ext:dual-stack-transport-preference
2073 {peers-dual-stack-transport-preference}?
2074 +--rw ldp-ext:max-wait? uint16
2075 +--rw ldp-ext:prefer-ipv4!
2076 +--rw ldp-ext:peer-list? peer-list-ref
2077
2078 rpcs:
2079 +---x mpls-ldp-clear-peer
2080 | +---w input
2081 | +---w protocol-name? leafref
2082 | +---w lsr-id? leafref
2083 | +---w label-space-id? leafref
2084 +---x mpls-ldp-clear-hello-adjacency
2085 | +---w input
2086 | +---w hello-adjacency
2087 | +---w protocol-name? leafref
2088 | +---w (hello-adjacency-type)?
2089 | +--:(targeted)
2090 | | +---w targeted!
2091 | | +---w target-address? inet:ip-address
2092 | +--:(link)
2093 | +---w link!
2094 | +---w next-hop-interface? leafref
2095 | +---w next-hop-address? inet:ip-address
2096 +---x mpls-ldp-clear-peer-statistics
2097 +---w input
2098 +---w protocol-name? leafref
2099 +---w lsr-id? leafref
2100 +---w label-space-id? leafref
2101
2102 notifications:
2103 +---n mpls-ldp-peer-event
2104 | +--ro event-type? oper-status-event-type
2105 | +--ro peer
2106 | +--ro protocol-name? leafref
2107 | +--ro lsr-id? leafref
2108 | +--ro label-space-id? leafref
2109 +---n mpls-ldp-hello-adjacency-event
2110 | +--ro event-type? oper-status-event-type
2111 | +--ro protocol-name? leafref
2112 | +--ro (hello-adjacency-type)?
2113 | +--:(targeted)
2114 | | +--ro targeted
2115 | | +--ro target-address? inet:ip-address
2116 | +--:(link)
2117 | +--ro link
2118 | +--ro next-hop-interface? if:interface-ref
2119 | +--ro next-hop-address? inet:ip-address
2120 +---n mpls-ldp-fec-event
2121 +--ro event-type? oper-status-event-type
2122 +--ro protocol-name? leafref
2123 +--ro fec? inet:ip-prefix
2124 </pre>
2125 </div>
2126 <figcaption><a href="#figure-2" class="selfRef">Figure 2</a>:
2127 <a href="#name-complete-tree" class="selfRef">Complete Tree</a>
2128 </figcaption></figure>
2129 </div>
2130 </section>
2131 <div id="section_ldp_cfg">
2132 <section id="section-5">
2133 <h2 id="name-configuration">
2134 <a href="#section-5" class="section-number selfRef">5. </a><a href="#name-configuration" class="section-name selfRef">Configuration</a>
2135 </h2>
2136 <p id="section-5-1"> This specification defines the configuration parameters for base
2137 LDP as specified in <span>[<a href="#RFC5036" class="xref">RFC5036</a>]</span> and LDP IPv6 <span>[<a href="#RFC7552" class="xref">RFC7552</a>]</span>. Moreover, it incorporates provisions to enable LDP
2138 Capabilities <span>[<a href="#RFC5561" class="xref">RFC5561</a>]</span> and defines some of the most
2139 significant and commonly used capabilities such as Typed Wildcard
2140 FEC <span>[<a href="#RFC5918" class="xref">RFC5918</a>]</span>, End-of-LIB
2141 <span>[<a href="#RFC5919" class="xref">RFC5919</a>]</span>, and LDP Upstream
2142 Label Assignment <span>[<a href="#RFC6389" class="xref">RFC6389</a>]</span>.<a href="#section-5-1" class="pilcrow">¶</a></p>
2143 <p id="section-5-2"> This model augments
2144 /rt:routing/rt:control-plane-protocols/rt:control-plane-protocol,
2145 which is defined in <span>[<a href="#RFC8349" class="xref">RFC8349</a>]</span> and follows NMDA as
2146 mentioned earlier.<a href="#section-5-2" class="pilcrow">¶</a></p>
2147 <p id="section-5-3">The following is the high-level configuration organization for the
2148 base LDP module:<a href="#section-5-3" class="pilcrow">¶</a></p>
2149 <span id="name-base-configuration-organiza"></span><div id="LDPCfgOrgHL">
2150 <figure id="figure-3">
2151 <div id="section-5-4.1">
2152 <pre class="lang-yangtree sourcecode">
2153 augment /rt:routing/rt:control-plane-protocols:
2154 /rt:control-plane-protocol:
2155 +-- mpls-ldp
2156 +-- global
2157 | +-- ...
2158 | +-- ...
2159 | +-- address-families
2160 | | +-- ipv4
2161 | | +-- . . .
2162 | | +-- . . .
2163 | +-- capability
2164 | +-- ...
2165 | +-- ...
2166 +-- discovery
2167 | +-- interfaces
2168 | | +-- ...
2169 | | +-- ...
2170 | | +-- interface* [interface]
2171 | | +-- ...
2172 | | +-- address-families
2173 | | +-- ipv4
2174 | | +-- ...
2175 | | +-- ...
2176 | +-- targeted
2177 | +-- ...
2178 | +-- address-families
2179 | +-- ipv4
2180 | +-- target* [adjacent-address]
2181 | +-- ...
2182 | +-- ...
2183 +-- peers
2184 +-- ...
2185 +-- ...
2186 +-- peer* [lsr-id label-space-id]
2187 +-- ...
2188 +-- ...
2189 </pre>
2190 </div>
2191 <figcaption><a href="#figure-3" class="selfRef">Figure 3</a>:
2192 <a href="#name-base-configuration-organiza" class="selfRef">Base Configuration Organization</a>
2193 </figcaption></figure>
2194 </div>
2195 <p id="section-5-5">The following is the high-level configuration organization for the
2196 extended LDP module:<a href="#section-5-5" class="pilcrow">¶</a></p>
2197 <span id="name-extended-configuration-orga"></span><div id="LDPCfgExtOrgHL">
2198 <figure id="figure-4">
2199 <div id="section-5-6.1">
2200 <pre class="lang-yangtree sourcecode">
2201 augment /rt:routing/rt:control-plane-protocols
2202 /rt:control-plane-protocol
2203 +-- mpls-ldp
2204 +-- global
2205 | +-- ...
2206 | +-- ...
2207 | +-- address-families
2208 | | +-- ipv4
2209 | | | +-- . . .
2210 | | | +-- . . .
2211 | | | +-- label-policy
2212 | | | +-- ...
2213 | | | +-- ...
2214 | | +-- ipv6
2215 | | +-- . . .
2216 | | +-- . . .
2217 | | +-- label-policy
2218 | | +-- ...
2219 | | +-- ...
2220 | +-- capability
2221 | | +-- ...
2222 | | +-- ...
2223 | +-- discovery
2224 | +-- interfaces
2225 | | +-- ...
2226 | | +-- ...
2227 | | +-- interface* [interface]
2228 | | +-- ...
2229 | | +-- address-families
2230 | | +-- ipv4
2231 | | | +-- ...
2232 | | | +-- ...
2233 | | +-- ipv6
2234 | | +-- ...
2235 | | +-- ...
2236 | +-- targeted
2237 | +-- ...
2238 | +-- address-families
2239 | +-- ipv6
2240 | +- target* [adjacent-address]
2241 | +- ...
2242 | +- ...
2243 +-- forwarding-nexthop
2244 | +-- ...
2245 | +-- ...
2246 +-- peers
2247 +-- ...
2248 +-- ...
2249 +-- peer*
2250 +-- ...
2251 +-- ...
2252 +-- label-policy
2253 | +-- ..
2254 +-- address-families
2255 +-- ipv4
2256 | +-- ...
2257 +-- ipv6
2258 +-- ...
2259 </pre>
2260 </div>
2261 <figcaption><a href="#figure-4" class="selfRef">Figure 4</a>:
2262 <a href="#name-extended-configuration-orga" class="selfRef">Extended Configuration Organization</a>
2263 </figcaption></figure>
2264 </div>
2265 <p id="section-5-7">Given the configuration hierarchy, the model allows inheritance
2266 such that an item in a child tree is able to derive value from a
2267 similar or related item in one of the parents. For instance, Hello
2268 holdtime can be configured per VRF or per VRF interface, thus allowing
2269 inheritance as well flexibility to override with a different value at
2270 any child level.<a href="#section-5-7" class="pilcrow">¶</a></p>
2271 <section id="section-5.1">
2272 <h3 id="name-configuration-hierarchy">
2273 <a href="#section-5.1" class="section-number selfRef">5.1. </a><a href="#name-configuration-hierarchy" class="section-name selfRef">Configuration Hierarchy</a>
2274 </h3>
2275 <p id="section-5.1-1">The LDP module resides under a network-instance and the scope of
2276 any LDP configuration defined under this tree is per network-instance
2277 (per-VRF). This configuration is further divided into sub categories
2278 as follows:<a href="#section-5.1-1" class="pilcrow">¶</a></p>
2279 <ul class="normal">
2280 <li class="normal" id="section-5.1-2.1">Global parameters<a href="#section-5.1-2.1" class="pilcrow">¶</a>
2281 </li>
2282 <li class="normal" id="section-5.1-2.2">Per-address-family parameters<a href="#section-5.1-2.2" class="pilcrow">¶</a>
2283 </li>
2284 <li class="normal" id="section-5.1-2.3">LDP Capabilities parameters<a href="#section-5.1-2.3" class="pilcrow">¶</a>
2285 </li>
2286 <li class="normal" id="section-5.1-2.4">
2287 <p id="section-5.1-2.4.1">Hello Discovery parameters<a href="#section-5.1-2.4.1" class="pilcrow">¶</a></p>
2288 <ul class="normal">
2289 <li class="normal" id="section-5.1-2.4.2.1">
2290 <p id="section-5.1-2.4.2.1.1">interfaces<a href="#section-5.1-2.4.2.1.1" class="pilcrow">¶</a></p>
2291 <ul class="normal">
2292 <li class="normal" id="section-5.1-2.4.2.1.2.1">Global<a href="#section-5.1-2.4.2.1.2.1" class="pilcrow">¶</a>
2293 </li>
2294 <li class="normal" id="section-5.1-2.4.2.1.2.2">Per-interface: Global<a href="#section-5.1-2.4.2.1.2.2" class="pilcrow">¶</a>
2295 </li>
2296 <li class="normal" id="section-5.1-2.4.2.1.2.3">Per-interface: Per-address-family<a href="#section-5.1-2.4.2.1.2.3" class="pilcrow">¶</a>
2297 </li>
2298 </ul>
2299 </li>
2300 <li class="normal" id="section-5.1-2.4.2.2">
2301 <p id="section-5.1-2.4.2.2.1">targeted<a href="#section-5.1-2.4.2.2.1" class="pilcrow">¶</a></p>
2302 <ul class="normal">
2303 <li class="normal" id="section-5.1-2.4.2.2.2.1">Global<a href="#section-5.1-2.4.2.2.2.1" class="pilcrow">¶</a>
2304 </li>
2305 <li class="normal" id="section-5.1-2.4.2.2.2.2">Per-address-family: Per-target<a href="#section-5.1-2.4.2.2.2.2" class="pilcrow">¶</a>
2306 </li>
2307 </ul>
2308 </li>
2309 </ul>
2310 </li>
2311 <li class="normal" id="section-5.1-2.5">
2312 <p id="section-5.1-2.5.1">Peer parameters<a href="#section-5.1-2.5.1" class="pilcrow">¶</a></p>
2313 <ul class="normal">
2314 <li class="normal" id="section-5.1-2.5.2.1">Global<a href="#section-5.1-2.5.2.1" class="pilcrow">¶</a>
2315 </li>
2316 <li class="normal" id="section-5.1-2.5.2.2">Per-peer: Global<a href="#section-5.1-2.5.2.2" class="pilcrow">¶</a>
2317 </li>
2318 <li class="normal" id="section-5.1-2.5.2.3">Per-peer: Per-address-family<a href="#section-5.1-2.5.2.3" class="pilcrow">¶</a>
2319 </li>
2320 </ul>
2321 </li>
2322 <li class="normal" id="section-5.1-2.6">Forwarding parameters<a href="#section-5.1-2.6" class="pilcrow">¶</a>
2323 </li>
2324 </ul>
2325 <p id="section-5.1-3">The following subsections briefly explain these configuration areas.<a href="#section-5.1-3" class="pilcrow">¶</a></p>
2326 <section id="section-5.1.1">
2327 <h4 id="name-global-parameters">
2328 <a href="#section-5.1.1" class="section-number selfRef">5.1.1. </a><a href="#name-global-parameters" class="section-name selfRef">Global Parameters</a>
2329 </h4>
2330 <p id="section-5.1.1-1"> There are configuration items that are available directly
2331 under a VRF instance and do not fall under any other subtree. An
2332 example of such a parameter is an LDP LSR Id that is typically
2333 configured per VRF. To keep legacy LDP features and applications
2334 working in an LDP IPv4 network with this model, this document
2335 recommends an operator to pick a routable IPv4 unicast address
2336 (within a routing domain) as an LSR Id.<a href="#section-5.1.1-1" class="pilcrow">¶</a></p>
2337 </section>
2338 <section id="section-5.1.2">
2339 <h4 id="name-capabilities-parameters">
2340 <a href="#section-5.1.2" class="section-number selfRef">5.1.2. </a><a href="#name-capabilities-parameters" class="section-name selfRef">Capabilities Parameters</a>
2341 </h4>
2342 <p id="section-5.1.2-1"> This container falls under the global tree and holds the LDP
2343 capabilities that are to be enabled for certain features. By
2344 default, an LDP capability is disabled unless explicitly
2345 enabled. These capabilities are typically used to negotiate with
2346 LDP peer(s) the support/non-support related to a feature and its
2347 parameters. The scope of a capability enabled under this
2348 container applies to all LDP peers in the given VRF
2349 instance. There is also a peer-level capability container that
2350 is provided to override a capability that is enabled/specified
2351 at VRF level.<a href="#section-5.1.2-1" class="pilcrow">¶</a></p>
2352 </section>
2353 <section id="section-5.1.3">
2354 <h4 id="name-per-address-family-paramete">
2355 <a href="#section-5.1.3" class="section-number selfRef">5.1.3. </a><a href="#name-per-address-family-paramete" class="section-name selfRef">Per-Address-Family Parameters</a>
2356 </h4>
2357 <p id="section-5.1.3-1"> Any LDP configuration parameter related to an IP address
2358 family (AF) whose scope is VRF wide is configured under this
2359 tree. The examples of per-AF parameters include enabling LDP for
2360 an address family, prefix-list-based label policies, and LDP
2361 transport address.<a href="#section-5.1.3-1" class="pilcrow">¶</a></p>
2362 </section>
2363 <section id="section-5.1.4">
2364 <h4 id="name-hello-discovery-parameters">
2365 <a href="#section-5.1.4" class="section-number selfRef">5.1.4. </a><a href="#name-hello-discovery-parameters" class="section-name selfRef">Hello Discovery Parameters</a>
2366 </h4>
2367 <p id="section-5.1.4-1"> This container is used to hold LDP configuration related to
2368 the Hello and discovery process for both basic (link) and extended
2369 (targeted) discovery.<a href="#section-5.1.4-1" class="pilcrow">¶</a></p>
2370 <p id="section-5.1.4-2"> The "interfaces" container is used to configure parameters
2371 related to VRF interfaces. There are parameters that apply to
2372 all interfaces (such as Hello timers) as well as parameters
2373 that can be configured per interface. Hence, an interface list
2374 is defined under the "interfaces" container. The model defines
2375 parameters to configure per-interface non-AF-related items as
2376 well as per-interface per-AF items. The example of the former is
2377 interface Hello timers, and an example of the latter is enabling
2378 hellos for a given AF under an interface.<a href="#section-5.1.4-2" class="pilcrow">¶</a></p>
2379 <p id="section-5.1.4-3"> The "targeted" container under a VRF instance allows for the
2380 configuration of parameters related to LDP targeted
2381 discovery. Within this container, the "target" list provides a
2382 means to configure multiple target addresses to perform extended
2383 discovery to a specific destination target, as well as to
2384 fine tune the per-target parameters.<a href="#section-5.1.4-3" class="pilcrow">¶</a></p>
2385 </section>
2386 <section id="section-5.1.5">
2387 <h4 id="name-peer-parameters">
2388 <a href="#section-5.1.5" class="section-number selfRef">5.1.5. </a><a href="#name-peer-parameters" class="section-name selfRef">Peer Parameters</a>
2389 </h4>
2390 <p id="section-5.1.5-1">
2391
2392 This container is used to hold LDP configuration related to LDP sessions and
2393 peers under a VRF instance.
2394
2395 This container allows for the configuration of parameters that either apply to
2396 all or a subset (peer-list) of peers in a given VRF.
2397
2398
2399 The example of such parameters includes authentication
2400 passwords, session KeepAlive (KA) timers, etc. Moreover, the
2401 model also allows per-peer parameter tuning by specifying a
2402 "peer" list under the "peers" container. A peer is uniquely
2403 identified by its LSR Id.<a href="#section-5.1.5-1" class="pilcrow">¶</a></p>
2404 <p id="section-5.1.5-2"> Like per-interface parameters, some per-peer parameters are
2405 AF agnostic (i.e., either non-AF related or apply to both IP
2406 address families), and some belong to an AF. The example of
2407 the former is per-peer session password configuration, whereas
2408 the example of the latter is prefix-lis-based label policies
2409 (inbound and outbound) that apply to a given peer.<a href="#section-5.1.5-2" class="pilcrow">¶</a></p>
2410 </section>
2411 <section id="section-5.1.6">
2412 <h4 id="name-forwarding-parameters">
2413 <a href="#section-5.1.6" class="section-number selfRef">5.1.6. </a><a href="#name-forwarding-parameters" class="section-name selfRef">Forwarding Parameters</a>
2414 </h4>
2415 <p id="section-5.1.6-1"> This container is used to hold configuration used to control LDP
2416 forwarding behavior under a VRF instance.
2417
2418 One example of a configuration under this container is when a user wishes to
2419 enable LDP neighbor discovery on an interface but wishes to disable use of the
2420 same interface for forwarding MPLS packets.
2421
2422 This example configuration makes sense only when there are more
2423 than one LDP-enabled interfaces towards a neighbor.<a href="#section-5.1.6-1" class="pilcrow">¶</a></p>
2424 </section>
2425 </section>
2426 </section>
2427 </div>
2428 <div id="section_ldp_oper">
2429 <section id="section-6">
2430 <h2 id="name-operational-state">
2431 <a href="#section-6" class="section-number selfRef">6. </a><a href="#name-operational-state" class="section-name selfRef">Operational State</a>
2432 </h2>
2433 <p id="section-6-1">The operational state of LDP can be queried and obtained from
2434 read-only state containers that fall under the same tree
2435 (/rt:routing/rt:control-plane-protocols/rt:control-plane-protocol) as
2436 the configuration.<a href="#section-6-1" class="pilcrow">¶</a></p>
2437 <p id="section-6-2">The following are main areas for which LDP operational state is defined:<a href="#section-6-2" class="pilcrow">¶</a></p>
2438 <ul class="normal">
2439 <li class="normal" id="section-6-3.1"> Neighbor Adjacencies<a href="#section-6-3.1" class="pilcrow">¶</a>
2440 </li>
2441 <li class="normal" id="section-6-3.2"> Peer<a href="#section-6-3.2" class="pilcrow">¶</a>
2442 </li>
2443 <li class="normal" id="section-6-3.3"> Bindings (FEC-Label and address)<a href="#section-6-3.3" class="pilcrow">¶</a>
2444 </li>
2445 <li class="normal" id="section-6-3.4"> Capabilities<a href="#section-6-3.4" class="pilcrow">¶</a>
2446 </li>
2447 </ul>
2448 <section id="section-6.1">
2449 <h3 id="name-adjacency-state">
2450 <a href="#section-6.1" class="section-number selfRef">6.1. </a><a href="#name-adjacency-state" class="section-name selfRef">Adjacency State</a>
2451 </h3>
2452 <p id="section-6.1-1"> Neighbor adjacencies are per-address-family Hello adjacencies
2453 that are formed with neighbors as a result of LDP basic or
2454 extended discovery. In terms of organization, there is a source of
2455 discovery (e.g., interface or target address) along with its
2456 associated parameters and one or more discovered neighbors along
2457 with neighbor-discovery-related parameters. For the basic
2458 discovery, there could be more than one discovered neighbor for a
2459 given source (interface), whereas there is at most one discovered
2460 neighbor for an extended discovery source (local-address and
2461 target-address). It is also to be noted that the reason for a
2462 targeted neighbor adjacency could be either an active source
2463 (locally configured targeted) or passive source (to allow any
2464 incoming extended/targeted hellos). A neighbor/adjacency record
2465 also contains session state that helps highlight whether a given
2466 adjacency has progressed to the subsequent session level or
2467 eventual peer level.<a href="#section-6.1-1" class="pilcrow">¶</a></p>
2468 <p id="section-6.1-2">The following captures high-level tree hierarchy for neighbor
2469 adjacency state. The tree is shown for ipv4 address-family only; a
2470 similar tree exists for ipv6 address-family as well.<a href="#section-6.1-2" class="pilcrow">¶</a></p>
2471 <span id="name-adjacency-state-2"></span><div id="LDPAdjState">
2472 <figure id="figure-5">
2473 <div id="section-6.1-3.1">
2474 <pre class="lang-yangtree sourcecode">
2475 +--rw mpls-ldp!
2476 +--rw discovery
2477 +--rw interfaces
2478 | +--rw interface* [interface]
2479 | +--rw address-families
2480 | +--rw ipv4
2481 | +--ro hello-adjacencies
2482 | +--ro hello-adjacencies* [adjacent-address]
2483 | +--ro adjacent-address
2484 | . . . .
2485 | . . . .
2486 +--rw targeted
2487 +--rw address-families
2488 +--rw ipv4
2489 +--ro hello-adjacencies
2490 +--ro hello-adjacencies*
2491 | [local-address adjacent-address]
2492 +--ro local-address
2493 +--ro adjacent-address
2494 . . . .
2495 . . . .
2496 </pre>
2497 </div>
2498 <figcaption><a href="#figure-5" class="selfRef">Figure 5</a>:
2499 <a href="#name-adjacency-state-2" class="selfRef">Adjacency State</a>
2500 </figcaption></figure>
2501 </div>
2502 </section>
2503 <section id="section-6.2">
2504 <h3 id="name-peer-state">
2505 <a href="#section-6.2" class="section-number selfRef">6.2. </a><a href="#name-peer-state" class="section-name selfRef">Peer State</a>
2506 </h3>
2507 <p id="section-6.2-1">Peer-related state is presented under a peers tree. This is one
2508 of the core states that provides info on the session-related
2509 parameters (mode, authentication, KA timeout, etc.), TCP connection
2510 info, Hello adjacencies for the peer, statistics related to
2511 messages and bindings, and capabilities exchange info.<a href="#section-6.2-1" class="pilcrow">¶</a></p>
2512 <p id="section-6.2-2">The following captures high-level tree hierarchy for peer
2513 state. The peer's Hello adjacencies tree is shown for ipv4
2514 address-family only; a similar tree exists for ipv6 address-family
2515 as well.<a href="#section-6.2-2" class="pilcrow">¶</a></p>
2516 <span id="name-peer-state-2"></span><div id="LDPPeerState">
2517 <figure id="figure-6">
2518 <div id="section-6.2-3.1">
2519 <pre class="lang-yangtree sourcecode">
2520 +--rw mpls-ldp!
2521 +--rw peers
2522 +--rw peer* [lsr-id label-space-id]
2523 +--rw lsr-id
2524 +--rw label-space-id
2525 +--ro label-advertisement-mode
2526 +--ro session-state
2527 +--ro tcp-connection
2528 +--ro session-holdtime?
2529 +--ro up-time
2530 +-- . . . .
2531 +--ro address-families
2532 | +--ro ipv4
2533 | +--ro hello-adjacencies
2534 | +--ro hello-adjacencies*
2535 | [local-address adjacent-address]
2536 | . . . .
2537 | . . . .
2538 +--ro received-peer-state
2539 | +--ro . . . .
2540 | +--ro capability
2541 | +--ro . . . .
2542 +--ro statistics
2543 +-- . . . .
2544 +-- received
2545 | +-- ...
2546 +-- sent
2547 +-- ...
2548 </pre>
2549 </div>
2550 <figcaption><a href="#figure-6" class="selfRef">Figure 6</a>:
2551 <a href="#name-peer-state-2" class="selfRef">Peer State</a>
2552 </figcaption></figure>
2553 </div>
2554 </section>
2555 <section id="section-6.3">
2556 <h3 id="name-bindings-state">
2557 <a href="#section-6.3" class="section-number selfRef">6.3. </a><a href="#name-bindings-state" class="section-name selfRef">Bindings State</a>
2558 </h3>
2559 <p id="section-6.3-1"> Bindings state provides information on LDP FEC-Label bindings
2560 as well as address bindings for both inbound (received) as well as
2561 outbound (advertised) direction. FEC-Label bindings are presented
2562 in a FEC-centric view, and address bindings are presented in an
2563 address-centric view:<a href="#section-6.3-1" class="pilcrow">¶</a></p>
2564 <span id="name-example-bindings"></span><div id="ExampleBndg">
2565 <figure id="figure-7">
2566 <div id="section-6.3-2.1">
2567 <pre class="sourcecode">
2568 FEC-Label bindings:
2569 FEC 203.0.113.1/32:
2570 advertised: local-label 16000
2571 peer 192.0.2.1:0
2572 peer 192.0.2.2:0
2573 peer 192.0.2.3:0
2574 received:
2575 peer 192.0.2.1:0, label 16002, used-in-forwarding=Yes
2576 peer 192.0.2.2:0, label 17002, used-in-forwarding=No
2577 FEC 203.0.113.2/32:
2578 . . . .
2579 FEC 198.51.100.0/24:
2580 . . . .
2581 FEC 2001:db8:0:2::
2582 . . . .
2583 FEC 2001:db8:0:3::
2584 . . . .
2585
2586 Address bindings:
2587 Addr 192.0.2.10:
2588 advertised
2589 Addr 2001:db8:0:10::
2590 advertised
2591
2592 Addr 192.0.2.1:
2593 received, peer 192.0.2.1:0
2594 Addr 192.0.2.2:
2595 received, peer 192.0.2.2:0
2596 Addr 192.0.2.3:
2597 received, peer 192.0.2.3:0
2598 Addr 2001:db8:0:2::
2599 received, peer 192.0.2.2:0
2600 Addr 2001:db8:0:3::
2601 received, peer 192.0.2.3:0
2602 </pre>
2603 </div>
2604 <figcaption><a href="#figure-7" class="selfRef">Figure 7</a>:
2605 <a href="#name-example-bindings" class="selfRef">Example Bindings</a>
2606 </figcaption></figure>
2607 </div>
2608 <p id="section-6.3-3"> Note that all local addresses are advertised to all peers;
2609 hence, there is no need to provide per-peer information for local address
2610 advertisement. Furthermore, note that it is easy to derive a
2611 peer-centric view for the bindings from the information already
2612 provided in this model.<a href="#section-6.3-3" class="pilcrow">¶</a></p>
2613 <p id="section-6.3-4">The following captures high-level tree hierarchy for bindings
2614 state. The tree shown below is for ipv4 address-family only; a
2615 similar tree exists for ipv6 address-family as well.<a href="#section-6.3-4" class="pilcrow">¶</a></p>
2616 <span id="name-bindings-state-2"></span><div id="LDPBndgState">
2617 <figure id="figure-8">
2618 <div id="section-6.3-5.1">
2619 <pre class="lang-yangtree sourcecode">
2620 +--rw mpls-ldp!
2621 +--rw global
2622 +--rw address-families
2623 +--rw ipv4
2624 +--ro bindings
2625 +--ro address* [address]
2626 | +--ro address (ipv4-address or ipv6-address)
2627 | +--ro advertisement-type? advertised-received
2628 | +--ro peer? leafref
2629 +--ro fec-label* [fec]
2630 +--ro fec (ipv4-prefix or ipv6-prefix)
2631 +--ro peer* [peer advertisement-type]
2632 +--ro peer leafref
2633 +--ro advertisement-type? advertised-received
2634 +--ro label? mpls:mpls-label
2635 +--ro used-in-forwarding? boolean
2636 </pre>
2637 </div>
2638 <figcaption><a href="#figure-8" class="selfRef">Figure 8</a>:
2639 <a href="#name-bindings-state-2" class="selfRef">Bindings State</a>
2640 </figcaption></figure>
2641 </div>
2642 </section>
2643 <section id="section-6.4">
2644 <h3 id="name-capabilities-state">
2645 <a href="#section-6.4" class="section-number selfRef">6.4. </a><a href="#name-capabilities-state" class="section-name selfRef">Capabilities State</a>
2646 </h3>
2647 <p id="section-6.4-1"> LDP capabilities state comprises two types of information:
2648 global information (such as timer, etc.) and per-peer
2649 information.<a href="#section-6.4-1" class="pilcrow">¶</a></p>
2650 <p id="section-6.4-2">The following captures high-level tree hierarchy for LDP capabilities state.<a href="#section-6.4-2" class="pilcrow">¶</a></p>
2651 <span id="name-capabilities-state-2"></span><div id="LDPCapState">
2652 <figure id="figure-9">
2653 <div id="section-6.4-3.1">
2654 <pre class="lang-yangtree sourcecode">
2655 +--rw mpls-ldp!
2656 +--rw peers
2657 +--rw peer* [lsr-id label-space-id]
2658 +--rw lsr-id yang:dotted-quad
2659 +--rw label-space-id
2660 +--ro received-peer-state
2661 +--ro capability
2662 +--ro . . . .
2663 +--ro . . . .
2664 </pre>
2665 </div>
2666 <figcaption><a href="#figure-9" class="selfRef">Figure 9</a>:
2667 <a href="#name-capabilities-state-2" class="selfRef">Capabilities State</a>
2668 </figcaption></figure>
2669 </div>
2670 </section>
2671 </section>
2672 </div>
2673 <div id="section_ldp_notif">
2674 <section id="section-7">
2675 <h2 id="name-notifications">
2676 <a href="#section-7" class="section-number selfRef">7. </a><a href="#name-notifications" class="section-name selfRef">Notifications</a>
2677 </h2>
2678 <p id="section-7-1"> This model defines a list of notifications to inform the client of
2679 important events detected during the protocol operation. These events
2680 include events related to changes in the operational state of an LDP
2681 peer, Hello adjacency, and FEC, etc. It is to be noted that an LDP FEC
2682 is treated as operational (up) as long as it has at least one Next Hop
2683 Label Forwarding Entry (NHLFE) with an outgoing label.<a href="#section-7-1" class="pilcrow">¶</a></p>
2684 <p id="section-7-2"> A simplified graphical representation of the data model for LDP notifications is shown in <a href="#ConsolidatedTree" class="xref">Figure 2</a>.<a href="#section-7-2" class="pilcrow">¶</a></p>
2685 </section>
2686 </div>
2687 <div id="section_ldp_action">
2688 <section id="section-8">
2689 <h2 id="name-action">
2690 <a href="#section-8" class="section-number selfRef">8. </a><a href="#name-action" class="section-name selfRef">Action</a>
2691 </h2>
2692 <p id="section-8-1"> This model defines a list of rpcs that allow performing an action
2693 or executing a command on the protocol. For example, it allows for the
2694 clearing (resetting) of LDP peers, hello-adjacencies, and
2695 statistics. The model makes an effort to provide a different level of
2696 control so that a user is able to either clear all, clear all for a
2697 given type, or clear a specific entity.<a href="#section-8-1" class="pilcrow">¶</a></p>
2698 <p id="section-8-2"> A simplified graphical representation of the data model for LDP actions is shown in <a href="#ConsolidatedTree" class="xref">Figure 2</a>.<a href="#section-8-2" class="pilcrow">¶</a></p>
2699 </section>
2700 </div>
2701 <div id="YANG">
2702 <section id="section-9">
2703 <h2 id="name-yang-specification">
2704 <a href="#section-9" class="section-number selfRef">9. </a><a href="#name-yang-specification" class="section-name selfRef">YANG Specification</a>
2705 </h2>
2706 <p id="section-9-1">The following sections specify the actual YANG (module) specification
2707 for LDP constructs defined earlier in the document.<a href="#section-9-1" class="pilcrow">¶</a></p>
2708 <div id="base_yang">
2709 <section id="section-9.1">
2710 <h3 id="name-base">
2711 <a href="#section-9.1" class="section-number selfRef">9.1. </a><a href="#name-base" class="section-name selfRef">Base</a>
2712 </h3>
2713 <p id="section-9.1-1">
2714 This YANG module imports types defined in <span>[<a href="#RFC6991" class="xref">RFC6991</a>]</span>, <span>[<a href="#RFC8177" class="xref">RFC8177</a>]</span>, <span>[<a href="#RFC8294" class="xref">RFC8294</a>]</span>, <span>[<a href="#RFC8343" class="xref">RFC8343</a>]</span>, <span>[<a href="#RFC8344" class="xref">RFC8344</a>]</span>, <span>[<a href="#RFC8349" class="xref">RFC8349</a>]</span>, and <span>[<a href="#RFC9067" class="xref">RFC9067</a>]</span>.<a href="#section-9.1-1" class="pilcrow">¶</a></p>
2715 <span id="name-ldp-base-module"></span><div id="BASE-YANG-FILE">
2716 <figure id="figure-10">
2717 <div id="section-9.1-2.1">
2718 <pre class="lang-yang sourcecode">&lt;CODE BEGINS&gt; file "[email protected]"
2719
2720 module ietf-mpls-ldp {
2721 yang-version 1.1;
2722 namespace "urn:ietf:params:xml:ns:yang:ietf-mpls-ldp";
2723 prefix ldp;
2724
2725 import ietf-inet-types {
2726 prefix inet;
2727 reference
2728 "RFC 6991: Common YANG Data Types";
2729 }
2730 import ietf-yang-types {
2731 prefix yang;
2732 reference
2733 "RFC 6991: Common YANG Data Types";
2734 }
2735 import ietf-routing {
2736 prefix rt;
2737 reference
2738 "RFC 8349: A YANG Data Model for Routing Management (NMDA
2739 version)";
2740 }
2741 import ietf-routing-types {
2742 prefix rt-types;
2743 reference
2744 "RFC 8294: Common YANG Data Types for the Routing Area";
2745 }
2746 import ietf-interfaces {
2747 prefix if;
2748 reference
2749 "RFC 8343: A YANG Data Model for Interface Management";
2750 }
2751 import ietf-ip {
2752 prefix ip;
2753 reference
2754 "RFC 8344: A YANG Data Model for IP Management";
2755 }
2756 import ietf-key-chain {
2757 prefix key-chain;
2758 reference
2759 "RFC 8177: YANG Data Model for Key Chains";
2760 }
2761
2762 organization
2763 "IETF MPLS Working Group";
2764 contact
2765 "WG Web: &lt;https://datatracker.ietf.org/wg/mpls/&gt;
2766 WG List: &lt;mailto:[email protected]&gt;
2767
2768 Editor: Kamran Raza
2769 &lt;mailto:[email protected]&gt;
2770
2771 Author: Rajiv Asati
2772 &lt;mailto:[email protected]&gt;
2773
2774 Author: Xufeng Liu
2775 &lt;mailto:[email protected]&gt;
2776
2777 Author: Santosh Easale
2778 &lt;mailto:[email protected]&gt;
2779
2780 Author: Xia Chen
2781 &lt;mailto:[email protected]&gt;
2782
2783 Author: Himanshu Shah
2784 &lt;mailto:[email protected]&gt;";
2785 description
2786 "This YANG module defines the essential components for the
2787 management of Multiprotocol Label Switching (MPLS) Label
2788 Distribution Protocol (LDP). It is also the base model to
2789 be augmented for Multipoint LDP (mLDP).
2790
2791 Copyright (c) 2022 IETF Trust and the persons identified as
2792 authors of the code. All rights reserved.
2793
2794 Redistribution and use in source and binary forms, with or
2795 without modification, is permitted pursuant to, and subject
2796 to the license terms contained in, the Revised BSD License
2797 set forth in Section 4.c of the IETF Trust's Legal Provisions
2798 Relating to IETF Documents
2799 (https://trustee.ietf.org/license-info).
2800
2801 This version of this YANG module is part of RFC 9070; see the
2802 RFC itself for full legal notices.";
2803
2804 revision 2022-03-14 {
2805 description
2806 "Initial revision.";
2807 reference
2808 "RFC 9070: YANG Data Model for MPLS LDP";
2809 }
2810
2811 /*
2812 * Typedefs
2813 */
2814
2815 typedef advertised-received {
2816 type enumeration {
2817 enum advertised {
2818 description
2819 "Advertised information.";
2820 }
2821 enum received {
2822 description
2823 "Received information.";
2824 }
2825 }
2826 description
2827 "Received or advertised.";
2828 }
2829
2830 typedef downstream-upstream {
2831 type enumeration {
2832 enum downstream {
2833 description
2834 "Downstream information.";
2835 }
2836 enum upstream {
2837 description
2838 "Upstream information.";
2839 }
2840 }
2841 description
2842 "Downstream or upstream.";
2843 }
2844
2845 typedef label-adv-mode {
2846 type enumeration {
2847 enum downstream-unsolicited {
2848 description
2849 "Downstream Unsolicited.";
2850 }
2851 enum downstream-on-demand {
2852 description
2853 "Downstream on Demand.";
2854 }
2855 }
2856 description
2857 "Label Advertisement Mode.";
2858 }
2859
2860 typedef oper-status-event-type {
2861 type enumeration {
2862 enum up {
2863 value 1;
2864 description
2865 "Operational status changed to up.";
2866 }
2867 enum down {
2868 value 2;
2869 description
2870 "Operational status changed to down.";
2871 }
2872 }
2873 description
2874 "Operational status event type for notifications.";
2875 }
2876
2877 /*
2878 * Identities
2879 */
2880
2881 identity mpls-ldp {
2882 base rt:control-plane-protocol;
2883 description
2884 "LDP protocol.";
2885 reference
2886 "RFC 5036: LDP Specification";
2887 }
2888
2889 identity adjacency-flag-base {
2890 description
2891 "Base type for adjacency flags.";
2892 }
2893
2894 identity adjacency-flag-active {
2895 base adjacency-flag-base;
2896 description
2897 "This adjacency is configured and actively created.";
2898 }
2899
2900 identity adjacency-flag-passive {
2901 base adjacency-flag-base;
2902 description
2903 "This adjacency is not configured and passively accepted.";
2904 }
2905
2906 /*
2907 * Groupings
2908 */
2909
2910 grouping adjacency-state-attributes {
2911 description
2912 "The operational state attributes of an LDP Hello adjacency,
2913 which can used for basic and extended discoveries, in IPv4 and
2914 IPv6 address families.";
2915 leaf-list flag {
2916 type identityref {
2917 base adjacency-flag-base;
2918 }
2919 description
2920 "One or more flags to indicate whether the adjacency is
2921 actively created, passively accepted, or both.";
2922 }
2923 container hello-holdtime {
2924 description
2925 "Containing Hello holdtime state information.";
2926 leaf adjacent {
2927 type uint16;
2928 units "seconds";
2929 description
2930 "The holdtime value learned from the adjacent LSR.";
2931 }
2932 leaf negotiated {
2933 type uint16;
2934 units "seconds";
2935 description
2936 "The holdtime negotiated between this LSR and the adjacent
2937 LSR.";
2938 }
2939 leaf remaining {
2940 type uint16;
2941 units "seconds";
2942 description
2943 "The time remaining until the holdtime timer expires.";
2944 }
2945 }
2946 leaf next-hello {
2947 type uint16;
2948 units "seconds";
2949 description
2950 "The time when the next Hello message will be sent.";
2951 }
2952 container statistics {
2953 description
2954 "Statistics objects.";
2955 leaf discontinuity-time {
2956 type yang:date-and-time;
2957 mandatory true;
2958 description
2959 "The time on the most recent occasion at which any one or
2960 more of this interface's counters suffered a
2961 discontinuity. If no such discontinuities have occurred
2962 since the last re-initialization of the local management
2963 subsystem, then this node contains the time the local
2964 management subsystem re-initialized itself.";
2965 }
2966 leaf hello-received {
2967 type yang:counter64;
2968 description
2969 "The number of Hello messages received.";
2970 }
2971 leaf hello-dropped {
2972 type yang:counter64;
2973 description
2974 "The number of Hello messages dropped.";
2975 }
2976 } // statistics
2977 } // adjacency-state-attributes
2978
2979 grouping basic-discovery-timers {
2980 description
2981 "The timer attributes for basic discovery, used in the
2982 per-interface setting and in the all-interface setting.";
2983 leaf hello-holdtime {
2984 type uint16 {
2985 range "15..3600";
2986 }
2987 units "seconds";
2988 description
2989 "The time interval for which an LDP link Hello adjacency
2990 is maintained in the absence of link Hello messages from
2991 the LDP neighbor.
2992 This leaf may be configured at the per-interface level or
2993 the global level, with precedence given to the value at the
2994 per-interface level. If the leaf is not configured at
2995 either level, the default value at the global level is
2996 used.";
2997 }
2998 leaf hello-interval {
2999 type uint16 {
3000 range "5..1200";
3001 }
3002 units "seconds";
3003 description
3004 "The interval between consecutive LDP link Hello messages
3005 used in basic LDP discovery.
3006 This leaf may be configured at the per-interface level or
3007 the global level, with precedence given to the value at the
3008 per-interface level. If the leaf is not configured at
3009 either level, the default value at the global level is
3010 used.";
3011 }
3012 } // basic-discovery-timers
3013
3014 grouping binding-address-state-attributes {
3015 description
3016 "Operational state attributes of an address binding, used in
3017 IPv4 and IPv6 address families.";
3018 leaf advertisement-type {
3019 type advertised-received;
3020 description
3021 "Received or advertised.";
3022 }
3023 container peer {
3024 when "../advertisement-type = 'received'" {
3025 description
3026 "Applicable for received address.";
3027 }
3028 description
3029 "LDP peer from which this address is received.";
3030 uses ldp-peer-ref-from-binding;
3031 }
3032 } // binding-address-state-attributes
3033
3034 grouping binding-label-state-attributes {
3035 description
3036 "Operational state attributes for a FEC-Label binding, used in
3037 IPv4 and IPv6 address families.";
3038 list peer {
3039 key "lsr-id label-space-id advertisement-type";
3040 description
3041 "List of advertised and received peers.";
3042 uses ldp-peer-ref-from-binding {
3043 description
3044 "The LDP peer from which this binding is received, or to
3045 which this binding is advertised.
3046 The peer is identified by its LDP ID, which consists of
3047 the LSR Id and the label space Id.";
3048 }
3049 leaf advertisement-type {
3050 type advertised-received;
3051 description
3052 "Received or advertised.";
3053 }
3054 leaf label {
3055 type rt-types:mpls-label;
3056 description
3057 "Advertised (outbound) or received (inbound)
3058 label.";
3059 }
3060 leaf used-in-forwarding {
3061 type boolean;
3062 description
3063 "'true' if the label is used in forwarding.";
3064 }
3065 } // peer
3066 } // binding-label-state-attributes
3067
3068 grouping graceful-restart-attributes-per-peer {
3069 description
3070 "Per-peer graceful restart attributes.
3071 On the local side, these attributes are configuration and
3072 operational state data. On the peer side, these attributes
3073 are operational state data received from the peer.";
3074 container graceful-restart {
3075 description
3076 "Attributes for graceful restart.";
3077 leaf enabled {
3078 type boolean;
3079 description
3080 "Enable or disable graceful restart.
3081 This leaf may be configured at the per-peer level or the
3082 global level, with precedence given to the value at the
3083 per-peer level. If the leaf is not configured at either
3084 level, the default value at the global level is used.";
3085 }
3086 leaf reconnect-time {
3087 type uint16 {
3088 range "10..1800";
3089 }
3090 units "seconds";
3091 description
3092 "Specifies the time interval that the remote LDP peer
3093 must wait for the local LDP peer to reconnect after the
3094 remote peer detects the LDP communication failure.
3095 This leaf may be configured at the per-peer level or the
3096 global level, with precedence given to the value at the
3097 per-peer level. If the leaf is not configured at either
3098 level, the default value at the global level is used.";
3099 }
3100 leaf recovery-time {
3101 type uint16 {
3102 range "30..3600";
3103 }
3104 units "seconds";
3105 description
3106 "Specifies the time interval, in seconds, that the remote
3107 LDP peer preserves its MPLS forwarding state after
3108 receiving the Initialization message from the restarted
3109 local LDP peer.
3110 This leaf may be configured at the per-peer level or the
3111 global level, with precedence given to the value at the
3112 per-peer level. If the leaf is not configured at either
3113 level, the default value at the global level is used.";
3114 }
3115 } // graceful-restart
3116 } // graceful-restart-attributes-per-peer
3117
3118 grouping ldp-interface-ref {
3119 description
3120 "Defining a reference to an LDP interface.";
3121 leaf name {
3122 type if:interface-ref;
3123 must '(/if:interfaces/if:interface[if:name=current()]/ip:ipv4)'
3124 + ' or '
3125 + '(/if:interfaces/if:interface[if:name=current()]/ip:ipv6)'
3126 {
3127 description
3128 "Interface is IPv4 or IPv6.";
3129 }
3130 description
3131 "The name of an LDP interface.";
3132 }
3133 }
3134
3135 grouping ldp-peer-ref-absolute {
3136 description
3137 "An absolute reference to an LDP peer, by the LDP ID, which
3138 consists of the LSR Id and the label space Id.";
3139 leaf protocol-name {
3140 type leafref {
3141 path "/rt:routing/rt:control-plane-protocols/"
3142 + "rt:control-plane-protocol/rt:name";
3143 }
3144 description
3145 "The name of the LDP protocol instance.";
3146 }
3147 leaf lsr-id {
3148 type leafref {
3149 path "/rt:routing/rt:control-plane-protocols/"
3150 + "rt:control-plane-protocol"
3151 + "[rt:name=current()/../protocol-name]/"
3152 + "ldp:mpls-ldp/ldp:peers/ldp:peer/ldp:lsr-id";
3153 }
3154 description
3155 "The LSR Id of the peer, as a portion of the peer LDP ID.";
3156 }
3157 leaf label-space-id {
3158 type leafref {
3159 path "/rt:routing/rt:control-plane-protocols/"
3160 + "rt:control-plane-protocol"
3161 + "[rt:name=current()/../protocol-name]/"
3162 + "ldp:mpls-ldp/ldp:peers/"
3163 + "ldp:peer[ldp:lsr-id=current()/../lsr-id]/"
3164 + "ldp:label-space-id";
3165 }
3166 description
3167 "The label space Id of the peer, as a portion of the peer
3168 LDP ID.";
3169 }
3170 } // ldp-peer-ref-absolute
3171
3172 grouping ldp-peer-ref-from-binding {
3173 description
3174 "A relative reference to an LDP peer, by the LDP ID, which
3175 consists of the LSR Id and the label space Id.";
3176 leaf lsr-id {
3177 type leafref {
3178 path "../../../../../../../ldp:peers/ldp:peer/ldp:lsr-id";
3179 }
3180 description
3181 "The LSR Id of the peer, as a portion of the peer LDP ID.";
3182 }
3183 leaf label-space-id {
3184 type leafref {
3185 path "../../../../../../../ldp:peers/"
3186 + "ldp:peer[ldp:lsr-id=current()/../lsr-id]/"
3187 + "ldp:label-space-id";
3188 }
3189 description
3190 "The label space Id of the peer, as a portion of the peer
3191 LDP ID.";
3192 }
3193 } // ldp-peer-ref-from-binding
3194
3195 grouping ldp-peer-ref-from-interface {
3196 description
3197 "A relative reference to an LDP peer, by the LDP ID, which
3198 consists of the LSR Id and the label space Id.";
3199 container peer {
3200 description
3201 "Reference to an LDP peer, by the LDP ID, which consists of
3202 the LSR Id and the label space Id.";
3203 leaf lsr-id {
3204 type leafref {
3205 path "../../../../../../../../../ldp:peers/ldp:peer/"
3206 + "ldp:lsr-id";
3207 }
3208 description
3209 "The LSR Id of the peer, as a portion of the peer LDP ID.";
3210 }
3211 leaf label-space-id {
3212 type leafref {
3213 path "../../../../../../../../../ldp:peers/"
3214 + "ldp:peer[ldp:lsr-id=current()/../lsr-id]/"
3215 + "ldp:label-space-id";
3216 }
3217 description
3218 "The label space Id of the peer, as a portion of the peer
3219 LDP ID.";
3220 }
3221 } // peer
3222 } // ldp-peer-ref-from-interface
3223
3224 grouping ldp-peer-ref-from-target {
3225 description
3226 "A relative reference to an LDP peer, by the LDP ID, which
3227 consists of the LSR Id and the label space Id.";
3228 container peer {
3229 description
3230 "Reference to an LDP peer, by the LDP ID, which consists of
3231 the LSR Id and the label space Id.";
3232 leaf lsr-id {
3233 type leafref {
3234 path "../../../../../../../../ldp:peers/ldp:peer/"
3235 + "ldp:lsr-id";
3236 }
3237 description
3238 "The LSR Id of the peer, as a portion of the peer LDP ID.";
3239 }
3240 leaf label-space-id {
3241 type leafref {
3242 path "../../../../../../../../ldp:peers/"
3243 + "ldp:peer[ldp:lsr-id=current()/../lsr-id]/"
3244 + "ldp:label-space-id";
3245 }
3246 description
3247 "The label space Id of the peer, as a portion of the peer
3248 LDP ID.";
3249 }
3250 } // peer
3251 } // ldp-peer-ref-from-target
3252
3253 grouping peer-attributes {
3254 description
3255 "Peer configuration attributes, used in the per-peer setting
3256 can in the all-peer setting.";
3257 leaf session-ka-holdtime {
3258 type uint16 {
3259 range "45..3600";
3260 }
3261 units "seconds";
3262 description
3263 "The time interval after which an inactive LDP session
3264 terminates and the corresponding TCP session closes.
3265 Inactivity is defined as not receiving LDP packets from the
3266 peer.
3267 This leaf may be configured at the per-peer level or the
3268 global level, with precedence given to the value at the
3269 per-peer level. If the leaf is not configured at either
3270 level, the default value at the global level is used.";
3271 }
3272 leaf session-ka-interval {
3273 type uint16 {
3274 range "15..1200";
3275 }
3276 units "seconds";
3277 description
3278 "The interval between successive transmissions of KeepAlive
3279 packets. Keepalive packets are only sent in the absence of
3280 other LDP packets transmitted over the LDP session.
3281 This leaf may be configured at the per-peer level or the
3282 global level, with precedence given to the value at the
3283 per-peer level. If the leaf is not configured at either
3284 level, the default value at the global level is used.";
3285 }
3286 } // peer-attributes
3287
3288 grouping peer-authentication {
3289 description
3290 "Peer authentication container, used in the per-peer setting
3291 can in the all-peer setting.";
3292 container authentication {
3293 description
3294 "Containing authentication information.";
3295 choice authentication-type {
3296 description
3297 "Choice of authentication.";
3298 case password {
3299 leaf key {
3300 type string;
3301 description
3302 "This leaf specifies the authentication key. The
3303 length of the key may be dependent on the
3304 cryptographic algorithm.";
3305 }
3306 leaf crypto-algorithm {
3307 type identityref {
3308 base key-chain:crypto-algorithm;
3309 }
3310 description
3311 "Cryptographic algorithm associated with key.";
3312 }
3313 }
3314 }
3315 }
3316 } // peer-authentication
3317
3318 grouping peer-state-derived {
3319 description
3320 "The peer state information derived from the LDP protocol
3321 operations.";
3322 container label-advertisement-mode {
3323 config false;
3324 description
3325 "Label advertisement mode state.";
3326 leaf local {
3327 type label-adv-mode;
3328 description
3329 "Local Label Advertisement Mode.";
3330 }
3331 leaf peer {
3332 type label-adv-mode;
3333 description
3334 "Peer Label Advertisement Mode.";
3335 }
3336 leaf negotiated {
3337 type label-adv-mode;
3338 description
3339 "Negotiated Label Advertisement Mode.";
3340 }
3341 }
3342 leaf next-keep-alive {
3343 type uint16;
3344 units "seconds";
3345 config false;
3346 description
3347 "Time duration from now until sending the next KeepAlive
3348 message.";
3349 }
3350 container received-peer-state {
3351 config false;
3352 description
3353 "Operational state information learned from the peer.";
3354 uses graceful-restart-attributes-per-peer;
3355 container capability {
3356 description
3357 "Peer capability information.";
3358 container end-of-lib {
3359 description
3360 "Peer's end-of-lib capability.";
3361 leaf enabled {
3362 type boolean;
3363 description
3364 "'true' if peer's end-of-lib capability is enabled.";
3365 }
3366 }
3367 container typed-wildcard-fec {
3368 description
3369 "Peer's typed-wildcard-fec capability.";
3370 leaf enabled {
3371 type boolean;
3372 description
3373 "'true' if peer's typed-wildcard-fec capability is
3374 enabled.";
3375 }
3376 }
3377 container upstream-label-assignment {
3378 description
3379 "Peer's upstream label assignment capability.";
3380 leaf enabled {
3381 type boolean;
3382 description
3383 "'true' if peer's upstream label assignment is
3384 enabled.";
3385 }
3386 }
3387 } // capability
3388 } // received-peer-state
3389 container session-holdtime {
3390 config false;
3391 description
3392 "Session holdtime state.";
3393 leaf peer {
3394 type uint16;
3395 units "seconds";
3396 description
3397 "Peer holdtime.";
3398 }
3399 leaf negotiated {
3400 type uint16;
3401 units "seconds";
3402 description
3403 "Negotiated holdtime.";
3404 }
3405 leaf remaining {
3406 type uint16;
3407 units "seconds";
3408 description
3409 "Remaining holdtime.";
3410 }
3411 } // session-holdtime
3412 leaf session-state {
3413 type enumeration {
3414 enum non-existent {
3415 description
3416 "NON EXISTENT state. Transport disconnected.";
3417 }
3418 enum initialized {
3419 description
3420 "INITIALIZED state.";
3421 }
3422 enum openrec {
3423 description
3424 "OPENREC state.";
3425 }
3426 enum opensent {
3427 description
3428 "OPENSENT state.";
3429 }
3430 enum operational {
3431 description
3432 "OPERATIONAL state.";
3433 }
3434 }
3435 config false;
3436 description
3437 "Representing the operational status of the LDP session.";
3438 reference
3439 "RFC 5036: LDP Specification, Sec. 2.5.4.";
3440 }
3441 container tcp-connection {
3442 config false;
3443 description
3444 "TCP connection state.";
3445 leaf local-address {
3446 type inet:ip-address;
3447 description
3448 "Local address.";
3449 }
3450 leaf local-port {
3451 type inet:port-number;
3452 description
3453 "Local port number.";
3454 }
3455 leaf remote-address {
3456 type inet:ip-address;
3457 description
3458 "Remote address.";
3459 }
3460 leaf remote-port {
3461 type inet:port-number;
3462 description
3463 "Remote port number.";
3464 }
3465 } // tcp-connection
3466 leaf up-time {
3467 type rt-types:timeticks64;
3468 config false;
3469 description
3470 "The number of time ticks (hundredths of a second) since the
3471 state of the session with the peer changed to
3472 OPERATIONAL.";
3473 }
3474 container statistics {
3475 config false;
3476 description
3477 "Statistics objects.";
3478 leaf discontinuity-time {
3479 type yang:date-and-time;
3480 mandatory true;
3481 description
3482 "The time on the most recent occasion at which any one or
3483 more of this interface's counters suffered a
3484 discontinuity. If no such discontinuities have occurred
3485 since the last re-initialization of the local management
3486 subsystem, then this node contains the time the local
3487 management subsystem re-initialized itself.";
3488 }
3489 container received {
3490 description
3491 "Inbound statistics.";
3492 uses statistics-peer-received-sent;
3493 }
3494 container sent {
3495 description
3496 "Outbound statistics.";
3497 uses statistics-peer-received-sent;
3498 }
3499 leaf total-addresses {
3500 type uint32;
3501 description
3502 "The number of learned addresses.";
3503 }
3504 leaf total-labels {
3505 type uint32;
3506 description
3507 "The number of learned labels.";
3508 }
3509 leaf total-fec-label-bindings {
3510 type uint32;
3511 description
3512 "The number of learned label-address bindings.";
3513 }
3514 } // statistics
3515 } // peer-state-derived
3516
3517 grouping statistics-peer-received-sent {
3518 description
3519 "Inbound and outbound statistic counters.";
3520 leaf total-octets {
3521 type yang:counter64;
3522 description
3523 "The total number of octets sent or received.";
3524 }
3525 leaf total-messages {
3526 type yang:counter64;
3527 description
3528 "The number of messages sent or received.";
3529 }
3530 leaf address {
3531 type yang:counter64;
3532 description
3533 "The number of Address messages sent or received.";
3534 }
3535 leaf address-withdraw {
3536 type yang:counter64;
3537 description
3538 "The number of address-withdraw messages sent or received.";
3539 }
3540 leaf initialization {
3541 type yang:counter64;
3542 description
3543 "The number of Initialization messages sent or received.";
3544 }
3545 leaf keepalive {
3546 type yang:counter64;
3547 description
3548 "The number of KeepAlive messages sent or received.";
3549 }
3550 leaf label-abort-request {
3551 type yang:counter64;
3552 description
3553 "The number of label-abort-request messages sent or
3554 received.";
3555 }
3556 leaf label-mapping {
3557 type yang:counter64;
3558 description
3559 "The number of label-mapping messages sent or received.";
3560 }
3561 leaf label-release {
3562 type yang:counter64;
3563 description
3564 "The number of label-release messages sent or received.";
3565 }
3566 leaf label-request {
3567 type yang:counter64;
3568 description
3569 "The number of label-request messages sent or received.";
3570 }
3571 leaf label-withdraw {
3572 type yang:counter64;
3573 description
3574 "The number of label-withdraw messages sent or received.";
3575 }
3576 leaf notification {
3577 type yang:counter64;
3578 description
3579 "The number of notification messages sent or received.";
3580 }
3581 } // statistics-peer-received-sent
3582
3583 /*
3584 * Configuration data and operational state data nodes
3585 */
3586
3587 augment "/rt:routing/rt:control-plane-protocols/"
3588 + "rt:control-plane-protocol" {
3589 when "derived-from-or-self(rt:type, 'ldp:mpls-ldp')" {
3590 description
3591 "This augmentation is only valid for a control plane
3592 protocol instance of LDP (type 'mpls-ldp').";
3593 }
3594 description
3595 "LDP augmentation to routing control plane protocol
3596 configuration and state.";
3597 container mpls-ldp {
3598 must "not (../../rt:control-plane-protocol"
3599 + "[derived-from-or-self(rt:type, 'ldp:mpls-ldp')]"
3600 + "[rt:name!=current()/../rt:name])" {
3601 description
3602 "Only one LDP instance is allowed.";
3603 }
3604 description
3605 "Containing configuration and operational data for the LDP
3606 protocol.";
3607 container global {
3608 description
3609 "Global attributes for LDP.";
3610 container capability {
3611 description
3612 "Containing the LDP capability data. The container is
3613 used for augmentations.";
3614 reference
3615 "RFC 5036: LDP Specification, Sec. 1.5.";
3616 }
3617 container graceful-restart {
3618 description
3619 "Attributes for graceful restart.";
3620 leaf enabled {
3621 type boolean;
3622 default "false";
3623 description
3624 "Enable or disable graceful restart.";
3625 }
3626 leaf reconnect-time {
3627 type uint16 {
3628 range "10..1800";
3629 }
3630 units "seconds";
3631 default "120";
3632 description
3633 "Specifies the time interval that the remote LDP peer
3634 must wait for the local LDP peer to reconnect after
3635 the remote peer detects the LDP communication
3636 failure.";
3637 }
3638 leaf recovery-time {
3639 type uint16 {
3640 range "30..3600";
3641 }
3642 units "seconds";
3643 default "120";
3644 description
3645 "Specifies the time interval, in seconds, that the
3646 remote LDP peer preserves its MPLS forwarding state
3647 after receiving the Initialization message from the
3648 restarted local LDP peer.";
3649 }
3650 leaf forwarding-holdtime {
3651 type uint16 {
3652 range "30..3600";
3653 }
3654 units "seconds";
3655 default "180";
3656 description
3657 "Specifies the time interval, in seconds, before the
3658 termination of the recovery phase.";
3659 }
3660 } // graceful-restart
3661 leaf lsr-id {
3662 type rt-types:router-id;
3663 description
3664 "Specifies the value to act as the LDP LSR Id.
3665 If this attribute is not specified, LDP uses the router
3666 ID as determined by the system.";
3667 }
3668 container address-families {
3669 description
3670 "Per-address-family configuration and operational state.
3671 The address family can be either IPv4 or IPv6.";
3672 container ipv4 {
3673 presence "Present if IPv4 is enabled, unless the
3674 'enabled' leaf is set to 'false'.";
3675 description
3676 "Containing data related to the IPv4 address family.";
3677 leaf enabled {
3678 type boolean;
3679 default "true";
3680 description
3681 "'false' to disable the address family.";
3682 }
3683 leaf label-distribution-control-mode {
3684 type enumeration {
3685 enum independent {
3686 description
3687 "Independent label distribution control.";
3688 }
3689 enum ordered {
3690 description
3691 "Ordered label distribution control.";
3692 }
3693 }
3694 config false;
3695 description
3696 "Label distribution control mode.";
3697 reference
3698 "RFC 5036: LDP Specification, Sec. 2.6.";
3699 }
3700 // ipv4 bindings
3701 container bindings {
3702 config false;
3703 description
3704 "LDP address and label binding information.";
3705 list address {
3706 key "address";
3707 description
3708 "List of address bindings learned by LDP.";
3709 leaf address {
3710 type inet:ipv4-address;
3711 description
3712 "The IPv4 address learned from an Address
3713 message received from or advertised to a peer.";
3714 }
3715 uses binding-address-state-attributes;
3716 }
3717 list fec-label {
3718 key "fec";
3719 description
3720 "List of FEC-label bindings learned by LDP.";
3721 leaf fec {
3722 type inet:ipv4-prefix;
3723 description
3724 "The prefix FEC value in the FEC-Label binding,
3725 learned in a Label Mapping message received from
3726 or advertised to a peer.";
3727 }
3728 uses binding-label-state-attributes;
3729 }
3730 } // bindings
3731 } // ipv4
3732 } // address-families
3733 } // global
3734 container discovery {
3735 description
3736 "Neighbor-discovery configuration and operational state.";
3737 container interfaces {
3738 description
3739 "A list of interfaces for LDP Basic Discovery.";
3740 reference
3741 "RFC 5036: LDP Specification, Sec. 2.4.1.";
3742 uses basic-discovery-timers {
3743 refine "hello-holdtime" {
3744 default "15";
3745 }
3746 refine "hello-interval" {
3747 default "5";
3748 }
3749 }
3750 list interface {
3751 key "name";
3752 description
3753 "List of LDP interfaces used for LDP Basic Discovery.";
3754 uses ldp-interface-ref;
3755 leaf next-hello {
3756 type uint16;
3757 units "seconds";
3758 config false;
3759 description
3760 "Time to send the next Hello message.";
3761 }
3762 container address-families {
3763 description
3764 "Container for address families.";
3765 container ipv4 {
3766 presence "Present if IPv4 is enabled, unless the
3767 'enabled' leaf is set to 'false'.";
3768 description
3769 "IPv4 address family.";
3770 leaf enabled {
3771 type boolean;
3772 default "true";
3773 description
3774 "Set to false to disable the address family on
3775 the interface.";
3776 }
3777 container hello-adjacencies {
3778 config false;
3779 description
3780 "Containing a list of Hello adjacencies.";
3781 list hello-adjacency {
3782 key "adjacent-address";
3783 config false;
3784 description
3785 "List of Hello adjacencies.";
3786 leaf adjacent-address {
3787 type inet:ipv4-address;
3788 description
3789 "Neighbor address of the Hello adjacency.";
3790 }
3791 uses adjacency-state-attributes;
3792 uses ldp-peer-ref-from-interface;
3793 }
3794 }
3795 } // ipv4
3796 } // address-families
3797 } // interface
3798 } // interfaces
3799 container targeted {
3800 description
3801 "A list of targeted neighbors for extended discovery.";
3802 leaf hello-holdtime {
3803 type uint16 {
3804 range "15..3600";
3805 }
3806 units "seconds";
3807 default "45";
3808 description
3809 "The time interval for which an LDP targeted Hello
3810 adjacency is maintained in the absence of targeted
3811 Hello messages from an LDP neighbor.";
3812 }
3813 leaf hello-interval {
3814 type uint16 {
3815 range "5..3600";
3816 }
3817 units "seconds";
3818 default "15";
3819 description
3820 "The interval between consecutive LDP targeted Hello
3821 messages used in extended LDP discovery.";
3822 }
3823 container hello-accept {
3824 description
3825 "LDP policy to control the acceptance of extended
3826 neighbor-discovery Hello messages.";
3827 leaf enabled {
3828 type boolean;
3829 default "false";
3830 description
3831 "'true' to accept; 'false' to deny.";
3832 }
3833 }
3834 container address-families {
3835 description
3836 "Container for address families.";
3837 container ipv4 {
3838 presence "Present if IPv4 is enabled.";
3839 description
3840 "IPv4 address family.";
3841 container hello-adjacencies {
3842 config false;
3843 description
3844 "Containing a list of Hello adjacencies.";
3845 list hello-adjacency {
3846 key "local-address adjacent-address";
3847 description
3848 "List of Hello adjacencies.";
3849 leaf local-address {
3850 type inet:ipv4-address;
3851 description
3852 "Local address of the Hello adjacency.";
3853 }
3854 leaf adjacent-address {
3855 type inet:ipv4-address;
3856 description
3857 "Neighbor address of the Hello adjacency.";
3858 }
3859 uses adjacency-state-attributes;
3860 uses ldp-peer-ref-from-target;
3861 }
3862 }
3863 list target {
3864 key "adjacent-address";
3865 description
3866 "Targeted discovery params.";
3867 leaf adjacent-address {
3868 type inet:ipv4-address;
3869 description
3870 "Configures a remote LDP neighbor for the
3871 extended LDP discovery.";
3872 }
3873 leaf enabled {
3874 type boolean;
3875 default "true";
3876 description
3877 "'true' to enable the target.";
3878 }
3879 leaf local-address {
3880 type inet:ipv4-address;
3881 description
3882 "The local address used as the source address to
3883 send targeted Hello messages.
3884 If the value is not specified, the
3885 transport address is used as the source
3886 address.";
3887 }
3888 } // target
3889 } // ipv4
3890 } // address-families
3891 } // targeted
3892 } // discovery
3893 container peers {
3894 description
3895 "Peers configuration attributes.";
3896 uses peer-authentication;
3897 uses peer-attributes {
3898 refine "session-ka-holdtime" {
3899 default "180";
3900 }
3901 refine "session-ka-interval" {
3902 default "60";
3903 }
3904 }
3905 list peer {
3906 key "lsr-id label-space-id";
3907 description
3908 "List of peers.";
3909 leaf lsr-id {
3910 type rt-types:router-id;
3911 description
3912 "The LSR Id of the peer, used to identify the globally
3913 unique LSR. This is the first four octets of the LDP
3914 ID. This leaf is used together with the leaf
3915 'label-space-id' to form the LDP ID.";
3916 reference
3917 "RFC 5036: LDP Specification, Sec. 2.2.2.";
3918 }
3919 leaf label-space-id {
3920 type uint16;
3921 description
3922 "The label space Id of the peer, used to identify a
3923 specific label space within the LSR. This is the last
3924 two octets of the LDP ID. This leaf is used together
3925 with the leaf 'lsr-id' to form the LDP ID.";
3926 reference
3927 "RFC 5036: LDP Specification, Sec. 2.2.2.";
3928 }
3929 uses peer-authentication;
3930 container address-families {
3931 description
3932 "Per-vrf per-af params.";
3933 container ipv4 {
3934 presence "Present if IPv4 is enabled.";
3935 description
3936 "IPv4 address family.";
3937 container hello-adjacencies {
3938 config false;
3939 description
3940 "Containing a list of Hello adjacencies.";
3941 list hello-adjacency {
3942 key "local-address adjacent-address";
3943 description
3944 "List of Hello adjacencies.";
3945 leaf local-address {
3946 type inet:ipv4-address;
3947 description
3948 "Local address of the Hello adjacency.";
3949 }
3950 leaf adjacent-address {
3951 type inet:ipv4-address;
3952 description
3953 "Neighbor address of the Hello adjacency.";
3954 }
3955 uses adjacency-state-attributes;
3956 leaf interface {
3957 type if:interface-ref;
3958 description
3959 "Interface for this adjacency.";
3960 }
3961 }
3962 }
3963 } // ipv4
3964 } // address-families
3965 uses peer-state-derived;
3966 } // list peer
3967 } // peers
3968 } // container mpls-ldp
3969 }
3970
3971 /*
3972 * RPCs
3973 */
3974
3975 rpc mpls-ldp-clear-peer {
3976 description
3977 "Clears the session to the peer.";
3978 input {
3979 uses ldp-peer-ref-absolute {
3980 description
3981 "The LDP peer to be cleared. If this is not provided,
3982 then all peers are cleared.
3983 The peer is identified by its LDP ID, which consists of
3984 the LSR Id and the label space Id.";
3985 }
3986 }
3987 }
3988
3989 rpc mpls-ldp-clear-hello-adjacency {
3990 description
3991 "Clears the Hello adjacency.";
3992 input {
3993 container hello-adjacency {
3994 description
3995 "Link adjacency or targeted adjacency. If this is not
3996 provided, then all Hello adjacencies are cleared.";
3997 leaf protocol-name {
3998 type leafref {
3999 path "/rt:routing/rt:control-plane-protocols/"
4000 + "rt:control-plane-protocol/rt:name";
4001 }
4002 description
4003 "The name of the LDP protocol instance.";
4004 }
4005 choice hello-adjacency-type {
4006 description
4007 "Adjacency type.";
4008 case targeted {
4009 container targeted {
4010 presence "Present to clear targeted adjacencies.";
4011 description
4012 "Clear targeted adjacencies.";
4013 leaf target-address {
4014 type inet:ip-address;
4015 description
4016 "The target address. If this is not provided, then
4017 all targeted adjacencies are cleared.";
4018 }
4019 }
4020 }
4021 case link {
4022 container link {
4023 presence "Present to clear link adjacencies.";
4024 description
4025 "Clear link adjacencies.";
4026 leaf next-hop-interface {
4027 type leafref {
4028 path "/rt:routing/rt:control-plane-protocols/"
4029 + "rt:control-plane-protocol/mpls-ldp/"
4030 + "discovery/interfaces/interface/name";
4031 }
4032 description
4033 "Interface connecting to a next hop. If this is
4034 not provided, then all link adjacencies are
4035 cleared.";
4036 }
4037 leaf next-hop-address {
4038 type inet:ip-address;
4039 must '../next-hop-interface' {
4040 description
4041 "Applicable when an interface is specified.";
4042 }
4043 description
4044 "IP address of a next hop. If this is not
4045 provided, then adjacencies to all next hops on the
4046 given interface are cleared.";
4047 }
4048 }
4049 }
4050 } // hello-adjacency-type
4051 } // hello-adjacency
4052 } // input
4053 } // mpls-ldp-clear-hello-adjacency
4054
4055 rpc mpls-ldp-clear-peer-statistics {
4056 description
4057 "Clears protocol statistics (e.g., sent and received
4058 counters).";
4059 input {
4060 uses ldp-peer-ref-absolute {
4061 description
4062 "The LDP peer whose statistics are to be cleared.
4063 If this is not provided, then all peers' statistics are
4064 cleared.
4065 The peer is identified by its LDP ID, which consists of
4066 the LSR Id and the label space Id.";
4067 }
4068 }
4069 }
4070
4071 /*
4072 * Notifications
4073 */
4074
4075 notification mpls-ldp-peer-event {
4076 description
4077 "Notification event for a change of LDP peer operational
4078 status.";
4079 leaf event-type {
4080 type oper-status-event-type;
4081 description
4082 "Event type.";
4083 }
4084 container peer {
4085 description
4086 "Reference to an LDP peer, by the LDP ID, which consists of
4087 the LSR Id and the label space Id.";
4088 uses ldp-peer-ref-absolute;
4089 }
4090 }
4091
4092 notification mpls-ldp-hello-adjacency-event {
4093 description
4094 "Notification event for a change of LDP adjacency operational
4095 status.";
4096 leaf event-type {
4097 type oper-status-event-type;
4098 description
4099 "Event type.";
4100 }
4101 leaf protocol-name {
4102 type leafref {
4103 path "/rt:routing/rt:control-plane-protocols/"
4104 + "rt:control-plane-protocol/rt:name";
4105 }
4106 description
4107 "The name of the LDP protocol instance.";
4108 }
4109 choice hello-adjacency-type {
4110 description
4111 "Interface or targeted adjacency.";
4112 case targeted {
4113 container targeted {
4114 description
4115 "Targeted adjacency through LDP extended discovery.";
4116 leaf target-address {
4117 type inet:ip-address;
4118 description
4119 "The target adjacent-address learned.";
4120 }
4121 }
4122 }
4123 case link {
4124 container link {
4125 description
4126 "Link adjacency through LDP basic discovery.";
4127 leaf next-hop-interface {
4128 type if:interface-ref;
4129 description
4130 "The interface connecting to the adjacent next hop.";
4131 }
4132 leaf next-hop-address {
4133 type inet:ip-address;
4134 must '../next-hop-interface' {
4135 description
4136 "Applicable when an interface is specified.";
4137 }
4138 description
4139 "IP address of the next hop. This can be IPv4 or IPv6
4140 address.";
4141 }
4142 }
4143 }
4144 } // hello-adjacency-type
4145 } // mpls-ldp-hello-adjacency-event
4146
4147 notification mpls-ldp-fec-event {
4148 description
4149 "Notification event for a change of FEC status.";
4150 leaf event-type {
4151 type oper-status-event-type;
4152 description
4153 "Event type.";
4154 }
4155 leaf protocol-name {
4156 type leafref {
4157 path "/rt:routing/rt:control-plane-protocols/"
4158 + "rt:control-plane-protocol/rt:name";
4159 }
4160 description
4161 "The name of the LDP protocol instance.";
4162 }
4163 leaf fec {
4164 type inet:ip-prefix;
4165 description
4166 "The address prefix element of the FEC whose status
4167 has changed.";
4168 }
4169 }
4170 }
4171
4172
4173 &lt;CODE ENDS&gt;</pre>
4174 </div>
4175 <figcaption><a href="#figure-10" class="selfRef">Figure 10</a>:
4176 <a href="#name-ldp-base-module" class="selfRef">LDP Base Module</a>
4177 </figcaption></figure>
4178 </div>
4179 </section>
4180 </div>
4181 <section id="section-9.2">
4182 <h3 id="name-extended">
4183 <a href="#section-9.2" class="section-number selfRef">9.2. </a><a href="#name-extended" class="section-name selfRef">Extended</a>
4184 </h3>
4185 <p id="section-9.2-1">
4186 This YANG module imports types defined in <span>[<a href="#RFC5036" class="xref">RFC5036</a>]</span>, <span>[<a href="#RFC6991" class="xref">RFC6991</a>]</span>, <span>[<a href="#RFC8349" class="xref">RFC8349</a>]</span>, <span>[<a href="#RFC8177" class="xref">RFC8177</a>]</span>, <span>[<a href="#RFC8343" class="xref">RFC8343</a>]</span>, and <span>[<a href="#RFC9067" class="xref">RFC9067</a>]</span>.<a href="#section-9.2-1" class="pilcrow">¶</a></p>
4187 <span id="name-ldp-extended-module"></span><div id="EXT-YANG-FILE">
4188 <figure id="figure-11">
4189 <div id="section-9.2-2.1">
4190 <pre class="lang-yang sourcecode">&lt;CODE BEGINS&gt; file "[email protected]"
4191
4192 module ietf-mpls-ldp-extended {
4193 yang-version 1.1;
4194 namespace "urn:ietf:params:xml:ns:yang:ietf-mpls-ldp-extended";
4195 prefix ldp-ext;
4196
4197 import ietf-inet-types {
4198 prefix inet;
4199 reference
4200 "RFC 6991: Common YANG Data Types";
4201 }
4202 import ietf-routing {
4203 prefix rt;
4204 reference
4205 "RFC 8349: A YANG Data Model for Routing Management (NMDA
4206 version)";
4207 }
4208 import ietf-key-chain {
4209 prefix key-chain;
4210 reference
4211 "RFC 8177: YANG Data Model for Key Chains";
4212 }
4213 import ietf-mpls-ldp {
4214 prefix ldp;
4215 reference
4216 "RFC 9070: YANG Data Model for MPLS LDP";
4217 }
4218 import ietf-interfaces {
4219 prefix if;
4220 reference
4221 "RFC 8343: A YANG Data Model for Interface Management";
4222 }
4223 import ietf-routing-policy {
4224 prefix rt-pol;
4225 reference
4226 "RFC 9067: A YANG Data Model for Routing Policy";
4227 }
4228
4229 organization
4230 "IETF MPLS Working Group";
4231 contact
4232 "WG Web: &lt;https://datatracker.ietf.org/wg/mpls/&gt;
4233 WG List: &lt;mailto:[email protected]&gt;
4234
4235 Editor: Kamran Raza
4236 &lt;mailto:[email protected]&gt;
4237
4238 Author: Rajiv Asati
4239 &lt;mailto:[email protected]&gt;
4240
4241 Author: Xufeng Liu
4242 &lt;mailto:[email protected]&gt;
4243
4244 Author: Santosh Easale
4245 &lt;mailto:[email protected]&gt;
4246
4247 Author: Xia Chen
4248 &lt;mailto:[email protected]&gt;
4249
4250 Author: Himanshu Shah
4251 &lt;mailto:[email protected]&gt;";
4252 description
4253 "This YANG module defines the extended components for the
4254 management of Multiprotocol Label Switching (MPLS) Label
4255 Distribution Protocol (LDP). It is also the model to
4256 be augmented for extended Multipoint LDP (mLDP).
4257
4258 Copyright (c) 2022 IETF Trust and the persons identified as
4259 authors of the code. All rights reserved.
4260
4261 Redistribution and use in source and binary forms, with or
4262 without modification, is permitted pursuant to, and subject
4263 to the license terms contained in, the Revised BSD License set
4264 forth in Section 4.c of the IETF Trust's Legal Provisions
4265 Relating to IETF Documents
4266 (https://trustee.ietf.org/license-info).
4267
4268 This version of this YANG module is part of RFC 9070; see the
4269 RFC itself for full legal notices.";
4270
4271 revision 2022-03-14 {
4272 description
4273 "Initial revision.";
4274 reference
4275 "RFC 9070: YANG Data Model for MPLS LDP";
4276 }
4277
4278 /*
4279 * Features
4280 */
4281
4282 feature capability-end-of-lib {
4283 description
4284 "This feature indicates that the system allows for the
4285 configuration of LDP end-of-lib capability.";
4286 }
4287
4288 feature capability-typed-wildcard-fec {
4289 description
4290 "This feature indicates that the system allows for the
4291 configuration of LDP typed-wildcard-fec capability.";
4292 }
4293
4294 feature capability-upstream-label-assignment {
4295 description
4296 "This feature indicates that the system allows for the
4297 configuration of LDP upstream label assignment capability.";
4298 }
4299
4300 feature forwarding-nexthop-config {
4301 description
4302 "This feature indicates that the system allows for controlling
4303 MPLS forwarding on an LDP interface.";
4304 }
4305
4306 feature graceful-restart-helper-mode {
4307 description
4308 "This feature indicates that the system supports graceful
4309 restart helper mode. We call an LSR to be operating in GR
4310 helper mode when it advertises 0 as its FT Reconnect Timeout
4311 in the FT Session TLV.
4312 Please refer to Section 2 of RFC 3478 for details.";
4313 }
4314
4315 feature key-chain {
4316 description
4317 "This feature indicates that the system supports key-chain for
4318 authentication.";
4319 }
4320
4321 feature peers-dual-stack-transport-preference {
4322 description
4323 "This feature indicates that the system allows for the
4324 configuration of the transport connection preference in a
4325 dual-stack setup for peers.";
4326 }
4327
4328 feature per-interface-timer-config {
4329 description
4330 "This feature indicates that the system allows for the
4331 configuration of interface Hello timers at the per-interface
4332 level.";
4333 }
4334
4335 feature per-peer-admin-down {
4336 description
4337 "This feature indicates that the system allows for the
4338 administrative disabling of a peer.";
4339 }
4340
4341 feature per-peer-graceful-restart-config {
4342 description
4343 "This feature indicates that the system allows for the
4344 configuration of graceful restart at the per-peer level.";
4345 }
4346
4347 feature per-peer-session-attributes-config {
4348 description
4349 "This feature indicates that the system allows for the
4350 configuration of session attributes at the per-peer level.";
4351 }
4352
4353 feature policy-label-assignment-config {
4354 description
4355 "This feature indicates that the system allows for the
4356 configuration of policies to assign labels according to
4357 certain prefixes.";
4358 }
4359
4360 feature policy-ordered-label-config {
4361 description
4362 "This feature indicates that the system allows for the
4363 configuration of ordered label policies.";
4364 }
4365
4366 feature policy-targeted-discovery-config {
4367 description
4368 "This feature indicates that the system allows for the
4369 configuration of policies to control the acceptance of
4370 targeted neighbor-discovery Hello messages.";
4371 }
4372
4373 feature session-downstream-on-demand-config {
4374 description
4375 "This feature indicates that the system allows for the
4376 configuration of session downstream on demand.";
4377 }
4378
4379 /*
4380 * Typedefs
4381 */
4382
4383 typedef neighbor-list-ref {
4384 type leafref {
4385 path "/rt-pol:routing-policy/rt-pol:defined-sets/"
4386 + "rt-pol:neighbor-sets/rt-pol:neighbor-set/rt-pol:name";
4387 }
4388 description
4389 "A type for a reference to a neighbor address list.
4390 The string value is the name identifier for uniquely
4391 identifying the referenced address list, which contains a list
4392 of addresses that a routing policy can applied.";
4393 reference
4394 "RFC 9067: A YANG Data Model for Routing Policy";
4395 }
4396
4397 typedef prefix-list-ref {
4398 type leafref {
4399 path "/rt-pol:routing-policy/rt-pol:defined-sets/"
4400 + "rt-pol:prefix-sets/rt-pol:prefix-set/rt-pol:name";
4401 }
4402 description
4403 "A type for a reference to a prefix list.
4404 The string value is the name identifier for uniquely
4405 identifying the referenced prefix set, which contains a list
4406 of prefixes that a routing policy can applied.";
4407 reference
4408 "RFC 9067: A YANG Data Model for Routing Policy";
4409 }
4410
4411 typedef peer-list-ref {
4412 type leafref {
4413 path "/rt-pol:routing-policy/rt-pol:defined-sets/"
4414 + "rt-pol:neighbor-sets/rt-pol:neighbor-set/rt-pol:name";
4415 }
4416 description
4417 "A type for a reference to a peer address list.
4418 The string value is the name identifier for uniquely
4419 identifying the referenced address list, which contains a list
4420 of addresses that a routing policy can applied.";
4421 reference
4422 "RFC 9067: A YANG Data Model for Routing Policy";
4423 }
4424
4425 /*
4426 * Identities
4427 */
4428 /*
4429 * Groupings
4430 */
4431
4432 grouping address-family-ipv4-augment {
4433 description
4434 "Augmentation to address family IPv4.";
4435 uses policy-container;
4436 leaf transport-address {
4437 type inet:ipv4-address;
4438 description
4439 "The transport address advertised in LDP Hello messages.
4440 If this value is not specified, the LDP LSR Id is used as
4441 the transport address.";
4442 reference
4443 "RFC 5036: LDP Specification, Sec. 3.5.2.";
4444 }
4445 }
4446
4447 grouping authentication-keychain-augment {
4448 description
4449 "Augmentation to authentication to add key-chain.";
4450 leaf key-chain {
4451 type key-chain:key-chain-ref;
4452 description
4453 "key-chain name.
4454 If not specified, no key chain is used.";
4455 }
4456 }
4457
4458 grouping capability-augment {
4459 description
4460 "Augmentation to capability.";
4461 container end-of-lib {
4462 if-feature "capability-end-of-lib";
4463 description
4464 "Configure end-of-lib capability.";
4465 leaf enabled {
4466 type boolean;
4467 default "false";
4468 description
4469 "'true' to enable end-of-lib capability.";
4470 }
4471 }
4472 container typed-wildcard-fec {
4473 if-feature "capability-typed-wildcard-fec";
4474 description
4475 "Configure typed-wildcard-fec capability.";
4476 leaf enabled {
4477 type boolean;
4478 default "false";
4479 description
4480 "'true' to enable typed-wildcard-fec capability.";
4481 }
4482 }
4483 container upstream-label-assignment {
4484 if-feature "capability-upstream-label-assignment";
4485 description
4486 "Configure upstream label assignment capability.";
4487 leaf enabled {
4488 type boolean;
4489 default "false";
4490 description
4491 "'true' to enable upstream label assignment.";
4492 }
4493 }
4494 } // capability-augment
4495
4496 grouping global-augment {
4497 description
4498 "Augmentation to global attributes.";
4499 leaf igp-synchronization-delay {
4500 type uint16 {
4501 range "0 | 3..300";
4502 }
4503 units "seconds";
4504 default "0";
4505 description
4506 "Sets the interval that the LDP waits before notifying the
4507 Interior Gateway Protocol (IGP) that label exchange is
4508 completed so that IGP can start advertising the normal
4509 metric for the link.
4510 If the value is not specified, there is no delay.";
4511 }
4512 }
4513
4514 grouping global-forwarding-nexthop-augment {
4515 description
4516 "Augmentation at the global level for controlling MPLS
4517 forwarding on LDP interfaces.";
4518 container forwarding-nexthop {
4519 if-feature "forwarding-nexthop-config";
4520 description
4521 "Configuration for controlling MPLS forwarding on LDP
4522 interfaces.";
4523 container interfaces {
4524 description
4525 "Containing a list of interfaces on which forwarding can be
4526 disabled.";
4527 list interface {
4528 key "name";
4529 description
4530 "List of LDP interfaces on which forwarding can be
4531 disabled.";
4532 uses ldp:ldp-interface-ref;
4533 list address-family {
4534 key "afi";
4535 description
4536 "Per-vrf per-af params.";
4537 leaf afi {
4538 type identityref {
4539 base rt:address-family;
4540 }
4541 description
4542 "Address family type value.";
4543 }
4544 leaf ldp-disable {
4545 type boolean;
4546 default "false";
4547 description
4548 "'true' to disable LDP forwarding on the interface.";
4549 }
4550 }
4551 } // interface
4552 } // interfaces
4553 } // forwarding-nexthop
4554 } // global-forwarding-nexthop-augment
4555
4556 grouping graceful-restart-augment {
4557 description
4558 "Augmentation to graceful restart.";
4559 leaf helper-enabled {
4560 if-feature "graceful-restart-helper-mode";
4561 type boolean;
4562 default "false";
4563 description
4564 "Enable or disable graceful restart helper mode.";
4565 }
4566 }
4567
4568 grouping interface-address-family-ipv4-augment {
4569 description
4570 "Augmentation to interface address family IPv4.";
4571 leaf transport-address {
4572 type union {
4573 type enumeration {
4574 enum use-global-transport-address {
4575 description
4576 "Use the transport address set at the global level
4577 common for all interfaces for this address family.";
4578 }
4579 enum use-interface-address {
4580 description
4581 "Use interface address as the transport address.";
4582 }
4583 }
4584 type inet:ipv4-address;
4585 }
4586 default "use-global-transport-address";
4587 description
4588 "IP address to be advertised as the LDP transport address.";
4589 }
4590 }
4591
4592 grouping interface-address-family-ipv6-augment {
4593 description
4594 "Augmentation to interface address family IPv6.";
4595 leaf transport-address {
4596 type union {
4597 type enumeration {
4598 enum use-global-transport-address {
4599 description
4600 "Use the transport address set at the global level
4601 common for all interfaces for this address family.";
4602 }
4603 enum use-interface-address {
4604 description
4605 "Use interface address as the transport address.";
4606 }
4607 }
4608 type inet:ipv6-address;
4609 }
4610 default "use-global-transport-address";
4611 description
4612 "IP address to be advertised as the LDP transport address.";
4613 }
4614 }
4615
4616 grouping interface-augment {
4617 description
4618 "Augmentation to interface.";
4619 uses ldp:basic-discovery-timers {
4620 if-feature "per-interface-timer-config";
4621 }
4622 leaf igp-synchronization-delay {
4623 if-feature "per-interface-timer-config";
4624 type uint16 {
4625 range "0 | 3..300";
4626 }
4627 units "seconds";
4628 description
4629 "Sets the interval that the LDP waits before notifying the
4630 Interior Gateway Protocol (IGP) that label exchange is
4631 completed so that IGP can start advertising the normal
4632 metric for the link.
4633 This leaf may be configured at the per-interface level or
4634 the global level, with precedence given to the value at the
4635 per-interface level. If the leaf is not configured at
4636 either level, the default value at the global level is
4637 used.";
4638 }
4639 }
4640
4641 grouping peer-af-policy-container {
4642 description
4643 "LDP policy attribute container under peer address family.";
4644 container label-policy {
4645 description
4646 "Label policy attributes.";
4647 container advertise {
4648 description
4649 "Label advertising policies.";
4650 leaf prefix-list {
4651 type prefix-list-ref;
4652 description
4653 "Applies the prefix list to filter outgoing label
4654 advertisements.
4655 If the value is not specified, no prefix filter
4656 is applied.";
4657 }
4658 }
4659 container accept {
4660 description
4661 "Label advertisement acceptance policies.";
4662 leaf prefix-list {
4663 type prefix-list-ref;
4664 description
4665 "Applies the prefix list to filer incoming label
4666 advertisements.
4667 If the value is not specified, no prefix filter
4668 is applied.";
4669 }
4670 }
4671 }
4672 } // peer-af-policy-container
4673
4674 grouping peer-augment {
4675 description
4676 "Augmentation to each peer list entry.";
4677 leaf admin-down {
4678 if-feature "per-peer-admin-down";
4679 type boolean;
4680 default "false";
4681 description
4682 "'true' to disable the peer.";
4683 }
4684 uses ldp:graceful-restart-attributes-per-peer {
4685 if-feature "per-peer-graceful-restart-config";
4686 }
4687 uses ldp:peer-attributes {
4688 if-feature "per-peer-session-attributes-config";
4689 }
4690 }
4691
4692 grouping peers-augment {
4693 description
4694 "Augmentation to peers container.";
4695 container session-downstream-on-demand {
4696 if-feature "session-downstream-on-demand-config";
4697 description
4698 "Session downstream-on-demand attributes.";
4699 leaf enabled {
4700 type boolean;
4701 default "false";
4702 description
4703 "'true' if session downstream on demand is enabled.";
4704 }
4705 leaf peer-list {
4706 type peer-list-ref;
4707 description
4708 "The name of a peer ACL, to be applied to the
4709 downstream-on-demand sessions.
4710 If this value is not specified, no filter is applied to
4711 any downstream-on-demand sessions.";
4712 }
4713 }
4714 container dual-stack-transport-preference {
4715 if-feature "peers-dual-stack-transport-preference";
4716 description
4717 "The settings of peers to establish TCP connection in a
4718 dual-stack setup.";
4719 leaf max-wait {
4720 type uint16 {
4721 range "0..60";
4722 }
4723 default "30";
4724 description
4725 "The maximum wait time in seconds for preferred transport
4726 connection establishment. 0 indicates no preference.";
4727 }
4728 container prefer-ipv4 {
4729 presence "Present if IPv4 is preferred for transport
4730 connection establishment, subject to the
4731 'peer-list' in this container.";
4732 description
4733 "Uses IPv4 as the preferred address family for transport
4734 connection establishment, subject to the 'peer-list' in
4735 this container.
4736 If this container is not present, as a default, IPv6 is
4737 the preferred address family for transport connection
4738 establishment.";
4739 leaf peer-list {
4740 type peer-list-ref;
4741 description
4742 "The name of a peer ACL, to be applied to the IPv4
4743 transport connections.
4744 If this value is not specified, no filter is applied,
4745 and the IPv4 is preferred for all peers.";
4746 }
4747 }
4748 }
4749 } // peers-augment
4750
4751 grouping policy-container {
4752 description
4753 "LDP policy attributes.";
4754 container label-policy {
4755 description
4756 "Label policy attributes.";
4757 container advertise {
4758 description
4759 "Label advertising policies.";
4760 container egress-explicit-null {
4761 description
4762 "Enables an egress router to advertise an
4763 explicit null label (value 0) in place of an
4764 implicit null label (value 3) to the
4765 penultimate hop router.";
4766 leaf enabled {
4767 type boolean;
4768 default "false";
4769 description
4770 "'true' to enable explicit null.";
4771 }
4772 }
4773 leaf prefix-list {
4774 type prefix-list-ref;
4775 description
4776 "Applies the prefix list to filter outgoing label
4777 advertisements.
4778 If the value is not specified, no prefix filter
4779 is applied.";
4780 }
4781 }
4782 container accept {
4783 description
4784 "Label advertisement acceptance policies.";
4785 leaf prefix-list {
4786 type prefix-list-ref;
4787 description
4788 "Applies the prefix list to filter incoming label
4789 advertisements.
4790 If the value is not specified, no prefix filter
4791 is applied.";
4792 }
4793 }
4794 container assign {
4795 if-feature "policy-label-assignment-config";
4796 description
4797 "Label assignment policies.";
4798 container independent-mode {
4799 description
4800 "Independent label policy attributes.";
4801 leaf prefix-list {
4802 type prefix-list-ref;
4803 description
4804 "Assign labels according to certain prefixes.
4805 If the value is not specified, no prefix filter
4806 is applied (labels are assigned to all learned
4807 routes).";
4808 }
4809 }
4810 container ordered-mode {
4811 if-feature "policy-ordered-label-config";
4812 description
4813 "Ordered label policy attributes.";
4814 leaf egress-prefix-list {
4815 type prefix-list-ref;
4816 description
4817 "Assign labels according to certain prefixes for
4818 egress LSR.";
4819 }
4820 }
4821 } // assign
4822 } // label-policy
4823 } // policy-container
4824
4825 /*
4826 * Configuration and state data nodes
4827 */
4828 // Forwarding nexthop augmentation to the global tree
4829
4830 augment "/rt:routing/rt:control-plane-protocols/"
4831 + "rt:control-plane-protocol/ldp:mpls-ldp/ldp:global" {
4832 description
4833 "Forwarding nexthop augmentation.";
4834 uses global-forwarding-nexthop-augment;
4835 }
4836
4837 // global/address-families/ipv6
4838
4839 augment "/rt:routing/rt:control-plane-protocols/"
4840 + "rt:control-plane-protocol/ldp:mpls-ldp/ldp:global/"
4841 + "ldp:address-families" {
4842 description
4843 "Global IPv6 augmentation.";
4844 container ipv6 {
4845 presence "Present if IPv6 is enabled, unless the 'enabled'
4846 leaf is set to 'false'.";
4847 description
4848 "Containing data related to the IPv6 address family.";
4849 leaf enabled {
4850 type boolean;
4851 default "true";
4852 description
4853 "'false' to disable the address family.";
4854 }
4855 uses policy-container;
4856 leaf transport-address {
4857 type inet:ipv6-address;
4858 mandatory true;
4859 description
4860 "The transport address advertised in LDP Hello messages.";
4861 }
4862 leaf label-distribution-control-mode {
4863 type enumeration {
4864 enum independent {
4865 description
4866 "Independent label distribution control.";
4867 }
4868 enum ordered {
4869 description
4870 "Ordered label distribution control.";
4871 }
4872 }
4873 config false;
4874 description
4875 "Label distribution control mode.";
4876 reference
4877 "RFC 5036: LDP Specification, Sec. 2.6.";
4878 }
4879 // ipv6 bindings
4880 container bindings {
4881 config false;
4882 description
4883 "LDP address and label binding information.";
4884 list address {
4885 key "address";
4886 description
4887 "List of address bindings learned by LDP.";
4888 leaf address {
4889 type inet:ipv6-address;
4890 description
4891 "The IPv6 address learned from an Address
4892 message received from or advertised to a peer.";
4893 }
4894 uses ldp:binding-address-state-attributes;
4895 }
4896 list fec-label {
4897 key "fec";
4898 description
4899 "List of FEC-label bindings learned by LDP.";
4900 leaf fec {
4901 type inet:ipv6-prefix;
4902 description
4903 "The prefix FEC value in the FEC-Label binding,
4904 learned in a Label Mapping message received from
4905 or advertised to a peer.";
4906 }
4907 uses ldp:binding-label-state-attributes;
4908 }
4909 } // bindings
4910 } // ipv6
4911 }
4912
4913 // discovery/interfaces/interface/address-families/ipv6
4914
4915 augment "/rt:routing/rt:control-plane-protocols/"
4916 + "rt:control-plane-protocol/ldp:mpls-ldp/ldp:discovery/"
4917 + "ldp:interfaces/ldp:interface/"
4918 + "ldp:address-families" {
4919 description
4920 "Interface IPv6 augmentation.";
4921 container ipv6 {
4922 presence "Present if IPv6 is enabled, unless the 'enabled'
4923 leaf is set to 'false'.";
4924 description
4925 "IPv6 address family.";
4926 leaf enabled {
4927 type boolean;
4928 default "true";
4929 description
4930 "'false' to disable the address family on the interface.";
4931 }
4932 container hello-adjacencies {
4933 config false;
4934 description
4935 "Containing a list of Hello adjacencies.";
4936 list hello-adjacency {
4937 key "adjacent-address";
4938 config false;
4939 description
4940 "List of Hello adjacencies.";
4941 leaf adjacent-address {
4942 type inet:ipv6-address;
4943 description
4944 "Neighbor address of the Hello adjacency.";
4945 }
4946 uses ldp:adjacency-state-attributes;
4947 uses ldp:ldp-peer-ref-from-interface;
4948 }
4949 }
4950 } // ipv6
4951 }
4952
4953 // discovery/targeted/address-families/ipv6
4954
4955 augment "/rt:routing/rt:control-plane-protocols/"
4956 + "rt:control-plane-protocol/ldp:mpls-ldp/ldp:discovery/"
4957 + "ldp:targeted/ldp:address-families" {
4958 description
4959 "Targeted discovery IPv6 augmentation.";
4960 container ipv6 {
4961 presence "Present if IPv6 is enabled.";
4962 description
4963 "IPv6 address family.";
4964 container hello-adjacencies {
4965 config false;
4966 description
4967 "Containing a list of Hello adjacencies.";
4968 list hello-adjacency {
4969 key "local-address adjacent-address";
4970 config false;
4971 description
4972 "List of Hello adjacencies.";
4973 leaf local-address {
4974 type inet:ipv6-address;
4975 description
4976 "Local address of the Hello adjacency.";
4977 }
4978 leaf adjacent-address {
4979 type inet:ipv6-address;
4980 description
4981 "Neighbor address of the Hello adjacency.";
4982 }
4983 uses ldp:adjacency-state-attributes;
4984 uses ldp:ldp-peer-ref-from-target;
4985 }
4986 }
4987 list target {
4988 key "adjacent-address";
4989 description
4990 "Targeted discovery params.";
4991 leaf adjacent-address {
4992 type inet:ipv6-address;
4993 description
4994 "Configures a remote LDP neighbor for the
4995 extended LDP discovery.";
4996 }
4997 leaf enabled {
4998 type boolean;
4999 default "true";
5000 description
5001 "'true' to enable the target.";
5002 }
5003 leaf local-address {
5004 type inet:ipv6-address;
5005 description
5006 "The local address used as the source address to send
5007 targeted Hello messages.
5008 If the value is not specified, the transport address
5009 is used as the source address.";
5010 }
5011 } // target
5012 } // ipv6
5013 }
5014
5015 // /peers/peer/state/address-families/ipv6
5016
5017 augment "/rt:routing/rt:control-plane-protocols/"
5018 + "rt:control-plane-protocol/ldp:mpls-ldp/ldp:peers/"
5019 + "ldp:peer/ldp:address-families" {
5020 description
5021 "Peer state IPv6 augmentation.";
5022 container ipv6 {
5023 presence "Present if IPv6 is enabled.";
5024 description
5025 "IPv6 address family.";
5026 container hello-adjacencies {
5027 config false;
5028 description
5029 "Containing a list of Hello adjacencies.";
5030 list hello-adjacency {
5031 key "local-address adjacent-address";
5032 description
5033 "List of Hello adjacencies.";
5034 leaf local-address {
5035 type inet:ipv6-address;
5036 description
5037 "Local address of the Hello adjacency.";
5038 }
5039 leaf adjacent-address {
5040 type inet:ipv6-address;
5041 description
5042 "Neighbor address of the Hello adjacency.";
5043 }
5044 uses ldp:adjacency-state-attributes;
5045 leaf interface {
5046 type if:interface-ref;
5047 description
5048 "Interface for this adjacency.";
5049 }
5050 }
5051 }
5052 } // ipv6
5053 }
5054
5055 /*
5056 * Configuration data and operational state data nodes
5057 */
5058
5059 augment "/rt:routing/rt:control-plane-protocols/"
5060 + "rt:control-plane-protocol/ldp:mpls-ldp/ldp:global" {
5061 description
5062 "Graceful restart augmentation.";
5063 uses global-augment;
5064 }
5065
5066 augment "/rt:routing/rt:control-plane-protocols/"
5067 + "rt:control-plane-protocol/ldp:mpls-ldp/ldp:global/"
5068 + "ldp:capability" {
5069 description
5070 "Capability augmentation.";
5071 uses capability-augment;
5072 }
5073
5074 augment "/rt:routing/rt:control-plane-protocols/"
5075 + "rt:control-plane-protocol/ldp:mpls-ldp/ldp:global/"
5076 + "ldp:graceful-restart" {
5077 description
5078 "Graceful restart augmentation.";
5079 uses graceful-restart-augment;
5080 }
5081
5082 augment "/rt:routing/rt:control-plane-protocols/"
5083 + "rt:control-plane-protocol/ldp:mpls-ldp/ldp:global/"
5084 + "ldp:address-families/ldp:ipv4" {
5085 description
5086 "Address family IPv4 augmentation.";
5087 uses address-family-ipv4-augment;
5088 }
5089
5090 augment "/rt:routing/rt:control-plane-protocols/"
5091 + "rt:control-plane-protocol/ldp:mpls-ldp/ldp:discovery/"
5092 + "ldp:interfaces/ldp:interface" {
5093 description
5094 "Interface augmentation.";
5095 uses interface-augment;
5096 }
5097
5098 augment "/rt:routing/rt:control-plane-protocols/"
5099 + "rt:control-plane-protocol/ldp:mpls-ldp/ldp:discovery/"
5100 + "ldp:interfaces/ldp:interface/ldp:address-families/"
5101 + "ldp:ipv4" {
5102 description
5103 "Interface address family IPv4 augmentation.";
5104 uses interface-address-family-ipv4-augment;
5105 }
5106
5107 augment "/rt:routing/rt:control-plane-protocols/"
5108 + "rt:control-plane-protocol/ldp:mpls-ldp/ldp:discovery/"
5109 + "ldp:interfaces/ldp:interface/ldp:address-families/"
5110 + "ldp-ext:ipv6" {
5111 description
5112 "Interface address family IPv6 augmentation.";
5113 uses interface-address-family-ipv6-augment;
5114 }
5115
5116 augment "/rt:routing/rt:control-plane-protocols/"
5117 + "rt:control-plane-protocol/ldp:mpls-ldp/ldp:discovery/"
5118 + "ldp:targeted/ldp:hello-accept" {
5119 description
5120 "Targeted discovery augmentation.";
5121 leaf neighbor-list {
5122 if-feature "policy-targeted-discovery-config";
5123 type neighbor-list-ref;
5124 description
5125 "The name of a neighbor ACL, used to accept Hello messages
5126 from LDP peers as permitted by the neighbor-list policy.
5127 If this value is not specified, targeted Hello messages
5128 from any source are accepted.";
5129 }
5130 }
5131
5132 augment "/rt:routing/rt:control-plane-protocols/"
5133 + "rt:control-plane-protocol/ldp:mpls-ldp/ldp:peers" {
5134 description
5135 "Peers augmentation.";
5136 uses peers-augment;
5137 }
5138
5139 augment "/rt:routing/rt:control-plane-protocols/"
5140 + "rt:control-plane-protocol/ldp:mpls-ldp/ldp:peers/"
5141 + "ldp:authentication/ldp:authentication-type" {
5142 if-feature "key-chain";
5143 description
5144 "Peers authentication augmentation.";
5145 case key-chain {
5146 uses authentication-keychain-augment;
5147 }
5148 }
5149
5150 augment "/rt:routing/rt:control-plane-protocols/"
5151 + "rt:control-plane-protocol/ldp:mpls-ldp/ldp:peers/"
5152 + "ldp:peer" {
5153 description
5154 "Peer list entry augmentation.";
5155 uses peer-augment;
5156 }
5157
5158 augment "/rt:routing/rt:control-plane-protocols/"
5159 + "rt:control-plane-protocol/ldp:mpls-ldp/ldp:peers/"
5160 + "ldp:peer/ldp:authentication/ldp:authentication-type" {
5161 if-feature "key-chain";
5162 description
5163 "Peer list entry authentication augmentation.";
5164 case key-chain {
5165 uses authentication-keychain-augment;
5166 }
5167 }
5168
5169 augment "/rt:routing/rt:control-plane-protocols/"
5170 + "rt:control-plane-protocol/ldp:mpls-ldp/ldp:peers/"
5171 + "ldp:peer/ldp:address-families/ldp:ipv4" {
5172 description
5173 "Peer list entry IPv4 augmentation.";
5174 uses peer-af-policy-container;
5175 }
5176
5177 augment "/rt:routing/rt:control-plane-protocols/"
5178 + "rt:control-plane-protocol/ldp:mpls-ldp/ldp:peers/"
5179 + "ldp:peer/ldp:address-families/ldp-ext:ipv6" {
5180 description
5181 "Peer list entry IPv6 augmentation.";
5182 uses peer-af-policy-container;
5183 }
5184 }
5185
5186 &lt;CODE ENDS&gt;</pre>
5187 </div>
5188 <figcaption><a href="#figure-11" class="selfRef">Figure 11</a>:
5189 <a href="#name-ldp-extended-module" class="selfRef">LDP Extended Module</a>
5190 </figcaption></figure>
5191 </div>
5192 </section>
5193 </section>
5194 </div>
5195 <section id="section-10">
5196 <h2 id="name-security-considerations">
5197 <a href="#section-10" class="section-number selfRef">10. </a><a href="#name-security-considerations" class="section-name selfRef">Security Considerations</a>
5198 </h2>
5199 <p id="section-10-1"> This specification inherits the security
5200 considerations captured in <span>[<a href="#RFC5920" class="xref">RFC5920</a>]</span> and the LDP protocol specification documents, namely base LDP
5201 <span>[<a href="#RFC5036" class="xref">RFC5036</a>]</span>, LDP IPv6 <span>[<a href="#RFC7552" class="xref">RFC7552</a>]</span>, LDP Capabilities
5202 <span>[<a href="#RFC5561" class="xref">RFC5561</a>]</span>, Typed Wildcard FEC <span>[<a href="#RFC5918" class="xref">RFC5918</a>]</span>, LDP End-of-LIB
5203 <span>[<a href="#RFC5919" class="xref">RFC5919</a>]</span>, and LDP Upstream Label Assignment
5204 <span>[<a href="#RFC6389" class="xref">RFC6389</a>]</span>.<a href="#section-10-1" class="pilcrow">¶</a></p>
5205 <section id="section-10.1">
5206 <h3 id="name-yang-data-model">
5207 <a href="#section-10.1" class="section-number selfRef">10.1. </a><a href="#name-yang-data-model" class="section-name selfRef">YANG Data Model</a>
5208 </h3>
5209 <p id="section-10.1-1"> The YANG modules specified in this document define a schema for data that is designed to be accessed via network management protocols such as NETCONF <span>[<a href="#RFC6241" class="xref">RFC6241</a>]</span> or RESTCONF <span>[<a href="#RFC8040" class="xref">RFC8040</a>]</span>. The lowest NETCONF layer is the secure transport layer, and the mandatory-to-implement secure transport is Secure Shell (SSH) <span>[<a href="#RFC6242" class="xref">RFC6242</a>]</span>. The lowest RESTCONF layer is HTTPS, and the mandatory-to-implement secure transport is TLS <span>[<a href="#RFC8446" class="xref">RFC8446</a>]</span>.<a href="#section-10.1-1" class="pilcrow">¶</a></p>
5210 <p id="section-10.1-2"> The Network Configuration Access Control Model (NACM) <span>[<a href="#RFC8341" class="xref">RFC8341</a>]</span> provides the means to restrict access for particular NETCONF or RESTCONF users to a preconfigured subset of all available NETCONF or RESTCONF protocol operations and content.<a href="#section-10.1-2" class="pilcrow">¶</a></p>
5211 <section id="section-10.1.1">
5212 <h4 id="name-writable-nodes">
5213 <a href="#section-10.1.1" class="section-number selfRef">10.1.1. </a><a href="#name-writable-nodes" class="section-name selfRef">Writable Nodes</a>
5214 </h4>
5215 <p id="section-10.1.1-1"> There are a number of data nodes defined in these YANG modules that are writable/creatable/deletable (i.e., config true, which is the default). These data nodes may be considered sensitive or vulnerable in some network environments. Write operations (e.g., edit-config) to these data nodes without proper protection can have a negative effect on network operations.<a href="#section-10.1.1-1" class="pilcrow">¶</a></p>
5216 <p id="section-10.1.1-2"> For LDP, the ability to modify MPLS LDP configuration may allow the entire MPLS LDP domain to be compromised including forming LDP adjacencies and/or peer sessions with unauthorized
5217 routers to mount a massive Denial-of-Service (DoS) attack. In particular, the following are the subtrees and data nodes that are sensitive and vulnerable:<a href="#section-10.1.1-2" class="pilcrow">¶</a></p>
5218 <span class="break"></span><dl class="dlParallel" id="section-10.1.1-3">
5219 <dt id="section-10.1.1-3.1">/mpls-ldp/discovery/interfaces/interface:
5220 </dt>
5221 <dd style="margin-left: 1.5em" id="section-10.1.1-3.2">Adding LDP on any unprotected interface could allow an LDP Hello adjacency
5222 to be formed with an unauthorized and malicious neighbor. Once a Hello
5223 adjacency is formed, a peer session could progress with this neighbor.<a href="#section-10.1.1-3.2" class="pilcrow">¶</a>
5224 </dd>
5225 <dd class="break"></dd>
5226 <dt id="section-10.1.1-3.3">/mpls-ldp/discovery/targeted/hello-accept:
5227 </dt>
5228 <dd style="margin-left: 1.5em" id="section-10.1.1-3.4"> Allowing acceptance of targeted-hellos could open LDP to DoS attacks
5229 related to incoming targeted hellos from malicious sources.<a href="#section-10.1.1-3.4" class="pilcrow">¶</a>
5230 </dd>
5231 <dd class="break"></dd>
5232 <dt id="section-10.1.1-3.5">/mpls-ldp/peers/authentication:
5233 </dt>
5234 <dd style="margin-left: 1.5em" id="section-10.1.1-3.6">Allowing a peer session establishment is typically controlled via LDP
5235 authentication where a proper and secure authentication password/key
5236 management is warranted.<a href="#section-10.1.1-3.6" class="pilcrow">¶</a>
5237 </dd>
5238 <dd class="break"></dd>
5239 <dt id="section-10.1.1-3.7">/mpls-ldp/peers/peer/authentication:
5240 </dt>
5241 <dd style="margin-left: 1.5em" id="section-10.1.1-3.8">Same as above.<a href="#section-10.1.1-3.8" class="pilcrow">¶</a>
5242 </dd>
5243 <dd class="break"></dd>
5244 </dl>
5245 </section>
5246 <section id="section-10.1.2">
5247 <h4 id="name-readable-nodes">
5248 <a href="#section-10.1.2" class="section-number selfRef">10.1.2. </a><a href="#name-readable-nodes" class="section-name selfRef">Readable Nodes</a>
5249 </h4>
5250 <p id="section-10.1.2-1"> Some of the readable data nodes in these YANG modules may be considered sensitive or vulnerable in some network environments. It is thus important to control read access (e.g., via get, get-config, or notification) to these data nodes. These are the subtrees and data nodes and their sensitivity/vulnerability:<a href="#section-10.1.2-1" class="pilcrow">¶</a></p>
5251 <p id="section-10.1.2-2">The exposure of LDP databases (such as Hello adjacencies, peers, address bindings, and FEC-Label bindings) beyond the scope of the LDP admin domain may be undesirable. The relevant subtrees and data nodes are as follows:<a href="#section-10.1.2-2" class="pilcrow">¶</a></p>
5252 <ul class="normal">
5253 <li class="normal" id="section-10.1.2-3.1"> /mpls-ldp/global/address-families/ipv4/bindings/address<a href="#section-10.1.2-3.1" class="pilcrow">¶</a>
5254 </li>
5255 <li class="normal" id="section-10.1.2-3.2"> /mpls-ldp/global/address-families/ipv6/bindings/address<a href="#section-10.1.2-3.2" class="pilcrow">¶</a>
5256 </li>
5257 <li class="normal" id="section-10.1.2-3.3"> /mpls-ldp/global/address-families/ipv4/bindings/fec-label<a href="#section-10.1.2-3.3" class="pilcrow">¶</a>
5258 </li>
5259 <li class="normal" id="section-10.1.2-3.4"> /mpls-ldp/global/address-families/ipv6/bindings/fec-label<a href="#section-10.1.2-3.4" class="pilcrow">¶</a>
5260 </li>
5261 <li class="normal" id="section-10.1.2-3.5"> /mpls-ldp/discovery/interfaces/interface/address-families/ipv4/hello-adjacencies<a href="#section-10.1.2-3.5" class="pilcrow">¶</a>
5262 </li>
5263 <li class="normal" id="section-10.1.2-3.6"> /mpls-ldp/discovery/interfaces/interface/address-families/ipv6/hello-adjacencies<a href="#section-10.1.2-3.6" class="pilcrow">¶</a>
5264 </li>
5265 <li class="normal" id="section-10.1.2-3.7"> /mpls-ldp/discovery/targeted/address-families/ipv4/hello-adjacencies<a href="#section-10.1.2-3.7" class="pilcrow">¶</a>
5266 </li>
5267 <li class="normal" id="section-10.1.2-3.8"> /mpls-ldp/discovery/targeted/address-families/ipv6/hello-adjacencies<a href="#section-10.1.2-3.8" class="pilcrow">¶</a>
5268 </li>
5269 <li class="normal" id="section-10.1.2-3.9"> /mpls-ldp/peers<a href="#section-10.1.2-3.9" class="pilcrow">¶</a>
5270 </li>
5271 </ul>
5272 <p id="section-10.1.2-4"> The configuration for LDP peer authentication is supported via the
5273 key-chain specification <span>[<a href="#RFC8177" class="xref">RFC8177</a>]</span> or via direct
5274 specification of a key associated with a crypto algorithm (such as MD5).
5275 The relevant subtrees and data nodes are as follows:<a href="#section-10.1.2-4" class="pilcrow">¶</a></p>
5276 <ul class="normal">
5277 <li class="normal" id="section-10.1.2-5.1"> /mpls-ldp/peers/authentication<a href="#section-10.1.2-5.1" class="pilcrow">¶</a>
5278 </li>
5279 <li class="normal" id="section-10.1.2-5.2"> /mpls-ldp/peers/peer/authentication<a href="#section-10.1.2-5.2" class="pilcrow">¶</a>
5280 </li>
5281 </ul>
5282 <p id="section-10.1.2-6"> The actual authentication key data (whether locally specified or part of a
5283 key-chain) is sensitive and needs to be kept secret from unauthorized parties.
5284 For key-chain-based authentication, this model inherits the security
5285 considerations of <span>[<a href="#RFC8040" class="xref">RFC8040</a>]</span> (that includes the considerations
5286 with respect to the local storage and handling of authentication keys). A
5287 similar procedure for storage and access to direct keys is warranted.<a href="#section-10.1.2-6" class="pilcrow">¶</a></p>
5288 </section>
5289 <section id="section-10.1.3">
5290 <h4 id="name-rpc-operations">
5291 <a href="#section-10.1.3" class="section-number selfRef">10.1.3. </a><a href="#name-rpc-operations" class="section-name selfRef">RPC Operations</a>
5292 </h4>
5293 <p id="section-10.1.3-1">Some of the RPC operations in these YANG modules may be considered sensitive or vulnerable in some network environments. It is thus important to control access to these operations; otherwise, control plane flaps, network outages, and DoS attacks are possible. The RPC operations are:<a href="#section-10.1.3-1" class="pilcrow">¶</a></p>
5294 <ul class="normal">
5295 <li class="normal" id="section-10.1.3-2.1"> mpls-ldp-clear-peer<a href="#section-10.1.3-2.1" class="pilcrow">¶</a>
5296 </li>
5297 <li class="normal" id="section-10.1.3-2.2"> mpls-ldp-clear-hello-adjacency<a href="#section-10.1.3-2.2" class="pilcrow">¶</a>
5298 </li>
5299 </ul>
5300 </section>
5301 <section id="section-10.1.4">
5302 <h4 id="name-notifications-2">
5303 <a href="#section-10.1.4" class="section-number selfRef">10.1.4. </a><a href="#name-notifications-2" class="section-name selfRef">Notifications</a>
5304 </h4>
5305 <p id="section-10.1.4-1"> The model describes several notifications. The implementations must rate-limit the generation of these notifications to avoid creating
5306 significant notification load and possible side effects on the system stability.<a href="#section-10.1.4-1" class="pilcrow">¶</a></p>
5307 </section>
5308 </section>
5309 </section>
5310 <section id="section-11">
5311 <h2 id="name-iana-considerations">
5312 <a href="#section-11" class="section-number selfRef">11. </a><a href="#name-iana-considerations" class="section-name selfRef">IANA Considerations</a>
5313 </h2>
5314 <p id="section-11-1">Per this document, the following URIs have been registered in the IETF "XML
5315 Registry" <span>[<a href="#RFC3688" class="xref">RFC3688</a>]</span>:<a href="#section-11-1" class="pilcrow">¶</a></p>
5316 <span class="break"></span><dl class="dlCompact dlParallel" id="section-11-2">
5317 <dt id="section-11-2.1">URI:
5318 </dt>
5319 <dd style="margin-left: 1.5em" id="section-11-2.2">urn:ietf:params:xml:ns:yang:ietf-mpls-ldp<a href="#section-11-2.2" class="pilcrow">¶</a>
5320 </dd>
5321 <dd class="break"></dd>
5322 <dt id="section-11-2.3">Registrant:
5323 </dt>
5324 <dd style="margin-left: 1.5em" id="section-11-2.4">The IESG<a href="#section-11-2.4" class="pilcrow">¶</a>
5325 </dd>
5326 <dd class="break"></dd>
5327 <dt id="section-11-2.5">XML:
5328 </dt>
5329 <dd style="margin-left: 1.5em" id="section-11-2.6">N/A<a href="#section-11-2.6" class="pilcrow">¶</a>
5330 </dd>
5331 <dd class="break"></dd>
5332 </dl>
5333 <span class="break"></span><dl class="dlCompact dlParallel" id="section-11-3">
5334 <dt id="section-11-3.1">URI:
5335 </dt>
5336 <dd style="margin-left: 1.5em" id="section-11-3.2">urn:ietf:params:xml:ns:yang:ietf-mpls-ldp-extended<a href="#section-11-3.2" class="pilcrow">¶</a>
5337 </dd>
5338 <dd class="break"></dd>
5339 <dt id="section-11-3.3">Registrant:
5340 </dt>
5341 <dd style="margin-left: 1.5em" id="section-11-3.4">The IESG<a href="#section-11-3.4" class="pilcrow">¶</a>
5342 </dd>
5343 <dd class="break"></dd>
5344 <dt id="section-11-3.5">XML:
5345 </dt>
5346 <dd style="margin-left: 1.5em" id="section-11-3.6">N/A<a href="#section-11-3.6" class="pilcrow">¶</a>
5347 </dd>
5348 <dd class="break"></dd>
5349 </dl>
5350 <p id="section-11-4">Per this document, the following YANG modules have been registered in the
5351 "YANG Module Names" registry <span>[<a href="#RFC6020" class="xref">RFC6020</a>]</span>:<a href="#section-11-4" class="pilcrow">¶</a></p>
5352 <span class="break"></span><dl class="dlCompact dlParallel" id="section-11-5">
5353 <dt id="section-11-5.1">Name:
5354 </dt>
5355 <dd style="margin-left: 1.5em" id="section-11-5.2">ietf-mpls-ldp<a href="#section-11-5.2" class="pilcrow">¶</a>
5356 </dd>
5357 <dd class="break"></dd>
5358 <dt id="section-11-5.3">Namespace:
5359 </dt>
5360 <dd style="margin-left: 1.5em" id="section-11-5.4">urn:ietf:params:xml:ns:yang:ietf-mpls-ldp<a href="#section-11-5.4" class="pilcrow">¶</a>
5361 </dd>
5362 <dd class="break"></dd>
5363 <dt id="section-11-5.5">Prefix:
5364 </dt>
5365 <dd style="margin-left: 1.5em" id="section-11-5.6">ldp<a href="#section-11-5.6" class="pilcrow">¶</a>
5366 </dd>
5367 <dd class="break"></dd>
5368 <dt id="section-11-5.7">Reference:
5369 </dt>
5370 <dd style="margin-left: 1.5em" id="section-11-5.8">RFC 9070<a href="#section-11-5.8" class="pilcrow">¶</a>
5371 </dd>
5372 <dd class="break"></dd>
5373 </dl>
5374 <span class="break"></span><dl class="dlCompact dlParallel" id="section-11-6">
5375 <dt id="section-11-6.1">Name:
5376 </dt>
5377 <dd style="margin-left: 1.5em" id="section-11-6.2">ietf-mpls-ldp-extended<a href="#section-11-6.2" class="pilcrow">¶</a>
5378 </dd>
5379 <dd class="break"></dd>
5380 <dt id="section-11-6.3">Namespace:
5381 </dt>
5382 <dd style="margin-left: 1.5em" id="section-11-6.4">urn:ietf:params:xml:ns:yang:ietf-mpls-ldp-extended<a href="#section-11-6.4" class="pilcrow">¶</a>
5383 </dd>
5384 <dd class="break"></dd>
5385 <dt id="section-11-6.5">Prefix:
5386 </dt>
5387 <dd style="margin-left: 1.5em" id="section-11-6.6">ldp-ext<a href="#section-11-6.6" class="pilcrow">¶</a>
5388 </dd>
5389 <dd class="break"></dd>
5390 <dt id="section-11-6.7">Reference:
5391 </dt>
5392 <dd style="margin-left: 1.5em" id="section-11-6.8">RFC 9070<a href="#section-11-6.8" class="pilcrow">¶</a>
5393 </dd>
5394 <dd class="break"></dd>
5395 </dl>
5396 </section>
5397 <section id="section-12">
5398 <h2 id="name-normative-references">
5399 <a href="#section-12" class="section-number selfRef">12. </a><a href="#name-normative-references" class="section-name selfRef">Normative References</a>
5400 </h2>
5401 <dl class="references">
5402 <dt id="RFC3478">[RFC3478]</dt>
5403 <dd>
5404 <span class="refAuthor">Leelanivas, M.</span>, <span class="refAuthor">Rekhter, Y.</span>, and <span class="refAuthor">R. Aggarwal</span>, <span class="refTitle">"Graceful Restart Mechanism for Label Distribution Protocol"</span>, <span class="seriesInfo">RFC 3478</span>, <span class="seriesInfo">DOI 10.17487/RFC3478</span>, <time datetime="2003-02" class="refDate">February 2003</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc3478">https://www.rfc-editor.org/info/rfc3478</a>&gt;</span>. </dd>
5405 <dd class="break"></dd>
5406 <dt id="RFC3688">[RFC3688]</dt>
5407 <dd>
5408 <span class="refAuthor">Mealling, M.</span>, <span class="refTitle">"The IETF XML Registry"</span>, <span class="seriesInfo">BCP 81</span>, <span class="seriesInfo">RFC 3688</span>, <span class="seriesInfo">DOI 10.17487/RFC3688</span>, <time datetime="2004-01" class="refDate">January 2004</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc3688">https://www.rfc-editor.org/info/rfc3688</a>&gt;</span>. </dd>
5409 <dd class="break"></dd>
5410 <dt id="RFC5036">[RFC5036]</dt>
5411 <dd>
5412 <span class="refAuthor">Andersson, L., Ed.</span>, <span class="refAuthor">Minei, I., Ed.</span>, and <span class="refAuthor">B. Thomas, Ed.</span>, <span class="refTitle">"LDP Specification"</span>, <span class="seriesInfo">RFC 5036</span>, <span class="seriesInfo">DOI 10.17487/RFC5036</span>, <time datetime="2007-10" class="refDate">October 2007</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc5036">https://www.rfc-editor.org/info/rfc5036</a>&gt;</span>. </dd>
5413 <dd class="break"></dd>
5414 <dt id="RFC5331">[RFC5331]</dt>
5415 <dd>
5416 <span class="refAuthor">Aggarwal, R.</span>, <span class="refAuthor">Rekhter, Y.</span>, and <span class="refAuthor">E. Rosen</span>, <span class="refTitle">"MPLS Upstream Label Assignment and Context-Specific Label Space"</span>, <span class="seriesInfo">RFC 5331</span>, <span class="seriesInfo">DOI 10.17487/RFC5331</span>, <time datetime="2008-08" class="refDate">August 2008</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc5331">https://www.rfc-editor.org/info/rfc5331</a>&gt;</span>. </dd>
5417 <dd class="break"></dd>
5418 <dt id="RFC5443">[RFC5443]</dt>
5419 <dd>
5420 <span class="refAuthor">Jork, M.</span>, <span class="refAuthor">Atlas, A.</span>, and <span class="refAuthor">L. Fang</span>, <span class="refTitle">"LDP IGP Synchronization"</span>, <span class="seriesInfo">RFC 5443</span>, <span class="seriesInfo">DOI 10.17487/RFC5443</span>, <time datetime="2009-03" class="refDate">March 2009</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc5443">https://www.rfc-editor.org/info/rfc5443</a>&gt;</span>. </dd>
5421 <dd class="break"></dd>
5422 <dt id="RFC5561">[RFC5561]</dt>
5423 <dd>
5424 <span class="refAuthor">Thomas, B.</span>, <span class="refAuthor">Raza, K.</span>, <span class="refAuthor">Aggarwal, S.</span>, <span class="refAuthor">Aggarwal, R.</span>, and <span class="refAuthor">JL. Le Roux</span>, <span class="refTitle">"LDP Capabilities"</span>, <span class="seriesInfo">RFC 5561</span>, <span class="seriesInfo">DOI 10.17487/RFC5561</span>, <time datetime="2009-07" class="refDate">July 2009</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc5561">https://www.rfc-editor.org/info/rfc5561</a>&gt;</span>. </dd>
5425 <dd class="break"></dd>
5426 <dt id="RFC5918">[RFC5918]</dt>
5427 <dd>
5428 <span class="refAuthor">Asati, R.</span>, <span class="refAuthor">Minei, I.</span>, and <span class="refAuthor">B. Thomas</span>, <span class="refTitle">"Label Distribution Protocol (LDP) 'Typed Wildcard' Forward Equivalence Class (FEC)"</span>, <span class="seriesInfo">RFC 5918</span>, <span class="seriesInfo">DOI 10.17487/RFC5918</span>, <time datetime="2010-08" class="refDate">August 2010</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc5918">https://www.rfc-editor.org/info/rfc5918</a>&gt;</span>. </dd>
5429 <dd class="break"></dd>
5430 <dt id="RFC5919">[RFC5919]</dt>
5431 <dd>
5432 <span class="refAuthor">Asati, R.</span>, <span class="refAuthor">Mohapatra, P.</span>, <span class="refAuthor">Chen, E.</span>, and <span class="refAuthor">B. Thomas</span>, <span class="refTitle">"Signaling LDP Label Advertisement Completion"</span>, <span class="seriesInfo">RFC 5919</span>, <span class="seriesInfo">DOI 10.17487/RFC5919</span>, <time datetime="2010-08" class="refDate">August 2010</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc5919">https://www.rfc-editor.org/info/rfc5919</a>&gt;</span>. </dd>
5433 <dd class="break"></dd>
5434 <dt id="RFC5920">[RFC5920]</dt>
5435 <dd>
5436 <span class="refAuthor">Fang, L., Ed.</span>, <span class="refTitle">"Security Framework for MPLS and GMPLS Networks"</span>, <span class="seriesInfo">RFC 5920</span>, <span class="seriesInfo">DOI 10.17487/RFC5920</span>, <time datetime="2010-07" class="refDate">July 2010</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc5920">https://www.rfc-editor.org/info/rfc5920</a>&gt;</span>. </dd>
5437 <dd class="break"></dd>
5438 <dt id="RFC6020">[RFC6020]</dt>
5439 <dd>
5440 <span class="refAuthor">Bjorklund, M., Ed.</span>, <span class="refTitle">"YANG - A Data Modeling Language for the Network Configuration Protocol (NETCONF)"</span>, <span class="seriesInfo">RFC 6020</span>, <span class="seriesInfo">DOI 10.17487/RFC6020</span>, <time datetime="2010-10" class="refDate">October 2010</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc6020">https://www.rfc-editor.org/info/rfc6020</a>&gt;</span>. </dd>
5441 <dd class="break"></dd>
5442 <dt id="RFC6241">[RFC6241]</dt>
5443 <dd>
5444 <span class="refAuthor">Enns, R., Ed.</span>, <span class="refAuthor">Bjorklund, M., Ed.</span>, <span class="refAuthor">Schoenwaelder, J., Ed.</span>, and <span class="refAuthor">A. Bierman, Ed.</span>, <span class="refTitle">"Network Configuration Protocol (NETCONF)"</span>, <span class="seriesInfo">RFC 6241</span>, <span class="seriesInfo">DOI 10.17487/RFC6241</span>, <time datetime="2011-06" class="refDate">June 2011</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc6241">https://www.rfc-editor.org/info/rfc6241</a>&gt;</span>. </dd>
5445 <dd class="break"></dd>
5446 <dt id="RFC6242">[RFC6242]</dt>
5447 <dd>
5448 <span class="refAuthor">Wasserman, M.</span>, <span class="refTitle">"Using the NETCONF Protocol over Secure Shell (SSH)"</span>, <span class="seriesInfo">RFC 6242</span>, <span class="seriesInfo">DOI 10.17487/RFC6242</span>, <time datetime="2011-06" class="refDate">June 2011</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc6242">https://www.rfc-editor.org/info/rfc6242</a>&gt;</span>. </dd>
5449 <dd class="break"></dd>
5450 <dt id="RFC6389">[RFC6389]</dt>
5451 <dd>
5452 <span class="refAuthor">Aggarwal, R.</span> and <span class="refAuthor">JL. Le Roux</span>, <span class="refTitle">"MPLS Upstream Label Assignment for LDP"</span>, <span class="seriesInfo">RFC 6389</span>, <span class="seriesInfo">DOI 10.17487/RFC6389</span>, <time datetime="2011-11" class="refDate">November 2011</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc6389">https://www.rfc-editor.org/info/rfc6389</a>&gt;</span>. </dd>
5453 <dd class="break"></dd>
5454 <dt id="RFC6991">[RFC6991]</dt>
5455 <dd>
5456 <span class="refAuthor">Schoenwaelder, J., Ed.</span>, <span class="refTitle">"Common YANG Data Types"</span>, <span class="seriesInfo">RFC 6991</span>, <span class="seriesInfo">DOI 10.17487/RFC6991</span>, <time datetime="2013-07" class="refDate">July 2013</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc6991">https://www.rfc-editor.org/info/rfc6991</a>&gt;</span>. </dd>
5457 <dd class="break"></dd>
5458 <dt id="RFC7552">[RFC7552]</dt>
5459 <dd>
5460 <span class="refAuthor">Asati, R.</span>, <span class="refAuthor">Pignataro, C.</span>, <span class="refAuthor">Raza, K.</span>, <span class="refAuthor">Manral, V.</span>, and <span class="refAuthor">R. Papneja</span>, <span class="refTitle">"Updates to LDP for IPv6"</span>, <span class="seriesInfo">RFC 7552</span>, <span class="seriesInfo">DOI 10.17487/RFC7552</span>, <time datetime="2015-06" class="refDate">June 2015</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc7552">https://www.rfc-editor.org/info/rfc7552</a>&gt;</span>. </dd>
5461 <dd class="break"></dd>
5462 <dt id="RFC7950">[RFC7950]</dt>
5463 <dd>
5464 <span class="refAuthor">Bjorklund, M., Ed.</span>, <span class="refTitle">"The YANG 1.1 Data Modeling Language"</span>, <span class="seriesInfo">RFC 7950</span>, <span class="seriesInfo">DOI 10.17487/RFC7950</span>, <time datetime="2016-08" class="refDate">August 2016</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc7950">https://www.rfc-editor.org/info/rfc7950</a>&gt;</span>. </dd>
5465 <dd class="break"></dd>
5466 <dt id="RFC8040">[RFC8040]</dt>
5467 <dd>
5468 <span class="refAuthor">Bierman, A.</span>, <span class="refAuthor">Bjorklund, M.</span>, and <span class="refAuthor">K. Watsen</span>, <span class="refTitle">"RESTCONF Protocol"</span>, <span class="seriesInfo">RFC 8040</span>, <span class="seriesInfo">DOI 10.17487/RFC8040</span>, <time datetime="2017-01" class="refDate">January 2017</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8040">https://www.rfc-editor.org/info/rfc8040</a>&gt;</span>. </dd>
5469 <dd class="break"></dd>
5470 <dt id="RFC8177">[RFC8177]</dt>
5471 <dd>
5472 <span class="refAuthor">Lindem, A., Ed.</span>, <span class="refAuthor">Qu, Y.</span>, <span class="refAuthor">Yeung, D.</span>, <span class="refAuthor">Chen, I.</span>, and <span class="refAuthor">J. Zhang</span>, <span class="refTitle">"YANG Data Model for Key Chains"</span>, <span class="seriesInfo">RFC 8177</span>, <span class="seriesInfo">DOI 10.17487/RFC8177</span>, <time datetime="2017-06" class="refDate">June 2017</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8177">https://www.rfc-editor.org/info/rfc8177</a>&gt;</span>. </dd>
5473 <dd class="break"></dd>
5474 <dt id="RFC8294">[RFC8294]</dt>
5475 <dd>
5476 <span class="refAuthor">Liu, X.</span>, <span class="refAuthor">Qu, Y.</span>, <span class="refAuthor">Lindem, A.</span>, <span class="refAuthor">Hopps, C.</span>, and <span class="refAuthor">L. Berger</span>, <span class="refTitle">"Common YANG Data Types for the Routing Area"</span>, <span class="seriesInfo">RFC 8294</span>, <span class="seriesInfo">DOI 10.17487/RFC8294</span>, <time datetime="2017-12" class="refDate">December 2017</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8294">https://www.rfc-editor.org/info/rfc8294</a>&gt;</span>. </dd>
5477 <dd class="break"></dd>
5478 <dt id="RFC8341">[RFC8341]</dt>
5479 <dd>
5480 <span class="refAuthor">Bierman, A.</span> and <span class="refAuthor">M. Bjorklund</span>, <span class="refTitle">"Network Configuration Access Control Model"</span>, <span class="seriesInfo">STD 91</span>, <span class="seriesInfo">RFC 8341</span>, <span class="seriesInfo">DOI 10.17487/RFC8341</span>, <time datetime="2018-03" class="refDate">March 2018</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8341">https://www.rfc-editor.org/info/rfc8341</a>&gt;</span>. </dd>
5481 <dd class="break"></dd>
5482 <dt id="RFC8342">[RFC8342]</dt>
5483 <dd>
5484 <span class="refAuthor">Bjorklund, M.</span>, <span class="refAuthor">Schoenwaelder, J.</span>, <span class="refAuthor">Shafer, P.</span>, <span class="refAuthor">Watsen, K.</span>, and <span class="refAuthor">R. Wilton</span>, <span class="refTitle">"Network Management Datastore Architecture (NMDA)"</span>, <span class="seriesInfo">RFC 8342</span>, <span class="seriesInfo">DOI 10.17487/RFC8342</span>, <time datetime="2018-03" class="refDate">March 2018</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8342">https://www.rfc-editor.org/info/rfc8342</a>&gt;</span>. </dd>
5485 <dd class="break"></dd>
5486 <dt id="RFC8343">[RFC8343]</dt>
5487 <dd>
5488 <span class="refAuthor">Bjorklund, M.</span>, <span class="refTitle">"A YANG Data Model for Interface Management"</span>, <span class="seriesInfo">RFC 8343</span>, <span class="seriesInfo">DOI 10.17487/RFC8343</span>, <time datetime="2018-03" class="refDate">March 2018</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8343">https://www.rfc-editor.org/info/rfc8343</a>&gt;</span>. </dd>
5489 <dd class="break"></dd>
5490 <dt id="RFC8344">[RFC8344]</dt>
5491 <dd>
5492 <span class="refAuthor">Bjorklund, M.</span>, <span class="refTitle">"A YANG Data Model for IP Management"</span>, <span class="seriesInfo">RFC 8344</span>, <span class="seriesInfo">DOI 10.17487/RFC8344</span>, <time datetime="2018-03" class="refDate">March 2018</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8344">https://www.rfc-editor.org/info/rfc8344</a>&gt;</span>. </dd>
5493 <dd class="break"></dd>
5494 <dt id="RFC8349">[RFC8349]</dt>
5495 <dd>
5496 <span class="refAuthor">Lhotka, L.</span>, <span class="refAuthor">Lindem, A.</span>, and <span class="refAuthor">Y. Qu</span>, <span class="refTitle">"A YANG Data Model for Routing Management (NMDA Version)"</span>, <span class="seriesInfo">RFC 8349</span>, <span class="seriesInfo">DOI 10.17487/RFC8349</span>, <time datetime="2018-03" class="refDate">March 2018</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8349">https://www.rfc-editor.org/info/rfc8349</a>&gt;</span>. </dd>
5497 <dd class="break"></dd>
5498 <dt id="RFC8407">[RFC8407]</dt>
5499 <dd>
5500 <span class="refAuthor">Bierman, A.</span>, <span class="refTitle">"Guidelines for Authors and Reviewers of Documents Containing YANG Data Models"</span>, <span class="seriesInfo">BCP 216</span>, <span class="seriesInfo">RFC 8407</span>, <span class="seriesInfo">DOI 10.17487/RFC8407</span>, <time datetime="2018-10" class="refDate">October 2018</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8407">https://www.rfc-editor.org/info/rfc8407</a>&gt;</span>. </dd>
5501 <dd class="break"></dd>
5502 <dt id="RFC8446">[RFC8446]</dt>
5503 <dd>
5504 <span class="refAuthor">Rescorla, E.</span>, <span class="refTitle">"The Transport Layer Security (TLS) Protocol Version 1.3"</span>, <span class="seriesInfo">RFC 8446</span>, <span class="seriesInfo">DOI 10.17487/RFC8446</span>, <time datetime="2018-08" class="refDate">August 2018</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8446">https://www.rfc-editor.org/info/rfc8446</a>&gt;</span>. </dd>
5505 <dd class="break"></dd>
5506 <dt id="RFC8529">[RFC8529]</dt>
5507 <dd>
5508 <span class="refAuthor">Berger, L.</span>, <span class="refAuthor">Hopps, C.</span>, <span class="refAuthor">Lindem, A.</span>, <span class="refAuthor">Bogdanovic, D.</span>, and <span class="refAuthor">X. Liu</span>, <span class="refTitle">"YANG Data Model for Network Instances"</span>, <span class="seriesInfo">RFC 8529</span>, <span class="seriesInfo">DOI 10.17487/RFC8529</span>, <time datetime="2019-03" class="refDate">March 2019</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8529">https://www.rfc-editor.org/info/rfc8529</a>&gt;</span>. </dd>
5509 <dd class="break"></dd>
5510 <dt id="RFC9067">[RFC9067]</dt>
5511 <dd>
5512 <span class="refAuthor">Qu, Y.</span>, <span class="refAuthor">Tantsura, J.</span>, <span class="refAuthor">Lindem, A.</span>, and <span class="refAuthor">X. Liu</span>, <span class="refTitle">"A YANG Data Model for Routing Policy"</span>, <span class="seriesInfo">RFC 9067</span>, <span class="seriesInfo">DOI 10.17487/RFC9067</span>, <time datetime="2021-10" class="refDate">October 2021</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc9067">https://www.rfc-editor.org/info/rfc9067</a>&gt;</span>. </dd>
5513 <dd class="break"></dd>
5514 </dl>
5515 </section>
5516 <section id="section-13">
5517 <h2 id="name-informative-references">
5518 <a href="#section-13" class="section-number selfRef">13. </a><a href="#name-informative-references" class="section-name selfRef">Informative References</a>
5519 </h2>
5520 <dl class="references">
5521 <dt id="I-D.ietf-mpls-mldp-yang">[MPLS-MLDP-YANG]</dt>
5522 <dd>
5523 <span class="refAuthor">Raza, K., Ed.</span>, <span class="refAuthor">Liu, X.</span>, <span class="refAuthor">Esale, S.</span>, <span class="refAuthor">Andersson, L.</span>, <span class="refAuthor">Tantsura, J.</span>, and <span class="refAuthor">S. Krishnaswamy</span>, <span class="refTitle">"YANG Data Model for MPLS mLDP"</span>, <span class="refContent">Work in Progress</span>, <span class="seriesInfo">Internet-Draft, draft-ietf-mpls-mldp-yang-10</span>, <time datetime="2021-11-11" class="refDate">11 November 2021</time>, <span>&lt;<a href="https://datatracker.ietf.org/doc/html/draft-ietf-mpls-mldp-yang-10">https://datatracker.ietf.org/doc/html/draft-ietf-mpls-mldp-yang-10</a>&gt;</span>. </dd>
5524 <dd class="break"></dd>
5525 <dt id="RFC4364">[RFC4364]</dt>
5526 <dd>
5527 <span class="refAuthor">Rosen, E.</span> and <span class="refAuthor">Y. Rekhter</span>, <span class="refTitle">"BGP/MPLS IP Virtual Private Networks (VPNs)"</span>, <span class="seriesInfo">RFC 4364</span>, <span class="seriesInfo">DOI 10.17487/RFC4364</span>, <time datetime="2006-02" class="refDate">February 2006</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc4364">https://www.rfc-editor.org/info/rfc4364</a>&gt;</span>. </dd>
5528 <dd class="break"></dd>
5529 <dt id="RFC7307">[RFC7307]</dt>
5530 <dd>
5531 <span class="refAuthor">Zhao, Q.</span>, <span class="refAuthor">Raza, K.</span>, <span class="refAuthor">Zhou, C.</span>, <span class="refAuthor">Fang, L.</span>, <span class="refAuthor">Li, L.</span>, and <span class="refAuthor">D. King</span>, <span class="refTitle">"LDP Extensions for Multi-Topology"</span>, <span class="seriesInfo">RFC 7307</span>, <span class="seriesInfo">DOI 10.17487/RFC7307</span>, <time datetime="2014-07" class="refDate">July 2014</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc7307">https://www.rfc-editor.org/info/rfc7307</a>&gt;</span>. </dd>
5532 <dd class="break"></dd>
5533 <dt id="RFC7951">[RFC7951]</dt>
5534 <dd>
5535 <span class="refAuthor">Lhotka, L.</span>, <span class="refTitle">"JSON Encoding of Data Modeled with YANG"</span>, <span class="seriesInfo">RFC 7951</span>, <span class="seriesInfo">DOI 10.17487/RFC7951</span>, <time datetime="2016-08" class="refDate">August 2016</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc7951">https://www.rfc-editor.org/info/rfc7951</a>&gt;</span>. </dd>
5536 <dd class="break"></dd>
5537 <dt id="RFC8340">[RFC8340]</dt>
5538 <dd>
5539 <span class="refAuthor">Bjorklund, M.</span> and <span class="refAuthor">L. Berger, Ed.</span>, <span class="refTitle">"YANG Tree Diagrams"</span>, <span class="seriesInfo">BCP 215</span>, <span class="seriesInfo">RFC 8340</span>, <span class="seriesInfo">DOI 10.17487/RFC8340</span>, <time datetime="2018-03" class="refDate">March 2018</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8340">https://www.rfc-editor.org/info/rfc8340</a>&gt;</span>. </dd>
5540 <dd class="break"></dd>
5541 </dl>
5542 </section>
5543 <section id="appendix-A">
5544 <h2 id="name-data-tree-example">
5545 <a href="#appendix-A" class="section-number selfRef">Appendix A. </a><a href="#name-data-tree-example" class="section-name selfRef">Data Tree Example</a>
5546 </h2>
5547 <p id="appendix-A-1">
5548 This section contains an example of an instance data tree in the JSON
5549 encoding <span>[<a href="#RFC7951" class="xref">RFC7951</a>]</span>, containing both configuration and
5550 state data.<a href="#appendix-A-1" class="pilcrow">¶</a></p>
5551 <span id="name-example-topology"></span><div id="ex_top">
5552 <figure id="figure-12">
5553 <div class="alignLeft art-text artwork" id="appendix-A-2.1">
5554 <pre>
5555 +---------------------+
5556 | |
5557 | Router 203.0.113.1 |
5558 | |
5559 +----------+----------+
5560 |eth1
5561 |2001:db8:0:1::1/64
5562 |
5563 |
5564 |2001:db8:0:1::2/64
5565 +----------+----------+
5566 | | |
5567 | Another Router +---------| 2001:db8:0:2::/64
5568 | | |
5569 +---------------------+
5570 </pre>
5571 </div>
5572 <figcaption><a href="#figure-12" class="selfRef">Figure 12</a>:
5573 <a href="#name-example-topology" class="selfRef">Example Topology</a>
5574 </figcaption></figure>
5575 </div>
5576 <p id="appendix-A-3">
5577 The configuration instance data tree for Router 203.0.113.1 in <a href="#ex_top" class="xref">Figure 12</a> could be as follows:<a href="#appendix-A-3" class="pilcrow">¶</a></p>
5578 <span id="name-example-configuration-data-"></span><figure id="figure-13">
5579 <div id="appendix-A-4.1">
5580 <pre class="lang-json sourcecode">
5581
5582 {
5583 "ietf-interfaces:interfaces": {
5584 "interface": [
5585 {
5586 "name": "eth1",
5587 "description": "An interface with LDP enabled.",
5588 "type": "iana-if-type:ethernetCsmacd",
5589 "ietf-ip:ipv6": {
5590 "address": [
5591 {
5592 "ip": "2001:db8:0:1::1",
5593 "prefix-length": 64
5594 }
5595 ],
5596 "forwarding": true
5597 }
5598 }
5599 ]
5600 },
5601 "ietf-routing:routing": {
5602 "router-id": "203.0.113.1",
5603 "control-plane-protocols": {
5604 "control-plane-protocol": [
5605 {
5606 "type": "ietf-mpls-ldp:mpls-ldp",
5607 "name": "ldp-1",
5608 "ietf-mpls-ldp:mpls-ldp": {
5609 "global": {
5610 "address-families": {
5611 "ietf-mpls-ldp-extended:ipv6": {
5612 "enabled": true,
5613 "transport-address": "2001:db8:0:1::1"
5614 }
5615 }
5616 },
5617 "discovery": {
5618 "interfaces": {
5619 "interface": [
5620 {
5621 "name": "eth1",
5622 "address-families": {
5623 "ietf-mpls-ldp-extended:ipv6": {
5624 "enabled": true
5625 }
5626 }
5627 }
5628 ]
5629 }
5630 }
5631 }
5632 }
5633 ]
5634 }
5635 }
5636 }
5637
5638 </pre>
5639 </div>
5640 <figcaption><a href="#figure-13" class="selfRef">Figure 13</a>:
5641 <a href="#name-example-configuration-data-" class="selfRef">Example Configuration Data in JSON</a>
5642 </figcaption></figure>
5643 <p id="appendix-A-5">
5644 The corresponding operational state data for Router 203.0.113.1
5645 could be as follows:<a href="#appendix-A-5" class="pilcrow">¶</a></p>
5646 <span id="name-example-operational-data-in"></span><figure id="figure-14">
5647 <div id="appendix-A-6.1">
5648 <pre class="lang-json sourcecode">
5649 {
5650 "ietf-interfaces:interfaces": {
5651 "interface": [
5652 {
5653 "name": "eth1",
5654 "description": "An interface with LDP enabled.",
5655 "type": "iana-if-type:ethernetCsmacd",
5656 "phys-address": "00:00:5e:00:53:01",
5657 "oper-status": "up",
5658 "statistics": {
5659 "discontinuity-time": "2018-09-10T15:16:27-05:00"
5660 },
5661 "ietf-ip:ipv6": {
5662 "forwarding": true,
5663 "mtu": 1500,
5664 "address": [
5665 {
5666 "ip": "2001:db8:0:1::1",
5667 "prefix-length": 64,
5668 "origin": "static",
5669 "status": "preferred"
5670 },
5671 {
5672 "ip": "fe80::200:5eff:fe00:5301",
5673 "prefix-length": 64,
5674 "origin": "link-layer",
5675 "status": "preferred"
5676 }
5677 ],
5678 "neighbor": [
5679 {
5680 "ip": "2001:db8:0:1::2",
5681 "link-layer-address": "00:00:5e:00:53:02",
5682 "origin": "dynamic",
5683 "is-router": [null],
5684 "state": "reachable"
5685 },
5686 {
5687 "ip": "fe80::200:5eff:fe00:5302",
5688 "link-layer-address": "00:00:5e:00:53:02",
5689 "origin": "dynamic",
5690 "is-router": [null],
5691 "state": "reachable"
5692 }
5693 ]
5694 }
5695 }
5696 ]
5697 },
5698 "ietf-routing:routing": {
5699 "router-id": "203.0.113.1",
5700 "interfaces": {
5701 "interface": [
5702 "eth1"
5703 ]
5704 },
5705 "control-plane-protocols": {
5706 "control-plane-protocol": [
5707 {
5708 "type": "ietf-mpls-ldp:mpls-ldp",
5709 "name": "ldp-1",
5710 "ietf-mpls-ldp:mpls-ldp": {
5711 "global": {
5712 "address-families": {
5713 "ietf-mpls-ldp-extended:ipv6": {
5714 "enabled": true,
5715 "transport-address": "2001:db8:0:1::1"
5716 }
5717 }
5718 },
5719 "discovery": {
5720 "interfaces": {
5721 "interface": [
5722 {
5723 "name": "eth1",
5724 "address-families": {
5725 "ietf-mpls-ldp-extended:ipv6": {
5726 "enabled": true,
5727 "hello-adjacencies": {
5728 "hello-adjacency": [
5729 {
5730 "adjacent-address":
5731 "fe80::200:5eff:fe00:5302",
5732 "flag": ["adjacency-flag-active"],
5733 "hello-holdtime": {
5734 "adjacent": 15,
5735 "negotiated": 15,
5736 "remaining": 9
5737 },
5738 "next-hello": 3,
5739 "statistics": {
5740 "discontinuity-time":
5741 "2018-09-10T15:16:27-05:00"
5742 },
5743 "peer": {
5744 "lsr-id": "203.0.113.2",
5745 "label-space-id": 0
5746 }
5747 }
5748 ]
5749 }
5750 }
5751 }
5752 }
5753 ]
5754 }
5755 },
5756 "peers": {
5757 "peer": [
5758 {
5759 "lsr-id": "203.0.113.2",
5760 "label-space-id": 0,
5761 "label-advertisement-mode": {
5762 "local": "downstream-unsolicited",
5763 "peer": "downstream-unsolicited",
5764 "negotiated": "downstream-unsolicited"
5765 },
5766 "next-keep-alive": 5,
5767 "session-holdtime": {
5768 "peer": 180,
5769 "negotiated": 180,
5770 "remaining": 78
5771 },
5772 "session-state": "operational",
5773 "tcp-connection": {
5774 "local-address": "fe80::200:5eff:fe00:5301",
5775 "local-port": 646,
5776 "remote-address": "fe80::200:5eff:fe00:5302",
5777 "remote-port": 646
5778 },
5779 "up-time": 3438100,
5780 "statistics": {
5781 "discontinuity-time": "2018-09-10T15:16:27-05:00"
5782 }
5783 }
5784 ]
5785 }
5786 }
5787 }
5788 ]
5789 }
5790 }
5791 }
5792 </pre>
5793 </div>
5794 <figcaption><a href="#figure-14" class="selfRef">Figure 14</a>:
5795 <a href="#name-example-operational-data-in" class="selfRef">Example Operational Data in JSON</a>
5796 </figcaption></figure>
5797 </section>
5798 <section id="appendix-B">
5799 <h2 id="name-acknowledgments">
5800 <a href="#name-acknowledgments" class="section-name selfRef">Acknowledgments</a>
5801 </h2>
5802 <p id="appendix-B-1">The authors would like to acknowledge <span class="contact-name">Eddie Chami</span>, <span class="contact-name">Nagendra Kumar</span>, <span class="contact-name">Mannan Venkatesan</span>, and <span class="contact-name">Pavan Beeram</span> for their contribution to this
5803 document.<a href="#appendix-B-1" class="pilcrow">¶</a></p>
5804 <p id="appendix-B-2"> We also acknowledge <span class="contact-name">Ladislav Lhotka</span>,
5805 <span class="contact-name">Jan Lindblad</span>, <span class="contact-name">Tom Petch</span>, <span class="contact-name">Yingzhen Qu</span>, and <span class="contact-name">Benjamin Kaduk</span> for their detailed review of the
5806 model during WG and IESG processes.<a href="#appendix-B-2" class="pilcrow">¶</a></p>
5807 </section>
5808 <section id="appendix-C">
5809 <h2 id="name-contributors">
5810 <a href="#name-contributors" class="section-name selfRef">Contributors</a>
5811 </h2>
5812 <address class="vcard">
5813 <div dir="auto" class="left"><span class="fn nameRole">Danial Johari</span></div>
5814 <div dir="auto" class="left"><span class="org">Cisco Systems</span></div>
5815 <div class="email">
5816 <span>Email:</span>
5817 <a href="mailto:[email protected]" class="email">[email protected]</a>
5818 </div>
5819 </address>
5820 <address class="vcard">
5821 <div dir="auto" class="left"><span class="fn nameRole">Loa Andersson</span></div>
5822 <div dir="auto" class="left"><span class="org">Huawei Technologies</span></div>
5823 <div class="email">
5824 <span>Email:</span>
5825 <a href="mailto:[email protected]" class="email">[email protected]</a>
5826 </div>
5827 </address>
5828 <address class="vcard">
5829 <div dir="auto" class="left"><span class="fn nameRole">Jeff Tantsura</span></div>
5830 <div dir="auto" class="left"><span class="org">Apstra</span></div>
5831 <div class="email">
5832 <span>Email:</span>
5833 <a href="mailto:[email protected]" class="email">[email protected]</a>
5834 </div>
5835 </address>
5836 <address class="vcard">
5837 <div dir="auto" class="left"><span class="fn nameRole">Matthew Bocci</span></div>
5838 <div dir="auto" class="left"><span class="org">Nokia</span></div>
5839 <div class="email">
5840 <span>Email:</span>
5841 <a href="mailto:[email protected]" class="email">[email protected]</a>
5842 </div>
5843 </address>
5844 <address class="vcard">
5845 <div dir="auto" class="left"><span class="fn nameRole">Reshad Rahman</span></div>
5846 <div class="email">
5847 <span>Email:</span>
5848 <a href="mailto:[email protected]" class="email">[email protected]</a>
5849 </div>
5850 </address>
5851 <address class="vcard">
5852 <div dir="auto" class="left"><span class="fn nameRole">Stephane Litkowski</span></div>
5853 <div dir="auto" class="left"><span class="org">Cisco Systems</span></div>
5854 <div class="email">
5855 <span>Email:</span>
5856 <a href="mailto:[email protected]" class="email">[email protected]</a>
5857 </div>
5858 </address>
5859 </section>
5860 <div id="authors-addresses">
5861 <section id="appendix-D">
5862 <h2 id="name-authors-addresses">
5863 <a href="#name-authors-addresses" class="section-name selfRef">Authors' Addresses</a>
5864 </h2>
5865 <address class="vcard">
5866 <div dir="auto" class="left"><span class="fn nameRole">Kamran Raza (<span class="role">editor</span>)</span></div>
5867 <div dir="auto" class="left"><span class="org">Cisco Systems</span></div>
5868 <div dir="auto" class="left"><span class="country-name">Canada</span></div>
5869 <div class="email">
5870 <span>Email:</span>
5871 <a href="mailto:[email protected]" class="email">[email protected]</a>
5872 </div>
5873 </address>
5874 <address class="vcard">
5875 <div dir="auto" class="left"><span class="fn nameRole">Rajiv Asati</span></div>
5876 <div dir="auto" class="left"><span class="org">Cisco Systems</span></div>
5877 <div dir="auto" class="left"><span class="country-name">United States of America</span></div>
5878 <div class="email">
5879 <span>Email:</span>
5880 <a href="mailto:[email protected]" class="email">[email protected]</a>
5881 </div>
5882 </address>
5883 <address class="vcard">
5884 <div dir="auto" class="left"><span class="fn nameRole">Xufeng Liu</span></div>
5885 <div dir="auto" class="left"><span class="org">IBM Corporation</span></div>
5886 <div dir="auto" class="left"><span class="country-name">United States of America</span></div>
5887 <div class="email">
5888 <span>Email:</span>
5889 <a href="mailto:[email protected]" class="email">[email protected]</a>
5890 </div>
5891 </address>
5892 <address class="vcard">
5893 <div dir="auto" class="left"><span class="fn nameRole">Santosh Easale</span></div>
5894 <div dir="auto" class="left"><span class="org">Juniper Networks</span></div>
5895 <div dir="auto" class="left"><span class="country-name">United States of America</span></div>
5896 <div class="email">
5897 <span>Email:</span>
5898 <a href="mailto:[email protected]" class="email">[email protected]</a>
5899 </div>
5900 </address>
5901 <address class="vcard">
5902 <div dir="auto" class="left"><span class="fn nameRole">Xia Chen</span></div>
5903 <div dir="auto" class="left"><span class="org">Huawei Technologies</span></div>
5904 <div dir="auto" class="left"><span class="country-name">China</span></div>
5905 <div class="email">
5906 <span>Email:</span>
5907 <a href="mailto:[email protected]" class="email">[email protected]</a>
5908 </div>
5909 </address>
5910 <address class="vcard">
5911 <div dir="auto" class="left"><span class="fn nameRole">Himanshu Shah</span></div>
5912 <div dir="auto" class="left"><span class="org">Ciena Corporation</span></div>
5913 <div dir="auto" class="left"><span class="country-name">United States of America</span></div>
5914 <div class="email">
5915 <span>Email:</span>
5916 <a href="mailto:[email protected]" class="email">[email protected]</a>
5917 </div>
5918 </address>
5919 </section>
5920 </div>
5921 <script>const toc = document.getElementById("toc");
5922 toc.querySelector("h2").addEventListener("click", e => {
5923 toc.classList.toggle("active");
5924 });
5925 toc.querySelector("nav").addEventListener("click", e => {
5926 toc.classList.remove("active");
5927 });
5928 </script>
5929 </body>
5930 </html>