< draft-ietf-isis-sr-yang-03.txt   draft-ietf-isis-sr-yang-04.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: July 19, 2018 Huawei Expires: December 31, 2018 Huawei
P. Sarkar P. Sarkar
Individual Individual
I. Chen I. Chen
Jabil Jabil
J. Tantsura J. Tantsura
Individual Individual
January 15, 2018 June 29, 2018
YANG Data Model for IS-IS Segment Routing YANG Data Model for IS-IS Segment Routing
draft-ietf-isis-sr-yang-03 draft-ietf-isis-sr-yang-04
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 38 skipping to change at page 1, line 38
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
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 https://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 July 19, 2018. This Internet-Draft will expire on December 31, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2018 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 (https://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 . . . . . . . . . . . . . . 5 4. IS-IS Segment Routing YANG Module . . . . . . . . . . . . . . 6
5. Security Considerations . . . . . . . . . . . . . . . . . . . 20 5. Security Considerations . . . . . . . . . . . . . . . . . . . 20
6. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 20 6. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 20
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 20 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 21
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 20 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 21
9. Change log for ietf-isis-sr YANG module . . . . . . . . . . . 21 9. Change log for ietf-isis-sr YANG module . . . . . . . . . . . 21
9.1. From version -02 to version -03 . . . . . . . . . . . . . 21 9.1. From version -03 to version -04 . . . . . . . . . . . . . 21
9.2. From isis-sr document version -01 to version -02 . . . . 21 9.2. From version -02 to version -03 . . . . . . . . . . . . . 21
9.3. From isis-sr document version -00 to version -01 . . . . 21 9.3. From isis-sr document version -01 to version -02 . . . . 21
9.4. From isis document version -12 to isis-sr document 9.4. From isis-sr document version -00 to version -01 . . . . 22
version -00 . . . . . . . . . . . . . . . . . . . . . . . 21 9.5. From isis document version -12 to isis-sr document
9.5. From isis document version -12 to version -13 . . . . . . 21 version -00 . . . . . . . . . . . . . . . . . . . . . . . 22
9.6. From isis document version -09 to version -11 . . . . . . 22 9.6. From isis document version -12 to version -13 . . . . . . 22
9.7. From isis document version -08 to version -09 . . . . . . 22 9.7. From isis document version -09 to version -11 . . . . . . 22
9.8. From isis document version -07 to version -08 . . . . . . 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 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 27 skipping to change at page 3, line 28
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
/isis:isis/isis:interfaces/isis:interface/isis:fast-reroute/isis:lfa/isi +--rw ti-lfa {ti-lfa}?
s:remote-lfa: +--rw enable? boolean
+--rw use-segment-routing-path? boolean {remote-lfa-sr}? augment /rt:routing/rt:control-plane-protocols
augment /rt:routing/rt:control-plane-protocols/rt:control-plane-protocol /rt:control-plane-protocol/isis:isis/isis:interfaces
/isis:isis/isis:interfaces/isis:interface/isis:adjacencies/isis:adjacenc /isis:interface/isis:fast-reroute/isis:lfa/isis:remote-lfa:
y: +--rw use-segment-routing-path? boolean {remote-lfa-sr}?
+--ro adjacency-sid* [value] augment /rt:routing/rt:control-plane-protocols
+--ro af? iana-rt-types:address-family /rt:control-plane-protocol/isis:isis/isis:interfaces
+--ro value uint32 /isis:interface/isis:adjacencies/isis:adjacency:
+--ro weight? uint8 +--ro adjacency-sid* [value]
+--ro protection-requested? boolean +--ro af? iana-rt-types:address-family
augment /rt:routing/rt:control-plane-protocols/rt:control-plane-protocol +--ro value uint32
/isis:isis/isis:database/isis:level-db/isis:lsp/isis:router-capabilities +--ro weight? uint8
: +--ro protection-requested? boolean
+--ro sr-capability augment /rt:routing/rt:control-plane-protocols
| +--ro flags? bits /rt:control-plane-protocol/isis:isis/isis:database
| +--ro global-blocks /isis:level-db/isis:lsp/isis:router-capabilities:
| +--ro global-block* +--ro sr-capability
| ... | +--ro flags? bits
+--ro sr-algorithms | +--ro global-blocks
| +--ro sr-algorithm* uint8 | +--ro global-block*
+--ro local-blocks | +--ro range-size? uint32
| +--ro local-block* | +--ro sid-sub-tlv
| +--ro range-size? uint32 | +--ro sid? uint32
| +--ro sid-sub-tlv +--ro sr-algorithms
| ... | +--ro sr-algorithm* uint8
+--ro srms-preference +--ro local-blocks
+--ro preference? uint8 | +--ro local-block*
augment /rt:routing/rt:control-plane-protocols/rt:control-plane-protocol | +--ro range-size? uint32
/isis:isis/isis:database/isis:level-db/isis:lsp/isis:extended-is-neighbo | +--ro sid-sub-tlv
r/isis:neighbor: | +--ro sid? uint32
+--ro sid-list* [value] +--ro srms-preference
+--ro flags? bits +--ro preference? uint8
+--ro weight? uint8 augment /rt:routing/rt:control-plane-protocols
+--ro neighbor-id? isis:system-id /rt:control-plane-protocol/isis:isis/isis:database
+--ro value uint32 /isis:level-db/isis:lsp/isis:extended-is-neighbor
augment /rt:routing/rt:control-plane-protocols/rt:control-plane-protocol /isis:neighbor:
/isis:isis/isis:database/isis:level-db/isis:lsp/isis:mt-is-neighbor/isis +--ro sid-list* [value]
:neighbor: +--ro flags? bits
+--ro sid-list* [value] +--ro weight? uint8
+--ro flags? bits +--ro neighbor-id? isis:system-id
+--ro weight? uint8 +--ro value uint32
+--ro neighbor-id? isis:system-id augment /rt:routing/rt:control-plane-protocols
+--ro value uint32 /rt:control-plane-protocol/isis:isis/isis:database
augment /rt:routing/rt:control-plane-protocols/rt:control-plane-protocol /isis:level-db/isis:lsp/isis:mt-is-neighbor/isis:neighbor:
/isis:isis/isis:database/isis:level-db/isis:lsp/isis:extended-ipv4-reach +--ro sid-list* [value]
ability/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/rt:control-plane-protocols
augment /rt:routing/rt:control-plane-protocols/rt:control-plane-protocol /rt:control-plane-protocol/isis:isis/isis:database
/isis:isis/isis:database/isis:level-db/isis:lsp/isis:mt-extended-ipv4-re /isis:level-db/isis:lsp/isis:extended-ipv4-reachability
achability/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/rt:control-plane-protocols/rt:control-plane-protocol augment /rt:routing/rt:control-plane-protocols
/isis:isis/isis:database/isis:level-db/isis:lsp/isis:ipv6-reachability/i /rt:control-plane-protocol/isis:isis/isis:database
sis: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/rt:control-plane-protocols/rt:control-plane-protocol +--ro value uint32
/isis:isis/isis:database/isis:level-db/isis:lsp/isis:mt-ipv6-reachabilit augment /rt:routing/rt:control-plane-protocols
y/isis:prefixes: /rt:control-plane-protocol/isis:isis/isis:database
+--ro sid-list* [value] /isis:level-db/isis:lsp/isis:ipv6-reachability/isis:prefixes:
+--ro flags? bits +--ro sid-list* [value]
+--ro algorithm? uint8 +--ro flags? bits
+--ro value uint32 +--ro algorithm? uint8
augment /rt:routing/rt:control-plane-protocols/rt:control-plane-protocol +--ro value uint32
/isis:isis/isis:database/isis:level-db/isis:lsp: augment /rt:routing/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:mt-ipv6-reachability
+--ro range uint16 /isis:prefixes:
+--ro flags? bits +--ro sid-list* [value]
+--ro binding +--ro flags? bits
+--ro prefix-sid +--ro algorithm? uint8
... +--ro value uint32
augment /rt:routing/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 binding
+--ro prefix-sid
+--ro sid-list* [value]
+--ro flags? bits
+--ro algorithm? uint8
+--ro value 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 5, line 44 skipping to change at page 6, line 32
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@2018-01-15.yang" <CODE BEGINS> file "ietf-isis-sr@2018-06-25.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";
} }
import iana-routing-types { import iana-routing-types {
prefix "iana-rt-types"; prefix "iana-rt-types";
} }
organization organization
"IETF ISIS Working Group"; "IETF LSR - LSR Working Group";
contact contact
"WG List: &lt;mailto:spring@ietf.org&gt; "WG List: <mailto:lsr@ietf.org>
Editor: Stephane Litkowski Editor: Stephane Litkowski
&lt;mailto:stephane.litkowski@orange.com&gt; <mailto:stephane.litkowski@orange.com>
Acee Lindem Author: Acee Lindem
&lt;mailto:acee@cisco.com&gt; <mailto:acee@cisco.com>
Yingzhen Qu Author: Yingzhen Qu
&lt;mailto:yiqu@cisco.com&gt; <mailto:yiqu@cisco.com>
Pushpasis Sarkar Author: Pushpasis Sarkar
&lt;mailto:pushpasis.ietf@gmail.com&gt; <mailto:pushpasis.ietf@gmail.com>
Ing-Wher Chen Author: Ing-Wher Chen
&lt;mailto:ichen@kuatrotech.com&gt; <mailto:ichen@kuatrotech.com>
Jeff Tantsura Author: Jeff Tantsura
&lt;mailto:jefftant.ietf@gmail.com&gt; <mailto:jefftant.ietf@gmail.com>
";
"; description
"The YANG module defines a generic configuration model for
Segment routing ISIS extensions common across all of the vendor
implementations.";
description revision 2018-06-25 {
"The YANG module defines a generic configuration model for description
Segment routing ISIS extensions common across all of the vendor "Initial revision.";
implementations."; reference "RFC XXXX";
}
revision 2018-01-15 { /* Identities */
description
"Initial revision.";
reference "RFC XXXX";
}
/* Identities */ /* Features */
/* Features */ feature remote-lfa-sr {
description
"Enhance rLFA to use SR path.";
feature remote-lfa-sr { }
description
"Enhance rLFA to use SR path.";
}
feature ti-lfa { feature ti-lfa {
description description
"Enhance IPFRR with ti-lfa "Enhance IPFRR with ti-lfa
support"; support";
} }
/* Groupings */ /* Groupings */
grouping sid-sub-tlv { grouping sid-sub-tlv {
description "SID/Label sub-TLV grouping."; description "SID/Label sub-TLV grouping.";
container sid-sub-tlv { container sid-sub-tlv {
description description
"Used to advertise the SID/Label associated with a "Used to advertise the SID/Label associated with a
prefix or adjacency."; prefix or adjacency.";
leaf sid { leaf sid {
type uint32; type uint32;
description description
"Segment Identifier (SID) - A 20 bit label or "Segment Identifier (SID) - A 20 bit label or
32 bit SID."; 32 bit SID.";
} }
} }
} }
grouping sr-capability { grouping sr-capability {
description description
"SR capability grouping."; "SR capability grouping.";
container sr-capability { container sr-capability {
description description
"Segment Routing capability."; "Segment Routing capability.";
leaf flags { leaf flags {
type bits { type bits {
bit mpls-ipv4 { bit mpls-ipv4 {
position 0; position 0;
description description
"If set, then the router is capable of "If set, then the router is capable of
processing SR MPLS encapsulated IPv4 packets processing SR MPLS encapsulated IPv4 packets
on all interfaces."; on all interfaces.";
} }
bit mpls-ipv6 { bit mpls-ipv6 {
position 1; position 1;
description description
"If set, then the router is capable of "If set, then the router is capable of
processing SR MPLS encapsulated IPv6 packets processing SR MPLS encapsulated IPv6 packets
on all interfaces."; on all interfaces.";
} }
}
description }
description
"Flags."; "Flags.";
} }
container global-blocks { container global-blocks {
description description
"Segment Routing Global Blocks."; "Segment Routing Global Blocks.";
list global-block { list global-block {
description "Segment Routing Global Block."; description "Segment Routing Global Block.";
leaf range-size { leaf range-size {
type uint32; type uint32;
description "The SID range."; description "The SID range.";
} }
uses sid-sub-tlv; uses sid-sub-tlv;
} }
} }
} }
} }
grouping sr-algorithm { grouping sr-algorithm {
description description
"SR algorithm grouping."; "SR algorithm grouping.";
container sr-algorithms { container sr-algorithms {
description "All SR algorithms."; description "All SR algorithms.";
leaf-list sr-algorithm { leaf-list sr-algorithm {
type uint8; type uint8;
description description
"The Segment Routing (SR) algorithms that the router is "The Segment Routing (SR) algorithms that the router is
currently using."; currently using.";
} }
} }
} }
grouping srlb { grouping srlb {
description description
"SR Local Block grouping."; "SR Local Block grouping.";
container local-blocks { container local-blocks {
description "List of SRLBs."; description "List of SRLBs.";
list local-block { list local-block {
description "Segment Routing Local Block."; description "Segment Routing Local Block.";
leaf range-size { leaf range-size {
type uint32; type uint32;
description "The SID range."; description "The SID range.";
} }
uses sid-sub-tlv; uses sid-sub-tlv;
} }
} }
} }
grouping srms-preference {
grouping srms-preference { description "The SRMS preference TLV is used to advertise
description "The SRMS preference TLV is used to advertise a preference associated with the node that acts
a preference associated with the node that acts as an SR Mapping Server.";
as an SR Mapping Server."; container srms-preference {
container srms-preference { description "SRMS Preference TLV.";
description "SRMS Preference TLV."; leaf preference {
leaf preference { type uint8 {
type uint8 { range "0 .. 255";
range "0 .. 255"; }
} description "SRMS preference TLV, vlaue from 0 to 255.";
description "SRMS preference TLV, vlaue from 0 to 255."; }
} }
} }
}
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 iana-rt-types:address-family; type 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 {
type uint8; type uint8;
description description
"Weight associated with "Weight associated with
the adjacency SID."; the adjacency SID.";
} }
leaf protection-requested { leaf protection-requested {
type boolean; type boolean;
description description
"Describe if the adjacency SID "Describe if the adjacency SID
must be protected."; must be protected.";
} }
description description
"List of adjacency Segment IDs."; "List of adjacency Segment IDs.";
} }
} }
grouping prefix-segment-id {
grouping prefix-segment-id { description
description
"This group defines segment routing extensions "This group defines segment routing extensions
for prefixes."; for prefixes.";
list sid-list { list sid-list {
key value; key value;
leaf flags { leaf flags {
type bits { type bits {
bit readvertisment { bit readvertisment {
position 7; position 7;
description description
"If set, then the prefix to "If set, then the prefix to
which this Prefix-SID is attached, which this Prefix-SID is attached,
has been propagated by the has been propagated by the
router either from another level router either from another level
or from redistribution."; or from redistribution.";
} }
bit php {
bit php { position 5;
position 5; description
description "If set, then the penultimate hop MUST NOT
"If set, then the penultimate hop MUST NOT pop the Prefix-SID before delivering the packet
pop the Prefix-SID before delivering the packet to the node that advertised the Prefix-SID.";
to the node }
that advertised the Prefix-SID."; bit explicit-null {
} position 4;
bit explicit-null { description
position 4; "If set, any upstream neighbor of
description the Prefix-SID originator MUST replace
"If set, any upstream neighbor of the Prefix-SID with a
the Prefix-SID originator MUST replace Prefix-SID having an
the Prefix-SID with a Explicit-NULL value (0 for IPv4 and 2 for
Prefix-SID having an IPv6) before forwarding the packet.";
Explicit-NULL value (0 for IPv4 and 2 for }
IPv6) before forwarding the packet."; bit value {
} position 3;
bit value { description
position 3; "If set, then the Prefix-SID carries a
description value (instead of an index).
"If set, then the Prefix-SID carries a By default the flag is UNSET.";
value (instead of an index). }
By default the flag is UNSET."; bit local {
position 2;
description
"If set, then the value/index carried by
the Prefix-SID has local significance.
} By default the flag is UNSET.";
bit local { }
position 2; }
description description
"If set, then the value/index carried by
the Prefix-SID has local significance.
By default the flag is UNSET.";
}
}
description
"Describes flags associated with the "Describes flags associated with the
segment ID."; segment ID.";
} }
leaf algorithm { leaf algorithm {
type uint8; type uint8;
description description
"Algorithm to be used for path computation."; "Algorithm to be used for path computation.";
} }
leaf value { leaf value {
type uint32; type uint32;
description description
"Value of the prefix-SID."; "Value of the prefix-SID.";
} }
description description
"List of segments."; "List of segments.";
} }
} }
grouping adjacency-segment-id { grouping adjacency-segment-id {
description description
"This group defines segment routing extensions "This group defines segment routing extensions
for adjacencies."; for adjacencies.";
list sid-list { list sid-list {
key value; key value;
leaf flags { leaf flags {
type bits { type bits {
bit address-family { bit address-family {
position 7; position 7;
description description
"If unset, then the Adj-SID refers "If unset, then the Adj-SID refers
to an adjacency with outgoing IPv4 encapsulation. to an adjacency with outgoing IPv4 encapsulation.
If set then the Adj-SID refers to an adjacency If set then the Adj-SID refers to an adjacency
with outgoing IPv6 encapsulation."; with outgoing IPv6 encapsulation.";
} }
bit backup { bit backup {
position 6; position 6;
description description
"If set, the Adj-SID refers to an "If set, the Adj-SID refers to an
adjacency being protected adjacency being protected
(e.g.: using IPFRR or MPLS-FRR)"; (e.g.: using IPFRR or MPLS-FRR)";
} }
bit value { bit value {
position 5; position 5;
description description
"If set, then the SID carries a "If set, then the SID carries a
value (instead of an index). value (instead of an index).
By default the flag is SET."; By default the flag is SET.";
}
} bit local {
bit local { position 4;
position 4; description
description "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 {
bit persistent { position 2;
position 2; description
description "When set, the P-Flag indicates that the
"When set, the P-Flag indicates that the Adj-SID is persistently allocated.";
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
for the purpose of load balancing."; for the purpose of load balancing.";
} }
leaf neighbor-id { leaf neighbor-id {
type isis:system-id; type isis:system-id;
description description
"Describes the system ID of the neighbor "Describes the system ID of the neighbor
associated with the SID value. This is only associated with the SID value. This is only
used on LAN adjacencies."; used on LAN adjacencies.";
} }
leaf value { leaf value {
type uint32; type uint32;
description description
"Value of the Adj-SID."; "Value of the Adj-SID.";
} }
description description
"List of segments."; "List of segments.";
} }
}
}
grouping segment-routing-binding-tlv {
list segment-routing-bindings {
key "fec range"; grouping segment-routing-binding-tlv {
list segment-routing-bindings {
key "fec range";
leaf fec { leaf fec {
type string; type string;
description description
"IP (v4 or v6) range to be bound to SIDs."; "IP (v4 or v6) range to be bound to SIDs.";
} }
leaf range { leaf range {
type uint16; type uint16;
description description
"Describes number of elements to assign "Describes number of elements to assign
a binding to."; a binding to.";
} }
leaf flags { leaf flags {
type bits { type bits {
bit address-family { bit address-family {
position 7; position 7;
description description
"If unset, then the Prefix FEC "If unset, then the Prefix FEC
carries an IPv4 Prefix. carries an IPv4 Prefix.
If set then the Prefix FEC carries an If set then the Prefix FEC carries an
IPv6 Prefix."; IPv6 Prefix.";
} }
bit mirror { bit mirror {
position 6; position 6;
description description
"Set if the advertised SID/path "Set if the advertised SID/path
corresponds to a mirrored context. corresponds to a mirrored context.";
"; }
} bit flooding {
bit flooding { position 5;
position 5; description
description
"If the S bit is set(1), "If the S bit is set(1),
the IS-IS Router CAPABILITY TLV the IS-IS Router CAPABILITY TLV
MUST be flooded across the entire routing domain. MUST be flooded across the entire routing domain.
If the S bit is If the S bit is
not set(0), the TLV MUST NOT be leaked between levels. not set(0), the TLV MUST NOT be leaked between levels.
This bit MUST NOT be altered during the TLV leaking.";
}
bit down {
position 4;
description
"When the IS-IS Router CAPABILITY TLV is
leaked from level-2 to level-1, the D bit
MUST be set. Otherwise, this bit MUST
be clear. IS-IS Router capability TLVs
with the D bit set MUST NOT
be leaked from level-1 to level-2.
This is to prevent TLV looping.
";
}
bit attached {
position 3;
description
"The originator of the SID/Label Binding
TLV MAY set the A bit in order to signal
that the prefixes and
SIDs advertised in the SID/Label Binding
TLV are directly
connected to their originators.
";
} This bit MUST NOT be altered during the TLV leaking.";
}
bit down {
position 4;
description
"When the IS-IS Router CAPABILITY TLV is
leaked from level-2 to level-1, the D bit
MUST be set. Otherwise, this bit MUST
be clear. IS-IS Router capability TLVs
with the D bit set MUST NOT
be leaked from level-1 to level-2.
This is to prevent TLV looping.";
}
bit attached {
position 3;
description
"The originator of the SID/Label Binding TLV MAY set the
A bit in order to signal that the prefixes and SIDs
advertised in the SID/Label Binding TLV are directly
connected to their originators.";
}
} }
description description
"Flags of the binding."; "Flags of the binding.";
} }
container binding { container binding {
container prefix-sid { container prefix-sid {
uses prefix-segment-id; uses prefix-segment-id;
description description
"Binding prefix SID to the range."; "Binding prefix SID to the range.";
} }
description description
"Bindings associated with the range."; "Bindings associated with the range.";
} }
description description
"This container describes list of SID/Label "This container describes list of SID/Label bindings.
bindings. ISIS reference is TLV 149.";
ISIS reference is TLV 149."; }
} description
description
"Defines binding TLV for database."; "Defines binding TLV for database.";
}
} /* Cfg */
/* Cfg */
augment "/rt:routing/" + augment "/rt:routing/" +
"rt:control-plane-protocols/rt:control-plane-protocol"+ "rt:control-plane-protocols/rt:control-plane-protocol"+
"/isis:isis" { "/isis:isis" {
when "/rt:routing/rt:control-plane-protocols/"+ when "/rt:routing/rt:control-plane-protocols/"+
"rt:control-plane-protocol/rt:type = 'isis:isis'" { "rt:control-plane-protocol/rt:type = 'isis:isis'" {
description description
"This augment ISIS routing protocol when used"; "This augment ISIS routing protocol when used";
} }
description description
"This augments ISIS protocol configuration "This augments ISIS protocol configuration
with segment routing."; with segment routing.";
uses sr:controlplane-cfg; uses sr:controlplane-cfg;
container protocol-srgb { container protocol-srgb {
if-feature sr:protocol-srgb; if-feature sr:protocol-srgb;
uses sr-cmn:srgb-cfg; uses sr-cmn:srgb-cfg;
description description
"Per-protocol SRGB."; "Per-protocol SRGB.";
} }
} }
augment "/rt:routing/" +
"rt:control-plane-protocols/rt:control-plane-protocol"+ augment "/rt:routing/" +
"/isis:isis/isis:interfaces/isis:interface" { "rt:control-plane-protocols/rt:control-plane-protocol"+
when "/rt:routing/rt:control-plane-protocols/"+ "/isis:isis/isis:interfaces/isis:interface" {
when "/rt:routing/rt:control-plane-protocols/"+
"rt:control-plane-protocol/rt:type = 'isis:isis'" { "rt:control-plane-protocol/rt:type = 'isis:isis'" {
description description
"This augment ISIS routing protocol when used"; "This augment ISIS routing protocol when used";
} }
description description
"This augments ISIS protocol configuration "This augments ISIS protocol configuration
with segment routing."; with segment routing.";
uses sr:igp-interface-cfg; uses sr:igp-interface-cfg;
} }
augment "/rt:routing/" + augment "/rt:routing/" +
"rt:control-plane-protocols/rt:control-plane-protocol"+ "rt:control-plane-protocols/rt:control-plane-protocol"+
"/isis:isis/isis:interfaces/isis:interface"+ "/isis:isis/isis:interfaces/isis:interface"+
"/isis:fast-reroute" { "/isis:fast-reroute" {
when "/rt:routing/rt:control-plane-protocols/"+ when "/rt:routing/rt:control-plane-protocols/"+
"rt:control-plane-protocol/rt:type = 'isis:isis'" { "rt:control-plane-protocol/rt:type = 'isis:isis'" {
description description
"This augment ISIS routing protocol when used"; "This augment ISIS routing protocol when used";
} }
description description
"This augments ISIS IP FRR with TILFA."; "This augments ISIS IP FRR with TILFA.";
container ti-lfa { container ti-lfa {
if-feature ti-lfa; if-feature ti-lfa;
leaf enable { leaf enable {
type boolean; type boolean;
description description
"Enables TI-LFA computation."; "Enables TI-LFA computation.";
} }
description description
"TILFA configuration."; "TILFA configuration.";
} }
}
}
augment "/rt:routing/" + augment "/rt:routing/" +
"rt:control-plane-protocols/rt:control-plane-protocol"+ "rt:control-plane-protocols/rt:control-plane-protocol"+
"/isis:isis/isis:interfaces/isis:interface"+ "/isis:isis/isis:interfaces/isis:interface"+
"/isis:fast-reroute/isis:lfa/isis:remote-lfa" { "/isis:fast-reroute/isis:lfa/isis:remote-lfa" {
when "/rt:routing/rt:control-plane-protocols/"+ when "/rt:routing/rt:control-plane-protocols/"+
"rt:control-plane-protocol/rt:type = 'isis:isis'" { "rt:control-plane-protocol/rt:type = 'isis:isis'" {
description description
"This augment ISIS routing protocol when used"; "This augment ISIS routing protocol when used";
}
} description
description
"This augments ISIS remoteLFA config with "This augments ISIS remoteLFA config with
use of segment-routing path."; use of segment-routing path.";
leaf use-segment-routing-path {
if-feature remote-lfa-sr;
type boolean;
description
"force remote LFA to use segment routing
path instead of LDP path.";
}
} leaf use-segment-routing-path {
if-feature remote-lfa-sr;
type boolean;
description
"force remote LFA to use segment routing
path instead of LDP path.";
}
}
/* Operational states */ /* Operational states */
augment "/rt:routing/" + augment "/rt:routing/" +
"rt:control-plane-protocols/rt:control-plane-protocol"+ "rt:control-plane-protocols/rt:control-plane-protocol"+
"/isis:isis/isis:interfaces/isis:interface" + "/isis:isis/isis:interfaces/isis:interface" +
"/isis:adjacencies/isis:adjacency" { "/isis:adjacencies/isis:adjacency" {
when "/rt:routing/rt:control-plane-protocols/"+ when "/rt:routing/rt:control-plane-protocols/"+
"rt:control-plane-protocol/rt:type = 'isis:isis'" { "rt:control-plane-protocol/rt:type = 'isis:isis'" {
description description
"This augment ISIS routing protocol when used"; "This augment ISIS routing protocol when used";
} }
description description
"This augments ISIS protocol configuration "This augments ISIS protocol configuration
with segment routing."; with segment routing.";
uses adjacency-state; uses adjacency-state;
} }
augment "/rt:routing/" + augment "/rt:routing/" +
"rt:control-plane-protocols/rt:control-plane-protocol"+ "rt:control-plane-protocols/rt:control-plane-protocol"+
"/isis:isis/isis:database/isis:level-db/isis:lsp"+ "/isis:isis/isis:database/isis:level-db/isis:lsp"+
"/isis:router-capabilities" { "/isis:router-capabilities" {
when "/rt:routing/rt:control-plane-protocols/"+ when "/rt:routing/rt:control-plane-protocols/"+
"rt:control-plane-protocol/rt:type = 'isis:isis'" { "rt:control-plane-protocol/rt:type = 'isis:isis'" {
description description
"This augment ISIS routing protocol when used"; "This augment ISIS routing protocol when used";
} }
description description
"This augments ISIS protocol LSDB router capability."; "This augments ISIS protocol LSDB router capability.";
uses sr-capability; uses sr-capability;
uses sr-algorithm; uses sr-algorithm;
uses srlb; uses srlb;
uses srms-preference; uses srms-preference;
}
}
augment "/rt:routing/" + augment "/rt:routing/" +
"rt:control-plane-protocols/rt:control-plane-protocol"+ "rt:control-plane-protocols/rt:control-plane-protocol"+
"/isis:isis/isis:database/isis:level-db/isis:lsp"+ "/isis:isis/isis:database/isis:level-db/isis:lsp"+
"/isis:extended-is-neighbor/isis:neighbor" { "/isis:extended-is-neighbor/isis:neighbor" {
when "/rt:routing/rt:control-plane-protocols/"+ when "/rt:routing/rt:control-plane-protocols/"+
"rt:control-plane-protocol/rt:type = 'isis:isis'" { "rt:control-plane-protocol/rt:type = 'isis:isis'" {
description description
"This augment ISIS routing protocol when used"; "This augment ISIS routing protocol when used";
} }
description description
"This augments ISIS protocol LSDB neighbor."; "This augments ISIS protocol LSDB neighbor.";
uses adjacency-segment-id; uses adjacency-segment-id;
}
} augment "/rt:routing/" +
augment "/rt:routing/" + "rt:control-plane-protocols/rt:control-plane-protocol"+
"rt:control-plane-protocols/rt:control-plane-protocol"+ "/isis:isis/isis:database/isis:level-db/isis:lsp"+
"/isis:isis/isis:database/isis:level-db/isis:lsp"+ "/isis:mt-is-neighbor/isis:neighbor" {
"/isis:mt-is-neighbor/isis:neighbor" { when "/rt:routing/rt:control-plane-protocols/"+
when "/rt:routing/rt:control-plane-protocols/"+
"rt:control-plane-protocol/rt:type = 'isis:isis'" { "rt:control-plane-protocol/rt:type = 'isis:isis'" {
description description
"This augment ISIS routing protocol when used"; "This augment ISIS routing protocol when used";
} }
description description
"This augments ISIS protocol LSDB neighbor."; "This augments ISIS protocol LSDB neighbor.";
uses adjacency-segment-id; uses adjacency-segment-id;
} }
augment "/rt:routing/" +
augment "/rt:routing/" + "rt:control-plane-protocols/rt:control-plane-protocol"+
"rt:control-plane-protocols/rt:control-plane-protocol"+ "/isis:isis/isis:database/isis:level-db/isis:lsp"+
"/isis:isis/isis:database/isis:level-db/isis:lsp"+ "/isis:extended-ipv4-reachability/isis:prefixes" {
"/isis:extended-ipv4-reachability/isis:prefixes" { when "/rt:routing/rt:control-plane-protocols/"+
when "/rt:routing/rt:control-plane-protocols/"+
"rt:control-plane-protocol/rt:type = 'isis:isis'" { "rt:control-plane-protocol/rt:type = 'isis:isis'" {
description description
"This augment ISIS routing protocol when used"; "This augment ISIS routing protocol when used";
} }
description description
"This augments ISIS protocol LSDB prefix."; "This augments ISIS protocol LSDB prefix.";
uses prefix-segment-id;
}
uses prefix-segment-id; augment "/rt:routing/" +
} "rt:control-plane-protocols/rt:control-plane-protocol"+
"/isis:isis/isis:database/isis:level-db/isis:lsp"+
augment "/rt:routing/" + "/isis:mt-extended-ipv4-reachability/isis:prefixes" {
"rt:control-plane-protocols/rt:control-plane-protocol"+ when "/rt:routing/rt:control-plane-protocols/"+
"/isis:isis/isis:database/isis:level-db/isis:lsp"+
"/isis:mt-extended-ipv4-reachability/isis:prefixes" {
when "/rt:routing/rt:control-plane-protocols/"+
"rt:control-plane-protocol/rt:type = 'isis:isis'" { "rt:control-plane-protocol/rt:type = 'isis:isis'" {
description description
"This augment ISIS routing protocol when used"; "This augment ISIS routing protocol when used";
} }
description description
"This augments ISIS protocol LSDB prefix."; "This augments ISIS protocol LSDB prefix.";
uses prefix-segment-id; uses prefix-segment-id;
}
} augment "/rt:routing/" +
augment "/rt:routing/" + "rt:control-plane-protocols/rt:control-plane-protocol"+
"rt:control-plane-protocols/rt:control-plane-protocol"+ "/isis:isis/isis:database/isis:level-db/isis:lsp"+
"/isis:isis/isis:database/isis:level-db/isis:lsp"+ "/isis:ipv6-reachability/isis:prefixes" {
"/isis:ipv6-reachability/isis:prefixes" { when "/rt:routing/rt:control-plane-protocols/"+
when "/rt:routing/rt:control-plane-protocols/"+
"rt:control-plane-protocol/rt:type = 'isis:isis'" { "rt:control-plane-protocol/rt:type = 'isis:isis'" {
description description
"This augment ISIS routing protocol when used"; "This augment ISIS routing protocol when used";
} }
description description
"This augments ISIS protocol LSDB prefix."; "This augments ISIS protocol LSDB prefix.";
uses prefix-segment-id; uses prefix-segment-id;
}
} augment "/rt:routing/" +
augment "/rt:routing/" + "rt:control-plane-protocols/rt:control-plane-protocol"+
"rt:control-plane-protocols/rt:control-plane-protocol"+ "/isis:isis/isis:database/isis:level-db/isis:lsp"+
"/isis:isis/isis:database/isis:level-db/isis:lsp"+ "/isis:mt-ipv6-reachability/isis:prefixes" {
"/isis:mt-ipv6-reachability/isis:prefixes" { when "/rt:routing/rt:control-plane-protocols/"+
when "/rt:routing/rt:control-plane-protocols/"+
"rt:control-plane-protocol/rt:type = 'isis:isis'" { "rt:control-plane-protocol/rt:type = 'isis:isis'" {
description
"This augment ISIS routing protocol when used"; description
} "This augment ISIS routing protocol when used";
description }
description
"This augments ISIS protocol LSDB prefix."; "This augments ISIS protocol LSDB prefix.";
uses prefix-segment-id; uses prefix-segment-id;
}
} augment "/rt:routing/" +
augment "/rt:routing/" + "rt:control-plane-protocols/rt:control-plane-protocol"+
"rt:control-plane-protocols/rt:control-plane-protocol"+ "/isis:isis/isis:database/isis:level-db/isis:lsp" {
"/isis:isis/isis:database/isis:level-db/isis:lsp" { when "/rt:routing/rt:control-plane-protocols/"+
when "/rt:routing/rt:control-plane-protocols/"+
"rt:control-plane-protocol/rt:type = 'isis:isis'" { "rt:control-plane-protocol/rt:type = 'isis:isis'" {
description description
"This augment ISIS routing protocol when used"; "This augment ISIS routing protocol when used";
} }
description description
"This augments ISIS protocol LSDB."; "This augments ISIS protocol LSDB.";
uses segment-routing-binding-tlv; uses segment-routing-binding-tlv;
}
}
/* Notifications */
} /* Notifications */
<CODE ENDS> }
<CODE ENDS>
5. Security Considerations 5. Security Considerations
Configuration and state data defined in this document are designed to Configuration and state data defined in this document are designed to
be accessed via the NETCONF protocol [RFC6241]. be accessed via the NETCONF protocol [RFC6241].
As IS-IS is an IGP protocol (critical piece of the network), ensuring As IS-IS is an IGP protocol (critical piece of the network), ensuring
stability and security of the protocol is mandatory for the network stability and security of the protocol is mandatory for the network
service. service.
skipping to change at page 21, line 5 skipping to change at page 21, line 14
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 version -02 to version -03 9.1. From version -03 to version -04
o Fixed yang module indentations.
9.2. From version -02 to version -03
o Change address-family type according to routing types. o Change address-family type according to routing types.
9.2. From isis-sr document version -01 to version -02 9.3. 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.3. From isis-sr document version -00 to version -01 9.4. From isis-sr document version -00 to version -01
o Added P-Flag in Adj-SID. o Added P-Flag in Adj-SID.
9.4. From isis document version -12 to isis-sr document version -00 9.5. 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.5. From isis document version -12 to version -13 9.6. 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.6. From isis document version -09 to version -11 9.7. From isis document version -09 to version -11
o Fixed XPATH in 'when' expressions. o Fixed XPATH in 'when' expressions.
9.7. From isis document version -08 to version -09 9.8. 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.8. From isis document version -07 to version -08 9.9. 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., Ginsberg, L., Filsfils, C., Bashandy, A., Previdi, S., Ginsberg, L., Filsfils, C., Bashandy, A.,
Gredler, H., Litkowski, S., Decraene, B., and J. Tantsura, 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-15 (work in progress), December segment-routing-extensions-15 (work in progress), December
skipping to change at page 22, line 37 skipping to change at page 22, line 49
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-19 (work in progress), November 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-08 (work in progress), December 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,
RFC2119, March 1997, <https://www.rfc-editor.org/info/ DOI 10.17487/RFC2119, March 1997,
rfc2119>. <https://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, <https://www.rfc- DOI 10.17487/RFC3688, January 2004,
editor.org/info/rfc3688>. <https://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, <https://www.rfc- DOI 10.17487/RFC6020, October 2010,
editor.org/info/rfc6020>. <https://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,
<https://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,
10.17487/RFC6536, March 2012, <https://www.rfc- DOI 10.17487/RFC6536, March 2012,
editor.org/info/rfc6536>. <https://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,
<https://www.rfc-editor.org/info/rfc7950>. <https://www.rfc-editor.org/info/rfc7950>.
Authors' Addresses Authors' Addresses
Stephane Litkowski Stephane Litkowski
Orange Orange
 End of changes. 135 change blocks. 
722 lines changed or deleted 721 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/