draft-ietf-isis-sr-yang-05.txt   draft-ietf-isis-sr-yang-06.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: September 11, 2019 Huawei Expires: January 8, 2020 Futurewei
P. Sarkar P. Sarkar
Individual Individual
I. Chen I. Chen
The MITRE Corporation The MITRE Corporation
J. Tantsura J. Tantsura
Individual Individual
March 10, 2019 July 7, 2019
YANG Data Model for IS-IS Segment Routing YANG Data Model for IS-IS Segment Routing
draft-ietf-isis-sr-yang-05 draft-ietf-isis-sr-yang-06
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.
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.
skipping to change at page 1, line 38 skipping to change at page 1, line 38
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 https://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 September 11, 2019. This Internet-Draft will expire on January 8, 2020.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2019 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
(https://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
skipping to change at page 2, line 26 skipping to change at page 2, line 26
5.1. Segment Routing activation . . . . . . . . . . . . . . . 6 5.1. Segment Routing activation . . . . . . . . . . . . . . . 6
5.2. Advertising mapping server policy . . . . . . . . . . . . 6 5.2. Advertising mapping server policy . . . . . . . . . . . . 6
5.3. IP Fast reroute . . . . . . . . . . . . . . . . . . . . . 6 5.3. IP Fast reroute . . . . . . . . . . . . . . . . . . . . . 6
6. IS-IS Segment Routing YANG Module . . . . . . . . . . . . . . 6 6. IS-IS Segment Routing YANG Module . . . . . . . . . . . . . . 6
7. Security Considerations . . . . . . . . . . . . . . . . . . . 20 7. Security Considerations . . . . . . . . . . . . . . . . . . . 20
8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 21 8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 21
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 21 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 21
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 21 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 21
11. Change log for ietf-isis-sr YANG module . . . . . . . . . . . 21 11. Change log for ietf-isis-sr YANG module . . . . . . . . . . . 21
11.1. From version -03 to version -04 . . . . . . . . . . . . 21 11.1. From version -03 to version -04 . . . . . . . . . . . . 21
11.2. From version -02 to version -03 . . . . . . . . . . . . 21 11.2. From version -02 to version -03 . . . . . . . . . . . . 22
11.3. From isis-sr document version -01 to version -02 . . . . 22 11.3. From isis-sr document version -01 to version -02 . . . . 22
11.4. From isis-sr document version -00 to version -01 . . . . 22 11.4. From isis-sr document version -00 to version -01 . . . . 22
11.5. From isis document version -12 to isis-sr document 11.5. From isis document version -12 to isis-sr document
version -00 . . . . . . . . . . . . . . . . . . . . . . 22 version -00 . . . . . . . . . . . . . . . . . . . . . . 22
11.6. From isis document version -12 to version -13 . . . . . 22 11.6. From isis document version -12 to version -13 . . . . . 22
11.7. From isis document version -09 to version -11 . . . . . 22 11.7. From isis document version -09 to version -11 . . . . . 22
11.8. From isis document version -08 to version -09 . . . . . 22 11.8. From isis document version -08 to version -09 . . . . . 22
11.9. From isis document version -07 to version -08 . . . . . 22 11.9. From isis document version -07 to version -08 . . . . . 22
12. Normative References . . . . . . . . . . . . . . . . . . . . 22 12. Normative References . . . . . . . . . . . . . . . . . . . . 23
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 24 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 24
1. Overview 1. Overview
YANG [RFC6020] [RFC7950] is a data definition language used to define YANG [RFC6020] [RFC7950] is a data definition language used to define
the contents of a conceptual data store that allows networked devices the contents of a conceptual data store that allows networked devices
to be managed using NETCONF [RFC6241]. YANG is proving relevant to be managed using NETCONF [RFC6241]. YANG is proving relevant
beyond its initial confines, as bindings to other interfaces (e.g., beyond its initial confines, as bindings to other interfaces (e.g.,
ReST) and encodings other than XML (e.g., JSON) are being defined. ReST) and encodings other than XML (e.g., JSON) are being defined.
Furthermore, YANG data models can be used as the basis for Furthermore, YANG data models can be used as the basis for
skipping to change at page 3, line 39 skipping to change at page 3, line 39
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 augment /rt:routing/rt:control-plane-protocols
/rt:control-plane-protocol/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 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 augment /rt:routing/rt:control-plane-protocols
/rt:control-plane-protocol/isis:isis/isis:interfaces /rt:control-plane-protocol/isis:isis/isis:interfaces
/isis:interface: /isis:interface:
+--rw segment-routing +--rw segment-routing
+--rw adjacency-sid +--rw adjacency-sid
+--rw advertise-adj-group-sid* [group-id] +--rw adj-sids* [value]
| +--rw group-id uint32 | +--rw value-type? enumeration
+--rw advertise-protection? enumeration | +--rw value uint32
augment /rt:routing/rt:control-plane-protocols | +--rw protected? boolean
/rt:control-plane-protocol/isis:isis/isis:interfaces +--rw advertise-adj-group-sid* [group-id]
/isis:interface/isis:fast-reroute: | +--rw group-id uint32
+--rw ti-lfa {ti-lfa}? +--rw advertise-protection? enumeration
+--rw enable? boolean augment /rt:routing/rt:control-plane-protocols
augment /rt:routing/rt:control-plane-protocols /rt:control-plane-protocol/isis:isis/isis:interfaces
/rt:control-plane-protocol/isis:isis/isis:interfaces /isis:interface/isis:fast-reroute:
/isis:interface/isis:fast-reroute/isis:lfa/isis:remote-lfa: +--rw ti-lfa {ti-lfa}?
+--rw use-segment-routing-path? boolean {remote-lfa-sr}? +--rw enable? boolean
augment /rt:routing/rt:control-plane-protocols augment /rt:routing/rt:control-plane-protocols
/rt:control-plane-protocol/isis:isis/isis:interfaces /rt:control-plane-protocol/isis:isis/isis:interfaces
/isis:interface/isis:adjacencies/isis:adjacency: /isis:interface/isis:fast-reroute/isis:lfa/isis:remote-lfa:
+--ro adjacency-sid* [value] +--rw use-segment-routing-path? boolean {remote-lfa-sr}?
+--ro af? iana-rt-types:address-family augment /rt:routing/rt:control-plane-protocols
+--ro value uint32 /rt:control-plane-protocol/isis:isis/isis:interfaces
+--ro weight? uint8 /isis:interface/isis:adjacencies/isis:adjacency:
+--ro protection-requested? boolean +--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:database +--ro value uint32
/isis:level-db/isis:lsp/isis:router-capabilities: +--ro weight? uint8
+--ro sr-capability +--ro protection-requested? boolean
| +--ro flags? bits augment /rt:routing/rt:control-plane-protocols
| +--ro global-blocks /rt:control-plane-protocol/isis:isis/isis:database
| +--ro global-block* /isis:levels/isis:lsp/isis:router-capabilities:
| +--ro range-size? uint32 +--ro sr-capability
| +--ro sid-sub-tlv | +--ro flags? bits
| +--ro sid? uint32 | +--ro global-blocks
+--ro sr-algorithms | +--ro global-block*
| +--ro sr-algorithm* uint8 | +--ro range-size? uint32
+--ro local-blocks | +--ro sid-sub-tlv
| +--ro local-block* | +--ro sid? uint32
| +--ro range-size? uint32 +--ro sr-algorithms
| +--ro sid-sub-tlv | +--ro sr-algorithm* uint8
| +--ro sid? uint32 +--ro local-blocks
+--ro srms-preference | +--ro local-block*
+--ro preference? uint8 | +--ro range-size? uint32
augment /rt:routing/rt:control-plane-protocols | +--ro sid-sub-tlv
/rt:control-plane-protocol/isis:isis/isis:database | +--ro sid? uint32
/isis:level-db/isis:lsp/isis:extended-is-neighbor +--ro srms-preference
/isis:neighbor: +--ro preference? uint8
+--ro sid-list* [value] augment /rt:routing/rt:control-plane-protocols
+--ro flags? bits /rt:control-plane-protocol/isis:isis/isis:database
+--ro weight? uint8 /isis:levels/isis:lsp/isis:extended-is-neighbor
+--ro neighbor-id? isis:system-id /isis:neighbor:
+--ro value uint32 +--ro sid-list* [value]
augment /rt:routing/rt:control-plane-protocols +--ro flags? bits
/rt:control-plane-protocol/isis:isis/isis:database +--ro weight? uint8
/isis:level-db/isis:lsp/isis:mt-is-neighbor/isis:neighbor: +--ro neighbor-id? isis:system-id
+--ro sid-list* [value] +--ro value uint32
+--ro flags? bits augment /rt:routing/rt:control-plane-protocols
+--ro weight? uint8 /rt:control-plane-protocol/isis:isis/isis:database
+--ro neighbor-id? isis:system-id /isis:levels/isis:lsp/isis:mt-is-neighbor/isis:neighbor:
+--ro value uint32 +--ro sid-list* [value]
augment /rt:routing/rt:control-plane-protocols +--ro flags? bits
/rt:control-plane-protocol/isis:isis/isis:database +--ro weight? uint8
/isis:level-db/isis:lsp/isis:extended-ipv4-reachability +--ro neighbor-id? isis:system-id
/isis:prefixes: +--ro value uint32
+--ro sid-list* [value] augment /rt:routing/rt:control-plane-protocols
+--ro flags? bits /rt:control-plane-protocol/isis:isis/isis:database
+--ro algorithm? uint8 /isis:levels/isis:lsp/isis:extended-ipv4-reachability
+--ro value uint32 /isis:prefixes:
augment /rt:routing/rt:control-plane-protocols +--ro sid-list* [value]
/rt:control-plane-protocol/isis:isis/isis:database +--ro flags? bits
/isis:level-db/isis:lsp/isis:mt-extended-ipv4-reachability +--ro algorithm? uint8
/isis:prefixes: +--ro value uint32
+--ro sid-list* [value] augment /rt:routing/rt:control-plane-protocols
+--ro flags? bits /rt:control-plane-protocol/isis:isis/isis:database
+--ro algorithm? uint8 /isis:levels/isis:lsp/isis:mt-extended-ipv4-reachability
+--ro value uint32 /isis:prefixes:
augment /rt:routing/rt:control-plane-protocols +--ro sid-list* [value]
/rt:control-plane-protocol/isis:isis/isis:database +--ro flags? bits
/isis:level-db/isis:lsp/isis:ipv6-reachability/isis:prefixes: +--ro algorithm? uint8
+--ro sid-list* [value] +--ro value uint32
+--ro flags? bits augment /rt:routing/rt:control-plane-protocols
+--ro algorithm? uint8 /rt:control-plane-protocol/isis:isis/isis:database
+--ro value uint32 /isis:levels/isis:lsp/isis:ipv6-reachability/isis:prefixes:
augment /rt:routing/rt:control-plane-protocols +--ro sid-list* [value]
/rt:control-plane-protocol/isis:isis/isis:database +--ro flags? bits
/isis:level-db/isis:lsp/isis:mt-ipv6-reachability +--ro algorithm? uint8
/isis:prefixes: +--ro value uint32
+--ro sid-list* [value] augment /rt:routing/rt:control-plane-protocols
+--ro flags? bits /rt:control-plane-protocol/isis:isis/isis:database
+--ro algorithm? uint8 /isis:levels/isis:lsp/isis:mt-ipv6-reachability
+--ro value uint32 /isis:prefixes:
augment /rt:routing/rt:control-plane-protocols +--ro sid-list* [value]
/rt:control-plane-protocol/isis:isis/isis:database +--ro flags? bits
/isis:level-db/isis:lsp: +--ro algorithm? uint8
+--ro segment-routing-bindings* [fec range] +--ro value uint32
+--ro fec string augment /rt:routing/rt:control-plane-protocols
+--ro range uint16 /rt:control-plane-protocol/isis:isis/isis:database
+--ro flags? bits /isis:levels/isis:lsp:
+--ro binding +--ro segment-routing-bindings* [fec range]
+--ro prefix-sid +--ro fec string
+--ro sid-list* [value] +--ro range uint16
+--ro flags? bits +--ro flags? bits
+--ro algorithm? uint8 +--ro binding
+--ro value uint32 +--ro prefix-sid
+--ro sid-list* [value]
+--ro flags? bits
+--ro algorithm? uint8
+--ro value uint32
5. IS-IS Segment Routing configuration 5. IS-IS Segment Routing configuration
5.1. Segment Routing activation 5.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 40 skipping to change at page 6, line 44
5.3. IP Fast reroute 5.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.
6. IS-IS Segment Routing YANG Module 6. IS-IS Segment Routing YANG Module
<CODE BEGINS> file "ietf-isis-sr@2019-03-06.yang" <CODE BEGINS> file "ietf-isis-sr@2019-07-07.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 {
skipping to change at page 7, line 31 skipping to change at page 7, line 35
contact contact
"WG List: <mailto:lsr@ietf.org> "WG List: <mailto:lsr@ietf.org>
Editor: Stephane Litkowski Editor: Stephane Litkowski
<mailto:stephane.litkowski@orange.com> <mailto:stephane.litkowski@orange.com>
Author: Acee Lindem Author: Acee Lindem
<mailto:acee@cisco.com> <mailto:acee@cisco.com>
Author: Yingzhen Qu Author: Yingzhen Qu
<mailto:yingzhen.qu@huawei.com> <mailto:yingzhen.qu@futurewei.com>
Author: Pushpasis Sarkar Author: Pushpasis Sarkar
<mailto:pushpasis.ietf@gmail.com> <mailto:pushpasis.ietf@gmail.com>
Author: Ing-Wher Chen Author: Ing-Wher Chen
<mailto:ingwherchen@mitre.org> <mailto:ingwherchen@mitre.org>
Author: Jeff Tantsura Author: Jeff Tantsura
<mailto:jefftant.ietf@gmail.com> <mailto:jefftant.ietf@gmail.com>
"; ";
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 2019-03-06 { revision 2019-07-07 {
description description
"Initial revision."; "Initial revision.";
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 18, line 19 skipping to change at page 18, line 24
} }
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:levels/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:levels/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:levels/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:levels/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/" + 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:levels/isis:lsp"+
"/isis:mt-extended-ipv4-reachability/isis:prefixes" { "/isis:mt-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/" + 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:levels/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;
} }
skipping to change at page 20, line 11 skipping to change at page 20, line 17
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:levels/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 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:levels/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;
} }
skipping to change at page 24, line 18 skipping to change at page 24, line 26
<https://www.rfc-editor.org/info/rfc8342>. <https://www.rfc-editor.org/info/rfc8342>.
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 Futurewei
Email: yingzhen.qu@huawei.com Email: yingzhen.qu@Futurewei.com
Pushpasis Sarkar Pushpasis Sarkar
Individual Individual
Email: pushpasis.ietf@gmail.com Email: pushpasis.ietf@gmail.com
Ing-Wher Chen Ing-Wher Chen
The MITRE Corporation The MITRE Corporation
Email: ingwherchen@mitre.org Email: ingwherchen@mitre.org
 End of changes. 23 change blocks. 
137 lines changed or deleted 144 lines changed or added

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