--- 1/draft-ietf-isis-sr-yang-09.txt 2021-02-21 14:13:43.935351887 -0800 +++ 2/draft-ietf-isis-sr-yang-10.txt 2021-02-21 14:13:43.971352348 -0800 @@ -1,124 +1,349 @@ IS-IS Working Group S. Litkowski Internet-Draft Cisco Systems Intended status: Standards Track Y. Qu -Expires: July 15, 2021 Futurewei +Expires: August 25, 2021 Futurewei P. Sarkar Individual I. Chen The MITRE Corporation J. Tantsura Apstra - January 11, 2021 + February 21, 2021 YANG Data Model for IS-IS Segment Routing - draft-ietf-isis-sr-yang-09 + draft-ietf-isis-sr-yang-10 Abstract - This document defines a YANG data model that can be used to configure - and manage IS-IS Segment Routing. + This document defines a YANG data module that can be used to + configure and manage IS-IS Segment Routing, as well as a YANG data + module for the management of Signaling Maximum SID Depth (MSD) Using + IS-IS. 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 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 July 15, 2021. + This Internet-Draft will expire on August 25, 2021. Copyright Notice Copyright (c) 2021 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 (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. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 2 - 2. Requirements Language . . . . . . . . . . . . . . . . . . . . 3 - 3. Tree Diagrams . . . . . . . . . . . . . . . . . . . . . . . . 3 - 4. IS-IS Segment Routing . . . . . . . . . . . . . . . . . . . . 3 - 5. IS-IS Segment Routing configuration . . . . . . . . . . . . . 6 - 5.1. Segment Routing activation . . . . . . . . . . . . . . . 6 - 5.2. Advertising mapping server policy . . . . . . . . . . . . 6 - 5.3. IP Fast reroute . . . . . . . . . . . . . . . . . . . . . 6 - 6. IS-IS Segment Routing YANG Module . . . . . . . . . . . . . . 6 - 7. Security Considerations . . . . . . . . . . . . . . . . . . . 21 - 8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 22 - 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 23 - 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 23 - 11. Change log for ietf-isis-sr YANG module . . . . . . . . . . . 23 - 11.1. From version -03 to version -04 . . . . . . . . . . . . 23 - 11.2. From version -02 to version -03 . . . . . . . . . . . . 23 - 11.3. From isis-sr document version -01 to version -02 . . . . 23 - 11.4. From isis-sr document version -00 to version -01 . . . . 24 - 11.5. From isis document version -12 to isis-sr document - version -00 . . . . . . . . . . . . . . . . . . . . . . 24 - 11.6. From isis document version -12 to version -13 . . . . . 24 - 11.7. From isis document version -09 to version -11 . . . . . 24 - 11.8. From isis document version -08 to version -09 . . . . . 24 - 11.9. From isis document version -07 to version -08 . . . . . 24 - 12. Normative References . . . . . . . . . . . . . . . . . . . . 24 - Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 26 + 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3 + 1.2. Tree Diagrams . . . . . . . . . . . . . . . . . . . . . . 3 + 2. IS-IS MSD . . . . . . . . . . . . . . . . . . . . . . . . . . 3 + 2.1. IS-IS MSD YANG Module . . . . . . . . . . . . . . . . . . 4 + 3. IS-IS Segment Routing . . . . . . . . . . . . . . . . . . . . 8 + 3.1. IS-IS Segment Routing configuration . . . . . . . . . . . 11 + 3.1.1. Segment Routing activation . . . . . . . . . . . . . 11 + 3.1.2. Advertising mapping server policy . . . . . . . . . . 11 + 3.1.3. IP Fast reroute . . . . . . . . . . . . . . . . . . . 11 + 3.2. IS-IS Segment Routing YANG Module . . . . . . . . . . . . 11 + 4. Security Considerations . . . . . . . . . . . . . . . . . . . 26 + 5. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 27 + 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 27 + 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 27 + 8. Normative References . . . . . . . . . . . . . . . . . . . . 28 + Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 30 1. Overview YANG [RFC6020] [RFC7950] is a data definition language used to define the contents of a conceptual data store that allows networked devices to be managed using NETCONF [RFC6241]. YANG is proving relevant beyond its initial confines, as bindings to other interfaces (e.g., ReST) and encodings other than XML (e.g., JSON) are being defined. Furthermore, YANG data models can be used as the basis for implementation of other interfaces, such as CLI and programmatic APIs. - This document defines a YANG data model that can be used to configure - and manage IS-IS Segment Routing [RFC8667] and it is an augmentation - to the IS-IS YANG data model. + This document defines a YANG data module that can be used to + configure and manage IS-IS Segment Routing [RFC8667] and it is an + augmentation to the IS-IS YANG data model. + + This document also defines a YANG data module for the management of + Signaling Maximum SID Depth (MSD) Using IS-IS [RFC8491], which + augments the base IS-IS YANG data model. The YANG modules in this document conform to the Network Management Datastore Architecture (NMDA) [RFC8342]. -2. Requirements Language +1.1. Requirements Language The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here. -3. Tree Diagrams +1.2. Tree Diagrams This document uses the graphical representation of data models defined in [RFC8340]. -4. IS-IS Segment Routing +2. IS-IS MSD + + This document defines a model for Signaling Maximum SID Depth (MSD) + Using IS-IS[RFC8667]. It is an augmentation of the IS-IS base model. + + The figure below describes the overall structure of the isis-msd YANG + module: + + module: ietf-isis-msd + augment /rt:routing/rt:control-plane-protocols + /rt:control-plane-protocol/isis:isis/isis:database + /isis:levels/isis:lsp/isis:router-capabilities: + +--ro node-msd-tlv + +--ro node-msds* [msd-type] + +--ro msd-type identityref + +--ro msd-value? uint8 + augment /rt:routing/rt:control-plane-protocols + /rt:control-plane-protocol/isis:isis/isis:database + /isis:levels/isis:lsp/isis:extended-is-neighbor + /isis:neighbor: + +--ro link-msd-sub-tlv + +--ro link-msds* [msd-type] + +--ro msd-type identityref + +--ro msd-value? uint8 + augment /rt:routing/rt:control-plane-protocols + /rt:control-plane-protocol/isis:isis/isis:database + /isis:levels/isis:lsp/isis:mt-is-neighbor/isis:neighbor: + +--ro link-msd-sub-tlv + +--ro link-msds* [msd-type] + +--ro msd-type identityref + +--ro msd-value? uint8 + +2.1. IS-IS MSD YANG Module + + file "ietf-isis-msd@2021-02-21.yang" + module ietf-isis-msd { + yang-version 1.1; + namespace "urn:ietf:params:xml:ns:yang:ietf-isis-msd"; + prefix isis-msd; + + import ietf-routing { + prefix rt; + reference "RFC 8349: A YANG Data Model for Routing + Management (NMDA Version)"; + } + + import ietf-isis { + prefix isis; + } + + organization + "IETF LSR - LSR Working Group"; + contact + "WG Web: + WG List: + + Author: Yingzhen Qu + + Author: Acee Lindem + + Author: Stephane Litkowski + + Author: Jeff Tantsura + + + "; + description + "The YANG module augments the base ISIS model to + manage different types of MSDs. + + This YANG model conforms to the Network Management + Datastore Architecture (NMDA) as described in RFC 8342. + + Copyright (c) 2021 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 + (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. + + The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL + NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'NOT RECOMMENDED', + 'MAY', and 'OPTIONAL' in this document are to be interpreted as + described in BCP 14 (RFC 2119) (RFC 8174) when, and only when, + they appear in all capitals, as shown here."; + + reference "RFC XXXX: YANG Data Model for OSPF MSD."; + + revision 2021-02-21 { + description + "Initial Version"; + reference "RFC XXXX: YANG Data Model for ISIS MSD."; + } + + identity msd-base-type { + description + "Base identity for MSD Type"; + } + + identity base-mpls-msd { + base msd-base-type; + description + "Base MPLS Imposition MSD."; + reference + "RFC 8491: Singling MSD using IS-IS."; + } + + identity erld-msd { + base msd-base-type; + description + "ERLD-MSD is defined to advertise the ERLD."; + reference + "RFC 8662: Entropy Label for Source Packet Routing in + Networking (SPRING) Tunnels"; + } + + grouping node-msd-tlv { + description + "Grouping for node MSD."; + container node-msd-tlv { + list node-msds { + key "msd-type"; + leaf msd-type { + type identityref { + base msd-base-type; + } + description + "MSD-Types"; + } + leaf msd-value { + type uint8; + description + "MSD value, in the range of 0-255."; + } + description + "Node MSD is the smallest link MSD supported by + the node."; + } + description + "Node MSD is the number of SIDs supported by a node."; + reference + "RFC 8476: Signaling Maximum SID Depth (MSD) Using OSPF"; + } + } + + grouping link-msd-sub-tlv { + description + "Link Maximum SID Depth (MSD) grouping for an interface."; + container link-msd-sub-tlv { + list link-msds { + key "msd-type"; + leaf msd-type { + type identityref { + base msd-base-type; + } + description + "MSD-Types"; + } + leaf msd-value { + type uint8; + description + "MSD value, in the range of 0-255."; + } + description + "List of link MSDs"; + } + description + "Link MSD sub-tlvs."; + } + + } + + /* Node MSD TLV */ + augment "/rt:routing/" + + "rt:control-plane-protocols/rt:control-plane-protocol"+ + "/isis:isis/isis:database/isis:levels/isis:lsp"+ + "/isis:router-capabilities" { + when "/rt:routing/rt:control-plane-protocols/"+ + "rt:control-plane-protocol/rt:type = 'isis:isis'" { + description + "This augment ISIS routing protocol when used"; + } + description + "This augments ISIS protocol LSDB router capability."; + uses node-msd-tlv; + } + + /* link MSD sub-tlv */ + augment "/rt:routing/" + + "rt:control-plane-protocols/rt:control-plane-protocol"+ + "/isis:isis/isis:database/isis:levels/isis:lsp"+ + "/isis:extended-is-neighbor/isis:neighbor" { + when "/rt:routing/rt:control-plane-protocols/"+ + "rt:control-plane-protocol/rt:type = 'isis:isis'" { + description + "This augment ISIS routing protocol when used"; + } + description + "This augments ISIS protocol LSDB neighbor with + Link MSD sub-TLV."; + + uses link-msd-sub-tlv; + } + + augment "/rt:routing/" + + "rt:control-plane-protocols/rt:control-plane-protocol"+ + "/isis:isis/isis:database/isis:levels/isis:lsp"+ + "/isis:mt-is-neighbor/isis:neighbor" { + when "/rt:routing/rt:control-plane-protocols/"+ + "rt:control-plane-protocol/rt:type = 'isis:isis'" { + description + "This augment ISIS routing protocol when used"; + } + description + "This augments ISIS protocol LSDB neighbor."; + + uses link-msd-sub-tlv; + + } + } + + +3. IS-IS Segment Routing This document defines a model for IS-IS Segment Routing feature. It is an augmentation of the IS-IS base model. The IS-IS SR YANG module requires support for the base segment routing module [I-D.ietf-spring-sr-yang], which defines the global segment routing configuration independent of any specific routing protocol configuration, and support of IS-IS base model [I-D.ietf-isis-yang-isis-cfg] which defines basic IS-IS configuration and state. @@ -250,46 +474,46 @@ +--ro sid-binding-flags | +--ro bits* identityref +--ro binding +--ro prefix-sid +--ro sid-list* [value] +--ro perfix-sid-flags | +--ro bits* identityref +--ro algorithm? uint8 +--ro value uint32 -5. IS-IS Segment Routing configuration +3.1. IS-IS Segment Routing configuration -5.1. Segment Routing activation +3.1.1. Segment Routing activation Activation of segment-routing IS-IS is done by setting the "enable" leaf to true. This triggers advertisement of segment-routing extensions based on the configuration parameters that have been setup using the base segment routing module. -5.2. Advertising mapping server policy +3.1.2. Advertising mapping server policy The base segment routing module defines mapping server policies. By default, IS-IS will not advertise nor receive any mapping server entry. The IS-IS segment-routing module allows to advertise one or multiple mapping server policies through the "bindings/advertise/ policies" leaf-list. The "bindings/receive" leaf allows to enable the reception of mapping server entries. -5.3. IP Fast reroute +3.1.3. IP Fast reroute IS-IS SR model augments the fast-reroute container under interface. It brings the ability to activate TI-LFA (topology independent LFA) and also enhances remote LFA to use segment-routing tunneling instead of LDP. -6. IS-IS Segment Routing YANG Module +3.2. IS-IS Segment Routing YANG Module file "ietf-isis-sr@2021-01-11.yang" module ietf-isis-sr { yang-version 1.1; namespace "urn:ietf:params:xml:ns:" + "yang:ietf-isis-sr"; prefix isis-sr; import ietf-routing { prefix "rt"; @@ -990,21 +1220,21 @@ description "This augments ISIS protocol LSDB."; uses segment-routing-binding-tlv; } /* Notifications */ } -7. Security Considerations +4. Security Considerations The YANG module specified in this document defines a schema for data that is designed to be accessed via network management protocols such as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF layer is the secure transport layer, and the mandatory-to-implement secure transport is Secure Shell (SSH) [RFC6242]. The lowest RESTCONF layer is HTTPS, and the mandatory-to-implement secure transport is TLS [RFC8446]. The NETCONF Access Control Model (NACM) [RFC8341] provides the means @@ -1032,104 +1262,64 @@ notification) to these data nodes. /isis:router-capabilities/sr-capability /isis:router-capabilities/sr-algorithms /isis:router-capabilities/local-blocks /isis:router-capabilities/srms-preference + /isis:router-capabilities/node-msd-tlv + And the augmentations to the ISIS link state database. Unauthorized access to any data node of these subtrees can disclose the operational state information of IS-IS protocol on this device. -8. Contributors +5. Contributors Authors would like to thank Derek Yeung, Acee Lindem, Yi Yang for their major contributions to the draft. -9. Acknowledgements +6. Acknowledgements MITRE has approved this document for Public Release, Distribution Unlimited, with Public Release Case Number 19-3033. -10. IANA Considerations +7. IANA Considerations The IANA is requested to assign two new URIs from the IETF XML registry ([RFC3688]). Authors are suggesting the following URI: URI: urn:ietf:params:xml:ns:yang:ietf-isis-sr - Registrant Contact: IS-IS WG + Registrant Contact: The IESG. + XML: N/A, the requested URI is an XML namespace + + URI: urn:ietf:params:xml:ns:yang:ietf-isis-msd + Registrant Contact: The IESG. XML: N/A, the requested URI is an XML namespace This document also requests one new YANG module name in the YANG Module Names registry ([RFC6020]) with the following suggestion : name: ietf-isis-sr namespace: urn:ietf:params:xml:ns:yang:ietf-isis-sr prefix: isis-sr reference: RFC XXXX -11. Change log for ietf-isis-sr YANG module - -11.1. From version -03 to version -04 - - o Fixed yang module indentations. - -11.2. From version -02 to version -03 - - o Change address-family type according to routing types. - -11.3. From isis-sr document version -01 to version -02 - - o NMDA compliancy. - - o Added SRLB in configuration and LSDB. - - o Added SR capability in LSDB. - - o Added SR algorithms in LSDB. - - o Added SRMS preference in LSDB. - - o Alignment with iana-rt-types module. - - o Align binding SID with draft-ietf-isis-segment-routing-extensions- - 13. - -11.4. From isis-sr document version -00 to version -01 - - o Added P-Flag in Adj-SID. - -11.5. From isis document version -12 to isis-sr document version -00 - - o Separate document for IS-IS SR extensions. - -11.6. From isis document version -12 to version -13 - - o Align with new segment routing common module. - -11.7. From isis document version -09 to version -11 - - o Fixed XPATH in 'when' expressions. - -11.8. From isis document version -08 to version -09 - - o Align to draft-ietf-netmod-routing-cfg-23. - -11.9. From isis document version -07 to version -08 - - o Align to draft-ietf-netmod-routing-cfg-21. + name: ietf-isis-msd + namespace: urn:ietf:params:xml:ns:yang:ietf-isis-msd + prefix: isis-msd + reference: RFC XXXX -12. Normative References +8. Normative References [I-D.ietf-isis-yang-isis-cfg] Litkowski, S., Yeung, D., Lindem, A., Zhang, Z., and L. Lhotka, "YANG Data Model for IS-IS Protocol", draft-ietf- isis-yang-isis-cfg-42 (work in progress), October 2019. [I-D.ietf-spring-sr-yang] Litkowski, S., Qu, Y., Sarkar, P., and J. Tantsura, "YANG Data Model for Segment Routing", draft-ietf-spring-sr- yang-15 (work in progress), December 2017. @@ -1185,20 +1375,25 @@ [RFC8342] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K., and R. Wilton, "Network Management Datastore Architecture (NMDA)", RFC 8342, DOI 10.17487/RFC8342, March 2018, . [RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018, . + [RFC8491] Tantsura, J., Chunduri, U., Aldrin, S., and L. Ginsberg, + "Signaling Maximum SID Depth (MSD) Using IS-IS", RFC 8491, + DOI 10.17487/RFC8491, November 2018, + . + [RFC8667] Previdi, S., Ed., Ginsberg, L., Ed., Filsfils, C., Bashandy, A., Gredler, H., and B. Decraene, "IS-IS Extensions for Segment Routing", RFC 8667, DOI 10.17487/RFC8667, December 2019, . Authors' Addresses Stephane Litkowski Cisco Systems