idnits 2.17.1 draft-ietf-mpls-static-yang-09.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 08, 2019) is 1877 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 9, 2019 Cisco Systems, Inc. 6 X. Liu 7 Volta Networks 8 V. Beeram 9 Juniper Networks 10 I. Bryskin 11 Huawei Technologies 12 March 08, 2019 14 A YANG Data Model for MPLS Static LSPs 15 draft-ietf-mpls-static-yang-09 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 September 9, 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 (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 . . . . . . . . . . . . . . . . . . . . . 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-03-08.yang" 324 module ietf-mpls-static { 325 yang-version 1.1; 326 namespace "urn:ietf:params:xml:ns:yang:ietf-mpls-static"; 327 prefix "mpls-static"; 329 import ietf-mpls { 330 prefix "mpls"; 331 reference "draft-ietf-mpls-base-yang: MPLS Base YANG Data Model"; 332 } 334 import ietf-routing { 335 prefix "rt"; 336 reference "RFC8349: A YANG Data Model for Routing Management"; 337 } 339 import ietf-routing-types { 340 prefix "rt-types"; 341 reference "RFC8294: Common YANG Data Types for the Routing Area"; 342 } 344 import ietf-inet-types { 345 prefix inet; 346 reference "RFC6991: Common YANG Data Types"; 347 } 349 import ietf-interfaces { 350 prefix "if"; 351 reference "RFC7223: A YANG Data Model for Interface Management"; 352 } 354 organization "IETF MPLS Working Group"; 356 contact 357 "WG Web: 359 WG List: 361 WG Chair: Loa Andersson 362 364 WG Chair: Nic Leymann 365 367 Editor: Tarek Saad 368 370 Editor: Kamran Raza 371 373 Editor: Rakesh Gandhi 374 376 Editor: Xufeng Liu 377 379 Editor: Vishnu Pavan Beeram 380 382 Editor: Himanshu Shah 383 385 Editor: Igor Bryskin 386 "; 388 description 389 "This YANG module augments the 'ietf-routing' module with basic 390 configuration and operational state data for MPLS static 391 The model fully conforms to the Network Management Datastore 392 Architecture (NMDA). 394 Copyright (c) 2018 IETF Trust and the persons 395 identified as authors of the code. All rights reserved. 397 Redistribution and use in source and binary forms, with or 398 without modification, is permitted pursuant to, and subject 399 to the license terms contained in, the Simplified BSD License 400 set forth in Section 4.c of the IETF Trust's Legal Provisions 401 Relating to IETF Documents 402 (https://trustee.ietf.org/license-info). 403 This version of this YANG module is part of RFC XXXX; see 404 the RFC itself for full legal notices."; 406 // RFC Ed.: replace XXXX with actual RFC number and remove this 407 // note. 409 // RFC Ed.: update the date below with the date of RFC publication 410 // and remove this note. 412 revision "2019-03-08" { 413 description 414 "Latest revision of MPLS Static LSP YANG module"; 415 reference "RFC XXXX: A YANG Data Model for MPLS Static LSPs"; 416 } 418 typedef static-lsp-ref { 419 type leafref { 420 path "/rt:routing/mpls:mpls/mpls-static:static-lsps/" + 421 "mpls-static:static-lsp/mpls-static:name"; 422 } 423 description 424 "This type is used by data models that need to reference 425 configured static LSP."; 426 } 427 grouping in-segment { 428 description "In-segment grouping"; 429 container in-segment { 430 description "MPLS incoming segment"; 431 container fec { 432 description "Forwarding Equivalence Class grouping"; 433 choice type { 434 description "FEC type choices"; 435 case ip-prefix { 436 leaf ip-prefix { 437 type inet:ip-prefix; 438 description "An IP prefix"; 439 } 440 } 441 case mpls-label { 442 leaf incoming-label { 443 type rt-types:mpls-label; 444 description "label value on the incoming packet"; 445 } 446 } 447 } 448 leaf incoming-interface { 449 type if:interface-ref; 450 description 451 "Optional incoming interface if FEC is restricted 452 to traffic incoming on a specific interface"; 453 } 454 } 455 } 456 } 458 grouping out-segment { 459 description "Out-segment grouping"; 460 container out-segment { 461 description "MPLS outgoing segment"; 462 choice out-segment { 463 description "The MPLS out-segment type choice"; 464 case nhlfe-single { 465 container nhlfe-single { 466 description "Container for single NHLFE entry"; 467 uses mpls:nhlfe-single-contents; 468 leaf outgoing-interface { 469 type if:interface-ref; 470 description 471 "The outgoing interface"; 472 } 473 } 474 } 475 case nhlfe-multiple { 476 container nhlfe-multiple { 477 description "Container for multiple NHLFE entries"; 478 list nhlfe { 479 key index; 480 description "MPLS NHLFE entry"; 481 uses mpls:nhlfe-multiple-contents; 482 leaf outgoing-interface { 483 type if:interface-ref; 484 description 485 "The outgoing interface"; 486 } 487 } 488 } 489 } 490 } 491 } 492 } 494 augment "/rt:routing/mpls:mpls" { 495 description "Augmentations for MPLS Static LSPs"; 496 container static-lsps { 497 description 498 "Statically configured LSPs, without dynamic signaling"; 499 list static-lsp { 500 key name; 501 description "list of defined static LSPs"; 502 leaf name { 503 type string; 504 description "name to identify the LSP"; 505 } 506 leaf operation { 507 type mpls:mpls-operations-type; 508 description 509 "The MPLS operation to be executed on the incoming packet"; 510 } 511 uses in-segment; 512 uses out-segment; 513 } 514 } 515 } 516 } 517 519 The ietf-mpls-static-extended module imports the followinig modules: 521 o ietf-mpls defined in [I-D.ietf-mpls-base-yang] 522 o ietf-mpls-static defined in this document 524 o ietf-routing defined in [RFC8349] 526 The ietf-mpls-static-extended module is shown below: 528 file "ietf-mpls-static-extended@2019-03-08.yang" 529 module ietf-mpls-static-extended { 530 yang-version 1.1; 531 namespace "urn:ietf:params:xml:ns:yang:ietf-mpls-static-extended"; 532 prefix "mpls-static-ext"; 534 import ietf-mpls { 535 prefix "mpls"; 536 reference "draft-ietf-mpls-base-yang: MPLS Base YANG Data Model"; 537 } 539 import ietf-routing { 540 prefix "rt"; 541 reference "RFC8349: A YANG Data Model for Routing Management"; 542 } 544 import ietf-mpls-static { 545 prefix "mpls-static"; 546 reference "RFC XXXX: A YANG Data Model for MPLS Static LSPs"; 547 } 549 organization "IETF MPLS Working Group"; 551 contact 552 "WG Web: 554 WG List: 556 WG Chair: Loa Andersson 557 559 WG Chair: Nic Leymann 560 562 Editor: Tarek Saad 563 565 Editor: Kamran Raza 566 568 Editor: Rakesh Gandhi 569 571 Editor: Xufeng Liu 572 574 Editor: Vishnu Pavan Beeram 575 577 Editor: Himanshu Shah 578 580 Editor: Igor Bryskin 581 "; 583 description 584 "This YANG module contains the Extended MPLS Static LSP YANG 585 data model. The model fully conforms to the Network Management 586 Datastore Architecture (NMDA). 588 Copyright (c) 2018 IETF Trust and the persons 589 identified as authors of the code. All rights reserved. 591 Redistribution and use in source and binary forms, with or 592 without modification, is permitted pursuant to, and subject 593 to the license terms contained in, the Simplified BSD License 594 set forth in Section 4.c of the IETF Trust's Legal Provisions 595 Relating to IETF Documents 596 (https://trustee.ietf.org/license-info). 597 This version of this YANG module is part of RFC XXXX; see 598 the RFC itself for full legal notices."; 600 // RFC Ed.: replace XXXX with actual RFC number and remove this 601 // note. 603 // RFC Ed.: update the date below with the date of RFC publication 604 // and remove this note. 606 revision "2019-03-08" { 607 description 608 "Latest revision of MPLS Static LSP Extended YANG module"; 609 reference "RFC XXXX: A YANG Data Model for MPLS Static LSPs"; 610 } 612 grouping bidir-static-lsp { 613 description 614 "grouping for top level list of static bidirectional LSPs"; 615 leaf forward-lsp { 616 type mpls-static:static-lsp-ref; 617 description 618 "Reference to a configured static forward LSP"; 620 } 621 leaf reverse-lsp { 622 type mpls-static:static-lsp-ref; 623 description 624 "Reference to a configured static reverse LSP"; 625 } 626 } 628 augment "/rt:routing/mpls:mpls/mpls-static:static-lsps" { 629 description 630 "Augmentation for static MPLS LSPs"; 632 leaf bandwidth { 633 type uint32; 634 units "Mbps"; 635 description 636 "Bandwidth in Mbps, e.g., using offline calculation"; 637 } 638 leaf lsp-priority-setup { 639 type uint8 { 640 range "0..7"; 641 } 642 description "LSP setup priority"; 643 } 644 leaf lsp-priority-hold { 645 type uint8 { 646 range "0..7"; 647 } 648 description "LSP hold priority"; 649 } 650 } 652 augment "/rt:routing/mpls:mpls" { 653 description "Augmentations for MPLS Static LSPs"; 654 container bidir-static-lsps { 655 description 656 "Statically configured bidirectional LSPs"; 657 list bidir-static-lsp { 658 key name; 659 description "List of static bidirectional LSPs"; 661 leaf name { 662 type string; 663 description "Name that identifies the bidirectional LSP"; 664 } 665 uses bidir-static-lsp; 666 } 667 } 669 } 670 } 671 673 3. IANA Considerations 675 This document registers the following URIs in the IETF XML registry 676 [RFC3688]. Following the format in [RFC3688], the following 677 registration is requested to be made. 679 URI: urn:ietf:params:xml:ns:yang:ietf-mpls-static 680 Registrant Contact: The MPLS WG of the IETF. 681 XML: N/A, the requested URI is an XML namespace. 683 URI: urn:ietf:params:xml:ns:yang:ietf-mpls-static-extended 684 Registrant Contact: The MPLS WG of the IETF. 685 XML: N/A, the requested URI is an XML namespace. 687 This document registers two YANG modules in the YANG Module Names 688 registry [RFC6020]. 690 name: ietf-mpls-static 691 namespace: urn:ietf:params:xml:ns:yang:ietf-mpls-static 692 prefix: ietf-mpls-static 693 // RFC Ed.: replace XXXX with RFC number and remove this note 694 reference: RFCXXXX 696 name: ietf-mpls-static-extended 697 namespace: urn:ietf:params:xml:ns:yang:ietf-mpls-static-extended 698 prefix: ietf-mpls-static-extended 699 // RFC Ed.: replace XXXX with RFC number and remove this note 700 reference: RFCXXXX 702 4. Security Considerations 704 The YANG modules specified in this document define schemas for data 705 that is designed to be accessed via network management protocols such 706 as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF layer 707 is the secure transport layer, and the mandatory-to-implement secure 708 transport is Secure Shell (SSH) [RFC6242]. The lowest RESTCONF layer 709 is HTTPS, and the mandatory-to-implement secure transport is TLS 710 {!RFC8446}}. 712 The NETCONF access control model [RFC8341] provides the means to 713 restrict access for particular NETCONF or RESTCONF users to a 714 preconfigured subset of all available NETCONF or RESTCONF protocol 715 operations and content. 717 All nodes defined in this YANG module that are writable/creatable/ 718 deletable (i.e., config true, which is the default) may be considered 719 sensitive or vulnerable in some network environments. Write 720 operations (e.g., edit-config) to these data nodes without proper 721 protection can have a negative effect on network operations. These 722 are the subtrees and data nodes and their sensitivity/vulnerability: 724 o /ietf-routing:routing/ietf-mpls:mpls:/ietf-mpls:static-lsps: This 725 entire subtree is related to security. 727 An administrator needs to restrict write access to all configurable 728 objects within this data model. 730 5. Contributors 732 Himanshu Shah 733 Ciena 734 email: hshah@ciena.com 736 Kamran Raza 737 Cisco Systems, Inc. 738 email: skraza@cisco.com 740 6. References 742 6.1. Normative References 744 [I-D.ietf-mpls-base-yang] 745 Saad, T., Raza, K., Gandhi, R., Liu, X., and V. Beeram, "A 746 YANG Data Model for MPLS Base", draft-ietf-mpls-base- 747 yang-10 (work in progress), February 2019. 749 [I-D.ietf-teas-yang-te] 750 Saad, T., Gandhi, R., Liu, X., Beeram, V., and I. Bryskin, 751 "A YANG Data Model for Traffic Engineering Tunnels and 752 Interfaces", draft-ietf-teas-yang-te-19 (work in 753 progress), February 2019. 755 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 756 Requirement Levels", BCP 14, RFC 2119, 757 DOI 10.17487/RFC2119, March 1997, 758 . 760 [RFC3031] Rosen, E., Viswanathan, A., and R. Callon, "Multiprotocol 761 Label Switching Architecture", RFC 3031, 762 DOI 10.17487/RFC3031, January 2001, 763 . 765 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 766 DOI 10.17487/RFC3688, January 2004, 767 . 769 [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for 770 the Network Configuration Protocol (NETCONF)", RFC 6020, 771 DOI 10.17487/RFC6020, October 2010, 772 . 774 [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., 775 and A. Bierman, Ed., "Network Configuration Protocol 776 (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, 777 . 779 [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure 780 Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011, 781 . 783 [RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types", 784 RFC 6991, DOI 10.17487/RFC6991, July 2013, 785 . 787 [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", 788 RFC 7950, DOI 10.17487/RFC7950, August 2016, 789 . 791 [RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF 792 Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017, 793 . 795 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 796 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 797 May 2017, . 799 [RFC8294] Liu, X., Qu, Y., Lindem, A., Hopps, C., and L. Berger, 800 "Common YANG Data Types for the Routing Area", RFC 8294, 801 DOI 10.17487/RFC8294, December 2017, 802 . 804 [RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration 805 Access Control Model", STD 91, RFC 8341, 806 DOI 10.17487/RFC8341, March 2018, 807 . 809 [RFC8343] Bjorklund, M., "A YANG Data Model for Interface 810 Management", RFC 8343, DOI 10.17487/RFC8343, March 2018, 811 . 813 [RFC8349] Lhotka, L., Lindem, A., and Y. Qu, "A YANG Data Model for 814 Routing Management (NMDA Version)", RFC 8349, 815 DOI 10.17487/RFC8349, March 2018, 816 . 818 6.2. Informative References 820 [RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams", 821 BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018, 822 . 824 Authors' Addresses 826 Tarek Saad 827 Juniper Networks 829 Email: tsaad.net@gmail.com 831 Rakesh Gandhi 832 Cisco Systems, Inc. 834 Email: rgandhi@cisco.com 836 Xufeng Liu 837 Volta Networks 839 Email: xufeng.liu.ietf@gmail.com 841 Vishnu Pavan Beeram 842 Juniper Networks 844 Email: vbeeram@juniper.net 846 Igor Bryskin 847 Huawei Technologies 849 Email: Igor.Bryskin@huawei.com