idnits 2.17.1 draft-ietf-mpls-base-yang-11.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 (September 12, 2019) is 1687 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: March 15, 2020 R. Gandhi 6 Cisco Systems Inc 7 X. Liu 8 Volta Networks 9 V. Beeram 10 Juniper Networks 11 September 12, 2019 13 A YANG Data Model for MPLS Base 14 draft-ietf-mpls-base-yang-11 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 March 15, 2020. 41 Copyright Notice 43 Copyright (c) 2019 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 . . . . . . . . . . . . . . . . . . . . . . . . 16 70 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 17 71 7.1. Normative References . . . . . . . . . . . . . . . . . . 17 72 7.2. Informative References . . . . . . . . . . . . . . . . . 18 73 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 18 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 MPLS enabled interfaces 211 on a device. 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 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 236 +--ro local-label? rt-types:mpls-label 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 file "ietf-mpls@2019-09-11.yang" 300 module ietf-mpls { 301 yang-version 1.1; 303 namespace "urn:ietf:params:xml:ns:yang:ietf-mpls"; 305 /* Replace with IANA when assigned */ 306 prefix "mpls"; 308 import ietf-routing { 309 prefix "rt"; 310 reference "RFC8349: A YANG Data Model for Routing Management"; 311 } 313 import ietf-routing-types { 314 prefix "rt-types"; 315 reference "RFC8294:Common YANG Data Types for the Routing Area"; 316 } 318 import ietf-yang-types { 319 prefix "yang"; 320 reference "RFC6991: Common YANG Data Types"; 321 } 323 import ietf-interfaces { 324 prefix "if"; 325 reference "RFC8343: A YANG Data Model for Interface Management"; 326 } 328 organization "IETF MPLS Working Group"; 330 contact 331 "WG Web: 332 WG List: 334 Editor: Tarek Saad 335 337 Editor: Kamran Raza 338 340 Editor: Rakesh Gandhi 341 343 Editor: Xufeng Liu 344 346 Editor: Vishnu Pavan Beeram 347 "; 349 description 350 "This YANG module defines the essential components for the 351 management of the MPLS subsystem. The model fully conforms 352 to the Network Management Datastore Architecture (NMDA). 354 Copyright (c) 2018 IETF Trust and the persons 355 identified as authors of the code. All rights reserved. 357 Redistribution and use in source and binary forms, with or 358 without modification, is permitted pursuant to, and subject 359 to the license terms contained in, the Simplified BSD License 360 set forth in Section 4.c of the IETF Trust's Legal Provisions 361 Relating to IETF Documents 362 (https://trustee.ietf.org/license-info). 363 This version of this YANG module is part of RFC XXXX; see 364 the RFC itself for full legal notices."; 366 // RFC Ed.: replace XXXX with actual RFC number and remove this 367 // note. 369 // RFC Ed.: update the date below with the date of RFC publication 370 // and remove this note. 372 revision "2019-09-11" { 373 description 374 "Latest revision: 375 - Addressed review comments"; 376 reference "RFC XXXX: A YANG Data Model for base MPLS"; 377 } 379 /* Identities */ 380 identity mpls { 381 base rt:address-family; 382 description 383 "This identity represents the MPLS address family."; 384 } 386 identity label-block-alloc-mode { 387 description 388 "Base identity label-block allocation mode"; 389 } 391 identity label-block-alloc-mode-manager { 392 base label-block-alloc-mode; 393 description 394 "Label block allocation on reserved block 395 is managed by label manager"; 396 } 398 identity label-block-alloc-mode-application { 399 base label-block-alloc-mode; 400 description 401 "Label block allocation on reserved block 402 is managed by application"; 403 } 405 /** 406 * Typedefs 407 */ 408 typedef mpls-operations-type { 409 type enumeration { 410 enum impose-and-forward { 411 description 412 "Operation impose outgoing label(s) and forward to 413 next-hop"; 414 } 415 enum pop-and-forward { 416 description 417 "Operation pop incoming label and forward to next-hop"; 418 } 419 enum pop-impose-and-forward { 420 description 421 "Operation pop incoming label, impose one or more 422 outgoing label(s) and forward to next-hop"; 423 } 424 enum swap-and-forward { 425 description 426 "Operation swap incoming label, with outgoing label and 427 forward to next-hop"; 429 } 430 enum pop-and-lookup { 431 description 432 "Operation pop incoming label and perform a lookup"; 433 } 434 } 435 description "MPLS operations types"; 436 } 438 typedef nhlfe-role { 439 type enumeration { 440 enum PRIMARY { 441 description 442 "Next-hop acts as primary traffic carrying"; 443 } 444 enum BACKUP { 445 description 446 "Next-hop acts as backup"; 447 } 448 enum PRIMARY_AND_BACKUP { 449 description 450 "Next-hop acts as primary and backup simultaneously"; 451 } 452 } 453 description "The next-hop role"; 454 } 456 grouping nhlfe-single-contents { 457 description 458 "MPLS simple NHLFE contents"; 459 uses rt-types:mpls-label-stack; 460 } 462 grouping nhlfe-multiple-contents { 463 description 464 "MPLS NHLFE contents"; 465 leaf index { 466 type string; 467 description 468 "A user-specified identifier utilised to uniquely 469 reference the next-hop entry in the next-hop list. 470 The value of this index has no semantic meaning 471 other than for referencing the entry."; 472 } 474 leaf backup-index { 475 type string; 476 description 477 "A user-specified identifier utilised to uniquely 478 reference the backup next-hop entry in the NHLFE list. 479 The value of this index has no semantic meaning 480 other than for referencing the entry."; 481 } 483 leaf loadshare { 484 type uint16; 485 description 486 "This value is used to compute a loadshare to perform un-equal 487 load balancing when multiple outgoing next-hop(s) are 488 specified. A share is computed as a ratio of this number to the 489 total under all next-hops(s)."; 490 } 492 leaf role { 493 type nhlfe-role; 494 description "NHLFE role"; 495 } 497 uses nhlfe-single-contents; 498 } 500 grouping interface-mpls-properties { 501 description "MPLS interface contents grouping"; 502 leaf enabled { 503 type boolean; 504 description 505 "'true' if mpls encapsulation is enabled on the 506 interface. 'false' if mpls encapsulation is enabled 507 on the interface."; 508 } 509 leaf mtu { 510 type uint32; 511 description 512 "MPLS Maximum Transmission Unit (MTU) in bytes"; 513 } 514 } 516 grouping interfaces-mpls { 517 description "List of MPLS interfaces"; 518 list interface { 519 key "name"; 520 description "List of MPLS interfaces"; 521 leaf name { 522 type if:interface-ref; 523 description 524 "The name of a configured MPLS interface"; 526 } 527 uses interface-mpls-properties; 528 } 529 } 531 grouping label-block-properties { 532 description "Label-block configuration items"; 533 leaf index { 534 type string; 535 description 536 "A user-specified identifier utilised to uniquely 537 reference an MPLS label block"; 538 } 539 leaf start-label { 540 type rt-types:mpls-label; 541 must '. >= ../end-label' { 542 error-message 543 "The start-label must be less than or equal " + 544 "to end-label"; 545 } 546 description "Label-block start"; 547 } 548 leaf end-label { 549 type rt-types:mpls-label; 550 must '. <= ../start-label' { 551 error-message 552 "The end-label must be greater than or equal " + 553 "to start-label"; 554 } 555 description "Label-block end"; 556 } 557 leaf block-allocation-mode { 558 type identityref { 559 base label-block-alloc-mode; 560 } 561 description "Label-block allocation mode"; 562 } 563 } 565 grouping label-block_state { 566 description "Label-block state items"; 567 leaf free-labels-count { 568 when "../block-allocation-mode = " + 569 "'label-block-alloc-mode-manager'"; 570 type yang:counter32; 571 config false; 572 description "Label-block free labels count"; 573 } 574 leaf inuse-labels-count { 575 when "../block-allocation-mode = " + 576 "'label-block-alloc-mode-manager'"; 577 type yang:counter32; 578 config false; 579 description "Label-block inuse labels count"; 580 } 581 } 583 grouping globals { 584 description "MPLS global configuration grouping"; 585 leaf ttl-propagate { 586 type boolean; 587 default 'true'; 588 description "Propagate TTL between IP and MPLS"; 589 } 590 } 591 grouping label-blocks { 592 description "Label-block allocation grouping"; 593 container label-blocks { 594 description "Label-block allocation container"; 595 list label-block { 596 key index; 597 unique "start-label end-label"; 598 description "List of MPLS label-blocks"; 599 uses label-block-properties; 600 uses label-block_state; 601 } 602 } 603 } 605 augment "/rt:routing" { 606 description "MPLS augmentation."; 607 container mpls { 608 description 609 "MPLS container, to be used as an augmentation target node 610 other MPLS sub-features config, e.g. MPLS static LSP, MPLS 611 LDP LSPs, and Trafic Engineering MPLS LSP Tunnels, etc."; 612 uses globals; 613 uses label-blocks; 614 uses interfaces-mpls; 615 } 616 } 618 /* MPLS routes augmentation */ 619 augment "/rt:routing/rt:ribs/rt:rib/rt:routes/rt:route" { 620 description 621 "This is augmentation for all MPLS routes."; 623 leaf mpls-enabled { 624 type boolean; 625 default 'false'; 626 description 627 "Indicates whether MPLS is enabled for this route"; 628 } 629 leaf local-label { 630 when "../mpls-enabled = 'true'"; 631 type rt-types:mpls-label; 632 description "MPLS local label associated with the route."; 633 } 634 } 636 /* MPLS simple-next-hop augmentation */ 637 augment "/rt:routing/rt:ribs/rt:rib/rt:routes/rt:route/" 638 + "rt:next-hop/rt:next-hop-options/rt:simple-next-hop" { 639 description 640 "Augment 'simple-next-hop' case in IP unicast routes."; 641 uses nhlfe-single-contents { 642 when "/rt:routing/rt:ribs/rt:rib/rt:routes/rt:route" + 643 "/mpls:mpls-enabled = 'true'"; 644 } 645 } 647 /* MPLS next-hop-list augmentation */ 648 augment "/rt:routing/rt:ribs/rt:rib/rt:routes/rt:route/" 649 + "rt:next-hop/rt:next-hop-options/rt:next-hop-list/" 650 + "rt:next-hop-list/rt:next-hop" { 651 description 652 "This leaf augments the 'next-hop-list' case of IP unicast 653 routes."; 654 uses nhlfe-multiple-contents { 655 when "/rt:routing/rt:ribs/rt:rib/rt:routes/rt:route" + 656 "/mpls:mpls-enabled = 'true'"; 657 } 658 } 660 /* MPLS RPC input augmentation */ 661 augment 662 "/rt:routing/rt:ribs/rt:rib/rt:active-route/rt:input" { 663 description 664 "Input MPLS augmentation for the 'active-route' action 665 statement."; 666 leaf local-label { 667 type rt-types:mpls-label; 668 description 669 "MPLS local label."; 670 } 672 } 674 /* MPLS RPC output augmentation */ 675 augment "/rt:routing/rt:ribs/rt:rib/rt:active-route/" 676 + "rt:output/rt:route/" 677 + "rt:next-hop/rt:next-hop-options/rt:simple-next-hop" { 678 description 679 "Output MPLS augmentation for the 'active-route' action 680 statement."; 681 uses nhlfe-single-contents; 682 } 683 augment "/rt:routing/rt:ribs/rt:rib/rt:active-route/" 684 + "rt:output/rt:route/" 685 + "rt:next-hop/rt:next-hop-options/rt:next-hop-list/" 686 + "rt:next-hop-list/rt:next-hop" { 687 description 688 "Output MPLS augmentation for the 'active-route' action 689 statement."; 690 uses nhlfe-multiple-contents; 691 } 692 } 693 695 Figure 3: MPLS base YANG module 697 3. IANA Considerations 699 This document registers the following URIs in the IETF XML registry 700 [RFC3688]. Following the format in [RFC3688], the following 701 registration is requested to be made. 703 URI: urn:ietf:params:xml:ns:yang:ietf-mpls 704 Registrant Contact: The MPLS WG of the IETF. 705 XML: N/A, the requested URI is an XML namespace. 707 This document registers a YANG module in the YANG Module Names 708 registry [RFC6020]. 710 name: ietf-mpls 711 namespace: urn:ietf:params:xml:ns:yang:ietf-mpls 712 prefix: ietf-mpls 713 // RFC Ed.: replace XXXX with RFC number and remove this note 714 reference: RFCXXXX 716 4. Security Considerations 718 The YANG modules specified in this document define a schema for data 719 that is designed to be accessed via network management protocols such 720 as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF layer 721 is the secure transport layer, and the mandatory-to-implement secure 722 transport is Secure Shell (SSH) [RFC6242]. The lowest RESTCONF layer 723 is HTTPS, and the mandatory-to-implement secure transport is TLS 724 [RFC8446]. 726 The NETCONF access control model [RFC8341] provides the means to 727 restrict access for particular NETCONF or RESTCONF users to a 728 preconfigured subset of all available NETCONF or RESTCONF protocol 729 operations and content. 731 Some of the readable data nodes in these YANG modules may be 732 considered sensitive or vulnerable in some network environments. It 733 is thus important to control read access (e.g., via get, get-config, 734 or notification) to these data nodes. These are the subtrees and 735 data nodes and their sensitivity/vulnerability: 737 /rt:routing/rt:ribs/rt:rib/rt:active-route/rt:output/rt:route: this 738 path is augmented by additional MPLS leaf(s) defined in this model. 739 Access to this information may disclose the per prefix and/or other 740 information. 742 /rt:routing/rt:ribs/rt:rib/rt:active-route/rt:output/rt:route/ 743 rt:next-hop/rt:next-hop-options/rt:simple-next-hop: this path is 744 augmented by additional MPLS leaf(s) defined in this model. Access 745 to this information may disclose the next-hop or path per prefix and/ 746 or other information. 748 5. Acknowledgement 750 The authors would like to thank the members of the multi-vendor YANG 751 design team who are involved in the definition of this model. 753 6. Contributors 755 Igor Bryskin 756 Huawei Technologies 757 email: Igor.Bryskin@huawei.com 759 Himanshu Shah 760 Ciena 761 email: hshah@ciena.com 763 7. References 765 7.1. Normative References 767 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 768 Requirement Levels", BCP 14, RFC 2119, 769 DOI 10.17487/RFC2119, March 1997, 770 . 772 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 773 DOI 10.17487/RFC3688, January 2004, 774 . 776 [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for 777 the Network Configuration Protocol (NETCONF)", RFC 6020, 778 DOI 10.17487/RFC6020, October 2010, 779 . 781 [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., 782 and A. Bierman, Ed., "Network Configuration Protocol 783 (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, 784 . 786 [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure 787 Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011, 788 . 790 [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", 791 RFC 7950, DOI 10.17487/RFC7950, August 2016, 792 . 794 [RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF 795 Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017, 796 . 798 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 799 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 800 May 2017, . 802 [RFC8294] Liu, X., Qu, Y., Lindem, A., Hopps, C., and L. Berger, 803 "Common YANG Data Types for the Routing Area", RFC 8294, 804 DOI 10.17487/RFC8294, December 2017, 805 . 807 [RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams", 808 BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018, 809 . 811 [RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration 812 Access Control Model", STD 91, RFC 8341, 813 DOI 10.17487/RFC8341, March 2018, 814 . 816 [RFC8342] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K., 817 and R. Wilton, "Network Management Datastore Architecture 818 (NMDA)", RFC 8342, DOI 10.17487/RFC8342, March 2018, 819 . 821 [RFC8343] Bjorklund, M., "A YANG Data Model for Interface 822 Management", RFC 8343, DOI 10.17487/RFC8343, March 2018, 823 . 825 [RFC8349] Lhotka, L., Lindem, A., and Y. Qu, "A YANG Data Model for 826 Routing Management (NMDA Version)", RFC 8349, 827 DOI 10.17487/RFC8349, March 2018, 828 . 830 [RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol 831 Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018, 832 . 834 7.2. Informative References 836 [RFC3031] Rosen, E., Viswanathan, A., and R. Callon, "Multiprotocol 837 Label Switching Architecture", RFC 3031, 838 DOI 10.17487/RFC3031, January 2001, 839 . 841 Authors' Addresses 843 Tarek Saad 844 Juniper Networks 846 Email: tsaad@juniper.net 848 Kamran Raza 849 Cisco Systems Inc 851 Email: skraza@cisco.com 853 Rakesh Gandhi 854 Cisco Systems Inc 856 Email: rgandhi@cisco.com 857 Xufeng Liu 858 Volta Networks 860 Email: xufeng.liu.ietf@gmail.com 862 Vishnu Pavan Beeram 863 Juniper Networks 865 Email: vbeeram@juniper.net