< draft-ietf-isis-sr-yang-00.txt   draft-ietf-isis-sr-yang-01.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: May 7, 2017 Cisco Expires: November 6, 2017 Huawei
P. Sarkar P. Sarkar
Individual Individual
I. Chen I. Chen
Kuatro Technologies Jabil
J. Tantsura J. Tantsura
Individual Individual
November 03, 2016 May 05, 2017
YANG Data Model for IS-IS Segment Routing YANG Data Model for IS-IS Segment Routing
draft-ietf-isis-sr-yang-00 draft-ietf-isis-sr-yang-01
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 May 7, 2017. This Internet-Draft will expire on November 6, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2017 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
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 2
2. IS-IS Segment Routing . . . . . . . . . . . . . . . . . . . . 3 2. IS-IS Segment Routing . . . . . . . . . . . . . . . . . . . . 3
3. IS-IS Segment Routing configuration . . . . . . . . . . . . . 5 3. IS-IS Segment Routing configuration . . . . . . . . . . . . . 6
3.1. Segment Routing activation . . . . . . . . . . . . . . . 5 3.1. Segment Routing activation . . . . . . . . . . . . . . . 6
3.2. Advertising mapping server policy . . . . . . . . . . . . 5 3.2. Advertising mapping server policy . . . . . . . . . . . . 6
3.3. IP Fast reroute . . . . . . . . . . . . . . . . . . . . . 5 3.3. IP Fast reroute . . . . . . . . . . . . . . . . . . . . . 6
4. IS-IS Segment Routing YANG Module . . . . . . . . . . . . . . 6 4. IS-IS Segment Routing YANG Module . . . . . . . . . . . . . . 6
5. Security Considerations . . . . . . . . . . . . . . . . . . . 20 5. Security Considerations . . . . . . . . . . . . . . . . . . . 21
6. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 20 6. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 21
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 20 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 21
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 21 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 21
9. Change log for ietf-isis-sr YANG module . . . . . . . . . . . 21 9. Change log for ietf-isis-sr YANG module . . . . . . . . . . . 22
9.1. From isis document version -12 to isis-sr document 9.1. From isis document version -12 to isis-sr document
version -00 . . . . . . . . . . . . . . . . . . . . . . . 21 version -00 . . . . . . . . . . . . . . . . . . . . . . . 22
9.2. From isis document version -12 to version -13 . . . . . . 21 9.2. From isis document version -12 to version -13 . . . . . . 22
9.3. From isis document version -09 to version -11 . . . . . . 21 9.3. From isis document version -09 to version -11 . . . . . . 22
9.4. From isis document version -08 to version -09 . . . . . . 21 9.4. From isis document version -08 to version -09 . . . . . . 22
9.5. From isis document version -07 to version -08 . . . . . . 21 9.5. From isis document version -07 to version -08 . . . . . . 22
10. Normative References . . . . . . . . . . . . . . . . . . . . 21 9.6. From isis-sr document version -00 to version -01 . . . . 22
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 22 10. Normative References . . . . . . . . . . . . . . . . . . . . 22
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
defined. Furthermore, YANG data models can be used as the basis for defined. Furthermore, YANG data models can be used as the basis for
implementation of other interfaces, such as CLI and programmatic implementation of other interfaces, such as CLI and programmatic
skipping to change at page 3, line 24 skipping to change at page 3, line 26
The IS-IS SR YANG module requires support for the base segment The IS-IS SR YANG module requires support for the base segment
routing module [I-D.ietf-spring-sr-yang], which defines the global routing module [I-D.ietf-spring-sr-yang], which defines the global
segment routing configuration independent of any specific routing segment routing configuration independent of any specific routing
protocol configuration, and support of IS-IS base model protocol configuration, and support of IS-IS base model
[I-D.ietf-isis-yang-isis-cfg] which defines basic IS-IS configuration [I-D.ietf-isis-yang-isis-cfg] which defines basic IS-IS configuration
and state. and state.
The figure below describes the overall structure of the isis-sr YANG The figure below describes the overall structure of the isis-sr YANG
module: module:
module: ietf-isis-sr module: ietf-isis-sr
augment /rt:routing/rt:control-plane-protocols/rt:control-plane-protocol augment /rt:routing/rt:control-plane-protocols
/isis:isis: /rt:control-plane-protocol/isis:isis:
+--rw segment-routing +--rw segment-routing
| +--rw enabled? boolean | +--rw enabled? boolean
| +--rw bindings | +--rw bindings
| +--rw advertise | +--rw advertise
| | ... | | +--rw policies* string
| +--rw receive? boolean | +--rw receive? boolean
+--rw protocol-srgb {sr:protocol-srgb}? +--rw protocol-srgb {sr:protocol-srgb}?
+--rw srgb* [lower-bound upper-bound] +--rw srgb* [lower-bound upper-bound]
+--rw lower-bound uint32 +--rw lower-bound uint32
+--rw upper-bound uint32 +--rw upper-bound uint32
augment /rt:routing/rt:control-plane-protocols/rt:control-plane-protocol augment /rt:routing/rt:control-plane-protocols
/isis:isis/isis:interfaces/isis:interface: /rt:control-plane-protocol/isis:isis/isis:interfaces
+--rw segment-routing /isis:interface:
+--rw adjacency-sid +--rw segment-routing
+--rw advertise-adj-group-sid* [group-id] +--rw adjacency-sid
| ... +--rw advertise-adj-group-sid* [group-id]
+--rw advertise-protection? enumeration | +--rw group-id uint32
augment /rt:routing/rt:control-plane-protocols/rt:control-plane-protocol +--rw advertise-protection? enumeration
/isis:isis/isis:interfaces/isis:interface/isis:fast-reroute: augment /rt:routing/rt:control-plane-protocols
+--rw ti-lfa {ti-lfa}? /rt:control-plane-protocol/isis:isis/isis:interfaces
+--rw enable? boolean /isis:interface/isis:fast-reroute:
augment /rt:routing/rt:control-plane-protocols/rt:control-plane-protocol +--rw ti-lfa {ti-lfa}?
/isis:isis/isis:interfaces/isis:interface/isis:fast-reroute/isis:lfa/isi +--rw enable? boolean
s:remote-lfa:
+--rw use-segment-routing-path? boolean {remote-lfa-sr}?
augment /rt:routing-state/rt:control-plane-protocols/rt:control-plane-pr
otocol/isis:isis:
+--ro segment-routing
| +--ro enabled? boolean
| +--ro bindings
| +--ro advertise
| | ...
| +--ro receive? boolean augment /rt:routing/rt:control-plane-protocols
+--ro protocol-srgb {sr:protocol-srgb}? /rt:control-plane-protocol/isis:isis/isis:interfaces
+--ro srgb* [lower-bound upper-bound] /isis:interface/isis:fast-reroute/isis:lfa/isis:remote-lfa:
+--ro lower-bound uint32 +--rw use-segment-routing-path? boolean {remote-lfa-sr}?
+--ro upper-bound uint32 augment /rt:routing-state/rt:control-plane-protocols
augment /rt:routing-state/rt:control-plane-protocols/rt:control-plane-pr /rt:control-plane-protocol/isis:isis:
otocol/isis:isis/isis:interfaces/isis:interface: +--ro segment-routing
+--ro segment-routing | +--ro enabled? boolean
+--ro adjacency-sid | +--ro bindings
+--ro advertise-adj-group-sid* [group-id] | +--ro advertise
| ... | | +--ro policies* string
+--ro advertise-protection? enumeration | +--ro receive? boolean
augment /rt:routing-state/rt:control-plane-protocols/rt:control-plane-pr +--ro protocol-srgb {sr:protocol-srgb}?
otocol/isis:isis/isis:interfaces/isis:interface/isis:adjacencies/isis:ad +--ro srgb* [lower-bound upper-bound]
jacency: +--ro lower-bound uint32
+--ro adjacency-sid* [value] +--ro upper-bound uint32
+--ro af? identityref augment /rt:routing-state/rt:control-plane-protocols
+--ro value uint32 /rt:control-plane-protocol/isis:isis/isis:interfaces
+--ro weight? uint8 /isis:interface:
+--ro protection-requested? boolean +--ro segment-routing
augment /rt:routing-state/rt:control-plane-protocols/rt:control-plane-pr +--ro adjacency-sid
otocol/isis:isis/isis:database/isis:level-db/isis:lsp/isis:extended-is-n +--ro advertise-adj-group-sid* [group-id]
eighbor/isis:neighbor: | +--ro group-id uint32
+--ro sid-list* [value] +--ro advertise-protection? enumeration
+--ro flags? bits augment /rt:routing-state/rt:control-plane-protocols
+--ro weight? uint8 /rt:control-plane-protocol/isis:isis/isis:interfaces
+--ro neighbor-id? isis:system-id /isis:interface/isis:adjacencies/isis:adjacency:
+--ro value uint32 +--ro adjacency-sid* [value]
augment /rt:routing-state/rt:control-plane-protocols/rt:control-plane-pr +--ro af? identityref
otocol/isis:isis/isis:database/isis:level-db/isis:lsp/isis:mt-is-neighbo +--ro value uint32
r/isis:neighbor: +--ro weight? uint8
+--ro sid-list* [value] +--ro protection-requested? boolean
+--ro flags? bits augment /rt:routing-state/rt:control-plane-protocols
+--ro weight? uint8 /rt:control-plane-protocol/isis:isis/isis:database
+--ro neighbor-id? isis:system-id /isis:level-db/isis:lsp/isis:extended-is-neighbor
+--ro value uint32 /isis:neighbor:
augment /rt:routing-state/rt:control-plane-protocols/rt:control-plane-pr +--ro sid-list* [value]
otocol/isis:isis/isis:database/isis:level-db/isis:lsp/isis:extended-ipv4 +--ro flags? bits
-reachability/isis:prefixes: +--ro weight? uint8
+--ro sid-list* [value] +--ro neighbor-id? isis:system-id
+--ro flags? bits +--ro value uint32
+--ro algorithm? uint8 augment /rt:routing-state/rt:control-plane-protocols
+--ro value uint32 /rt:control-plane-protocol/isis:isis/isis:database
augment /rt:routing-state/rt:control-plane-protocols/rt:control-plane-pr /isis:level-db/isis:lsp/isis:mt-is-neighbor/isis:neighbor:
otocol/isis:isis/isis:database/isis:level-db/isis:lsp/isis:mt-extended-i +--ro sid-list* [value]
pv4-reachability/isis:prefixes: +--ro flags? bits
+--ro sid-list* [value] +--ro weight? uint8
+--ro flags? bits +--ro neighbor-id? isis:system-id
+--ro algorithm? uint8 +--ro value uint32
+--ro value uint32 augment /rt:routing-state/rt:control-plane-protocols
augment /rt:routing-state/rt:control-plane-protocols/rt:control-plane-pr /rt:control-plane-protocol/isis:isis/isis:database
otocol/isis:isis/isis:database/isis:level-db/isis:lsp/isis:ipv6-reachabi /isis:level-db/isis:lsp/isis:extended-ipv4-reachability
lity/isis:prefixes: /isis:prefixes:
+--ro sid-list* [value] +--ro sid-list* [value]
+--ro flags? bits +--ro flags? bits
+--ro algorithm? uint8 +--ro algorithm? uint8
+--ro value uint32 +--ro value uint32
augment /rt:routing-state/rt:control-plane-protocols/rt:control-plane-pr augment /rt:routing-state/rt:control-plane-protocols
otocol/isis:isis/isis:database/isis:level-db/isis:lsp/isis:mt-ipv6-reach /rt:control-plane-protocol/isis:isis/isis:database
ability/isis:prefixes: /isis:level-db/isis:lsp/isis:mt-extended-ipv4-reachability
+--ro sid-list* [value] /isis:prefixes:
+--ro flags? bits +--ro sid-list* [value]
+--ro algorithm? uint8 +--ro flags? bits
+--ro value uint32 +--ro algorithm? uint8
augment /rt:routing-state/rt:control-plane-protocols/rt:control-plane-pr +--ro value uint32
otocol/isis:isis/isis:database/isis:level-db/isis:lsp: augment /rt:routing-state/rt:control-plane-protocols
+--ro segment-routing-bindings* [fec range] /rt:control-plane-protocol/isis:isis/isis:database
+--ro fec string /isis:level-db/isis:lsp/isis:ipv6-reachability
+--ro range uint16 /isis:prefixes:
+--ro flags? bits +--ro sid-list* [value]
+--ro weight? uint8 +--ro flags? bits
+--ro binding +--ro algorithm? uint8
+--ro prefix-sid +--ro value uint32
| ... augment /rt:routing-state/rt:control-plane-protocols
+--ro ero-metric? uint32 /rt:control-plane-protocol/isis:isis/isis:database
+--ro ero /isis:level-db/isis:lsp/isis:mt-ipv6-reachability
| ... /isis:prefixes:
+--ro backup-ero +--ro sid-list* [value]
| ... +--ro flags? bits
+--ro unnumbered-interface-id-ero +--ro algorithm? uint8
| ... +--ro value uint32
+--ro backup-unnumbered-interface-id-ero augment /rt:routing-state/rt:control-plane-protocols
... /rt:control-plane-protocol/isis:isis/isis:database
/isis:level-db/isis:lsp:
+--ro segment-routing-bindings* [fec range]
+--ro fec string
+--ro range uint16
+--ro flags? bits
+--ro weight? uint8
+--ro binding
+--ro prefix-sid
| +--ro sid-list* [value]
| +--ro flags? bits
| +--ro algorithm? uint8
| +--ro value uint32
+--ro ero-metric? uint32
+--ro ero
| +--ro address-family? identityref
| +--ro loose? boolean
| +--ro address? string
+--ro backup-ero
| +--ro address-family? identityref
| +--ro loose? boolean
| +--ro address? string
+--ro unnumbered-interface-id-ero
| +--ro router-id? string
| +--ro interface-id? uint32
+--ro backup-unnumbered-interface-id-ero
+--ro router-id? string
+--ro interface-id? uint32
3. IS-IS Segment Routing configuration 3. IS-IS Segment Routing configuration
3.1. Segment Routing activation 3.1. Segment Routing activation
Activation of segment-routing IS-IS is done by setting the "enable" Activation of segment-routing IS-IS is done by setting the "enable"
leaf to true. This triggers advertisement of segment-routing leaf to true. This triggers advertisement of segment-routing
extensions based on the configuration parameters that have been setup extensions based on the configuration parameters that have been setup
using the base segment routing module. using the base segment routing module.
skipping to change at page 6, line 7 skipping to change at page 6, line 46
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@2016-11-03.yang" <CODE BEGINS> file "ietf-isis-sr@2017-05-05.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";
} }
import ietf-isis { import ietf-isis {
prefix "isis"; prefix "isis";
} }
organization organization
"IETF ISIS Working Group"; "IETF ISIS Working Group";
contact contact
"WG List: <mailto:spring@ietf.org&gt; "WG List: <mailto:isis@ietf.org&gt;
Editor: Stephane Litkowski Editor: Stephane Litkowski
<mailto:stephane.litkowski@orange.com&gt; <mailto:stephane.litkowski@orange.com&gt;
Acee Lindem Acee Lindem
<mailto:acee@cisco.com&gt; <mailto:acee@cisco.com&gt;
Yingzhen Qu Yingzhen Qu
<mailto:yiqu@cisco.com&gt; <mailto:yingzhen.qu@huawei.com&gt;
Pushpasis Sarkar Pushpasis Sarkar
<mailto:pushpasis.ietf@gmail.com&gt; <mailto:pushpasis.ietf@gmail.com&gt;
Ing-Wher Chen Ing-Wher Chen
<mailto:ichen@kuatrotech.com&gt; <mailto:ng-wher_chen@jabil.com&gt;
Jeff Tantsura Jeff Tantsura
<mailto:jefftant.ietf@gmail.com&gt; <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 2016-11-03 { revision 2017-05-05 {
description description
"Initial revision."; "Add p-flag in adj-sid.";
reference "RFC XXXX"; reference "RFC XXXX";
} }
/* Identities */ /* Identities */
/* Features */ /* Features */
feature remote-lfa-sr { feature remote-lfa-sr {
description description
"Enhance rLFA to use SR path."; "Enhance rLFA to use SR path.";
} }
feature ti-lfa { feature ti-lfa {
skipping to change at page 10, line 46 skipping to change at page 11, line 34
"If set, then the value/index carried by "If set, then the value/index carried by
the SID has local significance. the SID has local significance.
By default the flag is SET."; By default the flag is SET.";
} }
bit set { bit set {
position 3; position 3;
description description
"When set, the S-Flag indicates that the "When set, the S-Flag indicates that the
Adj-SID refers to a set of adjacencies"; Adj-SID refers to a set of adjacencies";
} }
bit persistent {
position 2;
description
"When set, the P-Flag indicates that the
Adj-SID is persistently allocated.";
}
} }
description description
"Describes flags associated with the "Describes flags associated with the
segment ID."; segment ID.";
} }
leaf weight { leaf weight {
type uint8; type uint8;
description description
"The value represents the weight of the Adj-SID "The value represents the weight of the Adj-SID
skipping to change at page 21, line 10 skipping to change at page 21, line 45
7. Acknowledgements 7. Acknowledgements
TBD. TBD.
8. IANA Considerations 8. IANA Considerations
The IANA is requested to assign two new URIs from the IETF XML The IANA is requested to assign two new URIs from the IETF XML
registry ([RFC3688]). Authors are suggesting the following URI: registry ([RFC3688]). Authors are suggesting the following URI:
URI: urn:ietf:params:xml:ns:yang:ietf-isis-sr URI: urn:ietf:params:xml:ns:yang:ietf-isis-sr
Registrant Contact: IS-IS WG Registrant Contact: IS-IS WG
XML: N/A, the requested URI is an XML namespace XML: N/A, the requested URI is an XML namespace
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 document version -12 to isis-sr document version -00 9.1. 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.2. From isis document version -12 to version -13 9.2. From isis document version -12 to version -13
o Align with new segment routing common module. o Align with new segment routing common module.
skipping to change at page 21, line 44 skipping to change at page 22, line 35
o Fixed XPATH in 'when' expressions. o Fixed XPATH in 'when' expressions.
9.4. From isis document version -08 to version -09 9.4. 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.5. From isis document version -07 to version -08 9.5. 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.
9.6. From isis-sr document version -00 to version -01
o Added P-Flag in Adj-SID..
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., Filsfils, C., Bashandy, A., Gredler, H.,
Litkowski, S., Decraene, B., and j. jefftant@gmail.com, Litkowski, S., Decraene, B., and j. jefftant@gmail.com,
"IS-IS Extensions for Segment Routing", draft-ietf-isis- "IS-IS Extensions for Segment Routing", draft-ietf-isis-
segment-routing-extensions-09 (work in progress), October segment-routing-extensions-12 (work in progress), April
2016. 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-13 (work in progress), October 2016. isis-yang-isis-cfg-17 (work in progress), March 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-05 (work in progress), October 2016. yang-06 (work in progress), March 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,
RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>. <http://www.rfc-editor.org/info/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,
<http://www.rfc-editor.org/info/rfc3688>. <http://www.rfc-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,
<http://www.rfc-editor.org/info/rfc6020>. <http://www.rfc-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>. <http://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,
10.17487/RFC6536, March 2012, DOI 10.17487/RFC6536, March 2012,
<http://www.rfc-editor.org/info/rfc6536>. <http://www.rfc-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>. <http://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
Cisco
Email: yiqu@cisco.com Yingzhen Qu
Huawei
Email: yingzhen.qu@huawei.com
Pushpasis Sarkar Pushpasis Sarkar
Individual Individual
Email: pushpasis.ietf@gmail.com Email: pushpasis.ietf@gmail.com
Ing-Wher Chen Ing-Wher Chen
Kuatro Technologies Jabil
Email: ichen@kuatrotech.com Email: Ing-Wher_chen@jabil.com
Jeff Tantsura Jeff Tantsura
Individual Individual
Email: jefftant.ietf@gmail.com Email: jefftant.ietf@gmail.com
 End of changes. 39 change blocks. 
173 lines changed or deleted 198 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/