idnits 2.17.1 draft-ietf-mpls-static-yang-08.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 (March 02, 2019) is 1882 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-10 == Outdated reference: A later version (-36) exists of draft-ietf-teas-yang-te-19 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: September 3, 2019 Cisco Systems, Inc. 6 X. Liu 7 Volta Networks 8 V. Beeram 9 Juniper Networks 10 I. Bryskin 11 Huawei Technologies 12 March 02, 2019 14 A YANG Data Model for MPLS Static LSPs 15 draft-ietf-mpls-static-yang-08 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 http://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 September 3, 2019. 44 Copyright Notice 46 Copyright (c) 2019 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 (http://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 . . . . . . . . . . . . . . . . . . . . . 15 70 4. Security Considerations . . . . . . . . . . . . . . . . . . . 15 71 5. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 16 72 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 16 73 6.1. Normative References . . . . . . . . . . . . . . . . . . 16 74 6.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 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 259 o Traffic carried on a TE tunnel whose LSP is 260 statically created via this model. 262 out-segment: 264 A YANG grouping that describes parameters for the forwarding 265 path(s) and their associated attributes for an LSP. The model 266 allows for the following cases: 268 o single forwarding path or NHLFE 269 o multiple forwarding path(s) or NHLFE(s), each of which can 270 serve a primary, backup or both role(s). 272 The ietf-mpls-static-extended module contains the following high- 273 level types and groupings: 275 bidir-static-lsp: 277 A YANG grouping that describes list of static bidirectional LSPs 279 The ietf-mpls-static-extended augments the ietf-mpls-static model 280 with additional parameters to configure and manage: 282 o Bidirectional Static LSP(s) 283 o Defining Static LSP bandwidth allocation 285 o Defining Static LSP preemption priorities 287 2.4. Model YANG Module(s) 289 Configuring LSPs through an LSR/LER involves the following steps: 291 o Enabling MPLS on MPLS capable interfaces. 293 o Configuring in-segments and out-segments on LER(s) and LSR(s) 294 traversed by the LSP. 296 o Setting up the cross-connect per LSP to associate segments and/or 297 to indicate connection origination and termination. 299 o Optionally specifying label stack actions. 301 o Optionally specifying segment traffic parameters. 303 The objects covered by this model are derived from the Incoming Label 304 Map (ILM) and Next Hop Label Forwarding Entry (NHLFE) as specified in 305 the MPLS architecture document [RFC3031]. 307 The ietf-mpls-static module imports the followinig modules: 309 o ietf-inet-types defined in [RFC6991] 311 o ietf-routing defined in [RFC8349] 313 o ietf-routing-types defined in [RFC8294] 315 o ietf-interfaces defined in [RFC8343] 317 o ietf-mpls defined in [I-D.ietf-mpls-base-yang] 319 o ietf-te defined in [I-D.ietf-teas-yang-te] 321 The ietf-mpls-static module is shown below: 323 file "ietf-mpls-static@2019-02-24.yang" 324 module ietf-mpls-static { 325 yang-version 1.1; 326 namespace "urn:ietf:params:xml:ns:yang:ietf-mpls-static"; 328 prefix "mpls-static"; 330 import ietf-mpls { 331 prefix "mpls"; 332 reference "draft-ietf-mpls-base-yang: MPLS Base YANG Data Model"; 333 } 335 import ietf-routing { 336 prefix "rt"; 337 reference "RFC8349: A YANG Data Model for Routing Management"; 338 } 340 import ietf-routing-types { 341 prefix "rt-types"; 342 reference "RFC8294: Common YANG Data Types"; 343 } 345 import ietf-inet-types { 346 prefix inet; 347 reference "RFC6991: Common YANG Data Types"; 348 } 350 import ietf-interfaces { 351 prefix "if"; 352 reference "RFC7223: A YANG Data Model for Interface Management"; 353 } 355 organization "IETF MPLS Working Group"; 357 contact 358 "WG Web: 360 WG List: 362 WG Chair: Loa Andersson 363 365 WG Chair: Nic Leymann 366 368 Editor: Tarek Saad 369 371 Editor: Kamran Raza 372 374 Editor: Rakesh Gandhi 375 377 Editor: Xufeng Liu 378 380 Editor: Vishnu Pavan Beeram 381 383 Editor: Himanshu Shah 384 386 Editor: Igor Bryskin 387 "; 389 description 390 "This YANG module augments the 'ietf-routing' module with basic 391 configuration and operational state data for MPLS static 392 The model fully conforms to the Network Management Datastore 393 Architecture (NMDA). 395 Copyright (c) 2018 IETF Trust and the persons 396 identified as authors of the code. All rights reserved. 398 Redistribution and use in source and binary forms, with or 399 without modification, is permitted pursuant to, and subject 400 to the license terms contained in, the Simplified BSD License 401 set forth in Section 4.c of the IETF Trust's Legal Provisions 402 Relating to IETF Documents 403 (https://trustee.ietf.org/license-info). 404 This version of this YANG module is part of RFC XXXX; see 405 the RFC itself for full legal notices."; 407 // RFC Ed.: replace XXXX with actual RFC number and remove this 408 // note. 410 // RFC Ed.: update the date below with the date of RFC publication 411 // and remove this note. 413 revision "2019-02-24" { 414 description 415 "Latest revision of MPLS Static LSP YANG module"; 416 reference "RFC XXXX: A YANG Data Model for MPLS Static LSPs"; 417 } 419 typedef static-lsp-ref { 420 type leafref { 421 path "/rt:routing/mpls:mpls/mpls-static:static-lsps/" + 422 "mpls-static:static-lsp/mpls-static:name"; 423 } 424 description 425 "This type is used by data models that need to reference 426 configured static LSP."; 427 } 428 grouping in-segment { 429 description "In-segment grouping"; 430 container in-segment { 431 description "MPLS incoming segment"; 432 container fec { 433 description "Forwarding Equivalence Class grouping"; 434 choice type { 435 description "FEC type choices"; 436 case ip-prefix { 437 leaf ip-prefix { 438 type inet:ip-prefix; 439 description "An IP prefix"; 440 } 441 } 442 case mpls-label { 443 leaf incoming-label { 444 type rt-types:mpls-label; 445 description "label value on the incoming packet"; 446 } 447 } 448 } 449 leaf incoming-interface { 450 type if:interface-ref; 451 description 452 "Optional incoming interface if FEC is restricted 453 to traffic incoming on a specific interface"; 454 } 455 } 456 } 457 } 459 grouping out-segment { 460 description "Out-segment grouping"; 461 container out-segment { 462 description "MPLS outgoing segment"; 463 choice out-segment { 464 description "The MPLS out-segment type choice"; 465 case nhlfe-single { 466 container nhlfe-single { 467 description "Container for single NHLFE entry"; 468 uses mpls:nhlfe-single-contents; 469 leaf outgoing-interface { 470 type if:interface-ref; 471 description 472 "The outgoing interface"; 473 } 474 } 475 } 476 case nhlfe-multiple { 477 container nhlfe-multiple { 478 description "Container for multiple NHLFE entries"; 479 list nhlfe { 480 key index; 481 description "MPLS NHLFE entry"; 482 uses mpls:nhlfe-multiple-contents; 483 leaf outgoing-interface { 484 type if:interface-ref; 485 description 486 "The outgoing interface"; 487 } 488 } 489 } 490 } 491 } 492 } 493 } 495 augment "/rt:routing/mpls:mpls" { 496 description "Augmentations for MPLS Static LSPs"; 497 container static-lsps { 498 description 499 "Statically configured LSPs, without dynamic signaling"; 500 list static-lsp { 501 key name; 502 description "list of defined static LSPs"; 503 leaf name { 504 type string; 505 description "name to identify the LSP"; 506 } 507 leaf operation { 508 type mpls:mpls-operations-type; 509 description 510 "The MPLS operation to be executed on the incoming packet"; 511 } 512 uses in-segment; 513 uses out-segment; 514 } 515 } 516 } 517 } 518 520 The ietf-mpls-static-extended module imports the followinig modules: 522 o ietf-mpls defined in [I-D.ietf-mpls-base-yang] 523 o ietf-mpls-static defined in this document 525 o ietf-routing defined in [RFC8349] 527 The ietf-mpls-static-extended module is shown below: 529 file "ietf-mpls-static-extended@2019-02-24.yang" 530 module ietf-mpls-static-extended { 531 yang-version 1.1; 532 namespace "urn:ietf:params:xml:ns:yang:ietf-mpls-static-extended"; 534 prefix "mpls-static-ext"; 536 import ietf-mpls { 537 prefix "mpls"; 538 reference "draft-ietf-mpls-base-yang: MPLS Base YANG Data Model"; 539 } 541 import ietf-routing { 542 prefix "rt"; 543 reference "RFC6991: Common YANG Data Types"; 544 } 546 import ietf-mpls-static { 547 prefix "mpls-static"; 548 reference "draft-ietf-mpls-static-yang: A YANG Data Model for MPLS 549 Static LSPs"; 550 } 552 organization "IETF MPLS Working Group"; 554 contact 555 "WG Web: 557 WG List: 559 WG Chair: Loa Andersson 560 562 WG Chair: Nic Leymann 563 565 Editor: Tarek Saad 566 568 Editor: Kamran Raza 569 571 Editor: Rakesh Gandhi 572 574 Editor: Xufeng Liu 575 577 Editor: Vishnu Pavan Beeram 578 580 Editor: Himanshu Shah 581 583 Editor: Igor Bryskin 584 "; 586 description 587 "This YANG module contains the Extended MPLS Static LSP YANG 588 data model. The model fully conforms to the Network Management 589 Datastore Architecture (NMDA). 591 Copyright (c) 2018 IETF Trust and the persons 592 identified as authors of the code. All rights reserved. 594 Redistribution and use in source and binary forms, with or 595 without modification, is permitted pursuant to, and subject 596 to the license terms contained in, the Simplified BSD License 597 set forth in Section 4.c of the IETF Trust's Legal Provisions 598 Relating to IETF Documents 599 (https://trustee.ietf.org/license-info). 600 This version of this YANG module is part of RFC XXXX; see 601 the RFC itself for full legal notices."; 603 // RFC Ed.: replace XXXX with actual RFC number and remove this 604 // note. 606 // RFC Ed.: update the date below with the date of RFC publication 607 // and remove this note. 609 revision "2019-02-24" { 610 description 611 "Latest revision of MPLS Static LSP Extended YANG module"; 612 reference "RFC XXXX: Extended YANG Data Model for MPLS Static LSPs"; 613 } 615 grouping bidir-static-lsp { 616 description 617 "grouping for top level list of static bidirectional LSPs"; 618 leaf forward-lsp { 619 type mpls-static:static-lsp-ref; 620 description 621 "Reference to a configured static forward LSP"; 622 } 623 leaf reverse-lsp { 624 type mpls-static:static-lsp-ref; 625 description 626 "Reference to a configured static reverse LSP"; 627 } 628 } 630 augment "/rt:routing/mpls:mpls/mpls-static:static-lsps" { 631 description 632 "Augmentation for static MPLS LSPs"; 634 leaf bandwidth { 635 type uint32; 636 units mbps; 637 description 638 "Bandwidth in Mbps, e.g., using offline calculation"; 639 } 640 leaf lsp-priority-setup { 641 type uint8 { 642 range "0..7"; 643 } 644 description "LSP setup priority"; 645 } 646 leaf lsp-priority-hold { 647 type uint8 { 648 range "0..7"; 649 } 650 description "LSP hold priority"; 651 } 652 } 654 augment "/rt:routing/mpls:mpls" { 655 description "Augmentations for MPLS Static LSPs"; 656 container bidir-static-lsps { 657 description 658 "Statically configured bidirectional LSPs"; 659 list bidir-static-lsp { 660 key name; 661 description "List of static bidirectional LSPs"; 663 leaf name { 664 type string; 665 description "Name that identifies the bidirectional LSP"; 666 } 667 uses bidir-static-lsp; 668 } 669 } 670 } 671 } 672 674 3. IANA Considerations 676 This document registers the following URIs in the IETF XML registry 677 [RFC3688]. Following the format in [RFC3688], the following 678 registration is requested to be made. 680 URI: urn:ietf:params:xml:ns:yang:ietf-mpls-static 681 Registrant Contact: The MPLS WG of the IETF. 682 XML: N/A, the requested URI is an XML namespace. 684 URI: urn:ietf:params:xml:ns:yang:ietf-mpls-static-extended 685 Registrant Contact: The MPLS WG of the IETF. 686 XML: N/A, the requested URI is an XML namespace. 688 This document registers two YANG modules in the YANG Module Names 689 registry [RFC6020]. 691 name: ietf-mpls-static 692 namespace: urn:ietf:params:xml:ns:yang:ietf-mpls-static 693 prefix: ietf-mpls-static 694 // RFC Ed.: replace XXXX with RFC number and remove this note 695 reference: RFCXXXX 697 name: ietf-mpls-static-extended 698 namespace: urn:ietf:params:xml:ns:yang:ietf-mpls-static-extended 699 prefix: ietf-mpls-static-extended 700 // RFC Ed.: replace XXXX with RFC number and remove this note 701 reference: RFCXXXX 703 4. Security Considerations 705 The YANG modules specified in this document define schemas for data 706 that is designed to be accessed via network management protocols such 707 as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF layer 708 is the secure transport layer, and the mandatory-to-implement secure 709 transport is Secure Shell (SSH) [RFC6242]. The lowest RESTCONF layer 710 is HTTPS, and the mandatory-to-implement secure transport is TLS 711 {!RFC8446}}. 713 The NETCONF access control model [RFC8341] provides the means to 714 restrict access for particular NETCONF or RESTCONF users to a 715 preconfigured subset of all available NETCONF or RESTCONF protocol 716 operations and content. 718 All nodes defined in this YANG module that are writable/creatable/ 719 deletable (i.e., config true, which is the default) may be considered 720 sensitive or vulnerable in some network environments. Write 721 operations (e.g., edit-config) to these data nodes without proper 722 protection can have a negative effect on network operations. These 723 are the subtrees and data nodes and their sensitivity/vulnerability: 725 o /ietf-routing:routing/ietf-mpls:mpls:/ietf-mpls:static-lsps: This 726 entire subtree is related to security. 728 An administrator needs to restrict write access to all configurable 729 objects within this data model. 731 5. Contributors 733 Himanshu Shah 734 Ciena 735 email: hshah@ciena.com 737 Kamran Raza 738 Cisco Systems, Inc. 739 email: skraza@cisco.com 741 6. References 743 6.1. Normative References 745 [I-D.ietf-mpls-base-yang] 746 Saad, T., Raza, K., Gandhi, R., Liu, X., and V. Beeram, "A 747 YANG Data Model for MPLS Base", draft-ietf-mpls-base- 748 yang-10 (work in progress), February 2019. 750 [I-D.ietf-teas-yang-te] 751 Saad, T., Gandhi, R., Liu, X., Beeram, V., and I. Bryskin, 752 "A YANG Data Model for Traffic Engineering Tunnels and 753 Interfaces", draft-ietf-teas-yang-te-19 (work in 754 progress), February 2019. 756 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 757 Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/ 758 RFC2119, March 1997, . 761 [RFC3031] Rosen, E., Viswanathan, A., and R. Callon, "Multiprotocol 762 Label Switching Architecture", RFC 3031, DOI 10.17487/ 763 RFC3031, January 2001, . 766 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 767 DOI 10.17487/RFC3688, January 2004, . 770 [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for 771 the Network Configuration Protocol (NETCONF)", RFC 6020, 772 DOI 10.17487/RFC6020, October 2010, . 775 [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., 776 and A. Bierman, Ed., "Network Configuration Protocol 777 (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, 778 . 780 [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure 781 Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011, 782 . 784 [RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types", RFC 785 6991, DOI 10.17487/RFC6991, July 2013, . 788 [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", 789 RFC 7950, DOI 10.17487/RFC7950, August 2016, 790 . 792 [RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF 793 Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017, 794 . 796 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 797 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 798 May 2017, . 800 [RFC8294] Liu, X., Qu, Y., Lindem, A., Hopps, C., and L. Berger, 801 "Common YANG Data Types for the Routing Area", RFC 8294, 802 DOI 10.17487/RFC8294, December 2017, . 805 [RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration 806 Access Control Model", STD 91, RFC 8341, DOI 10.17487/ 807 RFC8341, March 2018, . 810 [RFC8343] Bjorklund, M., "A YANG Data Model for Interface 811 Management", RFC 8343, DOI 10.17487/RFC8343, March 2018, 812 . 814 [RFC8349] Lhotka, L., Lindem, A., and Y. Qu, "A YANG Data Model for 815 Routing Management (NMDA Version)", RFC 8349, DOI 816 10.17487/RFC8349, March 2018, . 819 6.2. Informative References 821 [RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams", 822 BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018, 823 . 825 Authors' Addresses 827 Tarek Saad 828 Juniper Networks 830 Email: tsaad.net@gmail.com 832 Rakesh Gandhi 833 Cisco Systems, Inc. 835 Email: rgandhi@cisco.com 837 Xufeng Liu 838 Volta Networks 840 Email: xufeng.liu.ietf@gmail.com 842 Vishnu Pavan Beeram 843 Juniper Networks 845 Email: vbeeram@juniper.net 847 Igor Bryskin 848 Huawei Technologies 850 Email: Igor.Bryskin@huawei.com