idnits 2.17.1 draft-ietf-mpls-static-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 (April 20, 2020) is 1438 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-14 == Outdated reference: A later version (-36) exists of draft-ietf-teas-yang-te-23 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 Juniper Networks 4 Intended status: Standards Track R. Gandhi 5 Expires: October 22, 2020 Cisco Systems, Inc. 6 X. Liu 7 Volta Networks 8 V. Beeram 9 Juniper Networks 10 I. Bryskin 11 Huawei Technologies 12 April 20, 2020 14 A YANG Data Model for MPLS Static LSPs 15 draft-ietf-mpls-static-yang-11 17 Abstract 19 This document contains the specification for the MPLS Static Label 20 Switched Paths (LSPs) YANG model. The model allows for the 21 provisioning of static LSP(s) on Label Edge Router(s) LER(s) and 22 Label Switched Router(s) LSR(s) devices along a LSP path without the 23 dependency on any signaling protocol. The MPLS Static LSP model 24 augments the MPLS base YANG model with specific data to configure and 25 manage MPLS Static LSP(s). 27 Status of This Memo 29 This Internet-Draft is submitted in full conformance with the 30 provisions of BCP 78 and BCP 79. 32 Internet-Drafts are working documents of the Internet Engineering 33 Task Force (IETF). Note that other groups may also distribute 34 working documents as Internet-Drafts. The list of current Internet- 35 Drafts is at https://datatracker.ietf.org/drafts/current/. 37 Internet-Drafts are draft documents valid for a maximum of six months 38 and may be updated, replaced, or obsoleted by other documents at any 39 time. It is inappropriate to use Internet-Drafts as reference 40 material or to cite them other than as "work in progress." 42 This Internet-Draft will expire on October 22, 2020. 44 Copyright Notice 46 Copyright (c) 2020 IETF Trust and the persons identified as the 47 document authors. All rights reserved. 49 This document is subject to BCP 78 and the IETF Trust's Legal 50 Provisions Relating to IETF Documents 51 (https://trustee.ietf.org/license-info) in effect on the date of 52 publication of this document. Please review these documents 53 carefully, as they describe your rights and restrictions with respect 54 to this document. Code Components extracted from this document must 55 include Simplified BSD License text as described in Section 4.e of 56 the Trust Legal Provisions and are provided without warranty as 57 described in the Simplified BSD License. 59 Table of Contents 61 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 62 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 63 1.2. Acronyms and Abbreviations . . . . . . . . . . . . . . . 3 64 2. MPLS Static LSP Model . . . . . . . . . . . . . . . . . . . . 3 65 2.1. Model Organization . . . . . . . . . . . . . . . . . . . 4 66 2.2. Model Tree Diagram . . . . . . . . . . . . . . . . . . . 4 67 2.3. Model Overview . . . . . . . . . . . . . . . . . . . . . 6 68 2.4. Model YANG Module(s) . . . . . . . . . . . . . . . . . . 7 69 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14 70 4. Security Considerations . . . . . . . . . . . . . . . . . . . 15 71 5. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 15 72 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 16 73 6.1. Normative References . . . . . . . . . . . . . . . . . . 16 74 6.2. Informative References . . . . . . . . . . . . . . . . . 17 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 LER and LSR devices (ingress, transit, or egress 88 nodes) of the forwarding path. 90 For example, on an ingress LER device, the model is used to associate 91 a specific Forwarding Equivalence Class (FEC) of packets- e.g. 92 matching a specific IP prefix in a Virtual Routing or Forwarding 93 (VRF) instance- to an MPLS outgoing label imposition, next-hop(s) and 94 respective outgoing interface(s) to forward the packet. On an LSR 95 device, the model is used to create a binding that swaps the incoming 96 label with an outgoing label and forwards the packet on one or 97 multiple egress path(s). On an egress LER, it is used to create a 98 binding that decapsulates the incoming MPLS label and performs 99 forwarding based on the inner MPLS label (if present) or IP 100 forwarding in the packet. 102 The MPLS Static LSP YANG model is broken into two modules "ietf-mpls- 103 static" and "ietf-mpls-static-extended". The "ietf-mpls-static" 104 module covers basic features for the configuration and management of 105 unidirectional Static LSP(s), while "ietf-mpls-static-extended" 106 covers extended features like the configuration and management of 107 bidirectional Static LSP(s) and LSP admission control. 109 The module "ietf-mpls-static" augments the MPLS Base YANG model 110 defined in module "ietf-mpls" in [I-D.ietf-mpls-base-yang]. 112 1.1. Terminology 114 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 115 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 116 "OPTIONAL" in this document are to be interpreted as described in BCP 117 14 [RFC2119] [RFC8174] when, and only when, they appear in all 118 capitals, as shown here. 120 The terminology for describing YANG data models is found in 121 [RFC7950]. 123 1.2. Acronyms and Abbreviations 125 MPLS: Multiprotocol Label Switching 127 LSP: Label Switched Path 129 LSR: Label Switching Router 131 LER: Label Edge Router 133 FEC: Forwarding Equivalence Class 135 NHLFE: Next Hop Label Forwarding Entry 137 ILM: Incoming Label Map 139 2. MPLS Static LSP Model 140 2.1. Model Organization 142 The base MPLS Static LSP model covers the core features with the 143 minimal set of configuration parameters needed to manage and operate 144 MPLS Static LSPs. 146 Additional MPLS Static LSP parameters as well as optional feature(s) 147 are grouped in a separate MPLS Static LSP extended model. The 148 relationship between the MPLS base and other MPLS modules are shown 149 in Figure 1. 151 Routing module +---------------+ v: import 152 | ietf-routing | o: augment 153 +---------------+ 154 o 155 | 156 v 157 MPLS base +-----------+ v: import 158 module | ietf-mpls | o: augment 159 +-----------+ 160 o o 161 | \ 162 v v 163 +------------------+ +--------------------+ 164 MPLS Static | ietf-mpls-static | | ietf-mpls-ldp.yang | . . . 165 LSP module +------------------+ +--------------------+ 166 o 167 | 168 v 169 +---------------------------+ 170 Extended MPLS | ietf-mpls-static-extended | 171 Static LSP +---------------------------+ 172 module 174 Figure 1: Relationship between MPLS modules 176 2.2. Model Tree Diagram 178 The MPLS Static and extended LSP tree diagram as per [RFC8340] is 179 shown in Figure 2. 181 module: ietf-mpls-static 182 augment /rt:routing/mpls:mpls: 183 +--rw static-lsps 184 +--rw static-lsp* [name] 185 | +--rw name string 186 | +--rw operation? mpls:mpls-operations-type 187 | +--rw in-segment 188 | | +--rw fec 189 | | +--rw (type)? 190 | | | +--:(ip-prefix) 191 | | | | +--rw ip-prefix? inet:ip-prefix 192 | | | +--:(mpls-label) 193 | | | +--rw incoming-label? rt-types:mpls-label 194 | | +--rw incoming-interface? if:interface-ref 195 | +--rw out-segment 196 | +--rw (out-segment)? 197 | +--:(nhlfe-single) 198 | | +--rw nhlfe-single 199 | | +--rw mpls-label-stack 200 | | | +--rw entry* [id] 201 | | | +--rw id uint8 202 | | | +--rw label? rt-types:mpls-label 203 | | | +--rw ttl? uint8 204 | | | +--rw traffic-class? uint8 205 | | +--rw outgoing-interface? if:interface-ref 206 | +--:(nhlfe-multiple) 207 | +--rw nhlfe-multiple 208 | +--rw nhlfe* [index] 209 | +--rw index string 210 | +--rw backup-index? string 211 | +--rw loadshare? uint16 212 | +--rw role? nhlfe-role 213 | +--rw mpls-label-stack 214 | | +--rw entry* [id] 215 | | +--rw id uint8 216 | | +--rw label? 217 | | | rt-types:mpls-label 218 | | +--rw ttl? uint8 219 | | +--rw traffic-class? uint8 220 | +--rw outgoing-interface? if:interface-ref 221 +--rw mpls-static-ext:bandwidth? uint32 222 +--rw mpls-static-ext:lsp-priority-setup? uint8 223 +--rw mpls-static-ext:lsp-priority-hold? uint8 225 module: ietf-mpls-static-extended 226 augment /rt:routing/mpls:mpls: 227 +--rw bidir-static-lsps 228 +--rw bidir-static-lsp* [name] 229 +--rw name string 230 +--rw forward-lsp? mpls-static:static-lsp-ref 231 +--rw reverse-lsp? mpls-static:static-lsp-ref 233 Figure 2: MPLS Static LSP tree diagram 235 2.3. Model Overview 237 This document defines two YANG modules for MPLS Static LSP(s) 238 configuration and management: ietf-mpls-static.yang and ietf-mpls- 239 static-extended.yang. 241 The ietf-mpls-static module contains the following high-level types 242 and groupings: 244 static-lsp-ref: 246 A YANG reference type for a static LSP that can be used by data 247 models to reference a configured static LSP. 249 in-segment: 251 A YANG grouping that describes parameters of an incoming class of 252 FEC associated with a specific LSP as described in the MPLS 253 architecture document [RFC3031]. The model allows the following 254 types of traffic to be mapped onto the static LSP on an ingress 255 LER: 257 o Unlabeled traffic destined to a specific prefix 258 o Labeled traffic arriving with a specific label 260 out-segment: 262 A YANG grouping that describes parameters for the forwarding 263 path(s) and their associated attributes for an LSP. The model 264 allows for the following cases: 266 o single forwarding path or NHLFE 267 o multiple forwarding path(s) or NHLFE(s), each of which can 268 serve a primary, backup or both role(s). 270 The ietf-mpls-static-extended module contains the following high- 271 level types and groupings: 273 bidir-static-lsp: 275 A YANG grouping that describes list of static bidirectional LSPs 277 The ietf-mpls-static-extended augments the ietf-mpls-static model 278 with additional parameters to configure and manage: 280 o Bidirectional Static LSP(s) 282 o Defining Static LSP bandwidth allocation 283 o Defining Static LSP preemption priorities 285 2.4. Model YANG Module(s) 287 Configuring LSPs through an LSR/LER involves the following steps: 289 o Enabling MPLS on MPLS capable interfaces. 291 o Configuring in-segments and out-segments on LER(s) and LSR(s) 292 traversed by the LSP. 294 o Setting up the cross-connect per LSP to associate segments and/or 295 to indicate connection origination and termination. 297 o Optionally specifying label stack actions. 299 o Optionally specifying segment traffic parameters. 301 The objects covered by this model are derived from the Incoming Label 302 Map (ILM) and Next Hop Label Forwarding Entry (NHLFE) as specified in 303 the MPLS architecture document [RFC3031]. 305 The ietf-mpls-static module imports the followinig modules: 307 o ietf-inet-types defined in [RFC6991] 309 o ietf-routing defined in [RFC8349] 311 o ietf-routing-types defined in [RFC8294] 313 o ietf-interfaces defined in [RFC8343] 315 o ietf-mpls defined in [I-D.ietf-mpls-base-yang] 317 o ietf-te defined in [I-D.ietf-teas-yang-te] 319 The ietf-mpls-static module is shown below: 321 file "ietf-mpls-static@2019-09-12.yang" 322 module ietf-mpls-static { 323 yang-version 1.1; 324 namespace "urn:ietf:params:xml:ns:yang:ietf-mpls-static"; 325 prefix "mpls-static"; 327 import ietf-mpls { 328 prefix "mpls"; 329 reference "draft-ietf-mpls-base-yang: MPLS Base YANG Data Model"; 330 } 331 import ietf-routing { 332 prefix "rt"; 333 reference "RFC8349: A YANG Data Model for Routing Management"; 334 } 336 import ietf-routing-types { 337 prefix "rt-types"; 338 reference "RFC8294: Common YANG Data Types for the Routing Area"; 339 } 341 import ietf-inet-types { 342 prefix inet; 343 reference "RFC6991: Common YANG Data Types"; 344 } 346 import ietf-interfaces { 347 prefix "if"; 348 reference "RFC7223: A YANG Data Model for Interface Management"; 349 } 351 organization "IETF MPLS Working Group"; 353 contact 354 "WG Web: 356 WG List: 358 Editor: Tarek Saad 359 361 Editor: Rakesh Gandhi 362 364 Editor: Xufeng Liu 365 367 Editor: Vishnu Pavan Beeram 368 370 Editor: Igor Bryskin 371 "; 373 description 374 "This YANG module augments the 'ietf-routing' module with basic 375 configuration and operational state data for MPLS static 376 The model fully conforms to the Network Management Datastore 377 Architecture (NMDA). 379 Copyright (c) 2018 IETF Trust and the persons 380 identified as authors of the code. All rights reserved. 382 Redistribution and use in source and binary forms, with or 383 without modification, is permitted pursuant to, and subject 384 to the license terms contained in, the Simplified BSD License 385 set forth in Section 4.c of the IETF Trust's Legal Provisions 386 Relating to IETF Documents 387 (https://trustee.ietf.org/license-info). 388 This version of this YANG module is part of RFC XXXX; see 389 the RFC itself for full legal notices."; 391 // RFC Ed.: replace XXXX with actual RFC number and remove this 392 // note. 394 // RFC Ed.: update the date below with the date of RFC publication 395 // and remove this note. 397 revision "2019-09-12" { 398 description 399 "Latest revision of MPLS Static LSP YANG module"; 400 reference "RFC XXXX: A YANG Data Model for MPLS Static LSPs"; 401 } 403 typedef static-lsp-ref { 404 type leafref { 405 path "/rt:routing/mpls:mpls/mpls-static:static-lsps/" + 406 "mpls-static:static-lsp/mpls-static:name"; 407 } 408 description 409 "This type is used by data models that need to reference 410 configured static LSP."; 411 } 413 grouping in-segment { 414 description "In-segment grouping"; 415 container in-segment { 416 description "MPLS incoming segment"; 417 container fec { 418 description "Forwarding Equivalence Class grouping"; 419 choice type { 420 description "FEC type choices"; 421 case ip-prefix { 422 leaf ip-prefix { 423 type inet:ip-prefix; 424 description "An IP prefix"; 425 } 426 } 427 case mpls-label { 428 leaf incoming-label { 429 type rt-types:mpls-label; 430 description "label value on the incoming packet"; 431 } 432 } 433 } 434 leaf incoming-interface { 435 type if:interface-ref; 436 description 437 "Optional incoming interface if FEC is restricted 438 to traffic incoming on a specific interface"; 439 } 440 } 441 } 442 } 444 grouping out-segment { 445 description "Out-segment grouping"; 446 container out-segment { 447 description "MPLS outgoing segment"; 448 choice out-segment { 449 description "The MPLS out-segment type choice"; 450 case nhlfe-single { 451 container nhlfe-single { 452 description "Container for single NHLFE entry"; 453 uses mpls:nhlfe-single-contents; 454 leaf outgoing-interface { 455 type if:interface-ref; 456 description 457 "The outgoing interface"; 458 } 459 } 460 } 461 case nhlfe-multiple { 462 container nhlfe-multiple { 463 description "Container for multiple NHLFE entries"; 464 list nhlfe { 465 key index; 466 description "MPLS NHLFE entry"; 467 uses mpls:nhlfe-multiple-contents; 468 leaf outgoing-interface { 469 type if:interface-ref; 470 description 471 "The outgoing interface"; 472 } 473 } 474 } 476 } 477 } 478 } 479 } 481 augment "/rt:routing/mpls:mpls" { 482 description "Augmentations for MPLS Static LSPs"; 483 container static-lsps { 484 description 485 "Statically configured LSPs, without dynamic signaling"; 486 list static-lsp { 487 key name; 488 description "list of defined static LSPs"; 489 leaf name { 490 type string; 491 description "name to identify the LSP"; 492 } 493 leaf operation { 494 type mpls:mpls-operations-type; 495 description 496 "The MPLS operation to be executed on the incoming packet"; 497 } 498 uses in-segment; 499 uses out-segment; 500 } 501 } 502 } 503 } 504 506 The ietf-mpls-static-extended module imports the followinig modules: 508 o ietf-mpls defined in [I-D.ietf-mpls-base-yang] 510 o ietf-mpls-static defined in this document 512 o ietf-routing defined in [RFC8349] 514 The ietf-mpls-static-extended module is shown below: 516 file "ietf-mpls-static-extended@2019-09-12.yang" 517 module ietf-mpls-static-extended { 518 yang-version 1.1; 519 namespace "urn:ietf:params:xml:ns:yang:ietf-mpls-static-extended"; 520 prefix "mpls-static-ext"; 522 import ietf-mpls { 523 prefix "mpls"; 524 reference "draft-ietf-mpls-base-yang: MPLS Base YANG Data Model"; 525 } 527 import ietf-routing { 528 prefix "rt"; 529 reference "RFC8349: A YANG Data Model for Routing Management"; 530 } 532 import ietf-routing-types { 533 prefix "rt-types"; 534 reference "RFC8294: Common YANG Data Types for the Routing Area"; 535 } 537 import ietf-mpls-static { 538 prefix "mpls-static"; 539 reference "RFC XXXX: A YANG Data Model for MPLS Static LSPs"; 540 } 542 organization "IETF MPLS Working Group"; 544 contact 545 "WG Web: 547 WG List: 549 Editor: Tarek Saad 550 552 Editor: Rakesh Gandhi 553 555 Editor: Xufeng Liu 556 558 Editor: Vishnu Pavan Beeram 559 561 Editor: Igor Bryskin 562 "; 564 description 565 "This YANG module contains the Extended MPLS Static LSP YANG 566 data model. The model fully conforms to the Network Management 567 Datastore Architecture (NMDA). 569 Copyright (c) 2018 IETF Trust and the persons 570 identified as authors of the code. All rights reserved. 572 Redistribution and use in source and binary forms, with or 573 without modification, is permitted pursuant to, and subject 574 to the license terms contained in, the Simplified BSD License 575 set forth in Section 4.c of the IETF Trust's Legal Provisions 576 Relating to IETF Documents 577 (https://trustee.ietf.org/license-info). 578 This version of this YANG module is part of RFC XXXX; see 579 the RFC itself for full legal notices."; 581 // RFC Ed.: replace XXXX with actual RFC number and remove this 582 // note. 584 // RFC Ed.: update the date below with the date of RFC publication 585 // and remove this note. 587 revision "2019-09-12" { 588 description 589 "Latest revision of MPLS Static LSP Extended YANG module"; 590 reference "RFC XXXX: A YANG Data Model for MPLS Static LSPs"; 591 } 593 grouping bidir-static-lsp { 594 description 595 "grouping for top level list of static bidirectional LSPs"; 596 leaf forward-lsp { 597 type mpls-static:static-lsp-ref; 598 description 599 "Reference to a configured static forward LSP"; 600 } 601 leaf reverse-lsp { 602 type mpls-static:static-lsp-ref; 603 description 604 "Reference to a configured static reverse LSP"; 605 } 606 } 608 augment "/rt:routing/mpls:mpls/mpls-static:static-lsps" { 609 description 610 "Augmentation for static MPLS LSPs"; 612 leaf bandwidth { 613 type rt-types:bandwidth-ieee-float32; 614 units "Bytes per second"; 615 description 616 "Bandwidth using offline calculation"; 617 } 618 leaf lsp-priority-setup { 619 type uint8 { 620 range "0..7"; 621 } 622 description "LSP setup priority"; 623 } 624 leaf lsp-priority-hold { 625 type uint8 { 626 range "0..7"; 627 } 628 description "LSP hold priority"; 629 } 630 } 632 augment "/rt:routing/mpls:mpls" { 633 description "Augmentations for MPLS Static LSPs"; 634 container bidir-static-lsps { 635 description 636 "Statically configured bidirectional LSPs"; 637 list bidir-static-lsp { 638 key name; 639 description "List of static bidirectional LSPs"; 641 leaf name { 642 type string; 643 description "Name that identifies the bidirectional LSP"; 644 } 645 uses bidir-static-lsp; 646 } 647 } 648 } 649 } 650 652 3. IANA Considerations 654 This document registers the following URIs in the IETF XML registry 655 [RFC3688]. Following the format in [RFC3688], the following 656 registration is requested to be made. 658 URI: urn:ietf:params:xml:ns:yang:ietf-mpls-static 659 Registrant Contact: The MPLS WG of the IETF. 660 XML: N/A, the requested URI is an XML namespace. 662 URI: urn:ietf:params:xml:ns:yang:ietf-mpls-static-extended 663 Registrant Contact: The MPLS WG of the IETF. 664 XML: N/A, the requested URI is an XML namespace. 666 This document registers two YANG modules in the YANG Module Names 667 registry [RFC6020]. 669 name: ietf-mpls-static 670 namespace: urn:ietf:params:xml:ns:yang:ietf-mpls-static 671 prefix: ietf-mpls-static 672 // RFC Ed.: replace XXXX with RFC number and remove this note 673 reference: RFCXXXX 675 name: ietf-mpls-static-extended 676 namespace: urn:ietf:params:xml:ns:yang:ietf-mpls-static-extended 677 prefix: ietf-mpls-static-extended 678 // RFC Ed.: replace XXXX with RFC number and remove this note 679 reference: RFCXXXX 681 4. Security Considerations 683 The YANG modules specified in this document define schemas for data 684 that is designed to be accessed via network management protocols such 685 as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF layer 686 is the secure transport layer, and the mandatory-to-implement secure 687 transport is Secure Shell (SSH) [RFC6242]. The lowest RESTCONF layer 688 is HTTPS, and the mandatory-to-implement secure transport is TLS 689 {!RFC8446}}. 691 The NETCONF access control model [RFC8341] provides the means to 692 restrict access for particular NETCONF or RESTCONF users to a 693 preconfigured subset of all available NETCONF or RESTCONF protocol 694 operations and content. 696 All nodes defined in this YANG module that are writable/creatable/ 697 deletable (i.e., config true, which is the default) may be considered 698 sensitive or vulnerable in some network environments. Write 699 operations (e.g., edit-config) to these data nodes without proper 700 protection can have a negative effect on network operations. These 701 are the subtrees and data nodes and their sensitivity/vulnerability: 703 o /ietf-routing:routing/ietf-mpls:mpls:/ietf-mpls:static-lsps: This 704 entire subtree is related to security. 706 An administrator needs to restrict write access to all configurable 707 objects within this data model. 709 5. Contributors 710 Himanshu Shah 711 Ciena 712 email: hshah@ciena.com 714 Kamran Raza 715 Cisco Systems, Inc. 716 email: skraza@cisco.com 718 6. References 720 6.1. Normative References 722 [I-D.ietf-mpls-base-yang] 723 Saad, T., Raza, K., Gandhi, R., Liu, X., and V. Beeram, "A 724 YANG Data Model for MPLS Base", draft-ietf-mpls-base- 725 yang-14 (work in progress), March 2020. 727 [I-D.ietf-teas-yang-te] 728 Saad, T., Gandhi, R., Liu, X., Beeram, V., and I. Bryskin, 729 "A YANG Data Model for Traffic Engineering Tunnels and 730 Interfaces", draft-ietf-teas-yang-te-23 (work in 731 progress), March 2020. 733 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 734 Requirement Levels", BCP 14, RFC 2119, 735 DOI 10.17487/RFC2119, March 1997, 736 . 738 [RFC3031] Rosen, E., Viswanathan, A., and R. Callon, "Multiprotocol 739 Label Switching Architecture", RFC 3031, 740 DOI 10.17487/RFC3031, January 2001, 741 . 743 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 744 DOI 10.17487/RFC3688, January 2004, 745 . 747 [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for 748 the Network Configuration Protocol (NETCONF)", RFC 6020, 749 DOI 10.17487/RFC6020, October 2010, 750 . 752 [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., 753 and A. Bierman, Ed., "Network Configuration Protocol 754 (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, 755 . 757 [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure 758 Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011, 759 . 761 [RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types", 762 RFC 6991, DOI 10.17487/RFC6991, July 2013, 763 . 765 [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", 766 RFC 7950, DOI 10.17487/RFC7950, August 2016, 767 . 769 [RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF 770 Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017, 771 . 773 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 774 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 775 May 2017, . 777 [RFC8294] Liu, X., Qu, Y., Lindem, A., Hopps, C., and L. Berger, 778 "Common YANG Data Types for the Routing Area", RFC 8294, 779 DOI 10.17487/RFC8294, December 2017, 780 . 782 [RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration 783 Access Control Model", STD 91, RFC 8341, 784 DOI 10.17487/RFC8341, March 2018, 785 . 787 [RFC8343] Bjorklund, M., "A YANG Data Model for Interface 788 Management", RFC 8343, DOI 10.17487/RFC8343, March 2018, 789 . 791 [RFC8349] Lhotka, L., Lindem, A., and Y. Qu, "A YANG Data Model for 792 Routing Management (NMDA Version)", RFC 8349, 793 DOI 10.17487/RFC8349, March 2018, 794 . 796 6.2. Informative References 798 [RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams", 799 BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018, 800 . 802 Authors' Addresses 804 Tarek Saad 805 Juniper Networks 807 Email: tsaad.net@gmail.com 809 Rakesh Gandhi 810 Cisco Systems, Inc. 812 Email: rgandhi@cisco.com 814 Xufeng Liu 815 Volta Networks 817 Email: xufeng.liu.ietf@gmail.com 819 Vishnu Pavan Beeram 820 Juniper Networks 822 Email: vbeeram@juniper.net 824 Igor Bryskin 825 Huawei Technologies 827 Email: Igor.Bryskin@huawei.com