MPLS Working Group T. Saad Internet-Draft K. Raza Intended status: Standards Track R. Gandhi Expires: January 6, 2017 Cisco Systems Inc X. Liu Ericsson V. Beeram Juniper Networks H. Shah Ciena I. Bryskin X. Chen Huawei Technologies R. Jones Brocade B. Wen Comcast July 05, 2016 A YANG Data Model for MPLS Static LSPs draft-ietf-mpls-static-yang-01 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 LER(s) and 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/. 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 January 6, 2017. Saad, et al. Expires January 6, 2017 [Page 1] Internet-Draft MPLS Static LSPs YANG Data Model July 2016 Copyright Notice Copyright (c) 2016 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 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 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 1.2. Model Organization . . . . . . . . . . . . . . . . . . . 4 1.3. MPLS Static LSPs Model Tree Diagram . . . . . . . . . . . 4 1.4. MPLS Static LSP YANG Module(s) . . . . . . . . . . . . . 6 2. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15 3. Security Considerations . . . . . . . . . . . . . . . . . . . 16 4. References . . . . . . . . . . . . . . . . . . . . . . . . . 16 4.1. Normative References . . . . . . . . . . . . . . . . . . 16 4.2. Informative References . . . . . . . . . . . . . . . . . 17 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 17 1. Introduction This document describes a YANG data model for configuring and managing the Static LSPs feature. The model allows the configuration of LER and LSR devices with the necessary MPLS cross-connects or bindings to realize an end-to-end LSP service. A static LSP is established by manually specifying incoming and outgoing MPLS label(s) and necessary forwarding information on each of the traversed Label Edge Router (LER) and Label Switched Router (LSR) devices (ingress, transit, or egress nodes) of the forwarding path. For example, on an ingress LER device, the model is used to associate a specific Forwarding Equivalence Class (FEC) of packets- e.g. matching a specific IP prefix in a Virtual Routing or Forwarding (VRF) instance- to an MPLS outgoing label imposition, next-hop(s) and respective outgoing interface(s) to forward the packet. On an LSR device, the model is used to create a binding that swaps the incoming Saad, et al. Expires January 6, 2017 [Page 2] Internet-Draft MPLS Static LSPs YANG Data Model July 2016 label with an outgoing label and forwards the packet on one or multiple egress path(s). On an egress LER, it is used to create a binding that decapsulates the incoming MPLS label and performs forwarding based on the inner MPLS label (if present) or IP forwarding in the packet. The MPLS Static LSP YANG model is defined in module "ietf-mpls- static" and augments the MPLS Base YANG model defined in module "ietf-mpls" in [I-D.saad-mpls-static-yang]. The approach described in [I-D.openconfig-netmod-opstate] is adopted to represent data pertaining to configuration intended, applied state and derived state data elements. Each container in the model holds a "config" and "state" sub-container. The "config" sub-container is used to represent the intended configurable parameters, and the state sub- container is used to represent both the applied configurable parameters and any derived state, such as counters or statistical information. 1.1. Terminology In this document, the key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" are to be interpreted as described in BCP 14, RFC 2119 [RFC2119]. The following terms are defined in [RFC6020]: o augment, o configuration data, o data model, o data node, o feature, o mandatory node, o module, o schema tree, o state data, o RPC operation. Saad, et al. Expires January 6, 2017 [Page 3] Internet-Draft MPLS Static LSPs YANG Data Model July 2016 1.2. Model Organization The base MPLS Static LSP model covers the core features with the minimal set of configuration parameters needed to manage and operate MPLS Static LSPs. Additional MPLS Static LSP parameters as well as optional feature(s) are grouped in a separate MPLS Static LSP extended model. The relationship between the MPLS base and other MPLS modules are shown in Figure 1. MPLS base +-----------+ ^: import module | ietf-mpls | o: augment +-----------+ o o | \ v V +------------------+ +--------------------+ MPLS Static | ietf-mpls-static | | ietf-mpls-ldp.yang | . . . LSP module +------------------+ +--------------------+ ^ | o +---------------------------+ Extended MPLS | ietf-mpls-static-extended | Static LSP +---------------------------+ module Figure 1: Relationship between MPLS modules 1.3. MPLS Static LSPs Model Tree Diagram The MPLS Static LSP tree diagram is shown in Figure 2. module: ietf-mpls-static augment /rt:routing/mpls:mpls: +--rw static-lsps +--rw static-lsp* [name] | +--rw name string | +--rw config | | +--rw in-segment | | | +--rw (type)? | | | | +--:(ip-prefix) | | | | | +--rw ip-prefix? inet:ip-prefix | | | | +--:(mpls-label) | | | | | +--rw incoming-label? mpls:mpls-label | | | | +--:(tunnel) Saad, et al. Expires January 6, 2017 [Page 4] Internet-Draft MPLS Static LSPs YANG Data Model July 2016 | | | | +--rw tunnel? te:tunnel-ref | | | +--rw incoming-interface? if:interface-ref | | +--rw operation? enumeration | | +--rw (out-segment)? | | +--:(simple-path) | | | +--rw next-hop? inet:ip-address | | | +--rw outgoing-label? mpls:mpls-label | | | +--rw outgoing-interface? if:interface-ref | | +--:(path-list) | | +--rw paths* [path-index] | | +--rw path-index uint16 | | +--rw backup-path-index? uint16 | | +--rw next-hop? inet:ip-address | | +--rw outgoing-labels* mpls:mpls-label | | +--rw outgoing-interface? if:interface-ref | | +--rw loadshare? uint16 | | +--rw role? enumeration | +--ro state | +--ro in-segment | | +--ro (type)? | | | +--:(ip-prefix) | | | | +--ro ip-prefix? inet:ip-prefix | | | +--:(mpls-label) | | | | +--ro incoming-label? mpls:mpls-label | | | +--:(tunnel) | | | +--ro tunnel? te:tunnel-ref | | +--ro incoming-interface? if:interface-ref | +--ro operation? enumeration | +--ro (out-segment)? | +--:(simple-path) | | +--ro next-hop? inet:ip-address | | +--ro outgoing-label? mpls:mpls-label | | +--ro outgoing-interface? if:interface-ref | +--:(path-list) | +--ro paths* [path-index] | +--ro path-index uint16 | +--ro backup-path-index? uint16 | +--ro next-hop? inet:ip-address | +--ro outgoing-labels* mpls:mpls-label | +--ro outgoing-interface? if:interface-ref | +--ro loadshare? uint16 | +--ro role? enumeration +--rw mpls-static-ext:bandwidth? uint32 +--rw mpls-static-ext:lsp-priority-setup? uint8 +--rw mpls-static-ext:lsp-priority-hold? uint8 Figure 2: MPLS Static LSP tree diagram Saad, et al. Expires January 6, 2017 [Page 5] Internet-Draft MPLS Static LSPs YANG Data Model July 2016 1.4. MPLS Static LSP YANG Module(s) The MPLS Static LSP module is shown in Figure 3. file "ietf-mpls-static@2016-07-05.yang" module ietf-mpls-static { namespace "urn:ietf:params:xml:ns:yang:ietf-mpls-static"; prefix "mpls-static"; import ietf-mpls { prefix mpls; } import ietf-routing { prefix "rt"; } import ietf-inet-types { prefix inet; } import ietf-interfaces { prefix "if"; } /* Import TE generic types */ import ietf-te { prefix te; } organization "IETF MPLS Working Group"; contact "WG Web: WG List: WG Chair: Loa Andersson WG Chair: Ross Callon WG Chair: George Swallow Saad, et al. Expires January 6, 2017 [Page 6] Internet-Draft MPLS Static LSPs YANG Data Model July 2016 Editor: Tarek Saad Editor: Kamran Raza Editor: Rakesh Gandhi Editor: Xufeng Liu Editor: Vishnu Pavan Beeram Editor: Himanshu Shah Editor: Igor Bryskin Editor: Xia Chen Editor: Raqib Jones Editor: Bin Wen "; description "This YANG module augments the 'ietf-routing' module with basic configuration and operational state data for MPLS static"; revision "2016-07-05" { description "Latest revision: - Addressed MPLS-RT review comments"; reference "RFC 3031: A YANG Data Model for Static MPLS LSPs"; } typedef static-lsp-ref { type leafref { path "/rt:routing/mpls:mpls/mpls-static:static-lsps/" + "mpls-static:static-lsp/mpls-static:name"; } description "This type is used by data models that need to reference Saad, et al. Expires January 6, 2017 [Page 7] Internet-Draft MPLS Static LSPs YANG Data Model July 2016 configured static LSP."; } grouping path-basic_config { description "common definitions for statics"; leaf next-hop { type inet:ip-address; description "next hop IP address for the LSP"; } leaf outgoing-label { type mpls:mpls-label; description "label value to push at the current hop for the LSP"; } leaf outgoing-interface { type if:interface-ref; description "The outgoing interface"; } } grouping path-properties_config { description "MPLS path properties"; leaf path-index { type uint16; description "Path identifier"; } leaf backup-path-index { type uint16; description "Backup path identifier"; } leaf next-hop { type inet:ip-address; description "The address of the next-hop"; } leaf-list outgoing-labels { type mpls:mpls-label; Saad, et al. Expires January 6, 2017 [Page 8] Internet-Draft MPLS Static LSPs YANG Data Model July 2016 ordered-by user; description "The outgoing MPLS labels to impose"; } leaf outgoing-interface { type if:interface-ref; description "The outgoing interface"; } leaf loadshare { type uint16; description "This value is used to compute a loadshare to perform un-equal load balancing when multiple outgoing path(s) are specified. A share is computed as a ratio of this number to the total under all configured path(s)."; } leaf role { type enumeration { enum PRIMARY { description "Path as primary traffic carrying"; } enum BACKUP { description "Path acts as backup"; } enum PRIMARY_AND_BACKUP { description "Path acts as primary and backup simultaneously"; } } description "The MPLS path role"; } } grouping static-lsp_config { description "common definitions for static LSPs"; container in-segment { description "MPLS incoming segment"; choice type { description Saad, et al. Expires January 6, 2017 [Page 9] Internet-Draft MPLS Static LSPs YANG Data Model July 2016 "Basic FEC choice"; case ip-prefix { leaf ip-prefix { type inet:ip-prefix; description "An IP prefix"; } } case mpls-label { leaf incoming-label { type mpls:mpls-label; description "label value on the incoming packet"; } } case tunnel { leaf tunnel { type te:tunnel-ref; description "TE tunnel FEC mapping"; } } } leaf incoming-interface { type if:interface-ref; description "Optional incoming interface if FEC is restricted to traffic incoming on a specific interface"; } } leaf operation { type enumeration { enum impose-and-forward { description "Operation impose outgoing label(s) and forward to next-hop"; } enum pop-and-forward { description "Operation pop incoming label and forward to next-hop"; } enum pop-impose-and-forward { description "Operation pop incoming label, impose one or more outgoing label(s) and forward to next-hop"; } enum swap-and-forward { description "Operation swap incoming label, with outgoing label and forward to next-hop"; Saad, et al. Expires January 6, 2017 [Page 10] Internet-Draft MPLS Static LSPs YANG Data Model July 2016 } enum pop-and-lookup { description "Operation pop incoming label and perform a lookup"; } } description "The MPLS operation to be executed on the incoming packet"; } choice out-segment { description "The MPLS out-segment type choice"; case simple-path { uses path-basic_config; } case path-list { list paths { key path-index; description "The list of MPLS paths associated with the FEC"; uses path-properties_config; } } } } grouping static-lsp { description "grouping for top level list of static LSPs"; container config { description "Holds the intended configuration"; uses static-lsp_config; } container state { config false; description "Holds the state and inuse configuration"; uses static-lsp_config; } } augment "/rt:routing/mpls:mpls" { description "Augmentations for MPLS Static LSPs"; container static-lsps { description "Statically configured LSPs, without dynamic signaling"; list static-lsp { key name; Saad, et al. Expires January 6, 2017 [Page 11] Internet-Draft MPLS Static LSPs YANG Data Model July 2016 description "list of defined static LSPs"; leaf name { type string; description "name to identify the LSP"; } uses static-lsp; } } } } Figure 3: MPLS Static LSP YANG module The extended MPLS Static LSP module is shown in Figure 4. file "ietf-mpls-static-extended@2016-07-05.yang" module ietf-mpls-static-extended { namespace "urn:ietf:params:xml:ns:yang:ietf-mpls-static-extended"; prefix "mpls-static-ext"; import ietf-mpls { prefix "mpls"; } import ietf-routing { prefix "rt"; } import ietf-mpls-static { prefix "mpls-static"; } organization "IETF MPLS Working Group"; contact "WG Web: WG List: WG Chair: Loa Andersson WG Chair: Ross Callon Saad, et al. Expires January 6, 2017 [Page 12] Internet-Draft MPLS Static LSPs YANG Data Model July 2016 WG Chair: George Swallow Editor: Tarek Saad Editor: Kamran Raza Editor: Rakesh Gandhi Editor: Xufeng Liu Editor: Vishnu Pavan Beeram Editor: Himanshu Shah Editor: Igor Bryskin Editor: Xia Chen Editor: Raqib Jones Editor: Bin Wen "; description "This module contains the Extended RSVP YANG data model."; revision 2016-07-05 { description "Latest revision of RSVP extended yang module."; reference "RFC2205"; } /* RSVP features */ feature bandwidth { description "Indicates support for static LSP bandwidth allocation"; } grouping static-lsp-extended_config { Saad, et al. Expires January 6, 2017 [Page 13] Internet-Draft MPLS Static LSPs YANG Data Model July 2016 description "Configuration parameters for MPLS extended parameters"; leaf bandwidth { type uint32; 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 { type uint8 { range "0..7"; } description "LSP hold priority"; } } grouping bidir-static-lsp_config { description "common definitions for static 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"; } } grouping bidir-static-lsp { description "grouping for top level list of static LSPs"; container config { description "Holds the intended configuration"; uses bidir-static-lsp_config; } container state { config false; description "Holds the state and inuse configuration"; uses bidir-static-lsp_config; Saad, et al. Expires January 6, 2017 [Page 14] Internet-Draft MPLS Static LSPs YANG Data Model July 2016 } } augment "/rt:routing/mpls:mpls/mpls-static:static-lsps" { description "RSVP signaling all interfaces configuration extensions"; uses static-lsp-extended_config; } augment "/rt:routing/mpls:mpls" { description "Augmentations for MPLS Static LSPs"; container bidir-static-lsps { description "Statically configured LSPs, without dynamic signaling"; list bidir-static-lsp { key name; description "list of defined static LSPs"; leaf name { type string; description "name to identify the LSP"; } uses bidir-static-lsp; } } } } Figure 4: Extended MPLS Static LSP YANG module 2. IANA Considerations This document registers the following URIs in the IETF XML registry [RFC3688]. Following the format in [RFC3688], the following registration is requested to be made. URI: urn:ietf:params:xml:ns:yang:ietf-mpls-static XML: N/A, the requested URI is an XML namespace. URI: urn:ietf:params:xml:ns:yang:ietf-mpls-static-extended XML: N/A, the requested URI is an XML namespace. This document registers two YANG modules in the YANG Module Names registry [RFC6020]. name: ietf-mpls-static namespace: urn:ietf:params:xml:ns:yang:ietf- mpls-static prefix: ietf-mpls-static reference: RFC3031 Saad, et al. Expires January 6, 2017 [Page 15] Internet-Draft MPLS Static LSPs YANG Data Model July 2016 name: ietf-mpls-static-exteneded namespace: urn:ietf:params:xml:ns:yang:ietf-mpls-static-extended prefix: ietf- mpls-static reference: RFC3031 3. Security Considerations The YANG module defined in this memo is designed to be accessed via the NETCONF protocol [RFC6241]. The lowest NETCONF layer is the secure transport layer and the mandatory-to-implement secure transport is SSH [RFC6242]. The NETCONF access control model [RFC6536] provides means to restrict access for particular NETCONF users to a pre-configured subset of all available NETCONF protocol operations and content. There are a number of data nodes defined in the YANG module which are writable/creatable/deletable (i.e., config true, which is the default). These data nodes may be considered sensitive or vulnerable in some network environments. Write operations (e.g., ) to these data nodes without proper protection can have a negative effect on network operations. 4. References 4.1. Normative References [I-D.saad-mpls-static-yang] Saad, T., Raza, K., Gandhi, R., Liu, X., Beeram, V., Shah, H., Bryskin, I., Chen, X., Jones, R., and B. Wen, "A YANG Data Model for MPLS Static LSPs", draft-saad-mpls-static- yang-03 (work in progress), May 2016. [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/ RFC2119, March 1997, . [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 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, . Saad, et al. Expires January 6, 2017 [Page 16] Internet-Draft MPLS Static LSPs YANG Data Model July 2016 [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, . [RFC6536] Bierman, A. and M. Bjorklund, "Network Configuration Protocol (NETCONF) Access Control Model", RFC 6536, DOI 10.17487/RFC6536, March 2012, . 4.2. Informative References [I-D.openconfig-netmod-opstate] Shakir, R., Shaikh, A., and M. Hines, "Consistent Modeling of Operational State Data in YANG", draft-openconfig- netmod-opstate-01 (work in progress), July 2015. Authors' Addresses Tarek Saad Cisco Systems Inc Email: tsaad@cisco.com Kamran Raza Cisco Systems Inc Email: skraza@cisco.com Rakesh Gandhi Cisco Systems Inc Email: rgandhi@cisco.com Xufeng Liu Ericsson Email: xufeng.liu.ietf@gmail.com Saad, et al. Expires January 6, 2017 [Page 17] Internet-Draft MPLS Static LSPs YANG Data Model July 2016 Vishnu Pavan Beeram Juniper Networks Email: vbeeram@juniper.net Himanshu Shah Ciena Email: hshah@ciena.com Igor Bryskin Huawei Technologies Email: Igor.Bryskin@huawei.com Xia Chen Huawei Technologies Email: jescia.chenxia@huawei.com Raqib Jones Brocade Email: raqib@Brocade.com Bin Wen Comcast Email: Bin_Wen@cable.comcast.com Saad, et al. Expires January 6, 2017 [Page 18]