A YANG Data Model for Traffic Engineering Tunnels and Interfaces
draft-ietf-teas-yang-te-14
The information below is for an old version of the document.
Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Active".
|
|
---|---|---|---|
Authors | Tarek Saad , Rakesh Gandhi , Xufeng Liu , Vishnu Pavan Beeram , Himanshu C. Shah , Igor Bryskin | ||
Last updated | 2018-03-05 | ||
Replaces | draft-saad-teas-yang-te | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Formats | |||
Reviews |
YANGDOCTORS Early review
(of
-21)
by Radek Krejčí
On the Right Track
|
||
Additional resources | Mailing list discussion | ||
Stream | WG state | WG Document | |
Document shepherd | (None) | ||
IESG | IESG state | I-D Exists | |
Consensus boilerplate | Unknown | ||
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
draft-ietf-teas-yang-te-14
quot;; } enum seamless { description "BFD seamless session type."; } } default "classical"; description "Type of BFD session"; } Saad, et al. Expires September 6, 2018 [Page 160] Internet-Draft TE YANG Data Model March 2018 typedef bfd-encap-mode-type { type enumeration { enum gal { description "BFD with GAL mode"; } enum ip { description "BFD with IP mode"; } } default ip; description "Possible BFD transport modes when running over TE LSPs."; } } <CODE ENDS> Figure 11: TE MPLS types YANG module <CODE BEGINS> file "ietf-te-sr-mpls@2018-02-15.yang" module ietf-te-sr-mpls { namespace "urn:ietf:params:xml:ns:yang:ietf-te-sr-mpls"; /* Replace with IANA when assigned */ prefix "te-sr-mpls"; /* Import TE generic types */ import ietf-te { prefix te; } /* Import TE generic types */ import ietf-te-types { prefix te-types; } organization "IETF Traffic Engineering Architecture and Signaling (TEAS) Working Group"; contact "WG Web: <http://tools.ietf.org/wg/teas/> WG List: <mailto:teas@ietf.org> WG Chair: Lou Berger Saad, et al. Expires September 6, 2018 [Page 161] Internet-Draft TE YANG Data Model March 2018 <mailto:lberger@labn.net> WG Chair: Vishnu Pavan Beeram <mailto:vbeeram@juniper.net> Editor: Tarek Saad <mailto:tsaad@cisco.com> Editor: Rakesh Gandhi <mailto:rgandhi@cisco.com> Editor: Vishnu Pavan Beeram <mailto:vbeeram@juniper.net> Editor: Himanshu Shah <mailto:hshah@ciena.com> Editor: Xufeng Liu <mailto:xufeng.liu@ericsson.com> Editor: Xia Chen <mailto:jescia.chenxia@huawei.com> Editor: Raqib Jones <mailto:raqib@Brocade.com> Editor: Bin Wen <mailto:Bin_Wen@cable.comcast.com>"; description "YANG data module for MPLS TE configurations, state, RPC and notifications."; revision "2018-02-15" { description "Latest update to MPLS TE YANG module."; reference "TBD"; } identity sr-protection-type { description "The Adj-SID base protection types"; } identity sr-protection-type-protected { base sr-protection-type; description "The Adj-SID is eligible if protected"; } Saad, et al. Expires September 6, 2018 [Page 162] Internet-Draft TE YANG Data Model March 2018 identity sr-protection-type-unprotected { base sr-protection-type; description "The Adj-SID is eligible if unprotected"; } identity sr-protection-type-any { base sr-protection-type; description "The Adj-SID is eligible if protected or unprotected"; } typedef te-sid-selection-mode { type enumeration { enum ADJ_SID_ONLY { description "The SR-TE tunnel should only use adjacency SIDs to build the SID stack to be pushed for the LSP"; } enum MIXED_MODE { description "The SR-TE tunnel can use a mix of adjacency and prefix SIDs to build the SID stack to be pushed to the LSP"; } } description "SID selection mode type"; } /* MPLS SR-TE tunnel properties*/ grouping tunnel-sr-mpls-properties_config { description "MPLS TE SR tunnel properties"; leaf path-signaling-type { type identityref { base te-types:path-signaling-type; } description "TE tunnel path signaling type"; } } grouping te-sr-named-path-constraints_config { description "Configuration parameters relating to SR-TE LSPs"; leaf sid-selection-mode { type te-sid-selection-mode; default MIXED_MODE; description Saad, et al. Expires September 6, 2018 [Page 163] Internet-Draft TE YANG Data Model March 2018 "The restrictions placed on the SIDs to be selected by the calculation method for the explicit path when it is instantiated for a SR-TE LSP"; } leaf sid-protection { type identityref { base sr-protection-type; } default sr-protection-type-any; description "When set to protected only SIDs that are protected are to be selected by the calculating method when the explicit path is instantiated by a SR-TE LSP."; } } grouping te-sr-named-path-constraints { description "Named TE SR path constraints grouping"; uses te-sr-named-path-constraints_config; } /*** End of MPLS SR-TE tunnel configuration/state */ /** * MPLS TE augmentations */ augment "/te:te/te:globals/te:named-path-constraints" + "/te:named-path-constraint" { description "Augmentations for MPLS SR-TE config named constraints"; uses te-sr-named-path-constraints; } /* MPLS TE tunnel augmentations */ /* MPLS TE LSPs augmentations */ } <CODE ENDS> Figure 12: SR TE MPLS YANG module 5. 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. Saad, et al. Expires September 6, 2018 [Page 164] Internet-Draft TE YANG Data Model March 2018 URI: urn:ietf:params:xml:ns:yang:ietf-te XML: N/A, the requested URI is an XML namespace. URI: urn:ietf:params:xml:ns:yang:ietf-te-device XML: N/A, the requested URI is an XML namespace. URI: urn:ietf:params:xml:ns:yang:ietf-te-mpls XML: N/A, the requested URI is an XML namespace. URI: urn:ietf:params:xml:ns:yang:ietf-te-sr-mpls XML: N/A, the requested URI is an XML namespace. URI: urn:ietf:params:xml:ns:yang:ietf-te-types XML: N/A, the requested URI is an XML namespace. URI: urn:ietf:params:xml:ns:yang:ietf-te-mpls-types 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-te namespace: urn:ietf:params:xml:ns:yang:ietf-te prefix: ietf-te reference: RFC3209 name: ietf-te-device namespace: urn:ietf:params:xml:ns:yang:ietf-te prefix: ietf-te-device reference: RFC3209 name: ietf-te-mpls namespace: urn:ietf:params:xml:ns:yang:ietf-te- mpls prefix: ietf-te-mpls reference: RFC3209 name: ietf-te-sr-mpls namespace: urn:ietf:params:xml:ns:yang:ietf-te- sr-mpls prefix: ietf-te-sr-mpls name: ietf-te-types namespace: urn:ietf:params:xml:ns:yang:ietf-te- types prefix: ietf-te-types reference: RFC3209 name: ietf-te-mpls-types namespace: urn:ietf:params:xml:ns:yang:ietf- te-mpls-types prefix: ietf-te-mpls-types reference: RFC3209 6. 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 Saad, et al. Expires September 6, 2018 [Page 165] Internet-Draft TE YANG Data Model March 2018 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., <edit-config>) 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: "/te/globals": This module specifies the global TE configurations on a device. Unauthorized access to this container could cause the device to ignore packets it should receive and process. "/te/tunnels": This list specifies the configured TE tunnels on a device. Unauthorized access to this list could cause the device to ignore packets it should receive and process. "/te/lsps-state": This list specifies the state derived LSPs. Unauthorized access to this list could cause the device to ignore packets it should receive and process. "/te/interfaces": This list specifies the configured TE interfaces on a device. Unauthorized access to this list could cause the device to ignore packets it should receive and process. 7. Acknowledgement The authors would like to thank the members of the multi-vendor YANG design team who are involved in the definition of this model. The authors would also like to thank Loa Andersson, Lou Berger, Sergio Belotti, Italo Busi, Carlo Perocchio, Francesco Lazzeri, Aihua Guo, Dhruv Dhody, Anurag Sharma, and Xian Zhang for their comments and providing valuable feedback on this document. 8. Contributors Saad, et al. Expires September 6, 2018 [Page 166] Internet-Draft TE YANG Data Model March 2018 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 9. Normative References [I-D.ietf-teas-yang-rsvp] Beeram, V., Saad, T., Gandhi, R., Liu, X., Bryskin, I., and H. Shah, "A YANG Data Model for Resource Reservation Protocol (RSVP)", draft-ietf-teas-yang-rsvp-08 (work in progress), October 2017. [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, <https://www.rfc-editor.org/info/rfc2119>. [RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan, V., and G. Swallow, "RSVP-TE: Extensions to RSVP for LSP Tunnels", RFC 3209, DOI 10.17487/RFC3209, December 2001, <https://www.rfc-editor.org/info/rfc3209>. [RFC3473] Berger, L., Ed., "Generalized Multi-Protocol Label Switching (GMPLS) Signaling Resource ReserVation Protocol- Traffic Engineering (RSVP-TE) Extensions", RFC 3473, DOI 10.17487/RFC3473, January 2003, <https://www.rfc-editor.org/info/rfc3473>. [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, DOI 10.17487/RFC3688, January 2004, <https://www.rfc-editor.org/info/rfc3688>. Saad, et al. Expires September 6, 2018 [Page 167] Internet-Draft TE YANG Data Model March 2018 [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for the Network Configuration Protocol (NETCONF)", RFC 6020, DOI 10.17487/RFC6020, October 2010, <https://www.rfc-editor.org/info/rfc6020>. [RFC6107] Shiomoto, K., Ed. and A. Farrel, Ed., "Procedures for Dynamically Signaled Hierarchical Label Switched Paths", RFC 6107, DOI 10.17487/RFC6107, February 2011, <https://www.rfc-editor.org/info/rfc6107>. [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, <https://www.rfc-editor.org/info/rfc6241>. [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011, <https://www.rfc-editor.org/info/rfc6242>. [RFC6536] Bierman, A. and M. Bjorklund, "Network Configuration Protocol (NETCONF) Access Control Model", RFC 6536, DOI 10.17487/RFC6536, March 2012, <https://www.rfc-editor.org/info/rfc6536>. [RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types", RFC 6991, DOI 10.17487/RFC6991, July 2013, <https://www.rfc-editor.org/info/rfc6991>. [RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017, <https://www.rfc-editor.org/info/rfc8040>. Authors' Addresses Tarek Saad (editor) Cisco Systems Inc Email: tsaad@cisco.com Rakesh Gandhi Cisco Systems Inc Email: rgandhi@cisco.com Saad, et al. Expires September 6, 2018 [Page 168] Internet-Draft TE YANG Data Model March 2018 Xufeng Liu Jabil Email: Xufeng_Liu@jabil.com 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 Saad, et al. Expires September 6, 2018 [Page 169]