idnits 2.17.1 draft-ietf-mpls-static-yang-07.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 (November 04, 2018) is 2001 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) == Outdated reference: A later version (-17) exists of draft-ietf-mpls-base-yang-08 == Outdated reference: A later version (-36) exists of draft-ietf-teas-yang-te-17 Summary: 0 errors (**), 0 flaws (~~), 4 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 K. Raza 4 Intended status: Standards Track R. Gandhi 5 Expires: May 8, 2019 Cisco Systems, Inc. 6 X. Liu 7 Volta Networks 8 V. Beeram 9 Juniper Networks 10 H. Shah 11 Ciena 12 I. Bryskin 13 Huawei Technologies 14 November 04, 2018 16 A YANG Data Model for MPLS Static LSPs 17 draft-ietf-mpls-static-yang-07 19 Abstract 21 This document contains the specification for the MPLS Static Label 22 Switched Paths (LSPs) YANG model. The model allows for the 23 provisioning of static LSP(s) on LER(s) and LSR(s) devices along a 24 LSP path without the dependency on any signaling protocol. The MPLS 25 Static LSP model augments the MPLS base YANG model with specific data 26 to configure and manage MPLS Static LSP(s). 28 Status of This Memo 30 This Internet-Draft is submitted in full conformance with the 31 provisions of BCP 78 and BCP 79. 33 Internet-Drafts are working documents of the Internet Engineering 34 Task Force (IETF). Note that other groups may also distribute 35 working documents as Internet-Drafts. The list of current Internet- 36 Drafts is at https://datatracker.ietf.org/drafts/current/. 38 Internet-Drafts are draft documents valid for a maximum of six months 39 and may be updated, replaced, or obsoleted by other documents at any 40 time. It is inappropriate to use Internet-Drafts as reference 41 material or to cite them other than as "work in progress." 43 This Internet-Draft will expire on May 8, 2019. 45 Copyright Notice 47 Copyright (c) 2018 IETF Trust and the persons identified as the 48 document authors. All rights reserved. 50 This document is subject to BCP 78 and the IETF Trust's Legal 51 Provisions Relating to IETF Documents 52 (https://trustee.ietf.org/license-info) in effect on the date of 53 publication of this document. Please review these documents 54 carefully, as they describe your rights and restrictions with respect 55 to this document. Code Components extracted from this document must 56 include Simplified BSD License text as described in Section 4.e of 57 the Trust Legal Provisions and are provided without warranty as 58 described in the Simplified BSD License. 60 Table of Contents 62 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 63 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 64 1.2. Acronyms and Abbreviations . . . . . . . . . . . . . . . 3 65 2. MPLS Static LSP Model . . . . . . . . . . . . . . . . . . . . 4 66 2.1. Model Organization . . . . . . . . . . . . . . . . . . . 4 67 2.2. Model Tree Diagram . . . . . . . . . . . . . . . . . . . 4 68 2.3. Model Overview . . . . . . . . . . . . . . . . . . . . . 6 69 2.4. Model YANG Module(s) . . . . . . . . . . . . . . . . . . 7 70 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15 71 4. Security Considerations . . . . . . . . . . . . . . . . . . . 16 72 5. References . . . . . . . . . . . . . . . . . . . . . . . . . 16 73 5.1. Normative References . . . . . . . . . . . . . . . . . . 16 74 5.2. Informative References . . . . . . . . . . . . . . . . . 18 75 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 18 77 1. Introduction 79 This document describes a YANG [RFC7950] data model for configuring 80 and managing the Multiprotocol Label Switching (MPLS) [RFC3031] 81 Static LSPs. The model allows the configuration of LER and LSR 82 devices with the necessary MPLS cross-connects or bindings to realize 83 an end-to-end LSP service. 85 A static LSP is established by manually specifying incoming and 86 outgoing MPLS label(s) and necessary forwarding information on each 87 of the traversed Label Edge Router (LER) and Label Switched Router 88 (LSR) devices (ingress, transit, or egress nodes) of the forwarding 89 path. 91 For example, on an ingress LER device, the model is used to associate 92 a specific Forwarding Equivalence Class (FEC) of packets- e.g. 94 matching a specific IP prefix in a Virtual Routing or Forwarding 95 (VRF) instance- to an MPLS outgoing label imposition, next-hop(s) and 96 respective outgoing interface(s) to forward the packet. On an LSR 97 device, the model is used to create a binding that swaps the incoming 98 label with an outgoing label and forwards the packet on one or 99 multiple egress path(s). On an egress LER, it is used to create a 100 binding that decapsulates the incoming MPLS label and performs 101 forwarding based on the inner MPLS label (if present) or IP 102 forwarding in the packet. 104 The MPLS Static LSP YANG model is broken into two modules "ietf-mpls- 105 static" and "ietf-mpls-static-extended". The "ietf-mpls-static" 106 module covers basic features for the configuration and management of 107 unidirectional Static LSP(s), while "ietf-mpls-static-extended" 108 covers extended features like the configuration and management of 109 bidirectional Static LSP(s) and LSP admission control. 111 The module "ietf-mpls-static" augments the MPLS Base YANG model 112 defined in module "ietf-mpls" in [I-D.ietf-mpls-base-yang]. 114 1.1. Terminology 116 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 117 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 118 "OPTIONAL" in this document are to be interpreted as described in BCP 119 14 [RFC2119] [RFC8174] when, and only when, they appear in all 120 capitals, as shown here. 122 The terminology for describing YANG data models is found in 123 [RFC7950]. 125 1.2. Acronyms and Abbreviations 127 MPLS: Multiprotocol Label Switching 129 LSP: Label Switched Path 131 LSR: Label Switching Router 133 LER: Label Edge Router 135 FEC: Forwarding Equivalence Class 137 NHLFE: Next Hop Label Forwarding Entry 139 ILM: Incoming Label Map 141 2. MPLS Static LSP Model 143 2.1. Model Organization 145 The base MPLS Static LSP model covers the core features with the 146 minimal set of configuration parameters needed to manage and operate 147 MPLS Static LSPs. 149 Additional MPLS Static LSP parameters as well as optional feature(s) 150 are grouped in a separate MPLS Static LSP extended model. The 151 relationship between the MPLS base and other MPLS modules are shown 152 in Figure 1. 154 Routing module +---------------+ v: import 155 | ietf-routing | o: augment 156 +---------------+ 157 o 158 | 159 v 160 MPLS base +-----------+ v: import 161 module | ietf-mpls | o: augment 162 +-----------+ 163 o o 164 | \ 165 v v 166 +------------------+ +--------------------+ 167 MPLS Static | ietf-mpls-static | | ietf-mpls-ldp.yang | . . . 168 LSP module +------------------+ +--------------------+ 169 o 170 | 171 v 172 +---------------------------+ 173 Extended MPLS | ietf-mpls-static-extended | 174 Static LSP +---------------------------+ 175 module 177 Figure 1: Relationship between MPLS modules 179 2.2. Model Tree Diagram 181 The MPLS Static and extended LSP tree diagram as per [RFC8340] is 182 shown in Figure 2. 184 module: ietf-mpls-static 185 augment /rt:routing/mpls:mpls: 186 +--rw static-lsps 187 +--rw static-lsp* [name] 188 | +--rw name string 189 | +--rw operation? mpls:mpls-operations-type 190 | +--rw in-segment 191 | | +--rw fec 192 | | +--rw (type)? 193 | | | +--:(ip-prefix) 194 | | | | +--rw ip-prefix? inet:ip-prefix 195 | | | +--:(mpls-label) 196 | | | | +--rw incoming-label? rt-types:mpls-label 197 | | | +--:(tunnel) 198 | | | +--rw tunnel? te:tunnel-ref 199 | | +--rw incoming-interface? if:interface-ref 200 | +--rw out-segment 201 | +--rw (out-segment)? 202 | +--:(nhlfe-single) 203 | | +--rw nhlfe-single 204 | | +--rw mpls-label-stack 205 | | | +--rw entry* [id] 206 | | | +--rw id uint8 207 | | | +--rw label? rt-types:mpls-label 208 | | | +--rw ttl? uint8 209 | | | +--rw traffic-class? uint8 210 | | +--rw outgoing-interface? if:interface-ref 211 | +--:(nhlfe-multiple) 212 | +--rw nhlfe-multiple 213 | +--rw nhlfe* [index] 214 | +--rw index string 215 | +--rw backup-index? string 216 | +--rw loadshare? uint16 217 | +--rw role? nhlfe-role 218 | +--rw mpls-label-stack 219 | | +--rw entry* [id] 220 | | +--rw id uint8 221 | | +--rw label? rt-types:mpls-label 222 | | +--rw ttl? uint8 223 | | +--rw traffic-class? uint8 224 | +--rw outgoing-interface? if:interface-ref 225 +--rw mpls-static-ext:bandwidth? uint32 226 +--rw mpls-static-ext:lsp-priority-setup? uint8 227 +--rw mpls-static-ext:lsp-priority-hold? uint8 229 module: ietf-mpls-static-extended 230 augment /rt:routing/mpls:mpls: 231 +--rw bidir-static-lsps 232 +--rw bidir-static-lsp* [name] 233 +--rw name string 234 +--rw forward-lsp? mpls-static:static-lsp-ref 235 +--rw reverse-lsp? mpls-static:static-lsp-ref 236 Figure 2: MPLS Static LSP tree diagram 238 2.3. Model Overview 240 This document defines two YANG modules for MPLS Static LSP(s) 241 configuration and management: ietf-mpls-static.yang and ietf-mpls- 242 static-extended.yang. 244 The ietf-mpls-static module imports the followinig modules: 246 o ietf-inet-types defined in [RFC6991] 248 o ietf-routing defined in [RFC8349] 250 o ietf-routing-types defined in [RFC8294] 252 o ietf-interfaces defined in [RFC8343] 254 o ietf-mpls defined in [I-D.ietf-mpls-base-yang] 256 o ietf-te defined in [I-D.ietf-teas-yang-te] 258 The ietf-mpls-static module contains the following high-level types 259 and groupings: 261 static-lsp-ref: 263 A YANG reference type for a static LSP that can be used by data 264 models to reference a configured static LSP. 266 in-segment: 268 A YANG grouping that describes parameters of an incoming class of 269 FEC associated with a specific LSP as described in the MPLS 270 architecture document [RFC3031]. The model allows the following 271 types of traffic to be mapped onto the static LSP on an ingress 272 LER: 274 o Unlabeled traffic destined to a specific prefix 275 o Labeled traffic arriving with a specific label 276 o Traffic carried on a TE tunnel whose LSP is 277 statically created via this model. 279 out-segment: 281 A YANG grouping that describes parameters for the forwarding 282 path(s) and their associated attributes for an LSP. The model 283 allows for the following cases: 285 o single forwarding path or NHLFE 286 o multiple forwarding path(s) or NHLFE(s), each of which can 287 serve a primary, backup or both role(s). 289 The ietf-mpls-static-extended module imports the followinig modules: 291 o ietf-mpls defined in [I-D.ietf-mpls-base-yang] 293 o ietf-mpls-static defined in this document 295 o ietf-routing defined in [RFC8349] 297 The ietf-mpls-static-extended module contains the following high- 298 level types and groupings: 300 bidir-static-lsp: 302 A YANG grouping that describes list of static bidirectional LSPs 304 The ietf-mpls-static-extended augments the ietf-mpls-static model 305 with additional parameters to configure and manage: 307 o Bidirectional Static LSP(s) 309 o Defining Static LSP bandwidth allocation 311 o Defining Static LSP preemption priorities 313 2.4. Model YANG Module(s) 315 Configuring LSPs through an LSR/LER involves the following steps: 317 o Enabling MPLS on MPLS capable interfaces. 319 o Configuring in-segments and out-segments on LER(s) and LSR(s) 320 traversed by the LSP. 322 o Setting up the cross-connect per LSP to associate segments and/or 323 to indicate connection origination and termination. 325 o Optionally specifying label stack actions. 327 o Optionally specifying segment traffic parameters. 329 The objects covered by this model are derived from the Incoming Label 330 Map (ILM) and Next Hop Label Forwarding Entry (NHLFE) as specified in 331 the MPLS architecture document [RFC3031]. 333 The MPLS Static LSP and Extended Static LSP modules are shown in 334 Figure 3 and Figure 4 below respectively. 336 file "ietf-mpls-static@2018-11-04.yang" 337 module ietf-mpls-static { 338 yang-version 1.1; 339 namespace "urn:ietf:params:xml:ns:yang:ietf-mpls-static"; 341 prefix "mpls-static"; 343 import ietf-mpls { 344 prefix "mpls"; 345 reference "draft-ietf-mpls-base-yang: MPLS Base YANG Data Model"; 346 } 348 import ietf-routing { 349 prefix "rt"; 350 reference "RFC8349: A YANG Data Model for Routing Management"; 351 } 353 import ietf-routing-types { 354 prefix "rt-types"; 355 reference "RFC6991: Common YANG Data Types"; 356 } 358 import ietf-inet-types { 359 prefix inet; 360 reference "RFC6991: Common YANG Data Types"; 361 } 363 import ietf-interfaces { 364 prefix "if"; 365 reference "RFC7223: A YANG Data Model for Interface Management"; 366 } 368 /* Import TE Tunnel */ 369 import ietf-te { 370 prefix te; 371 reference "draft-ietf-teas-yang-te: A YANG Data Model for Traffic 372 Engineering Tunnels and Interfaces"; 373 } 375 organization "IETF MPLS Working Group"; 377 contact 378 "WG Web: 380 WG List: 381 WG Chair: Loa Andersson 382 384 WG Chair: Nic Leymann 385 387 Editor: Tarek Saad 388 390 Editor: Kamran Raza 391 393 Editor: Rakesh Gandhi 394 396 Editor: Xufeng Liu 397 399 Editor: Vishnu Pavan Beeram 400 402 Editor: Himanshu Shah 403 405 Editor: Igor Bryskin 406 "; 408 description 409 "This YANG module augments the 'ietf-routing' module with basic 410 configuration and operational state data for MPLS static 411 The model fully conforms to the Network Management Datastore 412 Architecture (NMDA). 414 Copyright (c) 2018 IETF Trust and the persons 415 identified as authors of the code. All rights reserved. 417 Redistribution and use in source and binary forms, with or 418 without modification, is permitted pursuant to, and subject 419 to the license terms contained in, the Simplified BSD License 420 set forth in Section 4.c of the IETF Trust's Legal Provisions 421 Relating to IETF Documents 422 (https://trustee.ietf.org/license-info). 423 This version of this YANG module is part of RFC XXXX; see 424 the RFC itself for full legal notices."; 426 // RFC Ed.: replace XXXX with actual RFC number and remove this 427 // note. 429 // RFC Ed.: update the date below with the date of RFC publication 430 // and remove this note. 432 revision "2018-11-04" { 433 description 434 "Latest revision: 435 - Addressed MPLS-RT review comments"; 436 reference "RFC XXXX: A YANG Data Model for MPLS Static LSPs"; 437 } 439 typedef static-lsp-ref { 440 type leafref { 441 path "/rt:routing/mpls:mpls/mpls-static:static-lsps/" + 442 "mpls-static:static-lsp/mpls-static:name"; 443 } 444 description 445 "This type is used by data models that need to reference 446 configured static LSP."; 447 } 449 grouping in-segment { 450 description "In-segment grouping"; 451 container in-segment { 452 description "MPLS incoming segment"; 453 container fec { 454 description "Forwarding Equivalence Class grouping"; 455 choice type { 456 description "FEC type choices"; 457 case ip-prefix { 458 leaf ip-prefix { 459 type inet:ip-prefix; 460 description "An IP prefix"; 461 } 462 } 463 case mpls-label { 464 leaf incoming-label { 465 type rt-types:mpls-label; 466 description "label value on the incoming packet"; 467 } 468 } 469 case tunnel { 470 leaf tunnel { 471 type te:tunnel-ref; 472 description "TE tunnel FEC mapping"; 473 } 474 } 475 } 476 leaf incoming-interface { 477 type if:interface-ref; 478 description 479 "Optional incoming interface if FEC is restricted 480 to traffic incoming on a specific interface"; 481 } 482 } 483 } 484 } 486 grouping out-segment { 487 description "Out-segment grouping"; 488 container out-segment { 489 description "MPLS outgoing segment"; 490 choice out-segment { 491 description "The MPLS out-segment type choice"; 492 case nhlfe-single { 493 container nhlfe-single { 494 description "Container for single NHLFE entry"; 495 uses mpls:nhlfe-single-contents; 496 leaf outgoing-interface { 497 type if:interface-ref; 498 description 499 "The outgoing interface"; 500 } 501 } 502 } 503 case nhlfe-multiple { 504 container nhlfe-multiple { 505 description "Container for multiple NHLFE entries"; 506 list nhlfe { 507 key index; 508 description "MPLS NHLFE entry"; 509 uses mpls:nhlfe-multiple-contents; 510 leaf outgoing-interface { 511 type if:interface-ref; 512 description 513 "The outgoing interface"; 514 } 515 } 516 } 517 } 518 } 519 } 520 } 522 augment "/rt:routing/mpls:mpls" { 523 description "Augmentations for MPLS Static LSPs"; 524 container static-lsps { 525 description 526 "Statically configured LSPs, without dynamic signaling"; 527 list static-lsp { 528 key name; 529 description "list of defined static LSPs"; 530 leaf name { 531 type string; 532 description "name to identify the LSP"; 533 } 534 leaf operation { 535 type mpls:mpls-operations-type; 536 description 537 "The MPLS operation to be executed on the incoming packet"; 538 } 539 uses in-segment; 540 uses out-segment; 541 } 542 } 543 } 544 } 545 547 Figure 3: MPLS Static LSP YANG module 549 The extended MPLS Static LSP module is shown in Figure 4. 551 file "ietf-mpls-static-extended@2018-11-04.yang" 552 module ietf-mpls-static-extended { 553 yang-version 1.1; 554 namespace "urn:ietf:params:xml:ns:yang:ietf-mpls-static-extended"; 556 prefix "mpls-static-ext"; 558 import ietf-mpls { 559 prefix "mpls"; 560 reference "draft-ietf-mpls-base-yang: MPLS Base YANG Data Model"; 561 } 563 import ietf-routing { 564 prefix "rt"; 565 reference "RFC6991: Common YANG Data Types"; 566 } 568 import ietf-mpls-static { 569 prefix "mpls-static"; 570 reference "draft-ietf-mpls-static-yang: A YANG Data Model for MPLS 571 Static LSPs"; 572 } 573 organization "IETF MPLS Working Group"; 575 contact 576 "WG Web: 578 WG List: 580 WG Chair: Loa Andersson 581 583 WG Chair: Nic Leymann 584 586 Editor: Tarek Saad 587 589 Editor: Kamran Raza 590 592 Editor: Rakesh Gandhi 593 595 Editor: Xufeng Liu 596 598 Editor: Vishnu Pavan Beeram 599 601 Editor: Himanshu Shah 602 604 Editor: Igor Bryskin 605 "; 607 description 608 "This YANG module contains the Extended MPLS Static LSP YANG 609 data model. The model fully conforms to the Network Management 610 Datastore Architecture (NMDA). 612 Copyright (c) 2018 IETF Trust and the persons 613 identified as authors of the code. All rights reserved. 615 Redistribution and use in source and binary forms, with or 616 without modification, is permitted pursuant to, and subject 617 to the license terms contained in, the Simplified BSD License 618 set forth in Section 4.c of the IETF Trust's Legal Provisions 619 Relating to IETF Documents 620 (https://trustee.ietf.org/license-info). 622 This version of this YANG module is part of RFC XXXX; see 623 the RFC itself for full legal notices."; 625 // RFC Ed.: replace XXXX with actual RFC number and remove this 626 // note. 628 // RFC Ed.: update the date below with the date of RFC publication 629 // and remove this note. 631 revision "2018-11-04" { 632 description "Latest revision of MPLS extended yang module."; 633 reference "RFC XXXX: Extended YANG Data Model for MPLS Static LSPs"; 634 } 636 grouping bidir-static-lsp { 637 description 638 "grouping for top level list of static bidirectional LSPs"; 639 leaf forward-lsp { 640 type mpls-static:static-lsp-ref; 641 description 642 "Reference to a configured static forward LSP"; 643 } 644 leaf reverse-lsp { 645 type mpls-static:static-lsp-ref; 646 description 647 "Reference to a configured static reverse LSP"; 648 } 649 } 651 augment "/rt:routing/mpls:mpls/mpls-static:static-lsps" { 652 description 653 "Augmentation for static MPLS LSPs"; 655 leaf bandwidth { 656 type uint32; 657 units mbps; 658 description 659 "Bandwidth in Mbps, e.g., using offline calculation"; 660 } 661 leaf lsp-priority-setup { 662 type uint8 { 663 range "0..7"; 664 } 665 description "LSP setup priority"; 666 } 667 leaf lsp-priority-hold { 668 type uint8 { 669 range "0..7"; 671 } 672 description "LSP hold priority"; 673 } 674 } 676 augment "/rt:routing/mpls:mpls" { 677 description "Augmentations for MPLS Static LSPs"; 678 container bidir-static-lsps { 679 description 680 "Statically configured bidirectional LSPs"; 681 list bidir-static-lsp { 682 key name; 683 description "List of static bidirectional LSPs"; 685 leaf name { 686 type string; 687 description "Name that identifies the bidirectional LSP"; 688 } 689 uses bidir-static-lsp; 690 } 691 } 692 } 693 } 694 696 Figure 4: Extended MPLS Static LSP YANG module 698 3. IANA Considerations 700 This document registers the following URIs in the IETF XML registry 701 [RFC3688]. Following the format in [RFC3688], the following 702 registration is requested to be made. 704 URI: urn:ietf:params:xml:ns:yang:ietf-mpls-static 705 Registrant Contact: The MPLS WG of the IETF. 706 XML: N/A, the requested URI is an XML namespace. 708 URI: urn:ietf:params:xml:ns:yang:ietf-mpls-static-extended 709 Registrant Contact: The MPLS WG of the IETF. 710 XML: N/A, the requested URI is an XML namespace. 712 This document registers two YANG modules in the YANG Module Names 713 registry [RFC6020]. 715 name: ietf-mpls-static 716 namespace: urn:ietf:params:xml:ns:yang:ietf-mpls-static 717 prefix: ietf-mpls-static 718 // RFC Ed.: replace XXXX with RFC number and remove this note 719 reference: RFCXXXX 721 name: ietf-mpls-static-extended 722 namespace: urn:ietf:params:xml:ns:yang:ietf-mpls-static-extended 723 prefix: ietf-mpls-static-extended 724 // RFC Ed.: replace XXXX with RFC number and remove this note 725 reference: RFCXXXX 727 4. Security Considerations 729 The YANG module defined in this document is designed to be accessed 730 via the NETCONF protocol [RFC6241]. The lowest NETCONF layer is the 731 secure transport layer and the mandatory-to-implement secure 732 transport is SSH [RFC6242]. The NETCONF access control model 733 [RFC8341] provides means to restrict access for particular NETCONF 734 users to a pre-configured subset of all available NETCONF protocol 735 operations and content. 737 There are certain objects or data nodes that are defined in this YANG 738 module which are writable/creatable/deletable and that can be 739 considered sensitive or vulnerable in some network environments. 740 Specifically, misconfiguration or manipulations of objects or data 741 node(s) defined in this model, including: in-segment(s), out- 742 segment(s) and their associated parameters that collectively allow 743 the provisioning of MPLS LSP(s) and associated parameters on a LSR 744 can potentially have disastrous results. 746 5. References 748 5.1. Normative References 750 [I-D.ietf-mpls-base-yang] 751 Saad, T., Raza, K., Gandhi, R., Liu, X., and V. Beeram, "A 752 YANG Data Model for MPLS Base", draft-ietf-mpls-base- 753 yang-08 (work in progress), October 2018. 755 [I-D.ietf-teas-yang-te] 756 Saad, T., Gandhi, R., Liu, X., Beeram, V., Shah, H., and 757 I. Bryskin, "A YANG Data Model for Traffic Engineering 758 Tunnels and Interfaces", draft-ietf-teas-yang-te-17 (work 759 in progress), October 2018. 761 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 762 Requirement Levels", BCP 14, RFC 2119, 763 DOI 10.17487/RFC2119, March 1997, 764 . 766 [RFC3031] Rosen, E., Viswanathan, A., and R. Callon, "Multiprotocol 767 Label Switching Architecture", RFC 3031, 768 DOI 10.17487/RFC3031, January 2001, 769 . 771 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 772 DOI 10.17487/RFC3688, January 2004, 773 . 775 [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for 776 the Network Configuration Protocol (NETCONF)", RFC 6020, 777 DOI 10.17487/RFC6020, October 2010, 778 . 780 [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., 781 and A. Bierman, Ed., "Network Configuration Protocol 782 (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, 783 . 785 [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure 786 Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011, 787 . 789 [RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types", 790 RFC 6991, DOI 10.17487/RFC6991, July 2013, 791 . 793 [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", 794 RFC 7950, DOI 10.17487/RFC7950, August 2016, 795 . 797 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 798 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 799 May 2017, . 801 [RFC8294] Liu, X., Qu, Y., Lindem, A., Hopps, C., and L. Berger, 802 "Common YANG Data Types for the Routing Area", RFC 8294, 803 DOI 10.17487/RFC8294, December 2017, 804 . 806 [RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration 807 Access Control Model", STD 91, RFC 8341, 808 DOI 10.17487/RFC8341, March 2018, 809 . 811 [RFC8343] Bjorklund, M., "A YANG Data Model for Interface 812 Management", RFC 8343, DOI 10.17487/RFC8343, March 2018, 813 . 815 [RFC8349] Lhotka, L., Lindem, A., and Y. Qu, "A YANG Data Model for 816 Routing Management (NMDA Version)", RFC 8349, 817 DOI 10.17487/RFC8349, March 2018, 818 . 820 5.2. Informative References 822 [RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams", 823 BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018, 824 . 826 Authors' Addresses 828 Tarek Saad 829 Cisco Systems, Inc. 831 Email: tsaad@cisco.com 833 Kamran Raza 834 Cisco Systems, Inc. 836 Email: skraza@cisco.com 838 Rakesh Gandhi 839 Cisco Systems, Inc. 841 Email: rgandhi@cisco.com 843 Xufeng Liu 844 Volta Networks 846 Email: xufeng.liu.ietf@gmail.com 847 Vishnu Pavan Beeram 848 Juniper Networks 850 Email: vbeeram@juniper.net 852 Himanshu Shah 853 Ciena 855 Email: hshah@ciena.com 857 Igor Bryskin 858 Huawei Technologies 860 Email: Igor.Bryskin@huawei.com