< draft-ietf-isis-sr-yang-02.txt   draft-ietf-isis-sr-yang-03.txt >
IS-IS Working Group S. Litkowski IS-IS Working Group S. Litkowski
Internet-Draft Orange Internet-Draft Orange
Intended status: Standards Track Y. Qu Intended status: Standards Track Y. Qu
Expires: January 26, 2018 Huawei Expires: July 19, 2018 Huawei
P. Sarkar P. Sarkar
Individual Individual
I. Chen I. Chen
Jabil Jabil
J. Tantsura J. Tantsura
Individual Individual
July 25, 2017 January 15, 2018
YANG Data Model for IS-IS Segment Routing YANG Data Model for IS-IS Segment Routing
draft-ietf-isis-sr-yang-02 draft-ietf-isis-sr-yang-03
Abstract Abstract
This document defines a YANG data model that can be used to configure This document defines a YANG data model that can be used to configure
and manage IS-IS Segment Routing and manage IS-IS Segment Routing
([I-D.ietf-isis-segment-routing-extensions]. ([I-D.ietf-isis-segment-routing-extensions].
Requirements Language Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
skipping to change at page 1, line 45 skipping to change at page 1, line 45
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on January 26, 2018. This Internet-Draft will expire on July 19, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2018 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 2, line 34 skipping to change at page 2, line 34
3. IS-IS Segment Routing configuration . . . . . . . . . . . . . 5 3. IS-IS Segment Routing configuration . . . . . . . . . . . . . 5
3.1. Segment Routing activation . . . . . . . . . . . . . . . 5 3.1. Segment Routing activation . . . . . . . . . . . . . . . 5
3.2. Advertising mapping server policy . . . . . . . . . . . . 5 3.2. Advertising mapping server policy . . . . . . . . . . . . 5
3.3. IP Fast reroute . . . . . . . . . . . . . . . . . . . . . 5 3.3. IP Fast reroute . . . . . . . . . . . . . . . . . . . . . 5
4. IS-IS Segment Routing YANG Module . . . . . . . . . . . . . . 5 4. IS-IS Segment Routing YANG Module . . . . . . . . . . . . . . 5
5. Security Considerations . . . . . . . . . . . . . . . . . . . 20 5. Security Considerations . . . . . . . . . . . . . . . . . . . 20
6. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 20 6. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 20
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 20 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 20
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 20 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 20
9. Change log for ietf-isis-sr YANG module . . . . . . . . . . . 21 9. Change log for ietf-isis-sr YANG module . . . . . . . . . . . 21
9.1. From isis-sr document version -01 to version -02 . . . . 21 9.1. From version -02 to version -03 . . . . . . . . . . . . . 21
9.2. From isis-sr document version -00 to version -01 . . . . 21 9.2. From isis-sr document version -01 to version -02 . . . . 21
9.3. From isis document version -12 to isis-sr document 9.3. From isis-sr document version -00 to version -01 . . . . 21
9.4. From isis document version -12 to isis-sr document
version -00 . . . . . . . . . . . . . . . . . . . . . . . 21 version -00 . . . . . . . . . . . . . . . . . . . . . . . 21
9.4. From isis document version -12 to version -13 . . . . . . 21 9.5. From isis document version -12 to version -13 . . . . . . 21
9.5. From isis document version -09 to version -11 . . . . . . 21 9.6. From isis document version -09 to version -11 . . . . . . 22
9.6. From isis document version -08 to version -09 . . . . . . 22 9.7. From isis document version -08 to version -09 . . . . . . 22
9.7. From isis document version -07 to version -08 . . . . . . 22 9.8. From isis document version -07 to version -08 . . . . . . 22
10. Normative References . . . . . . . . . . . . . . . . . . . . 22 10. Normative References . . . . . . . . . . . . . . . . . . . . 22
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 23 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 23
1. Overview 1. Overview
YANG [RFC6020] [RFC7950] is a data definition language used to YANG [RFC6020] [RFC7950] is a data definition language used to
define the contents of a conceptual data store that allows networked define the contents of a conceptual data store that allows networked
devices to be managed using NETCONF [RFC6241]. YANG is proving devices to be managed using NETCONF [RFC6241]. YANG is proving
relevant beyond its initial confines, as bindings to other interfaces relevant beyond its initial confines, as bindings to other interfaces
(e.g., ReST) and encodings other than XML (e.g., JSON) are being (e.g., ReST) and encodings other than XML (e.g., JSON) are being
skipping to change at page 3, line 58 skipping to change at page 4, line 4
+--rw ti-lfa {ti-lfa}? +--rw ti-lfa {ti-lfa}?
+--rw enable? boolean +--rw enable? boolean
augment /rt:routing/rt:control-plane-protocols/rt:control-plane-protocol augment /rt:routing/rt:control-plane-protocols/rt:control-plane-protocol
/isis:isis/isis:interfaces/isis:interface/isis:fast-reroute/isis:lfa/isi /isis:isis/isis:interfaces/isis:interface/isis:fast-reroute/isis:lfa/isi
s:remote-lfa: s:remote-lfa:
+--rw use-segment-routing-path? boolean {remote-lfa-sr}? +--rw use-segment-routing-path? boolean {remote-lfa-sr}?
augment /rt:routing/rt:control-plane-protocols/rt:control-plane-protocol augment /rt:routing/rt:control-plane-protocols/rt:control-plane-protocol
/isis:isis/isis:interfaces/isis:interface/isis:adjacencies/isis:adjacenc /isis:isis/isis:interfaces/isis:interface/isis:adjacencies/isis:adjacenc
y: y:
+--ro adjacency-sid* [value] +--ro adjacency-sid* [value]
+--ro af? identityref +--ro af? iana-rt-types:address-family
+--ro value uint32 +--ro value uint32
+--ro weight? uint8 +--ro weight? uint8
+--ro protection-requested? boolean +--ro protection-requested? boolean
augment /rt:routing/rt:control-plane-protocols/rt:control-plane-protocol augment /rt:routing/rt:control-plane-protocols/rt:control-plane-protocol
/isis:isis/isis:database/isis:level-db/isis:lsp/isis:router-capabilities /isis:isis/isis:database/isis:level-db/isis:lsp/isis:router-capabilities
: :
+--ro sr-capability +--ro sr-capability
| +--ro flags? bits | +--ro flags? bits
| +--ro global-blocks | +--ro global-blocks
| +--ro global-block* | +--ro global-block*
skipping to change at page 5, line 43 skipping to change at page 5, line 44
3.3. IP Fast reroute 3.3. IP Fast reroute
IS-IS SR model augments the fast-reroute container under interface. IS-IS SR model augments the fast-reroute container under interface.
It brings the ability to activate TI-LFA (topology independent LFA) It brings the ability to activate TI-LFA (topology independent LFA)
and also enhances remote LFA to use segment-routing tunneling instead and also enhances remote LFA to use segment-routing tunneling instead
of LDP. of LDP.
4. IS-IS Segment Routing YANG Module 4. IS-IS Segment Routing YANG Module
<CODE BEGINS> file "ietf-isis-sr@2017-07-25.yang" <CODE BEGINS> file "ietf-isis-sr@2018-01-15.yang"
module ietf-isis-sr { module ietf-isis-sr {
namespace "urn:ietf:params:xml:ns:" namespace "urn:ietf:params:xml:ns:"
+ "yang:ietf-isis-sr"; + "yang:ietf-isis-sr";
prefix isis-sr; prefix isis-sr;
import ietf-routing { import ietf-routing {
prefix "rt"; prefix "rt";
} }
import ietf-segment-routing-common { import ietf-segment-routing-common {
prefix "sr-cmn"; prefix "sr-cmn";
} }
import ietf-segment-routing { import ietf-segment-routing {
prefix "sr"; prefix "sr";
} }
skipping to change at page 6, line 50 skipping to change at page 6, line 50
Jeff Tantsura Jeff Tantsura
&lt;mailto:jefftant.ietf@gmail.com&gt; &lt;mailto:jefftant.ietf@gmail.com&gt;
"; ";
description description
"The YANG module defines a generic configuration model for "The YANG module defines a generic configuration model for
Segment routing ISIS extensions common across all of the vendor Segment routing ISIS extensions common across all of the vendor
implementations."; implementations.";
revision 2017-07-25 { revision 2018-01-15 {
description description
"Initial revision."; "Initial revision.";
reference "RFC XXXX"; reference "RFC XXXX";
} }
/* Identities */ /* Identities */
/* Features */ /* Features */
feature remote-lfa-sr { feature remote-lfa-sr {
skipping to change at page 9, line 40 skipping to change at page 9, line 41
} }
} }
grouping adjacency-state { grouping adjacency-state {
description description
"This group will extend adjacency state."; "This group will extend adjacency state.";
list adjacency-sid { list adjacency-sid {
key value; key value;
config false; config false;
leaf af { leaf af {
type identityref { type iana-rt-types:address-family;
base iana-rt-types:address-family;
}
description description
"Address-family associated with the "Address-family associated with the
segment ID"; segment ID";
} }
leaf value { leaf value {
type uint32; type uint32;
description description
"Value of the Adj-SID."; "Value of the Adj-SID.";
} }
leaf weight { leaf weight {
skipping to change at page 21, line 19 skipping to change at page 21, line 19
This document also requests one new YANG module name in the YANG This document also requests one new YANG module name in the YANG
Module Names registry ([RFC6020]) with the following suggestion : Module Names registry ([RFC6020]) with the following suggestion :
name: ietf-isis-sr name: ietf-isis-sr
namespace: urn:ietf:params:xml:ns:yang:ietf-isis-sr namespace: urn:ietf:params:xml:ns:yang:ietf-isis-sr
prefix: isis-sr prefix: isis-sr
reference: RFC XXXX reference: RFC XXXX
9. Change log for ietf-isis-sr YANG module 9. Change log for ietf-isis-sr YANG module
9.1. From isis-sr document version -01 to version -02 9.1. From version -02 to version -03
o Change address-family type according to routing types.
9.2. From isis-sr document version -01 to version -02
o NMDA compliancy. o NMDA compliancy.
o Added SRLB in configuration and LSDB. o Added SRLB in configuration and LSDB.
o Added SR capability in LSDB. o Added SR capability in LSDB.
o Added SR algorithms in LSDB. o Added SR algorithms in LSDB.
o Added SRMS preference in LSDB. o Added SRMS preference in LSDB.
o Alignment with iana-rt-types module. o Alignment with iana-rt-types module.
o Align binding SID with draft-ietf-isis-segment-routing-extensions- o Align binding SID with draft-ietf-isis-segment-routing-extensions-
13. 13.
9.2. From isis-sr document version -00 to version -01 9.3. From isis-sr document version -00 to version -01
o Added P-Flag in Adj-SID. o Added P-Flag in Adj-SID.
9.3. From isis document version -12 to isis-sr document version -00 9.4. From isis document version -12 to isis-sr document version -00
o Separate document for IS-IS SR extensions. o Separate document for IS-IS SR extensions.
9.4. From isis document version -12 to version -13 9.5. From isis document version -12 to version -13
o Align with new segment routing common module. o Align with new segment routing common module.
9.5. From isis document version -09 to version -11 9.6. From isis document version -09 to version -11
o Fixed XPATH in 'when' expressions. o Fixed XPATH in 'when' expressions.
9.6. From isis document version -08 to version -09 9.7. From isis document version -08 to version -09
o Align to draft-ietf-netmod-routing-cfg-23. o Align to draft-ietf-netmod-routing-cfg-23.
9.7. From isis document version -07 to version -08 9.8. From isis document version -07 to version -08
o Align to draft-ietf-netmod-routing-cfg-21. o Align to draft-ietf-netmod-routing-cfg-21.
10. Normative References 10. Normative References
[I-D.ietf-isis-segment-routing-extensions] [I-D.ietf-isis-segment-routing-extensions]
Previdi, S., Filsfils, C., Bashandy, A., Gredler, H., Previdi, S., Ginsberg, L., Filsfils, C., Bashandy, A.,
Litkowski, S., Decraene, B., and j. jefftant@gmail.com, Gredler, H., Litkowski, S., Decraene, B., and J. Tantsura,
"IS-IS Extensions for Segment Routing", draft-ietf-isis- "IS-IS Extensions for Segment Routing", draft-ietf-isis-
segment-routing-extensions-13 (work in progress), June segment-routing-extensions-15 (work in progress), December
2017. 2017.
[I-D.ietf-isis-yang-isis-cfg] [I-D.ietf-isis-yang-isis-cfg]
Litkowski, S., Yeung, D., Lindem, A., Zhang, Z., and L. Litkowski, S., Yeung, D., Lindem, A., Zhang, Z., and L.
Lhotka, "YANG Data Model for IS-IS protocol", draft-ietf- Lhotka, "YANG Data Model for IS-IS protocol", draft-ietf-
isis-yang-isis-cfg-17 (work in progress), March 2017. isis-yang-isis-cfg-19 (work in progress), November 2017.
[I-D.ietf-spring-sr-yang] [I-D.ietf-spring-sr-yang]
Litkowski, S., Qu, Y., Sarkar, P., and J. Tantsura, "YANG Litkowski, S., Qu, Y., Sarkar, P., and J. Tantsura, "YANG
Data Model for Segment Routing", draft-ietf-spring-sr- Data Model for Segment Routing", draft-ietf-spring-sr-
yang-07 (work in progress), July 2017. yang-08 (work in progress), December 2017.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/ Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/
RFC2119, March 1997, RFC2119, March 1997, <https://www.rfc-editor.org/info/
<http://www.rfc-editor.org/info/rfc2119>. rfc2119>.
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
DOI 10.17487/RFC3688, January 2004, DOI 10.17487/RFC3688, January 2004, <https://www.rfc-
<http://www.rfc-editor.org/info/rfc3688>. editor.org/info/rfc3688>.
[RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for
the Network Configuration Protocol (NETCONF)", RFC 6020, the Network Configuration Protocol (NETCONF)", RFC 6020,
DOI 10.17487/RFC6020, October 2010, DOI 10.17487/RFC6020, October 2010, <https://www.rfc-
<http://www.rfc-editor.org/info/rfc6020>. editor.org/info/rfc6020>.
[RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed.,
and A. Bierman, Ed., "Network Configuration Protocol and A. Bierman, Ed., "Network Configuration Protocol
(NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011,
<http://www.rfc-editor.org/info/rfc6241>. <https://www.rfc-editor.org/info/rfc6241>.
[RFC6536] Bierman, A. and M. Bjorklund, "Network Configuration [RFC6536] Bierman, A. and M. Bjorklund, "Network Configuration
Protocol (NETCONF) Access Control Model", RFC 6536, DOI Protocol (NETCONF) Access Control Model", RFC 6536, DOI
10.17487/RFC6536, March 2012, 10.17487/RFC6536, March 2012, <https://www.rfc-
<http://www.rfc-editor.org/info/rfc6536>. editor.org/info/rfc6536>.
[RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language",
RFC 7950, DOI 10.17487/RFC7950, August 2016, RFC 7950, DOI 10.17487/RFC7950, August 2016,
<http://www.rfc-editor.org/info/rfc7950>. <https://www.rfc-editor.org/info/rfc7950>.
Authors' Addresses Authors' Addresses
Stephane Litkowski Stephane Litkowski
Orange Orange
Email: stephane.litkowski@orange.com Email: stephane.litkowski@orange.com
Yinghzen Qu Yinghzen Qu
Huawei Huawei
 End of changes. 29 change blocks. 
41 lines changed or deleted 43 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/