--- 1/draft-ietf-isis-sr-yang-04.txt 2019-03-10 06:13:47.643415394 -0700 +++ 2/draft-ietf-isis-sr-yang-05.txt 2019-03-10 06:13:47.723417321 -0700 @@ -1,113 +1,126 @@ IS-IS Working Group S. Litkowski Internet-Draft Orange Intended status: Standards Track Y. Qu -Expires: December 31, 2018 Huawei +Expires: September 11, 2019 Huawei P. Sarkar Individual I. Chen - Jabil + The MITRE Corporation J. Tantsura Individual - June 29, 2018 + March 10, 2019 YANG Data Model for IS-IS Segment Routing - draft-ietf-isis-sr-yang-04 + draft-ietf-isis-sr-yang-05 Abstract This document defines a YANG data model that can be used to configure - and manage IS-IS Segment Routing - ([I-D.ietf-isis-segment-routing-extensions]. - -Requirements Language - - The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", - "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this - document are to be interpreted as described in [RFC2119]. + and manage IS-IS Segment Routing. 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 December 31, 2018. + This Internet-Draft will expire on September 11, 2019. Copyright Notice - Copyright (c) 2018 IETF Trust and the persons identified as the + 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 (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. IS-IS Segment Routing . . . . . . . . . . . . . . . . . . . . 3 - 3. IS-IS Segment Routing configuration . . . . . . . . . . . . . 6 - 3.1. Segment Routing activation . . . . . . . . . . . . . . . 6 - 3.2. Advertising mapping server policy . . . . . . . . . . . . 6 - 3.3. IP Fast reroute . . . . . . . . . . . . . . . . . . . . . 6 - 4. IS-IS Segment Routing YANG Module . . . . . . . . . . . . . . 6 - 5. Security Considerations . . . . . . . . . . . . . . . . . . . 20 - 6. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 20 - 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 21 - 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 21 - 9. Change log for ietf-isis-sr YANG module . . . . . . . . . . . 21 - 9.1. From version -03 to version -04 . . . . . . . . . . . . . 21 - 9.2. From version -02 to version -03 . . . . . . . . . . . . . 21 - 9.3. From isis-sr document version -01 to version -02 . . . . 21 - 9.4. From isis-sr document version -00 to version -01 . . . . 22 - 9.5. From isis document version -12 to isis-sr document - version -00 . . . . . . . . . . . . . . . . . . . . . . . 22 - 9.6. From isis document version -12 to version -13 . . . . . . 22 - 9.7. From isis document version -09 to version -11 . . . . . . 22 - 9.8. From isis document version -08 to version -09 . . . . . . 22 - 9.9. From isis document version -07 to version -08 . . . . . . 22 - 10. Normative References . . . . . . . . . . . . . . . . . . . . 22 - Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 23 + 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 . . . . . . . . . . . . . . . . . . . 20 + 8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 21 + 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 21 + 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 21 + 11. Change log for ietf-isis-sr YANG module . . . . . . . . . . . 21 + 11.1. From version -03 to version -04 . . . . . . . . . . . . 21 + 11.2. From version -02 to version -03 . . . . . . . . . . . . 21 + 11.3. From isis-sr document version -01 to version -02 . . . . 22 + 11.4. From isis-sr document version -00 to version -01 . . . . 22 + 11.5. From isis document version -12 to isis-sr document + version -00 . . . . . . . . . . . . . . . . . . . . . . 22 + 11.6. From isis document version -12 to version -13 . . . . . 22 + 11.7. From isis document version -09 to version -11 . . . . . 22 + 11.8. From isis document version -08 to version -09 . . . . . 22 + 11.9. From isis document version -07 to version -08 . . . . . 22 + 12. Normative References . . . . . . . . . . . . . . . . . . . . 22 + Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 24 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 + 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 and it is an augmentation to the IS- - IS YANG data model. + and manage IS-IS Segment Routing -2. IS-IS Segment Routing + [I-D.ietf-isis-segment-routing-extensions] and it is an augmentation + to the IS-IS YANG data model. + + The YANG modules in this document conform to the Network Management + Datastore Architecture (NMDA) [RFC8342]. + +2. 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 + + This document uses the graphical representation of data models + defined in [RFC8340]. + +4. 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. @@ -228,48 +240,48 @@ +--ro fec string +--ro range uint16 +--ro flags? bits +--ro binding +--ro prefix-sid +--ro sid-list* [value] +--ro flags? bits +--ro algorithm? uint8 +--ro value uint32 -3. IS-IS Segment Routing configuration +5. IS-IS Segment Routing configuration -3.1. Segment Routing activation +5.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. -3.2. Advertising mapping server policy +5.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. -3.3. IP Fast reroute +5.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. -4. IS-IS Segment Routing YANG Module +6. IS-IS Segment Routing YANG Module - file "ietf-isis-sr@2018-06-25.yang" + file "ietf-isis-sr@2019-03-06.yang" module ietf-isis-sr { namespace "urn:ietf:params:xml:ns:" + "yang:ietf-isis-sr"; prefix isis-sr; import ietf-routing { prefix "rt"; } import ietf-segment-routing-common { @@ -293,48 +305,46 @@ contact "WG List: Editor: Stephane Litkowski Author: Acee Lindem Author: Yingzhen Qu - + Author: Pushpasis Sarkar Author: Ing-Wher Chen - + Author: Jeff Tantsura "; description "The YANG module defines a generic configuration model for Segment routing ISIS extensions common across all of the vendor implementations."; - revision 2018-06-25 { + revision 2019-03-06 { description "Initial revision."; reference "RFC XXXX"; } - /* Identities */ /* Features */ feature remote-lfa-sr { description "Enhance rLFA to use SR path."; - } feature ti-lfa { description "Enhance IPFRR with ti-lfa support"; } /* Groupings */ @@ -718,42 +729,42 @@ "/isis:isis" { 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 configuration with segment routing."; - uses sr:controlplane-cfg; + uses sr:sr-controlplane; container protocol-srgb { if-feature sr:protocol-srgb; - uses sr-cmn:srgb-cfg; + uses sr-cmn:srgb; description "Per-protocol SRGB."; } } augment "/rt:routing/" + "rt:control-plane-protocols/rt:control-plane-protocol"+ "/isis:isis/isis:interfaces/isis:interface" { 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 configuration with segment routing."; - uses sr:igp-interface-cfg; + uses sr:igp-interface; } augment "/rt:routing/" + "rt:control-plane-protocols/rt:control-plane-protocol"+ "/isis:isis/isis:interfaces/isis:interface"+ "/isis:fast-reroute" { when "/rt:routing/rt:control-plane-protocols/"+ "rt:control-plane-protocol/rt:type = 'isis:isis'" { description "This augment ISIS routing protocol when used"; @@ -926,123 +937,127 @@ description "This augments ISIS protocol LSDB."; uses segment-routing-binding-tlv; } /* Notifications */ } -5. Security Considerations +7. Security Considerations Configuration and state data defined in this document are designed to be accessed via the NETCONF protocol [RFC6241]. As IS-IS is an IGP protocol (critical piece of the network), ensuring stability and security of the protocol is mandatory for the network service. Authors recommends to implement NETCONF access control model ([RFC6536]) to restrict access to all or part of the configuration to specific users. -6. Contributors +8. Contributors Authors would like to thank Derek Yeung, Acee Lindem, Yi Yang for their major contributions to the draft. -7. Acknowledgements +9. Acknowledgements - TBD. + Author affiliation with The MITRE Corporation is provided for + identification purposes only, and is not intended to convey or imply + MITRE's concurrence with, or support for, the positions, opinions or + viewpoints expressed. MITRE has approved this document for Public + Release, Distribution Unlimited, with Public Release Case Number + 18-3281. -8. IANA Considerations +10. 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 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 -9. Change log for ietf-isis-sr YANG module +11. Change log for ietf-isis-sr YANG module -9.1. From version -03 to version -04 +11.1. From version -03 to version -04 o Fixed yang module indentations. -9.2. From version -02 to version -03 +11.2. From version -02 to version -03 o Change address-family type according to routing types. -9.3. From isis-sr document version -01 to version -02 +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. -9.4. From isis-sr document version -00 to version -01 +11.4. From isis-sr document version -00 to version -01 o Added P-Flag in Adj-SID. -9.5. From isis document version -12 to isis-sr document version -00 +11.5. From isis document version -12 to isis-sr document version -00 o Separate document for IS-IS SR extensions. -9.6. From isis document version -12 to version -13 +11.6. From isis document version -12 to version -13 o Align with new segment routing common module. -9.7. From isis document version -09 to version -11 +11.7. From isis document version -09 to version -11 o Fixed XPATH in 'when' expressions. -9.8. From isis document version -08 to version -09 +11.8. From isis document version -08 to version -09 o Align to draft-ietf-netmod-routing-cfg-23. -9.9. From isis document version -07 to version -08 +11.9. From isis document version -07 to version -08 o Align to draft-ietf-netmod-routing-cfg-21. -10. Normative References +12. Normative References [I-D.ietf-isis-segment-routing-extensions] Previdi, S., Ginsberg, L., Filsfils, C., Bashandy, A., Gredler, H., Litkowski, S., Decraene, B., and J. Tantsura, "IS-IS Extensions for Segment Routing", draft-ietf-isis- - segment-routing-extensions-15 (work in progress), December - 2017. + segment-routing-extensions-22 (work in progress). [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-19 (work in progress), November 2017. + Lhotka, "YANG Data Model for IS-IS Protocol", draft-ietf- + isis-yang-isis-cfg-35 (work in progress), March 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-08 (work in progress), December 2017. [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, . @@ -1063,35 +1078,49 @@ [RFC6536] Bierman, A. and M. Bjorklund, "Network Configuration Protocol (NETCONF) Access Control Model", RFC 6536, DOI 10.17487/RFC6536, March 2012, . [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", RFC 7950, DOI 10.17487/RFC7950, August 2016, . + [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC + 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, + May 2017, . + + [RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams", + BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018, + . + + [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, + . + Authors' Addresses Stephane Litkowski Orange Email: stephane.litkowski@orange.com Yinghzen Qu Huawei Email: yingzhen.qu@huawei.com Pushpasis Sarkar Individual Email: pushpasis.ietf@gmail.com Ing-Wher Chen - Jabil + The MITRE Corporation + + Email: ingwherchen@mitre.org - Email: ing-wher_chen@jabil.com Jeff Tantsura Individual Email: jefftant.ietf@gmail.com