--- 1/draft-ietf-mpls-static-yang-08.txt 2019-03-08 11:13:38.465738092 -0800 +++ 2/draft-ietf-mpls-static-yang-09.txt 2019-03-08 11:13:38.505739081 -0800 @@ -1,61 +1,61 @@ MPLS Working Group T. Saad Internet-Draft Juniper Networks Intended status: Standards Track R. Gandhi -Expires: September 3, 2019 Cisco Systems, Inc. +Expires: September 9, 2019 Cisco Systems, Inc. X. Liu Volta Networks V. Beeram Juniper Networks I. Bryskin Huawei Technologies - March 02, 2019 + March 08, 2019 A YANG Data Model for MPLS Static LSPs - draft-ietf-mpls-static-yang-08 + draft-ietf-mpls-static-yang-09 Abstract This document contains the specification for the MPLS Static Label Switched Paths (LSPs) YANG model. The model allows for the provisioning of static LSP(s) on Label Edge Router(s) LER(s) and Label Switched Router(s) LSR(s) devices along a LSP path without the dependency on any signaling protocol. The MPLS Static LSP model augments the MPLS base YANG model with specific data to configure and manage MPLS Static LSP(s). Status of This Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- - Drafts is at http://datatracker.ietf.org/drafts/current/. + Drafts is at https://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." - This Internet-Draft will expire on September 3, 2019. + This Internet-Draft will expire on September 9, 2019. Copyright Notice Copyright (c) 2019 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents - (http://trustee.ietf.org/license-info) in effect on the date of + (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 @@ -313,25 +313,24 @@ o ietf-routing-types defined in [RFC8294] o ietf-interfaces defined in [RFC8343] o ietf-mpls defined in [I-D.ietf-mpls-base-yang] o ietf-te defined in [I-D.ietf-teas-yang-te] The ietf-mpls-static module is shown below: - file "ietf-mpls-static@2019-02-24.yang" + file "ietf-mpls-static@2019-03-08.yang" module ietf-mpls-static { yang-version 1.1; namespace "urn:ietf:params:xml:ns:yang:ietf-mpls-static"; - prefix "mpls-static"; import ietf-mpls { prefix "mpls"; reference "draft-ietf-mpls-base-yang: MPLS Base YANG Data Model"; } import ietf-routing { prefix "rt"; reference "RFC8349: A YANG Data Model for Routing Management"; @@ -332,21 +331,21 @@ reference "draft-ietf-mpls-base-yang: MPLS Base YANG Data Model"; } import ietf-routing { prefix "rt"; reference "RFC8349: A YANG Data Model for Routing Management"; } import ietf-routing-types { prefix "rt-types"; - reference "RFC8294: Common YANG Data Types"; + reference "RFC8294: Common YANG Data Types for the Routing Area"; } import ietf-inet-types { prefix inet; reference "RFC6991: Common YANG Data Types"; } import ietf-interfaces { prefix "if"; reference "RFC7223: A YANG Data Model for Interface Management"; @@ -403,21 +402,21 @@ (https://trustee.ietf.org/license-info). This version of this YANG module is part of RFC XXXX; see the RFC itself for full legal notices."; // RFC Ed.: replace XXXX with actual RFC number and remove this // note. // RFC Ed.: update the date below with the date of RFC publication // and remove this note. - revision "2019-02-24" { + revision "2019-03-08" { description "Latest revision of MPLS Static LSP YANG module"; reference "RFC XXXX: A YANG Data Model for MPLS Static LSPs"; } typedef static-lsp-ref { type leafref { path "/rt:routing/mpls:mpls/mpls-static:static-lsps/" + "mpls-static:static-lsp/mpls-static:name"; } @@ -519,41 +518,39 @@ The ietf-mpls-static-extended module imports the followinig modules: o ietf-mpls defined in [I-D.ietf-mpls-base-yang] o ietf-mpls-static defined in this document o ietf-routing defined in [RFC8349] The ietf-mpls-static-extended module is shown below: - file "ietf-mpls-static-extended@2019-02-24.yang" + file "ietf-mpls-static-extended@2019-03-08.yang" module ietf-mpls-static-extended { yang-version 1.1; namespace "urn:ietf:params:xml:ns:yang:ietf-mpls-static-extended"; - prefix "mpls-static-ext"; import ietf-mpls { prefix "mpls"; reference "draft-ietf-mpls-base-yang: MPLS Base YANG Data Model"; } import ietf-routing { prefix "rt"; - reference "RFC6991: Common YANG Data Types"; + reference "RFC8349: A YANG Data Model for Routing Management"; } import ietf-mpls-static { prefix "mpls-static"; - reference "draft-ietf-mpls-static-yang: A YANG Data Model for MPLS - Static LSPs"; + reference "RFC XXXX: A YANG Data Model for MPLS Static LSPs"; } organization "IETF MPLS Working Group"; contact "WG Web: WG List: WG Chair: Loa Andersson @@ -599,33 +596,34 @@ (https://trustee.ietf.org/license-info). This version of this YANG module is part of RFC XXXX; see the RFC itself for full legal notices."; // RFC Ed.: replace XXXX with actual RFC number and remove this // note. // RFC Ed.: update the date below with the date of RFC publication // and remove this note. - revision "2019-02-24" { + revision "2019-03-08" { description "Latest revision of MPLS Static LSP Extended YANG module"; - reference "RFC XXXX: Extended YANG Data Model for MPLS Static LSPs"; + reference "RFC XXXX: A YANG Data Model for MPLS Static LSPs"; } grouping bidir-static-lsp { description "grouping for top level list of static bidirectional LSPs"; leaf forward-lsp { type mpls-static:static-lsp-ref; description "Reference to a configured static forward LSP"; + } leaf reverse-lsp { type mpls-static:static-lsp-ref; description "Reference to a configured static reverse LSP"; } } augment "/rt:routing/mpls:mpls/mpls-static:static-lsps" { description @@ -626,21 +624,21 @@ "Reference to a configured static reverse LSP"; } } augment "/rt:routing/mpls:mpls/mpls-static:static-lsps" { description "Augmentation for static MPLS LSPs"; leaf bandwidth { type uint32; - units mbps; + units "Mbps"; description "Bandwidth in Mbps, e.g., using offline calculation"; } leaf lsp-priority-setup { type uint8 { range "0..7"; } description "LSP setup priority"; } leaf lsp-priority-hold { @@ -747,81 +746,81 @@ YANG Data Model for MPLS Base", draft-ietf-mpls-base- yang-10 (work in progress), February 2019. [I-D.ietf-teas-yang-te] Saad, T., Gandhi, R., Liu, X., Beeram, V., and I. Bryskin, "A YANG Data Model for Traffic Engineering Tunnels and Interfaces", draft-ietf-teas-yang-te-19 (work in progress), February 2019. [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate - Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/ - RFC2119, March 1997, . + Requirement Levels", BCP 14, RFC 2119, + DOI 10.17487/RFC2119, March 1997, + . [RFC3031] Rosen, E., Viswanathan, A., and R. Callon, "Multiprotocol - Label Switching Architecture", RFC 3031, DOI 10.17487/ - RFC3031, January 2001, . + Label Switching Architecture", RFC 3031, + DOI 10.17487/RFC3031, January 2001, + . [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, - DOI 10.17487/RFC3688, January 2004, . + DOI 10.17487/RFC3688, January 2004, + . [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for the Network Configuration Protocol (NETCONF)", RFC 6020, - DOI 10.17487/RFC6020, October 2010, . + DOI 10.17487/RFC6020, October 2010, + . [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., and A. Bierman, Ed., "Network Configuration Protocol (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, . [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011, . - [RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types", RFC - 6991, DOI 10.17487/RFC6991, July 2013, . + [RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types", + RFC 6991, DOI 10.17487/RFC6991, July 2013, + . [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", RFC 7950, DOI 10.17487/RFC7950, August 2016, . [RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017, . [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, May 2017, . [RFC8294] Liu, X., Qu, Y., Lindem, A., Hopps, C., and L. Berger, "Common YANG Data Types for the Routing Area", RFC 8294, - DOI 10.17487/RFC8294, December 2017, . + DOI 10.17487/RFC8294, December 2017, + . [RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration - Access Control Model", STD 91, RFC 8341, DOI 10.17487/ - RFC8341, March 2018, . + Access Control Model", STD 91, RFC 8341, + DOI 10.17487/RFC8341, March 2018, + . [RFC8343] Bjorklund, M., "A YANG Data Model for Interface Management", RFC 8343, DOI 10.17487/RFC8343, March 2018, . [RFC8349] Lhotka, L., Lindem, A., and Y. Qu, "A YANG Data Model for - Routing Management (NMDA Version)", RFC 8349, DOI - 10.17487/RFC8349, March 2018, . + Routing Management (NMDA Version)", RFC 8349, + DOI 10.17487/RFC8349, March 2018, + . 6.2. Informative References [RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams", BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018, . Authors' Addresses Tarek Saad