idnits 2.17.1 draft-ietf-mpls-static-yang-06.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 == Line 206 has weird spacing: '...w index uin...' == Line 218 has weird spacing: '...w index uin...' == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- The document date (October 10, 2018) is 2018 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-07 == Outdated reference: A later version (-36) exists of draft-ietf-teas-yang-te-16 Summary: 0 errors (**), 0 flaws (~~), 6 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: April 13, 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 October 10, 2018 16 A YANG Data Model for MPLS Static LSPs 17 draft-ietf-mpls-static-yang-06 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 April 13, 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 . . . . . . . . . . . . . . . . . . . . . 14 71 4. Security Considerations . . . . . . . . . . . . . . . . . . . 14 72 5. References . . . . . . . . . . . . . . . . . . . . . . . . . 15 73 5.1. Normative References . . . . . . . . . . . . . . . . . . 15 74 5.2. Informative References . . . . . . . . . . . . . . . . . 16 75 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 16 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 remote-labels 205 | | | +--rw remote-label* [index] 206 | | | +--rw index uint8 207 | | | +--rw label? rt-types:mpls-label 208 | | +--rw outgoing-interface? if:interface-ref 209 | +--:(nhlfe-multiple) 210 | +--rw nhlfe-multiple 211 | +--rw nhlfe* [index] 212 | +--rw index string 213 | +--rw backup-index? string 214 | +--rw loadshare? uint16 215 | +--rw role? nhlfe-role 216 | +--rw remote-labels 217 | | +--rw remote-label* [index] 218 | | +--rw index uint8 219 | | +--rw label? rt-types:mpls-label 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 imports the followinig modules: 243 o ietf-inet-types defined in [RFC6991] 245 o ietf-routing defined in [RFC8349] 247 o ietf-routing-types defined in [RFC8294] 249 o ietf-interfaces defined in [RFC8343] 251 o ietf-mpls defined in [I-D.ietf-mpls-base-yang] 253 o ietf-te defined in [I-D.ietf-teas-yang-te] 255 ietf-mpls-static module contains the following high-level types and 256 groupings: 258 static-lsp-ref: 260 A YANG reference type for a static LSP that can be used by data 261 models to reference a configured static LSP. 263 in-segment: 265 A YANG grouping that describes parameters of an incoming class of 266 FEC associated with a specific LSP as described in the MPLS 267 architecture document [RFC3031]. The model allows the following 268 types of traffic to be mapped onto the static LSP on an ingress 269 LER: 271 o Unlabeled traffic destined to a specific prefix 272 o Labeled traffic arriving with a specific label 273 o Traffic carried on a TE tunnel whose LSP is 274 statically created via this model. 276 out-segment: 278 A YANG grouping that describes parameters for the forwarding 279 path(s) and their associated attributes for an LSP. The model 280 allows for the following cases: 282 o single forwarding path or NHLFE 283 o multiple forwarding path(s) or NHLFE(s), each of which can 284 serve a primary, backup or both role(s). 286 2.4. Model YANG Module(s) 288 Configuring LSPs through an LSR/LER involves the following steps: 290 o Enabling MPLS on MPLS capable interfaces. 292 o Configuring in-segments and out-segments on LER(s) and LSR(s) 293 traversed by the LSP. 295 o Setting up the cross-connect per LSP to associate segments and/or 296 to indicate connection origination and termination. 298 o Optionally specifying label stack actions. 300 o Optionally specifying segment traffic parameters. 302 The objects covered by this model are derived from the Incoming Label 303 Map (ILM) and Next Hop Label Forwarding Entry (NHLFE) as specified in 304 the MPLS architecture document [RFC3031]. 306 The MPLS Static LSP module is shown in Figure 3. 308 file "ietf-mpls-static@2018-10-04.yang" 309 module ietf-mpls-static { 310 yang-version 1.1; 311 namespace "urn:ietf:params:xml:ns:yang:ietf-mpls-static"; 313 prefix "mpls-static"; 315 import ietf-mpls { 316 prefix "mpls"; 317 reference "draft-ietf-mpls-base-yang: MPLS Base YANG Data Model"; 318 } 320 import ietf-routing { 321 prefix "rt"; 322 reference "RFC8349: A YANG Data Model for Routing Management"; 323 } 325 import ietf-routing-types { 326 prefix "rt-types"; 327 reference "RFC6991: Common YANG Data Types"; 328 } 329 import ietf-inet-types { 330 prefix inet; 331 reference "RFC6991: Common YANG Data Types"; 332 } 334 import ietf-interfaces { 335 prefix "if"; 336 reference "RFC7223: A YANG Data Model for Interface Management"; 337 } 339 /* Import TE Tunnel */ 340 import ietf-te { 341 prefix te; 342 reference "draft-ietf-teas-yang-te: A YANG Data Model for Traffic 343 Engineering Tunnels and Interfaces"; 344 } 346 organization "IETF MPLS Working Group"; 348 contact 349 "WG Web: 351 WG List: 353 WG Chair: Loa Andersson 354 356 Editor: Tarek Saad 357 359 Editor: Kamran Raza 360 362 Editor: Rakesh Gandhi 363 365 Editor: Xufeng Liu 366 368 Editor: Vishnu Pavan Beeram 369 371 Editor: Himanshu Shah 372 374 Editor: Igor Bryskin 375 "; 377 description 378 "This YANG module augments the 'ietf-routing' module with basic 379 configuration and operational state data for MPLS static"; 381 revision "2018-10-04" { 382 description 383 "Latest revision: 384 - Addressed MPLS-RT review comments"; 385 reference "RFC 3031: Multiprotocol Label Switching Architecture"; 386 } 388 typedef static-lsp-ref { 389 type leafref { 390 path "/rt:routing/mpls:mpls/mpls-static:static-lsps/" + 391 "mpls-static:static-lsp/mpls-static:name"; 392 } 393 description 394 "This type is used by data models that need to reference 395 configured static LSP."; 396 } 398 grouping in-segment { 399 description "In-segment grouping"; 400 container in-segment { 401 description "MPLS incoming segment"; 402 container fec { 403 description "Forwarding Equivalence Class grouping"; 404 choice type { 405 description "FEC type choices"; 406 case ip-prefix { 407 leaf ip-prefix { 408 type inet:ip-prefix; 409 description "An IP prefix"; 410 } 411 } 412 case mpls-label { 413 leaf incoming-label { 414 type rt-types:mpls-label; 415 description "label value on the incoming packet"; 416 } 417 } 418 case tunnel { 419 leaf tunnel { 420 type te:tunnel-ref; 421 description "TE tunnel FEC mapping"; 422 } 423 } 424 } 425 leaf incoming-interface { 426 type if:interface-ref; 427 description 428 "Optional incoming interface if FEC is restricted 429 to traffic incoming on a specific interface"; 430 } 431 } 432 } 433 } 435 grouping out-segment { 436 description "Out-segment grouping"; 437 container out-segment { 438 description "MPLS outgoing segment"; 439 choice out-segment { 440 description "The MPLS out-segment type choice"; 441 case nhlfe-single { 442 container nhlfe-single { 443 description "Container for single NHLFE entry"; 444 uses mpls:nhlfe-single-contents; 445 leaf outgoing-interface { 446 type if:interface-ref; 447 description 448 "The outgoing interface"; 449 } 450 } 451 } 452 case nhlfe-multiple { 453 container nhlfe-multiple { 454 description "Container for multiple NHLFE entries"; 455 list nhlfe { 456 key index; 457 description "MPLS NHLFE entry"; 458 uses mpls:nhlfe-multiple-contents; 459 leaf outgoing-interface { 460 type if:interface-ref; 461 description 462 "The outgoing interface"; 463 } 464 } 465 } 466 } 467 } 468 } 469 } 471 augment "/rt:routing/mpls:mpls" { 472 description "Augmentations for MPLS Static LSPs"; 473 container static-lsps { 474 description 475 "Statically configured LSPs, without dynamic signaling"; 476 list static-lsp { 477 key name; 478 description "list of defined static LSPs"; 479 leaf name { 480 type string; 481 description "name to identify the LSP"; 482 } 483 leaf operation { 484 type mpls:mpls-operations-type; 485 description 486 "The MPLS operation to be executed on the incoming packet"; 487 } 488 uses in-segment; 489 uses out-segment; 490 } 491 } 492 } 493 } 494 496 Figure 3: MPLS Static LSP YANG module 498 The extended MPLS Static LSP module is shown in Figure 4. 500 file "ietf-mpls-static-extended@2018-10-04.yang" 501 module ietf-mpls-static-extended { 503 namespace "urn:ietf:params:xml:ns:yang:ietf-mpls-static-extended"; 505 prefix "mpls-static-ext"; 507 import ietf-mpls { 508 prefix "mpls"; 509 } 511 import ietf-routing { 512 prefix "rt"; 513 } 515 import ietf-mpls-static { 516 prefix "mpls-static"; 517 } 519 organization "IETF MPLS Working Group"; 520 contact 521 "WG Web: 523 WG List: 525 WG Chair: Loa Andersson 526 528 Editor: Tarek Saad 529 531 Editor: Kamran Raza 532 534 Editor: Rakesh Gandhi 535 537 Editor: Xufeng Liu 538 540 Editor: Vishnu Pavan Beeram 541 543 Editor: Himanshu Shah 544 546 Editor: Igor Bryskin 547 "; 549 description 550 "This module contains the Extended MPLS YANG data model."; 552 revision "2018-10-04" { 553 description "Latest revision of MPLS extended yang module."; 554 reference "RFC2205"; 555 } 557 /* RSVP features */ 558 feature bandwidth { 559 description 560 "Indicates support for static LSP bandwidth allocation"; 561 } 563 grouping bidir-static-lsp { 564 description 565 "grouping for top level list of static bidirectional LSPs"; 566 leaf forward-lsp { 567 type mpls-static:static-lsp-ref; 568 description 569 "Reference to a configured static forward LSP"; 570 } 571 leaf reverse-lsp { 572 type mpls-static:static-lsp-ref; 573 description 574 "Reference to a configured static reverse LSP"; 575 } 576 } 578 augment "/rt:routing/mpls:mpls/mpls-static:static-lsps" { 579 description 580 "Augmentation for static MPLS LSPs"; 582 leaf bandwidth { 583 type uint32; 584 description 585 "bandwidth in Mbps, e.g., using offline calculation"; 586 } 587 leaf lsp-priority-setup { 588 type uint8 { 589 range "0..7"; 590 } 591 description "LSP setup priority"; 592 } 593 leaf lsp-priority-hold { 594 type uint8 { 595 range "0..7"; 596 } 597 description "LSP hold priority"; 598 } 599 } 601 augment "/rt:routing/mpls:mpls" { 602 description "Augmentations for MPLS Static LSPs"; 603 container bidir-static-lsps { 604 description 605 "Statically configured LSPs, without dynamic signaling"; 606 list bidir-static-lsp { 607 key name; 608 description "list of defined static LSPs"; 610 leaf name { 611 type string; 612 description "name to identify the LSP"; 613 } 614 uses bidir-static-lsp; 616 } 617 } 618 } 619 } 620 622 Figure 4: Extended MPLS Static LSP YANG module 624 3. IANA Considerations 626 This document registers the following URIs in the IETF XML registry 627 [RFC3688]. Following the format in [RFC3688], the following 628 registration is requested to be made. 630 URI: urn:ietf:params:xml:ns:yang:ietf-mpls-static 631 XML: N/A, the requested URI is an XML namespace. 633 URI: urn:ietf:params:xml:ns:yang:ietf-mpls-static-extended 634 XML: N/A, the requested URI is an XML namespace. 636 This document registers two YANG modules in the YANG Module Names 637 registry [RFC6020]. 639 name: ietf-mpls-static 640 namespace: urn:ietf:params:xml:ns:yang:ietf-mpls-static 641 prefix: ietf-mpls-static 642 reference: RFC3031 644 name: ietf-mpls-static-extended 645 namespace: urn:ietf:params:xml:ns:yang:ietf-mpls-static-extended 646 prefix: ietf-mpls-static 647 reference: RFC3031 649 4. Security Considerations 651 The YANG module defined in this document is designed to be accessed 652 via the NETCONF protocol [RFC6241]. The lowest NETCONF layer is the 653 secure transport layer and the mandatory-to-implement secure 654 transport is SSH [RFC6242]. The NETCONF access control model 655 [RFC8341] provides means to restrict access for particular NETCONF 656 users to a pre-configured subset of all available NETCONF protocol 657 operations and content. 659 There are certain objects or data nodes that are defined in this YANG 660 module which are writable/creatable/deletable and that can be 661 considered sensitive or vulnerable in some network environments. 662 Specifically, misconfiguration or manipulations of objects or data 663 node(s) defined in this model, including: in-segment(s), out- 664 segment(s) and their associated parameters that collectively allow 665 the provisioning of MPLS LSP(s) and associated parameters on a LSR 666 can potentially have disastrous results. 668 5. References 670 5.1. Normative References 672 [I-D.ietf-mpls-base-yang] 673 Saad, T., Raza, K., Gandhi, R., Liu, X., and V. Beeram, "A 674 YANG Data Model for MPLS Base", draft-ietf-mpls-base- 675 yang-07 (work in progress), October 2018. 677 [I-D.ietf-teas-yang-te] 678 Saad, T., Gandhi, R., Liu, X., Beeram, V., Shah, H., and 679 I. Bryskin, "A YANG Data Model for Traffic Engineering 680 Tunnels and Interfaces", draft-ietf-teas-yang-te-16 (work 681 in progress), July 2018. 683 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 684 Requirement Levels", BCP 14, RFC 2119, 685 DOI 10.17487/RFC2119, March 1997, 686 . 688 [RFC3031] Rosen, E., Viswanathan, A., and R. Callon, "Multiprotocol 689 Label Switching Architecture", RFC 3031, 690 DOI 10.17487/RFC3031, January 2001, 691 . 693 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 694 DOI 10.17487/RFC3688, January 2004, 695 . 697 [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for 698 the Network Configuration Protocol (NETCONF)", RFC 6020, 699 DOI 10.17487/RFC6020, October 2010, 700 . 702 [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., 703 and A. Bierman, Ed., "Network Configuration Protocol 704 (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, 705 . 707 [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure 708 Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011, 709 . 711 [RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types", 712 RFC 6991, DOI 10.17487/RFC6991, July 2013, 713 . 715 [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", 716 RFC 7950, DOI 10.17487/RFC7950, August 2016, 717 . 719 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 720 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 721 May 2017, . 723 [RFC8294] Liu, X., Qu, Y., Lindem, A., Hopps, C., and L. Berger, 724 "Common YANG Data Types for the Routing Area", RFC 8294, 725 DOI 10.17487/RFC8294, December 2017, 726 . 728 [RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration 729 Access Control Model", STD 91, RFC 8341, 730 DOI 10.17487/RFC8341, March 2018, 731 . 733 [RFC8343] Bjorklund, M., "A YANG Data Model for Interface 734 Management", RFC 8343, DOI 10.17487/RFC8343, March 2018, 735 . 737 [RFC8349] Lhotka, L., Lindem, A., and Y. Qu, "A YANG Data Model for 738 Routing Management (NMDA Version)", RFC 8349, 739 DOI 10.17487/RFC8349, March 2018, 740 . 742 5.2. Informative References 744 [RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams", 745 BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018, 746 . 748 Authors' Addresses 750 Tarek Saad 751 Cisco Systems, Inc. 753 Email: tsaad@cisco.com 754 Kamran Raza 755 Cisco Systems, Inc. 757 Email: skraza@cisco.com 759 Rakesh Gandhi 760 Cisco Systems, Inc. 762 Email: rgandhi@cisco.com 764 Xufeng Liu 765 Volta Networks 767 Email: xufeng.liu.ietf@gmail.com 769 Vishnu Pavan Beeram 770 Juniper Networks 772 Email: vbeeram@juniper.net 774 Himanshu Shah 775 Ciena 777 Email: hshah@ciena.com 779 Igor Bryskin 780 Huawei Technologies 782 Email: Igor.Bryskin@huawei.com