idnits 2.17.1 draft-ietf-mpls-base-yang-12.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- The document date (February 19, 2020) is 1499 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) No issues found here. Summary: 0 errors (**), 0 flaws (~~), 2 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 MPLS Working Group T. Saad 3 Internet-Draft Juniper Networks 4 Intended status: Standards Track K. Raza 5 Expires: August 22, 2020 R. Gandhi 6 Cisco Systems Inc 7 X. Liu 8 Volta Networks 9 V. Beeram 10 Juniper Networks 11 February 19, 2020 13 A YANG Data Model for MPLS Base 14 draft-ietf-mpls-base-yang-12 16 Abstract 18 This document contains a specification of the MPLS base YANG model. 19 The MPLS base YANG model serves as a base framework for configuring 20 and managing an MPLS switching subsystem on an MPLS-enabled router. 21 It is expected that other MPLS YANG models (e.g. MPLS LSP Static, 22 LDP or RSVP-TE YANG models) will augment the MPLS base YANG model. 24 Status of This Memo 26 This Internet-Draft is submitted in full conformance with the 27 provisions of BCP 78 and BCP 79. 29 Internet-Drafts are working documents of the Internet Engineering 30 Task Force (IETF). Note that other groups may also distribute 31 working documents as Internet-Drafts. The list of current Internet- 32 Drafts is at https://datatracker.ietf.org/drafts/current/. 34 Internet-Drafts are draft documents valid for a maximum of six months 35 and may be updated, replaced, or obsoleted by other documents at any 36 time. It is inappropriate to use Internet-Drafts as reference 37 material or to cite them other than as "work in progress." 39 This Internet-Draft will expire on August 22, 2020. 41 Copyright Notice 43 Copyright (c) 2020 IETF Trust and the persons identified as the 44 document authors. All rights reserved. 46 This document is subject to BCP 78 and the IETF Trust's Legal 47 Provisions Relating to IETF Documents 48 (https://trustee.ietf.org/license-info) in effect on the date of 49 publication of this document. Please review these documents 50 carefully, as they describe your rights and restrictions with respect 51 to this document. Code Components extracted from this document must 52 include Simplified BSD License text as described in Section 4.e of 53 the Trust Legal Provisions and are provided without warranty as 54 described in the Simplified BSD License. 56 Table of Contents 58 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 59 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 60 1.2. Acronyms and Abbreviations . . . . . . . . . . . . . . . 3 61 2. MPLS Base Model . . . . . . . . . . . . . . . . . . . . . . . 3 62 2.1. Model Overview . . . . . . . . . . . . . . . . . . . . . 3 63 2.2. Model Organization . . . . . . . . . . . . . . . . . . . 4 64 2.3. Model Tree Diagram . . . . . . . . . . . . . . . . . . . 5 65 2.4. Model YANG Module . . . . . . . . . . . . . . . . . . . . 7 66 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15 67 4. Security Considerations . . . . . . . . . . . . . . . . . . . 16 68 5. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 16 69 6. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 17 70 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 17 71 7.1. Normative References . . . . . . . . . . . . . . . . . . 17 72 7.2. Informative References . . . . . . . . . . . . . . . . . 18 73 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 19 75 1. Introduction 77 A core routing data model is defined in [RFC8349], and it provides a 78 basis for the development of data models for routing protocols. The 79 MPLS base model augments core routing data model with additional data 80 specific to MPLS technology as described in the MPLS architecture 81 document [RFC3031]. 83 The MPLS base model serves as a basis for future development of MPLS 84 data models covering more-sophisticated MPLS feature(s) and sub- 85 system(s). The main purpose is to provide essential building blocks 86 for the more-complicated data models involving different control- 87 plane protocols, and advanced MPLS functions. 89 To this end, it is expected that the MPLS base data model will be 90 augmented by a number of other modules developed at IETF (e.g. by 91 TEAS and MPLS working groups). 93 The YANG module in this document conforms to the Network Management 94 Datastore Architecture (NMDA) [RFC8342]. 96 1.1. Terminology 98 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 99 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 100 "OPTIONAL" in this document are to be interpreted as described in BCP 101 14 [RFC2119] [RFC8174] when, and only when, they appear in all 102 capitals, as shown here. 104 The terminology for describing YANG data models is found in 105 [RFC7950]. 107 1.2. Acronyms and Abbreviations 109 MPLS: Multiprotocol Label Switching 111 RIB: Routing Information Base 113 LSP: Label Switched Path 115 LSR: Label Switching Router 117 LER: Label Edge Router 119 FEC: Forwarding Equivalence Class 121 NHLFE: Next Hop Label Forwarding Entry 123 ILM: Incoming Label Map 125 2. MPLS Base Model 127 This document describes the ietf-mpls YANG module that provides base 128 components of the MPLS data model. It is expected that other MPLS 129 YANG modules will augment the ietf-mpls base module for other MPLS 130 extension to provision LSP(s) (e.g. MPLS Static, MPLS LDP or MPLS 131 RSVP-TE LSP(s)). 133 2.1. Model Overview 135 This document defines a mechanism to model MPLS labeled routes as an 136 augmentation of the routing RIB data model defined in [RFC8349] for 137 IP prefix routes that are MPLS labeled. 139 The other MPLS route(s) that are non-IP prefix routes are modelled by 140 introducing a new "mpls" address-family RIB as per recommendation . 142 2.2. Model Organization 144 Routing module +---------------+ v: import 145 | ietf-routing | o: augment 146 +---------------+ 147 o 148 | 149 v 150 MPLS base +-----------+ v: import 151 module | ietf-mpls | o: augment 152 +-----------+ 153 o o------+ 154 | \ 155 v v 156 +-------------------+ +---------------------+ 157 MPLS Static | ietf-mpls-static@ | | ietf-mpls-ldp.yang@ | . . 158 LSP module +-------------------+ +---------------------+ 160 @: not in this document, shown for illustration only 162 Figure 1: Relationship between MPLS modules 164 ietf-mpls module contains the following high-level types and 165 groupings: 167 label-block-alloc-mode: 169 A base YANG identity for supported label block allocation mode(s). 171 mpls-operations-type: 173 An enumeration type that represents support possible MPLS 174 operation types (impose-and-forward, pop-and-forward, pop-impose- 175 and-forward, and pop-and-lookup) 177 nhlfe-role: 179 An enumeration type that represents the role of the NHLFE entry. 181 nhlfe-single-contents: 183 A YANG grouping that describes single NHLFE and its associated 184 parameters as described in the MPLS architecture document 185 [RFC3031]. 187 nhlfe-multiple-contents: 189 A YANG grouping that describes a set of NHLFE(s) and their 190 associated parameters as described in the MPLS architecture 191 document [RFC3031]. 193 interface-mpls-properties: 195 A YANG grouping that describes the properties of an MPLS interface 196 on a device. 198 interfaces-mpls: 200 A YANG grouping that describes the list of MPLS enabled interfaces 201 on a device. 203 label-block-properties: 205 A YANG grouping that describes the properties of an MPLS label 206 block. 208 label-blocks: 210 A YANG grouping that describes the list of assigned MPLS label 211 blocks and their properties. 213 2.3. Model Tree Diagram 215 The MPLS base tree diagram that follows the notation defined in 216 [RFC8340] is shown in Figure 2. 218 module: ietf-mpls 219 augment /rt:routing: 220 +--rw mpls {mpls}? 221 +--rw ttl-propagate? boolean 222 +--rw label-blocks 223 | +--rw label-block* [index] 224 | +--rw index string 225 | +--rw start-label? rt-types:mpls-label 226 | +--rw end-label? rt-types:mpls-label 227 | +--rw block-allocation-mode? identityref 228 | +--ro free-labels-count? yang:counter32 229 | +--ro inuse-labels-count? yang:counter32 230 +--rw interface* [name] 231 +--rw name if:interface-ref 232 +--rw enabled? boolean 233 +--rw mtu? uint32 234 augment /rt:routing/rt:ribs/rt:rib/rt:routes/rt:route: 235 +--ro mpls-enabled? boolean {mpls}? 236 +--ro local-label? rt-types:mpls-label {mpls}? 238 augment /rt:routing/rt:ribs/rt:rib/rt:routes/rt:route/rt:next-hop 239 /rt:next-hop-options/rt:simple-next-hop: 240 +--ro mpls-label-stack 241 +--ro entry* [id] 242 +--ro id uint8 243 +--ro label? rt-types:mpls-label 244 +--ro ttl? uint8 245 +--ro traffic-class? uint8 246 augment /rt:routing/rt:ribs/rt:rib/rt:routes/rt:route/rt:next-hop 247 /rt:next-hop-options/rt:next-hop-list/rt:next-hop-list 248 /rt:next-hop: 249 +--ro index? string 250 +--ro backup-index? string 251 +--ro loadshare? uint16 252 +--ro role? nhlfe-role 253 +--ro mpls-label-stack 254 +--ro entry* [id] 255 +--ro id uint8 256 +--ro label? rt-types:mpls-label 257 +--ro ttl? uint8 258 +--ro traffic-class? uint8 259 augment /rt:routing/rt:ribs/rt:rib/rt:active-route/rt:input: 260 +---w local-label? rt-types:mpls-label 261 augment /rt:routing/rt:ribs/rt:rib/rt:active-route/rt:output/rt:route 262 /rt:next-hop/rt:next-hop-options/rt:simple-next-hop: 263 +-- mpls-label-stack 264 +-- entry* [id] 265 +-- id uint8 266 +-- label? rt-types:mpls-label 267 +-- ttl? uint8 268 +-- traffic-class? uint8 269 augment /rt:routing/rt:ribs/rt:rib/rt:active-route/rt:output/rt:route 270 /rt:next-hop/rt:next-hop-options/rt:next-hop-list 271 /rt:next-hop-list/rt:next-hop: 272 +-- index? string 273 +-- backup-index? string 274 +-- loadshare? uint16 275 +-- role? nhlfe-role 276 +-- mpls-label-stack 277 +-- entry* [id] 278 +-- id uint8 279 +-- label? rt-types:mpls-label 280 +-- ttl? uint8 281 +-- traffic-class? uint8 283 Figure 2: MPLS Base tree diagram 285 2.4. Model YANG Module 287 This section describes the "ietf-mpls" YANG module that provides base 288 components of the MPLS data model. Other YANG module(s) may import 289 and augment the base MPLS module to add feature specific data. 291 The ietf-mpls module imports the following modules: 293 o ietf-routing defined in [RFC8349] 295 o ietf-routing-types defined in [RFC8294] 297 o ietf-interfaces defined in [RFC8343] 299 This model also references the following RFCs in defining the types 300 and YANG grouping of the YANG module: [RFC3031], and [RFC3032]. 302 file "ietf-mpls@2020-02-19.yang" 303 module ietf-mpls { 304 yang-version 1.1; 306 namespace "urn:ietf:params:xml:ns:yang:ietf-mpls"; 308 /* Replace with IANA when assigned */ 309 prefix "mpls"; 311 import ietf-routing { 312 prefix "rt"; 313 reference "RFC8349: A YANG Data Model for Routing Management"; 314 } 316 import ietf-routing-types { 317 prefix "rt-types"; 318 reference "RFC8294:Common YANG Data Types for the Routing Area"; 319 } 321 import ietf-yang-types { 322 prefix "yang"; 323 reference "RFC6991: Common YANG Data Types"; 324 } 326 import ietf-interfaces { 327 prefix "if"; 328 reference "RFC8343: A YANG Data Model for Interface Management"; 329 } 331 organization "IETF MPLS Working Group"; 332 contact 333 "WG Web: 335 WG List: 337 Editor: Tarek Saad 338 340 Editor: Kamran Raza 341 343 Editor: Rakesh Gandhi 344 346 Editor: Xufeng Liu 347 349 Editor: Vishnu Pavan Beeram 350 "; 352 description 353 "This YANG module defines the essential components for the 354 management of the MPLS subsystem. The model fully conforms 355 to the Network Management Datastore Architecture (NMDA). 357 Copyright (c) 2018 IETF Trust and the persons 358 identified as authors of the code. All rights reserved. 360 Redistribution and use in source and binary forms, with or 361 without modification, is permitted pursuant to, and subject 362 to the license terms contained in, the Simplified BSD License 363 set forth in Section 4.c of the IETF Trust's Legal Provisions 364 Relating to IETF Documents 365 (https://trustee.ietf.org/license-info). 366 This version of this YANG module is part of RFC XXXX; see 367 the RFC itself for full legal notices."; 369 // RFC Ed.: replace XXXX with actual RFC number and remove this 370 // note. 372 // RFC Ed.: update the date below with the date of RFC publication 373 // and remove this note. 375 revision "2020-02-19" { 376 description 377 "Latest revision: 378 - Addressed review comments"; 379 reference "RFC XXXX: A YANG Data Model for base MPLS"; 381 } 383 feature mpls { 384 description 385 "Indicates support for MPLS switching."; 386 reference "RFC3031"; 387 } 389 /* Identities */ 391 identity mpls { 392 base rt:address-family; 393 description 394 "This identity represents the MPLS address family."; 395 } 397 identity label-block-alloc-mode { 398 description 399 "Base identity label-block allocation mode"; 400 } 402 identity label-block-alloc-mode-manager { 403 base label-block-alloc-mode; 404 description 405 "Label block allocation on reserved block 406 is managed by label manager"; 407 } 409 identity label-block-alloc-mode-application { 410 base label-block-alloc-mode; 411 description 412 "Label block allocation on reserved block 413 is managed by application"; 414 } 416 /** 417 * Typedefs 418 */ 419 typedef mpls-operations-type { 420 type enumeration { 421 enum impose-and-forward { 422 description 423 "Operation impose outgoing label(s) and forward to 424 next-hop"; 425 } 426 enum pop-and-forward { 427 description 428 "Operation pop incoming label and forward to next-hop"; 430 } 431 enum pop-impose-and-forward { 432 description 433 "Operation pop incoming label, impose one or more 434 outgoing label(s) and forward to next-hop"; 435 } 436 enum swap-and-forward { 437 description 438 "Operation swap incoming label, with outgoing label and 439 forward to next-hop"; 440 } 441 enum pop-and-lookup { 442 description 443 "Operation pop incoming label and perform a lookup"; 444 } 445 } 446 description "MPLS operations types"; 447 } 449 typedef nhlfe-role { 450 type enumeration { 451 enum PRIMARY { 452 description 453 "Next-hop acts as primary traffic carrying"; 454 } 455 enum BACKUP { 456 description 457 "Next-hop acts as backup"; 458 } 459 enum PRIMARY_AND_BACKUP { 460 description 461 "Next-hop acts as primary and backup simultaneously"; 462 } 463 } 464 description "The next-hop role"; 465 } 467 grouping nhlfe-single-contents { 468 description 469 "MPLS simple NHLFE contents"; 470 uses rt-types:mpls-label-stack; 471 } 473 grouping nhlfe-multiple-contents { 474 description 475 "MPLS NHLFE contents"; 476 leaf index { 477 type string; 478 description 479 "A user-specified identifier utilised to uniquely 480 reference the next-hop entry in the next-hop list. 481 The value of this index has no semantic meaning 482 other than for referencing the entry."; 483 } 485 leaf backup-index { 486 type string; 487 description 488 "A user-specified identifier utilised to uniquely 489 reference the backup next-hop entry in the NHLFE list. 490 The value of this index has no semantic meaning 491 other than for referencing the entry."; 492 } 494 leaf loadshare { 495 type uint16; 496 description 497 "This value is used to compute a loadshare to perform un-equal 498 load balancing when multiple outgoing next-hop(s) are 499 specified. A share is computed as a ratio of this number to the 500 total under all next-hops(s)."; 501 reference "RFC3031, section 3.11 and 3.12."; 502 } 504 leaf role { 505 type nhlfe-role; 506 description "NHLFE role"; 507 } 509 uses nhlfe-single-contents; 510 } 512 grouping interface-mpls-properties { 513 description "MPLS interface contents grouping"; 514 leaf enabled { 515 type boolean; 516 description 517 "'true' if mpls encapsulation is enabled on the 518 interface. 'false' if mpls encapsulation is enabled 519 on the interface."; 520 } 521 leaf mtu { 522 type uint32; 523 description 524 "MPLS Maximum Transmission Unit (MTU) in bytes"; 525 reference "RFC3032, section 3.2."; 527 } 528 } 530 grouping interfaces-mpls { 531 description "List of MPLS interfaces"; 532 list interface { 533 key "name"; 534 description "List of MPLS interfaces"; 535 leaf name { 536 type if:interface-ref; 537 description 538 "The name of a configured MPLS interface"; 539 } 540 uses interface-mpls-properties; 541 } 542 } 544 grouping label-block-properties { 545 description "Label-block configuration items"; 546 leaf index { 547 type string; 548 description 549 "A user-specified identifier utilised to uniquely 550 reference an MPLS label block"; 551 } 552 leaf start-label { 553 type rt-types:mpls-label; 554 must '. >= ../end-label' { 555 error-message 556 "The start-label must be less than or equal " + 557 "to end-label"; 558 } 559 description "Label-block start"; 560 } 561 leaf end-label { 562 type rt-types:mpls-label; 563 must '. <= ../start-label' { 564 error-message 565 "The end-label must be greater than or equal " + 566 "to start-label"; 567 } 568 description "Label-block end"; 569 } 570 leaf block-allocation-mode { 571 type identityref { 572 base label-block-alloc-mode; 573 } 574 description "Label-block allocation mode"; 576 } 577 } 579 grouping label-block_state { 580 description "Label-block state items"; 581 leaf free-labels-count { 582 when "derived-from-or-self(../block-allocation-mode, " + 583 "'mpls:label-block-alloc-mode-manager')"; 584 type yang:counter32; 585 config false; 586 description "Label-block free labels count"; 587 } 588 leaf inuse-labels-count { 589 when "derived-from-or-self(../block-allocation-mode, " + 590 "'mpls:label-block-alloc-mode-manager')"; 591 type yang:counter32; 592 config false; 593 description "Label-block inuse labels count"; 594 } 595 } 597 grouping globals { 598 description "MPLS global configuration grouping"; 599 leaf ttl-propagate { 600 type boolean; 601 default 'true'; 602 description "Propagate TTL between IP and MPLS"; 603 } 604 } 605 grouping label-blocks { 606 description "Label-block allocation grouping"; 607 container label-blocks { 608 description "Label-block allocation container"; 609 list label-block { 610 key index; 611 unique "start-label end-label"; 612 description "List of MPLS label-blocks"; 613 uses label-block-properties; 614 uses label-block_state; 615 } 616 } 617 } 619 augment "/rt:routing" { 620 if-feature mpls; 621 description "MPLS augmentation."; 622 container mpls { 623 description 624 "MPLS container, to be used as an augmentation target node 625 other MPLS sub-features config, e.g. MPLS static LSP, MPLS 626 LDP LSPs, and Trafic Engineering MPLS LSP Tunnels, etc."; 627 uses globals; 628 uses label-blocks; 629 uses interfaces-mpls; 630 } 631 } 633 /* MPLS routes augmentation */ 634 augment "/rt:routing/rt:ribs/rt:rib/rt:routes/rt:route" { 635 if-feature mpls; 636 description 637 "This is augmentation for all MPLS routes."; 638 leaf mpls-enabled { 639 type boolean; 640 default 'false'; 641 description 642 "Indicates whether MPLS is enabled for this route"; 643 } 644 leaf local-label { 645 when "../mpls-enabled = 'true'"; 646 type rt-types:mpls-label; 647 description "MPLS local label associated with the route."; 648 } 649 } 651 /* MPLS simple-next-hop augmentation */ 652 augment "/rt:routing/rt:ribs/rt:rib/rt:routes/rt:route/" 653 + "rt:next-hop/rt:next-hop-options/rt:simple-next-hop" { 654 description 655 "Augment 'simple-next-hop' case in IP unicast routes."; 656 uses nhlfe-single-contents { 657 when "/rt:routing/rt:ribs/rt:rib/rt:routes/rt:route" + 658 "/mpls:mpls-enabled = 'true'"; 659 } 660 } 662 /* MPLS next-hop-list augmentation */ 663 augment "/rt:routing/rt:ribs/rt:rib/rt:routes/rt:route/" 664 + "rt:next-hop/rt:next-hop-options/rt:next-hop-list/" 665 + "rt:next-hop-list/rt:next-hop" { 666 description 667 "This leaf augments the 'next-hop-list' case of IP unicast 668 routes."; 669 uses nhlfe-multiple-contents { 670 when "/rt:routing/rt:ribs/rt:rib/rt:routes/rt:route" + 671 "/mpls:mpls-enabled = 'true'"; 673 } 674 } 676 /* MPLS RPC input augmentation */ 677 augment 678 "/rt:routing/rt:ribs/rt:rib/rt:active-route/rt:input" { 679 description 680 "Input MPLS augmentation for the 'active-route' action 681 statement."; 682 leaf local-label { 683 type rt-types:mpls-label; 684 description 685 "MPLS local label."; 686 } 687 } 689 /* MPLS RPC output augmentation */ 690 augment "/rt:routing/rt:ribs/rt:rib/rt:active-route/" 691 + "rt:output/rt:route/" 692 + "rt:next-hop/rt:next-hop-options/rt:simple-next-hop" { 693 description 694 "Output MPLS augmentation for the 'active-route' action 695 statement."; 696 uses nhlfe-single-contents; 697 } 698 augment "/rt:routing/rt:ribs/rt:rib/rt:active-route/" 699 + "rt:output/rt:route/" 700 + "rt:next-hop/rt:next-hop-options/rt:next-hop-list/" 701 + "rt:next-hop-list/rt:next-hop" { 702 description 703 "Output MPLS augmentation for the 'active-route' action 704 statement."; 705 uses nhlfe-multiple-contents; 706 } 707 } 708 710 Figure 3: MPLS base YANG module 712 3. IANA Considerations 714 This document registers the following URIs in the IETF XML registry 715 [RFC3688]. Following the format in [RFC3688], the following 716 registration is requested to be made. 718 URI: urn:ietf:params:xml:ns:yang:ietf-mpls 719 Registrant Contact: The MPLS WG of the IETF. 720 XML: N/A, the requested URI is an XML namespace. 722 This document registers a YANG module in the YANG Module Names 723 registry [RFC6020]. 725 name: ietf-mpls 726 namespace: urn:ietf:params:xml:ns:yang:ietf-mpls 727 prefix: ietf-mpls 728 // RFC Ed.: replace XXXX with RFC number and remove this note 729 reference: RFCXXXX 731 4. Security Considerations 733 The YANG modules specified in this document define a schema for data 734 that is designed to be accessed via network management protocols such 735 as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF layer 736 is the secure transport layer, and the mandatory-to-implement secure 737 transport is Secure Shell (SSH) [RFC6242]. The lowest RESTCONF layer 738 is HTTPS, and the mandatory-to-implement secure transport is TLS 739 [RFC8446]. 741 The NETCONF access control model [RFC8341] provides the means to 742 restrict access for particular NETCONF or RESTCONF users to a 743 preconfigured subset of all available NETCONF or RESTCONF protocol 744 operations and content. 746 Some of the readable data nodes in these YANG modules may be 747 considered sensitive or vulnerable in some network environments. It 748 is thus important to control read access (e.g., via get, get-config, 749 or notification) to these data nodes. These are the subtrees and 750 data nodes and their sensitivity/vulnerability: 752 /rt:routing/rt:ribs/rt:rib/rt:active-route/rt:output/rt:route: this 753 path is augmented by additional MPLS leaf(s) defined in this model. 754 Access to this information may disclose the per prefix and/or other 755 information. 757 /rt:routing/rt:ribs/rt:rib/rt:active-route/rt:output/rt:route/ 758 rt:next-hop/rt:next-hop-options/rt:simple-next-hop: this path is 759 augmented by additional MPLS leaf(s) defined in this model. Access 760 to this information may disclose the next-hop or path per prefix and/ 761 or other information. 763 5. Acknowledgement 765 The authors would like to thank the members of the multi-vendor YANG 766 design team who are involved in the definition of this model. 768 6. Contributors 770 Igor Bryskin 771 Huawei Technologies 772 email: Igor.Bryskin@huawei.com 774 Himanshu Shah 775 Ciena 776 email: hshah@ciena.com 778 7. References 780 7.1. Normative References 782 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 783 Requirement Levels", BCP 14, RFC 2119, 784 DOI 10.17487/RFC2119, March 1997, 785 . 787 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 788 DOI 10.17487/RFC3688, January 2004, 789 . 791 [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for 792 the Network Configuration Protocol (NETCONF)", RFC 6020, 793 DOI 10.17487/RFC6020, October 2010, 794 . 796 [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., 797 and A. Bierman, Ed., "Network Configuration Protocol 798 (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, 799 . 801 [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure 802 Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011, 803 . 805 [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", 806 RFC 7950, DOI 10.17487/RFC7950, August 2016, 807 . 809 [RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF 810 Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017, 811 . 813 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 814 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 815 May 2017, . 817 [RFC8294] Liu, X., Qu, Y., Lindem, A., Hopps, C., and L. Berger, 818 "Common YANG Data Types for the Routing Area", RFC 8294, 819 DOI 10.17487/RFC8294, December 2017, 820 . 822 [RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams", 823 BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018, 824 . 826 [RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration 827 Access Control Model", STD 91, RFC 8341, 828 DOI 10.17487/RFC8341, March 2018, 829 . 831 [RFC8342] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K., 832 and R. Wilton, "Network Management Datastore Architecture 833 (NMDA)", RFC 8342, DOI 10.17487/RFC8342, March 2018, 834 . 836 [RFC8343] Bjorklund, M., "A YANG Data Model for Interface 837 Management", RFC 8343, DOI 10.17487/RFC8343, March 2018, 838 . 840 [RFC8349] Lhotka, L., Lindem, A., and Y. Qu, "A YANG Data Model for 841 Routing Management (NMDA Version)", RFC 8349, 842 DOI 10.17487/RFC8349, March 2018, 843 . 845 [RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol 846 Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018, 847 . 849 7.2. Informative References 851 [RFC3031] Rosen, E., Viswanathan, A., and R. Callon, "Multiprotocol 852 Label Switching Architecture", RFC 3031, 853 DOI 10.17487/RFC3031, January 2001, 854 . 856 [RFC3032] Rosen, E., Tappan, D., Fedorkow, G., Rekhter, Y., 857 Farinacci, D., Li, T., and A. Conta, "MPLS Label Stack 858 Encoding", RFC 3032, DOI 10.17487/RFC3032, January 2001, 859 . 861 Authors' Addresses 863 Tarek Saad 864 Juniper Networks 866 Email: tsaad@juniper.net 868 Kamran Raza 869 Cisco Systems Inc 871 Email: skraza@cisco.com 873 Rakesh Gandhi 874 Cisco Systems Inc 876 Email: rgandhi@cisco.com 878 Xufeng Liu 879 Volta Networks 881 Email: xufeng.liu.ietf@gmail.com 883 Vishnu Pavan Beeram 884 Juniper Networks 886 Email: vbeeram@juniper.net