rfc9902v3.txt   rfc9902.txt 
skipping to change at line 76 skipping to change at line 76
Acknowledgements Acknowledgements
Authors' Addresses Authors' Addresses
1. Overview 1. Overview
This document defines a device YANG data model [RFC7950] that can be This document defines a device YANG data model [RFC7950] that can be
used to manage IS-IS extensions for Segment Routing (SR) [RFC8667] used to manage IS-IS extensions for Segment Routing (SR) [RFC8667]
over the MPLS data plane. It is an augmentation to the IS-IS YANG over the MPLS data plane. It is an augmentation to the IS-IS YANG
data model [RFC9130]. data model [RFC9130].
The YANG data model in this document conforms to the Network
Management Datastore Architecture (NMDA) [RFC8342].
1.1. Tree Diagrams 1.1. Tree Diagrams
This document uses the graphical representation of a data model as This document uses the graphical representation of a data model as
defined in [RFC8340]. defined in [RFC8340].
2. Design of the IS-IS MPLS Segment Routing Module 2. Design of the IS-IS MPLS Segment Routing Module
The IS-IS SR MPLS YANG module requires support for the base SR module The IS-IS SR MPLS YANG module requires support for the base SR module
[RFC9020], which defines the global SR management independent of any [RFC9020], which defines the global SR management independent of any
specific routing protocol configuration, and support of the IS-IS specific routing protocol configuration, and support of the IS-IS
skipping to change at line 186 skipping to change at line 183
Author: Yingzhen Qu Author: Yingzhen Qu
<mailto:yingzhen.ietf@gmail.com> <mailto:yingzhen.ietf@gmail.com>
Author: Acee Lindem Author: Acee Lindem
<mailto:acee.ietf@gmail.com> <mailto:acee.ietf@gmail.com>
Author: Ing-Wher Chen Author: Ing-Wher Chen
<mailto:ichen@redhat.com> <mailto:ichen@redhat.com>
Author: Jeff Tantsura Author: Jeff Tantsura
<mailto:jefftant.ietf@gmail.com> <mailto:jefftant.ietf@gmail.com>
"; ";
description description
"The YANG module defines the generic configuration and "This YANG module defines the generic configuration and
operational state for SR IS-IS extensions for the operational state for SR IS-IS extensions for the
MPLS data plane. MPLS data plane.
This YANG data model conforms to the Network Management
Datastore Architecture (NMDA) as described in RFC 8342.
Copyright (c) 2025 IETF Trust and the persons identified as Copyright (c) 2025 IETF Trust and the persons identified as
authors of the code. All rights reserved. authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with or Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject to without modification, is permitted pursuant to, and subject to
the license terms contained in, the Revised BSD License set the license terms contained in, the Revised BSD License set
forth in Section 4.c of the IETF Trust's Legal Provisions forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents Relating to IETF Documents
(https://trustee.ietf.org/license-info). (https://trustee.ietf.org/license-info).
skipping to change at line 678 skipping to change at line 672
grouping sid-binding-tlv { grouping sid-binding-tlv {
description description
"SID/Label Binding TLV, type 149."; "SID/Label Binding TLV, type 149.";
reference reference
"RFC 8667: IS-IS Extensions for Segment Routing, "RFC 8667: IS-IS Extensions for Segment Routing,
Section 2.4"; Section 2.4";
leaf prefix { leaf prefix {
type inet:ip-prefix; type inet:ip-prefix;
description description
"The prefix represents the Forwarding Equivalence "The prefix represents the Forwarding Equivalence
Class at the tail end of the advertised path."; Class (FEC)at the tail end of the advertised path.";
} }
leaf range { leaf range {
type uint16; type uint16;
description description
"Provides the ability to specify a range of addresses "Provides the ability to specify a range of addresses
and their associated Prefix-SIDs."; and their associated Prefix-SIDs.";
} }
container sid-binding-flags { container sid-binding-flags {
description description
"Binding TLV flags."; "Binding TLV flags.";
skipping to change at line 777 skipping to change at line 771
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:fast-reroute/isis:lfa" {
when "derived-from-or-self(../../../../../rt:type," when "derived-from-or-self(../../../../../rt:type,"
+ "'isis:isis')" { + "'isis:isis')" {
description description
"This augments the IS-IS routing protocol when used."; "This augments the IS-IS routing protocol when used.";
} }
description description
"This augments the IS-IS interface IP FRR with TI-LFA."; "This augments the IS-IS interface IP Fast Reroute (IP-FRR)
with TI-LFA.";
container ti-lfa { container ti-lfa {
if-feature "ti-lfa"; if-feature "ti-lfa";
description description
"Topology Independent Loop-Free Alternate "Topology Independent Loop-Free Alternate
(TI-LFA) support."; (TI-LFA) support.";
leaf enabled { leaf enabled {
type boolean; type boolean;
default "false"; default "false";
description description
"Enables TI-LFA computation."; "Enables TI-LFA computation.";
skipping to change at line 1184 skipping to change at line 1179
[RFC8294] Liu, X., Qu, Y., Lindem, A., Hopps, C., and L. Berger, [RFC8294] Liu, X., Qu, Y., Lindem, A., Hopps, C., and L. Berger,
"Common YANG Data Types for the Routing Area", RFC 8294, "Common YANG Data Types for the Routing Area", RFC 8294,
DOI 10.17487/RFC8294, December 2017, DOI 10.17487/RFC8294, December 2017,
<https://www.rfc-editor.org/info/rfc8294>. <https://www.rfc-editor.org/info/rfc8294>.
[RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration [RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration
Access Control Model", STD 91, RFC 8341, Access Control Model", STD 91, RFC 8341,
DOI 10.17487/RFC8341, March 2018, DOI 10.17487/RFC8341, March 2018,
<https://www.rfc-editor.org/info/rfc8341>. <https://www.rfc-editor.org/info/rfc8341>.
[RFC8342] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K.,
and R. Wilton, "Network Management Datastore Architecture
(NMDA)", RFC 8342, DOI 10.17487/RFC8342, March 2018,
<https://www.rfc-editor.org/info/rfc8342>.
[RFC8349] Lhotka, L., Lindem, A., and Y. Qu, "A YANG Data Model for [RFC8349] Lhotka, L., Lindem, A., and Y. Qu, "A YANG Data Model for
Routing Management (NMDA Version)", RFC 8349, Routing Management (NMDA Version)", RFC 8349,
DOI 10.17487/RFC8349, March 2018, DOI 10.17487/RFC8349, March 2018,
<https://www.rfc-editor.org/info/rfc8349>. <https://www.rfc-editor.org/info/rfc8349>.
[RFC8402] Filsfils, C., Ed., Previdi, S., Ed., Ginsberg, L., [RFC8402] Filsfils, C., Ed., Previdi, S., Ed., Ginsberg, L.,
Decraene, B., Litkowski, S., and R. Shakir, "Segment Decraene, B., Litkowski, S., and R. Shakir, "Segment
Routing Architecture", RFC 8402, DOI 10.17487/RFC8402, Routing Architecture", RFC 8402, DOI 10.17487/RFC8402,
July 2018, <https://www.rfc-editor.org/info/rfc8402>. July 2018, <https://www.rfc-editor.org/info/rfc8402>.
 End of changes. 6 change blocks. 
14 lines changed or deleted 4 lines changed or added

This html diff was produced by rfcdiff 1.48.