MPLS Working Group Rakesh Gandhi Internet-Draft Tarek Saad Intended Status: Standards Track Robert Sawaya Expires: April 16, 2015 Cisco Systems, Inc. October 13, 2014 YANG Data Model Tree Structures for MPLS Traffic Engineering Tunnels and Links draft-gandhi-mpls-te-yang-model-00 Abstract This document defines YANG data model high-level tree structures for the management of Multi-Protocol Label Switching Traffic Engineering (MPLS-TE) tunnels and links. Resource Reservation Protocol (RSVP) signaled MPLS-TE tunnels include tunnel interfaces and Label Switched Paths (LSPs). The data model trees cover configuration data, operational state data, execution commands and event notifications. Status of this Memo This Internet-Draft is submitted to IETF in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. 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." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt. The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. Copyright Notice Copyright (c) 2014 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 Gandhi, et al. Expires April 16, 2015 [Page 1] Internet-Draft Yang Data Model Trees for MPLS TE October 13, 2014 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 . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology and Notation . . . . . . . . . . . . . . . . . . . 3 2.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 2.2. Prefixes in Data Node Names . . . . . . . . . . . . . . . 3 3. Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . 4 4. MPLS-TE Data Models Overview . . . . . . . . . . . . . . . . . 4 4.1. Global MPLS-TE Data Model Overview . . . . . . . . . . . . 4 4.2. MPLS-TE Tunnel Interface Data Model Overview . . . . . . . 6 4.3. MPLS-TE Tunnel LSP Data Model Overview . . . . . . . . . . 7 4.4. MPLS-TE Link Data Model Overview . . . . . . . . . . . . . 8 5. High-level Tree Structure of MPLS-TE Data Model . . . . . . . 9 6. MPLS-TE Global Data Model Tree Structure . . . . . . . . . . . 11 6.1. MPLS-TE Global Attribute-set Lists . . . . . . . . . . . . 11 6.2. MPLS-TE Global Mesh-group Lists . . . . . . . . . . . . . 12 7. MPLS-TE Tunnel Interfaces Data Model Tree Structure . . . . . 12 7.1. MPLS-TE Tunnel Interface Lists . . . . . . . . . . . . . . 12 8. MPLS-TE Tunnel LSPs Data Model Tree Structure . . . . . . . . 13 8.1. MPLS-TE Tunnel LSP Lists . . . . . . . . . . . . . . . . . 13 9. MPLS-TE Links Data Model Tree Structure . . . . . . . . . . . 13 9.1. MPLS-TE Link Lists . . . . . . . . . . . . . . . . . . . . 14 10. MPLS-TE Global YANG Module . . . . . . . . . . . . . . . . . 14 11. MPLS-TE Tunnel Interfaces YANG Module . . . . . . . . . . . . 15 12. MPLS-TE Tunnel LSP YANG Module . . . . . . . . . . . . . . . 15 13. MPLS-TE Links YANG Module . . . . . . . . . . . . . . . . . . 16 14. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17 15. Security Considerations . . . . . . . . . . . . . . . . . . . 18 16. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 19 17. References . . . . . . . . . . . . . . . . . . . . . . . . . 19 17.1. Normative References . . . . . . . . . . . . . . . . . . 19 17.2. Informative References . . . . . . . . . . . . . . . . . 19 18. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . 20 Gandhi, et al. Expires April 16, 2015 [Page 2] Internet-Draft Yang Data Model Trees for MPLS TE October 13, 2014 1. Introduction This document defines YANG [RFC6020] data model high-level tree structures for the management of Multi-Protocol Label Switching Traffic Engineering (MPLS-TE) [RFC3209] tunnels and links. Resource Reservation Protocol (RSVP) signaled MPLS-TE tunnels can be represented as tunnel interfaces at the head-end Label Switching Router (LSR), and as Label Switched Paths (LSPs) at the head-end, mid-point and tail-end LSRs. The data model defined in this document includes configuration data, operational state data (status information and counters), execution requests using RPCs (Remote Procedure Calls), and event notifications pertaining to MPLS-TE tunnel interfaces, tunnel LSPs and MPLS-TE enabled links, as well as system-wide global MPLS-TE properties that relate to the behavior and operation of the TE enabled LSR node. Further modules augmenting this data model with advanced features can be handled in a future revision or a separate document. 2. Terminology and Notation 2.1. Terminology The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119]. 2.2. Prefixes in Data Node Names In this document, names of data nodes and other data model objects are often used without a prefix, as long as it is clear from the context in which YANG module each name is defined. Otherwise, names are prefixed using the standard prefix associated with the corresponding YANG module, as shown in Table 1. +--------+-----------------+-----------+ | Prefix | YANG module | Reference | +--------+-----------------+-----------+ | yang | ietf-yang-types | [RFC6991] | | inet | ietf-inet-types | [RFC6991] | +--------+-----------------+-----------+ Table 1: Prefixes and corresponding YANG modules Gandhi, et al. Expires April 16, 2015 [Page 3] Internet-Draft Yang Data Model Trees for MPLS TE October 13, 2014 3. Objectives This section outlines some of the design objectives for the model: o In case of existing implementations, it needs to map the data model defined in this document to their proprietary native data model. To facilitate such mappings, the data model should be simple. o The data model should be suitable for new implementations to use as is, without requiring a mapping to a different native model. o Mapping to the MPLS-TE MIB Module should be clear. o The data model should include read-only counters in order to gather statistics for sent and received octets and packets, received packets with errors, and packets that could not be sent due to errors. o It should be straight forward to augment the base data model for advanced MPLS-TE features. 4. MPLS-TE Data Models Overview MPLS-TE YANG data models are defined for various management components including configuration, operational state, execution commands and event notifications. Following sections provide overview and some selective examples of these management components for global MPLS-TE, MPLS-TE tunnel interfaces, MPLS-TE tunnel LSPs and MPLS-TE enabled links. 4.1. Global MPLS-TE Data Model Overview This module defines YANG model for configuration data, operational state data, execution commands and event notifications globally for MPLS-TE features. 1. Global MPLS-TE configuration data model: The global MPLS-TE configuration data model is a read-write YANG data model that controls the LSR behavior system-wide. Examples of such configuration items for global MPLS-TE are: o Auto-tunnel backup: controls and manages the automatic creation of fast reroute backup tunnels for protected MPLS-TE enabled links. o Auto-tunnel mesh-group: controls and manages the creation of auto-tunnel mesh-groups. o Auto-tunnel one-hop: controls and manages the Gandhi, et al. Expires April 16, 2015 [Page 4] Internet-Draft Yang Data Model Trees for MPLS TE October 13, 2014 creation of 1-hop auto-tunnels on MPLS-TE enabled links. o Auto-bandwidth parameters: controls and manages the auto-bandwidth specific system-wide properties. o Point-to-Multipoint (P2MP) TE parameters o Names for SRLG values o Names for link (extended) administrative groups (AG, EAG) o MPLS-TE Diff-Serve classes: controls and manages the Diff-Serve TE (DS-TE) model and class-types o System-wide timers that affect MPLS-TE features e.g. o Flooding timers o Re-optimization timers (periodic, installation, cleanup) o Topology database stale timeout o MPLS-TE attribute-sets: These are templates that can be used to instantiate tunnels and LSPs with identical configuration properties. o System-wide capabilities that affect the originating, traversing and terminating LSPs. For example: o Flooding parameters o CSPF metric (TE or IGP) o Handling for over-loaded nodes o (Soft) preemption parameters o Path protection parameters at the head-end LSR o Fast reroute parameters 2. Global MPLS-TE state data model: The global MPLS-TE state data model is a read-only YANG data model. This module defines system- wide operational data for various MPLS-TE features. Examples of such system-wide MPLS-TE states are: o Global statistics (signaling, admission, preemption, flooding) o Global counters (number of tunnel-interfaces/LSPs/links) 3. Global MPLS-TE execution data model: The global MPLS-TE execution model facilitates issuing commands to an LSR node and optionally returning responses. This model uses RPC operations and contains optional read-only input and output data. Examples of such global MPLS-TE commands are: o Clear global MPLS-TE statistics of various features 4. Global MPLS-TE events notification data model: The global MPLS- TE events notification model uses configuration data for registration. Node notifies the registered events to the server using notification messages. Notifications carry read-only data in the messages. Example of such global MPLS-TE events are: o Backup tunnel FRR active and not-active state transition events Gandhi, et al. Expires April 16, 2015 [Page 5] Internet-Draft Yang Data Model Trees for MPLS TE October 13, 2014 4.2. MPLS-TE Tunnel Interface Data Model Overview This module defines configuration data, operational state data, execution commands and event notifications for MPLS-TE tunnel interfaces and is applicable to head-end LSRs. 1. MPLS-TE tunnel interface configuration data model: The configuration data model is a read-write YANG data model. This module defines configuration items for the MPLS-TE tunnel interfaces. Examples of such configuration items are: o Name o Admin-state o Tunnel-type (such as P2P, P2MP) o Tunnel usage (auto-route announce, forwarding adjacency) o Static route information o LDP over tunnel parameters o Quality of Service (QoS) policy parameters o Policy based routing (PBR) parameters 2. MPLS-TE tunnel interface state data model: The MPLS-TE tunnel interface state data model is a read-only YANG data model. This module defines operational state data for MPLS-TE tunnel interfaces at the head-end LSRs. Examples of such MPLS-TE tunnel interface states are: o Name o Tunnel interface creation information (time and trigger: static-configuration/auto-tunnel) o State information (Up/Down: when and reason) o Traffic counters for the tunnel interface o History of events 3. MPLS-TE tunnel interface execution data model: The execution model facilitates issuing commands to an LSR node and optionally returning responses. This model uses RPC operations and contains optional read-only input and output data. Example commands for MPLS- TE tunnel interfaces are: o Clear statistics for all or for individual tunnel interfaces 4. MPLS-TE tunnel interface events notification data model: The notification model uses configuration data for registration. Node notifies the registered events to the server using notification messages. Notifications carry read-only data in the messages. Example events for MPLS-TE tunnel interfaces are: o Tunnel interface creation and deletion events Gandhi, et al. Expires April 16, 2015 [Page 6] Internet-Draft Yang Data Model Trees for MPLS TE October 13, 2014 o Tunnel interface state transition events 4.3. MPLS-TE Tunnel LSP Data Model Overview This module defines configuration data, operational state data, execution commands and event notifications for MPLS-TE tunnel LSPs and is applicable to head-end, mid-point and tail-end LSRs. 1. MPLS-TE tunnel LSP configuration data model: The configuration data model is a read-write YANG data model component. This module defines configuration items for the MPLS-TE tunnel LSP properties. Examples of such MPLS-TE tunnel LSP configuration items are: o Name o Bandwidth and class-type o Set-up and hold priority o Path-computation parameters (dynamic path, explicit path, cost-limit, hop-limit, metric type) o Affinity parameters (colors) o SRLG parameters 2. MPLS-TE tunnel LSP state data model: The MPLS-TE tunnel LSP state data model is a read-only YANG data model. This model defines the operational state data for MPLS-TE tunnel LSPs for head-end, mid- point and tail-end LSRs. Example states data for MPLS-TE tunnel LSPs are: o Name o LSP creation information (time) o State information (Up/Down: when and reason) o MPLS-TE attribute-set name o Signaling information (Explicit Route Object, Record Route Object, bandwidth, egress and ingress links) o FRR information (status, type of protection, backup tunnel) o Soft preemption information o Path protection information o Statistics o History of events 3. MPLS-TE tunnel LSP execution data model: The execution model facilitates issuing commands to an LSR node and optionally returning responses. This model uses RPC operations and contains optional read-only input and output data. Examples of such commands for MPLS-TE tunnel LSPs are: o Trigger re-optimization on all or on individual LSP o Trigger path protection switchover on an individual LSP o Trigger LSP path switchover on an individual LSP Gandhi, et al. Expires April 16, 2015 [Page 7] Internet-Draft Yang Data Model Trees for MPLS TE October 13, 2014 o Clear TE statistics for all or for individual LSPs 4. MPLS-TE tunnel LSP events notification data model: The notification model uses configuration data for registration. Node notifies the registered events to the server using notification messages. Notifications carry read-only data in the messages. Examples of such events for MPLS-TE LSPs are: o LSP creation and deletion events o LSP state transition events o LSP re-optimization including trigger reason o Fast Reroute (protection availability, activation) events o LSP signaling events o Auto-bandwidth changes o Path protection events o (Soft) Preemption events 4.4. MPLS-TE Link Data Model Overview This module defines configuration data, operational state data, execution commands and event notifications for MPLS-TE enabled links on an LSR. 1. MPLS-TE link configuration data model: The configuration data model is a read-write YANG data model component. This model defines configuration items for MPLS-TE enabled links used to advertise in TE topology database. Examples of such configuration items for MPLS-TE enabled links are: o Name o Maximum reservable bandwidth, bandwidth constraints (BC) values o (Extended) Administrative groups (AGs and EAGs) o SRLG values o TE metric o Flooding parameters o Flooding frequency o RSVP Parameters o RSVP authentication parameters o RSVP refresh reduction parameters o RSVP hello parameters o RSVP graceful restart (GR) o Fast reroute backup tunnel information (static, auto-tunnel) 2. MPLS-TE link state data model: The MPLS-TE link state model is a read-only YANG data model. This model defines operational state data for MPLS-TE enabled links for an LSR node. Examples of such state data for MPLS-TE links are: Gandhi, et al. Expires April 16, 2015 [Page 8] Internet-Draft Yang Data Model Trees for MPLS TE October 13, 2014 o Name o State information (UP/Down: when and reason) o IGP information o IGP neighbor o IGP metric o Bandwidth information: maximum bandwidth, reserved bandwidth at different priorities, available bandwidth at different priorities and for each class-type (CT) o Diff-Serve model (RDM, MAM) o List of admitted LSPs (name, bandwidth value and pool, time, priority) o Statistics: state counters, flooding counters, admission counters (accepted/rejected), preemption counters o History of events 3. MPLS-TE link execution data model: The execution model facilitates issuing commands to an LSR node and optionally returning responses. This model uses RPC operations and contains optional read-only input and output data. Examples of such commands for MPLS- TE links are: o Clear TE statistics for all or for individual links o Trigger immediate flooding for all TE links 4. MPLS-TE link events notification data model: The notification model uses configuration data for registration. Node notifies the registered events to the server using notification messages. Notifications carry read-only data in the messages. Example events for MPLS-TE links are as following: o Link creation and deletion events o Link state transition events o (Soft) preemption trigger events o Fast reroute activation events 5. High-level Tree Structure of MPLS-TE Data Model The module, "ietf-mpls-te", defines the YANG data model for various management components (configuration, operational, execution and notification) within MPLS-TE. The data module includes modules for global MPLS-TE, tunnel interfaces, tunnel LSPs and links and the tree structure is organized as shown below. The following notations are used for the data tree. Gandhi, et al. Expires April 16, 2015 [Page 9] Internet-Draft Yang Data Model Trees for MPLS TE October 13, 2014 is one of: + for current x for deprecated o for obsolete is one of: rw for read-write configuration data ro for read-only non-configuration data -x for execution rpcs -n for notifications is the name of the node If the node is augmented into the tree from another module, its name is printed as : is one of: ? for an optional leaf or node ! for a presence container * for a leaf-list or list Brackets [] for a list's keys Curly braces {} for optional feature that make node conditional Colon : for marking case nodes Ellipses ("...") subtree contents not shown is the name of the type for leafs and leaf-lists. module ietf-mpls-te +--rw mpls-te-global +--ro mpls-te-global-state +---x mpls-te-global-rpcs +---n mpls-te-global-notifications +--rw mpls-te-tunnel-ifs +--ro mpls-te-tunnel-ifs-state +---x mpls-te-tunnel-ifs-rpcs +---n mpls-te-tunnel-ifs-notifications +--rw mpls-te-lsps +--ro mpls-te-lsps-state +---x mpls-te-lsps-rpcs +---n mpls-te-lsps-notifications +--rw mpls-te-links +--ro mpls-te-links-state +---x mpls-te-links-rpcs +---n mpls-te-links-notifications Gandhi, et al. Expires April 16, 2015 [Page 10] Internet-Draft Yang Data Model Trees for MPLS TE October 13, 2014 As shown, data tree structure is organized by MPLS-TE data modules, which are global MPLS-TE, tunnel interfaces, tunnel LSPs and links. Each of this data model module contains various management components including configuration, operation, execution and notification. 6. MPLS-TE Global Data Model Tree Structure This document defines the YANG module "ietf-mpls-te-global", which has the following tree structure: +--rw mpls-te-global | +--rw mpls-te-attribute-sets | | +--rw attribute-set* [name] | | +--rw name string | +--rw mpls-te-mesh-groups | | +--rw mesh-group* [mesh-group-value] | | +--rw mesh-group-value int32 | | +--rw attribute-set string | +--rw mpls-te-auto-backup | | +--rw enabled boolean | | +--rw attribute-set string | +--rw mpls-te-global-configuration-to-be-defined +--ro mpls-te-global-state | +--ro mpls-te-attribute-sets-state | | +--ro attribute-set* [name] | | +--ro name string | +--ro mpls-te-mesh-groups-state | | +--ro mesh-group* [mesh-group-value] | | +--ro mesh-group-value int32 | +--ro mpls-te-global-operational-state-to-be-defined +---x mpls-te-global-rpcs | +---x te-global-rpcs-to-be-defined +---n mpls-te-global-notifications | +---n te-global-notifications-to-be-defined 6.1. MPLS-TE Global Attribute-set Lists The data model for mpls-te-attribute-sets presented in this document uses a flat list of attribute-sets. Each attribute-set in the list is identified by its name. An attribute-set is a configuration template that can be used to instantiate tunnels and LSPs with identical properties. There is one list for MPLS-TE attribute-set configurations ("/mpls-te-attribute-sets/attribute-set") and a separate list for operational state data ("/mpls-te-attribute-sets-state/attribute- Gandhi, et al. Expires April 16, 2015 [Page 11] Internet-Draft Yang Data Model Trees for MPLS TE October 13, 2014 set"). 6.2. MPLS-TE Global Mesh-group Lists The data model for mpls-te-mesh-groups presented in this document uses a flat list of mesh-groups. Each mesh-group in the list is identified by its mesh-group-value. There is one list for MPLS-TE mesh-group configurations ("/mpls-te-mesh-groups/mesh-group"), and a separate list for operational state data ("/mpls-te-mesh-groups-state/mesh-group"). 7. MPLS-TE Tunnel Interfaces Data Model Tree Structure This document defines the YANG module "ietf-mpls-te-tunnel-ifs", which has the following tree structure: +--rw mpls-te-tunnel-ifs | +--rw tunnel-if* [name] | | +--rw name string | | +--rw tunnel-type identityref | | +--rw tunnel-if-configuration-to-be-defined +--ro mpls-te-tunnel-ifs-state | +--ro tunnel-if* [name] | | +--ro name string | | +--ro tunnel-type identityref | | +--ro tunnel-if-operational-state-to-be-defined +---x mpls-te-tunnel-ifs-rpcs | +---x tunnel-if-rpcs-to-be-defined +---n mpls-te-tunnel-ifs-notifications | +---n tunnel-if-notifications-to-be-defined 7.1. MPLS-TE Tunnel Interface Lists The data model for mpls-te-tunnel-ifs presented in this document uses a flat list of tunnel-ifs. Each tunnel interface in the list is identified by its name. Furthermore, each tunnel interface has a mandatory "tunnel-type" leaf. There is one list for configured MPLS-TE tunnel interfaces ("/mpls-te-tunnel-ifs/tunnel-if"), and a separate list for the operational state of all MPLS-TE tunnel interfaces ("/mpls-te-tunnel-ifs-state/tunnel-if"). Gandhi, et al. Expires April 16, 2015 [Page 12] Internet-Draft Yang Data Model Trees for MPLS TE October 13, 2014 8. MPLS-TE Tunnel LSPs Data Model Tree Structure This document defines the YANG module "ietf-mpls-te-lsps", which has the following tree structure: +--rw mpls-te-lsps | +--rw te-lsp* [name] | | +--rw name string | | +--rw lsp-configuration-to-be-defined +--ro mpls-te-lsps-state | +--ro te-lsp* [name] | | +--ro name string | | +--ro lsp-operational-state-to-be-defined +---x mpls-te-lsps-rpcs | +---x lsp-rpcs-to-be-defined +---n mpls-te-lsps-notifications | +---n lsp-notifications-to-be-defined 8.1. MPLS-TE Tunnel LSP Lists The data model for mpls-te-lsps presented in this document uses a flat list of te-lsps. Each LSP in the list is identified by its name. There is one list for MPLS-TE tunnel LSP configurations ("/mpls-te-lsps/te-lsp"), and a separate list for the operational state of all MPLS-TE tunnel LSPs ("/mpls-te-lsps-state/te-lsp"). 9. MPLS-TE Links Data Model Tree Structure This document defines the YANG module "ietf-mpls-te-links", which has the following tree structure: +--rw mpls-te-links | +--rw te-link* [name] | | +--rw name string | | +--rw link-configuration-to-be-defined +--ro mpls-te-links-state | +--ro te-link* [name] | | +--ro name string | | +--ro link-operational-state-to-be-defined +---x mpls-te-links-rpcs | +---x link-rpcs-to-be-defined +---n mpls-te-links-notifications | +---n link-notifications-to-be-defined Gandhi, et al. Expires April 16, 2015 [Page 13] Internet-Draft Yang Data Model Trees for MPLS TE October 13, 2014 9.1. MPLS-TE Link Lists The data model for mpls-te-links presented in this document uses a flat list of te-links. Each link in the list is identified by its name. There is one list for MPLS-TE link configurations ("/mpls-te-links/te-link"), and a separate list for the operational state of all MPLS-TE links ("/mpls-te-links-state/te-link"). 10. MPLS-TE Global YANG Module file "ietf-mpls-te-global@2014-10-13.yang" module ietf-mpls-te-global { namespace "urn:ietf:params:xml:ns:yang:ietf-mpls-te:ietf-mpls-te- global"; organization "IETF NETMOD (NETCONF Data Modeling Language) Working Group"; contact "WG Web: WG List: mailto:netmod@ietf.org"; description "This module contains a collection of YANG definitions for managing MPLS-TE Global Data. Copyright (c) 2014 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info). This version of this YANG module is part of RFC XXXX; see the RFC itself for full legal notices."; reference "RFC XXXX: YANG Data Models for MPLS-TE Tunnels and Links"; /* * YANG Module to be defined in the next revision. */ Gandhi, et al. Expires April 16, 2015 [Page 14] Internet-Draft Yang Data Model Trees for MPLS TE October 13, 2014 } 11. MPLS-TE Tunnel Interfaces YANG Module An MPLS-TE tunnel interface is identified by its name. file "ietf-mpls-te-tunnel-ifs@2014-10-13.yang" module ietf-mpls-te-tunnel-ifs { namespace "urn:ietf:params:xml:ns:yang:ietf-mpls-te:ietf-mpls-te-tunnel- ifs"; organization "IETF NETMOD (NETCONF Data Modeling Language) Working Group"; contact "WG Web: WG List: mailto:netmod@ietf.org"; description "This module contains a collection of YANG definitions for managing MPLS-TE tunnel interfaces. Copyright (c) 2014 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info). This version of this YANG module is part of RFC XXXX; see the RFC itself for full legal notices."; /* * YANG Module to be defined in the next revision. */ } 12. MPLS-TE Tunnel LSP YANG Module Gandhi, et al. Expires April 16, 2015 [Page 15] Internet-Draft Yang Data Model Trees for MPLS TE October 13, 2014 An MPLS-TE tunnel LSP is identified by its name. file "ietf-mpls-te-lsps@2014-10-13.yang" module ietf-mpls-te-lsps { namespace "urn:ietf:params:xml:ns:yang:ietf-mpls-te:ietf-mpls-te-lsps"; organization "IETF NETMOD (NETCONF Data Modeling Language) Working Group"; contact "WG Web: WG List: mailto:netmod@ietf.org"; description "This module contains a collection of YANG definitions for managing MPLS-TE LSPs. Copyright (c) 2014 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info). This version of this YANG module is part of RFC XXXX; see the RFC itself for full legal notices."; /* * YANG Module to be defined in the next revision. */ } 13. MPLS-TE Links YANG Module An MPLS-TE link is identified by its name. file "ietf-mpls-te-links@2014-10-13.yang" module ietf-mpls-te-links { namespace Gandhi, et al. Expires April 16, 2015 [Page 16] Internet-Draft Yang Data Model Trees for MPLS TE October 13, 2014 "urn:ietf:params:xml:ns:yang:ietf-mpls-te:ietf-mpls-te-links"; organization "IETF NETMOD (NETCONF Data Modeling Language) Working Group"; contact "WG Web: WG List: mailto:netmod@ietf.org"; description "This module contains a collection of YANG definitions for managing MPLS-TE Links. Copyright (c) 2014 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info). This version of this YANG module is part of RFC XXXX; see the RFC itself for full legal notices."; /* * YANG Module to be defined in the next revision. */ } 14. IANA Considerations This document registers a URI 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-te:ietf-mpls-te-global XML: N/A, the requested URI is an XML namespace. URI: urn:ietf:params:xml:ns:yang:ietf-mpls-te:ietf-mpls-te-tunnel- ifs XML: N/A, the requested URI is an XML namespace. URI: urn:ietf:params:xml:ns:yang:ietf-mpls-te:ietf-mpls-te-lsps XML: N/A, the requested URI is an XML namespace. URI: urn:ietf:params:xml:ns:yang:ietf-mpls-te:ietf-mpls-te-links Gandhi, et al. Expires April 16, 2015 [Page 17] Internet-Draft Yang Data Model Trees for MPLS TE October 13, 2014 XML: N/A, the requested URI is an XML namespace. This document registers a YANG module in the YANG Module Names registry [RFC6020]. name: ietf-mpls-te-global namespace: urn:ietf:params:xml:ns:yang:ietf-mpls-te:ietf-mpls-te- global prefix: te-global reference: RFC XXXX name: ietf-mpls-te-tunnel-ifs namespace: urn:ietf:params:xml:ns:yang:ietf-mpls-te:ietf-mpls-te- tunnel-ifs prefix: te-if reference: RFC XXXX name: ietf-mpls-te-lsps namespace: urn:ietf:params:xml:ns:yang:ietf-mpls-te:ietf-mpls-te- lsps prefix: te-lsp reference: RFC XXXX name: ietf-mpls-te-links namespace: urn:ietf:params:xml:ns:yang:ietf-mpls-te:ietf-mpls-te- links prefix: te-link reference: RFC XXXX 15. 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. Following are the subtrees and data nodes and their sensitivity/vulnerability: Gandhi, et al. Expires April 16, 2015 [Page 18] Internet-Draft Yang Data Model Trees for MPLS TE October 13, 2014 /mpls-te-global: This module specifies the global MPLS-TE configurations on a device. Unauthorized access to this list could cause the device to ignore packets it should receive and process. /mpls-te-tunnel-ifs/tunnel-if: This list specifies the configured MPLS-TE tunnel interfaces on a device. Unauthorized access to this list could cause the device to ignore packets it should receive and process. /mpls-te-lsps/te-lsp: This list specifies the configured MPLS-TE LSPs on a device. Unauthorized access to this list could cause the device to ignore packets it should receive and process. /mpls-te-links/te-link: This list specifies the configured MPLS-TE links on a device. Unauthorized access to this list could cause the device to ignore packets it should receive and process. 16. Acknowledgement TBA. 17. References 17.1. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group MIB", RFC 2863, June 2000. [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, January 2004. [RFC6020] Bjorklund, M., "YANG - A Data Modeling Language for the Network Configuration Protocol (NETCONF)", RFC 6020, October 2010. [RFC6991] Schoenwaelder, J., "Common YANG Data Types", RFC 6991, July 2013. 17.2. Informative References [RFC2205] Braden, B., Zhang, L., Berson, S., Herzog, S., and S. Jamin, "Resource ReSerVation Protocol (RSVP) -- Version 1 Functional Specification", RFC 2205, September 1997. Gandhi, et al. Expires April 16, 2015 [Page 19] Internet-Draft Yang Data Model Trees for MPLS TE October 13, 2014 [RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan, V., and G. Swallow, "RSVP-TE: Extensions to RSVP for LSP Tunnels", RFC 3209, December 2001. [RFC6241] Enns, R., Bjorklund, M., Schoenwaelder, J., and A. Bierman, "Network Configuration Protocol (NETCONF)", RFC 6241, June 2011. [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure Shell (SSH)", RFC 6242, June 2011. [RFC6536] Bierman, A. and M. Bjorklund, "Network Configuration Protocol (NETCONF) Access Control Model", RFC 6536, March 2012. [I-D.ietf-netmod-routing-cfg] Lhotka, L., "A YANG Data Model for Routing Management", draft-ietf-netmod-routing-cfg-15 (work in progress), May 2014. [I-D.ietf-netmod-rfc6087bis] Bierman, A., "Guidelines for Authors and Reviewers of YANG Data Model Documents", draft-ietf-netmod-rfc6087bis-00 (work in progress), June 2014. 18. Authors' Addresses Rakesh Gandhi Cisco Systems, Inc. Email: rgandhi@cisco.com Tarek Saad Cisco Systems, Inc. Email: tsaad@cisco.com Robert Sawaya Cisco Systems, Inc. Email: rsawaya@cisco.com Gandhi, et al. Expires April 16, 2015 [Page 20] Internet-Draft Yang Data Model Trees for MPLS TE October 13, 2014 Gandhi, et al. Expires April 16, 2015 [Page 21]