]> Cisco Systems

slitkows.ietf@gmail.com

Futurewei Technologies

yingzhen.ietf@gmail.com

Individual

pushpasis.ietf@gmail.com

The MITRE Corporation

ingwherchen@mitre.org

Nvidia

jefftant.ietf@gmail.com

LSR Working Group This document defines a YANG data module that can be used to configure and manage IS-IS Segment Routing for MPLS data plane.

Overview This document defines a YANG data model that can be used to configure and manage IS-IS Segment Routing for MPLS data plane and it is an augmentation to the IS-IS YANG data model . The YANG module in this document conforms to the Network Management Datastore Architecture (NMDA) .

Requirements Language The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 when, and only when, they appear in all capitals, as shown here.

Tree Diagrams This document uses the graphical representation of data models defined in .

Design of the IS-IS MPLS Segment Routing Module This document defines a YANG model for IS-IS Segment Routing for the MPLS data plane. It is an augmentation of the IS-IS base model. The IS-IS SR MPLS YANG module requires support for the base segment routing module , which defines the global segment routing configuration independent of any specific routing protocol configuration, and support of IS-IS base model which defines basic IS-IS configuration and state.

Segment Routing Activation Activation of IS-IS SR MPLS is done by setting the "enable" leaf to true. This triggers advertisement of SR MPLS extensions based on the configuration parameters that have been setup using the base segment routing module.

Advertising Mapping Server Policy The base segment routing module defines mapping server policies. By default, IS-IS will not advertise or process any mapping server entry. The IS-IS SR MPLS module allows the advertisement of one or multiple mapping server policies through the "bindings/advertise/policies" leaf-list. The "bindings/receive" leaf controls the reception and process of mapping server entries.

IP Fast Reroute IS-IS SR MPLS model augments the fast-reroute container under interface. It brings the ability to activate TI-LFA (topology independent LFA) and also enhances remote LFA to use segment-routing tunneling instead of LDP.

IS-IS MPLS Segment Routing Module Tree The figure below describes the overall structure of the isis-sr-mpls YANG module: /rt:routing/sr:segment-routing | | /sr-mpls:sr-mpls/bindings | | /mapping-server/policy/name | +--rw receive? boolean +--rw protocol-srgb {sr-mpls:protocol-srgb}? +--rw srgb* [lower-bound upper-bound] +--rw lower-bound uint32 +--rw upper-bound uint32 augment /rt:routing/rt:control-plane-protocols /rt:control-plane-protocol/isis:isis /isis:interfaces/isis:interface: +--rw segment-routing +--rw adjacency-sid +--rw adj-sids* [value] | +--rw value-type? enumeration | +--rw value uint32 | +--rw protected? boolean | +--rw weight? uint8 +--rw advertise-adj-group-sid* [group-id] | +--rw group-id uint32 +--rw advertise-protection? enumeration augment /rt:routing/rt:control-plane-protocols /rt:control-plane-protocol/isis:isis/isis:interfaces /isis:interface/isis:fast-reroute/isis:lfa: +--rw ti-lfa {ti-lfa}? +--rw enable? boolean +--rw selection-tie-breakers +--rw node-protection! | +--rw priority? uint8 +--rw srlg-disjoint! +--rw priority? uint8 augment /rt:routing/rt:control-plane-protocols /rt:control-plane-protocol/isis:isis/isis:interfaces /isis:interface/isis:fast-reroute/isis:lfa/isis:level-1: +--rw ti-lfa {ti-lfa}? +--rw enable? boolean augment /rt:routing/rt:control-plane-protocols /rt:control-plane-protocol/isis:isis/isis:interfaces /isis:interface/isis:fast-reroute/isis:lfa/isis:level-2: +--rw ti-lfa {ti-lfa}? +--rw enable? boolean augment /rt:routing/rt:control-plane-protocols /rt:control-plane-protocol/isis:isis/isis:interfaces /isis:interface/isis:fast-reroute/isis:lfa/isis:remote-lfa: +--rw use-segment-routing-path? boolean {remote-lfa-sr}? augment /rt:routing/rt:control-plane-protocols /rt:control-plane-protocol/isis:isis/isis:interfaces /isis:interface/isis:adjacencies/isis:adjacency: +--ro adjacency-sid* [value] +--ro value uint32 +--ro af? iana-rt-types:address-family +--ro weight? uint8 +--ro protection-requested? boolean augment /rt:routing/rt:control-plane-protocols /rt:control-plane-protocol/isis:isis/isis:database /isis:levels/isis:lsp/isis:router-capabilities: +--ro sr-capability | +--ro sr-capability | | +--ro sr-capability-bits* identityref | +--ro global-blocks | +--ro global-block* [] | +--ro range-size? uint32 | +--ro sid-sub-tlv | +--ro sid? uint32 +--ro sr-algorithms | +--ro sr-algorithm* identityref +--ro local-blocks | +--ro local-block* [] | +--ro range-size? rt-types:uint24 | +--ro sid-sub-tlv | +--ro sid? uint32 +--ro srms-preference +--ro preference? uint8 augment /rt:routing/rt:control-plane-protocols /rt:control-plane-protocol/isis:isis/isis:database /isis:levels/isis:lsp/isis:extended-is-neighbor /isis:neighbor: +--ro sid-list* [value] +--ro value uint32 +--ro adj-sid-flags | +--ro bits* identityref +--ro weight? uint8 +--ro neighbor-id? isis:system-id augment /rt:routing/rt:control-plane-protocols /rt:control-plane-protocol/isis:isis/isis:database /isis:levels/isis:lsp/isis:mt-is-neighbor/isis:neighbor: +--ro sid-list* [value] +--ro value uint32 +--ro adj-sid-flags | +--ro bits* identityref +--ro weight? uint8 +--ro neighbor-id? isis:system-id augment /rt:routing/rt:control-plane-protocols /rt:control-plane-protocol/isis:isis/isis:database /isis:levels/isis:lsp/isis:extended-ipv4-reachability /isis:prefixes: +--ro sid-list* [value] +--ro value uint32 +--ro perfix-sid-flags | +--ro bits* identityref +--ro algorithm? identityref augment /rt:routing/rt:control-plane-protocols /rt:control-plane-protocol/isis:isis/isis:database /isis:levels/isis:lsp/isis:mt-extended-ipv4-reachability /isis:prefixes: +--ro sid-list* [value] +--ro value uint32 +--ro prefix-sid-flags | +--ro bits* identityref +--ro algorithm? identityref augment /rt:routing/rt:control-plane-protocols /rt:control-plane-protocol/isis:isis/isis:database /isis:levels/isis:lsp/isis:ipv6-reachability/isis:prefixes: +--ro sid-list* [value] +--ro value uint32 +--ro perfix-sid-flags | +--ro bits* identityref +--ro algorithm? identityref augment /rt:routing/rt:control-plane-protocols /rt:control-plane-protocol/isis:isis/isis:database /isis:levels/isis:lsp/isis:mt-ipv6-reachability /isis:prefixes: +--ro sid-list* [value] +--ro value uint32 +--ro perfix-sid-flags | +--ro bits* identityref +--ro algorithm? identityref augment /rt:routing/rt:control-plane-protocols /rt:control-plane-protocol/isis:isis/isis:database /isis:levels/isis:lsp: +--ro segment-routing-bindings* [prefix range] +--ro prefix inet:ip-prefix +--ro range uint16 +--ro sid-binding-flags | +--ro bits* identityref +--ro binding +--ro prefix-sid +--ro sid-list* [value] +--ro value uint32 +--ro perfix-sid-flags | +--ro bits* identityref +--ro algorithm? identityref ]]>

IS-IS MPLS Segment Routing YANG Module , , , , , and are referenced in the YANG model. WG List: Author: Stephane Litkowski Author: Yingzhen Qu Author: Acee Lindem Author: Pushpasis Sarkar Author: Ing-Wher Chen Author: Jeff Tantsura "; description "The YANG module defines the generic configuration and operational state for Segment Routing ISIS extensions for the MPLS data plane, which is common across all of the vendor implementations. This YANG model conforms to the Network Management Datastore Architecture (NMDA) as described in RFC 8342. Copyright (c) 2023 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Revised BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info). This version of this YANG module is part of RFC XXXX (https://www.rfc-editor.org/info/rfcXXXX); see the RFC itself for full legal notices. The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'NOT RECOMMENDED', 'MAY', and 'OPTIONAL' in this document are to be interpreted as described in BCP 14 (RFC 2119) (RFC 8174) when, and only when, they appear in all capitals, as shown here. This version of this YANG module is part of RFC XXXX; see the RFC itself for full legal notices."; reference "RFC XXXX"; revision 2023-12-16 { description "Initial revision."; reference "RFC XXXX: A YANG Data Model for IS-IS Segment Routing for the MPLS Data Plane"; } /* Identities */ identity sr-capability { description "Base identity for ISIS SR-Capabilities sub-TLV flags"; reference "RFC 8667 - IS-IS Extensions for Segment Routing"; } identity mpls-ipv4 { base sr-capability; description "If set, then the router is capable of processing SR MPLS encapsulated IPv4 packets on all interfaces."; } identity mpls-ipv6 { base sr-capability; description "If set, then the router is capable of processing SR MPLS encapsulated IPv6 packets on all interfaces."; } identity prefix-sid-bit { description "Base identity for prefix SID sub-TLV bits."; reference "RFC 8667 - IS-IS Extensions for Segment Routing"; } identity r-bit { base prefix-sid-bit; description "Re-advertisement Flag."; } identity n-bit { base prefix-sid-bit; description "Node-SID Flag."; } identity p-bit { base prefix-sid-bit; description "No-PHP (No Penultimate Hop-Popping) Flag."; } identity e-bit { base prefix-sid-bit; description "Explicit NULL Flag."; } identity v-bit { base prefix-sid-bit; description "Value Flag."; } identity l-bit { base prefix-sid-bit; description "Local Flag."; } identity adj-sid-bit { description "Base identity for Adj-SID sub-TLV bits."; reference "RFC 8667 - IS-IS Extensions for Segment Routing"; } identity f-bit { base adj-sid-bit; description "Address-Family flag."; } identity b-bit { base adj-sid-bit; description "Backup flag."; } identity vi-bit { base adj-sid-bit; description "Value/Index flag."; } identity lo-bit { base adj-sid-bit; description "Local flag."; } identity s-bit { base adj-sid-bit; description "Group flag."; } identity pe-bit { base adj-sid-bit; description "Persistent flag."; } identity sid-binding-bit { description "Base identity for sid binding tlv bits."; reference "RFC 8667 - IS-IS Extensions for Segment Routing"; } identity af-bit { base sid-binding-bit; description "Address-Family flag."; } identity m-bit { base sid-binding-bit; description "Mirror Context flag."; } identity sf-bit { base sid-binding-bit; description "S flag. If set, the binding label TLV should be flooded across the entire routing domain."; } identity d-bit { base sid-binding-bit; description "Leaking flag."; } identity a-bit { base sid-binding-bit; description "Attached flag."; } /* Features */ feature remote-lfa-sr { description "Enhance rLFA to use SR path."; reference "RFC 8102: Remote-LFA Node Protection and Manageability"; } feature ti-lfa { description "Topology-Independent Loop-Free Alternate (TI-LFA) computation using segment routing."; reference "draft-ietf-rtgwg-segment-routing-ti-lfa - Topology-Independent Fast Reroute using Segment Routing"; } /* Groupings */ grouping sid-sub-tlv { description "SID/Label sub-TLV grouping."; container sid-sub-tlv { description "Used to advertise the SID/Label associated with a prefix or adjacency."; leaf sid { type uint32; description "Segment Identifier (SID) - A 20 bit label or 32 bit SID."; } } } grouping sr-capability { description "SR capability grouping."; container sr-capability { description "Segment Routing capability."; container sr-capability { leaf-list sr-capability-bits { type identityref { base sr-capability; } description "SR Capability sub-TLV flags list."; } description "SR Capability Flags."; } container global-blocks { description "Segment Routing Global Blocks."; list global-block { description "Segment Routing Global Block."; leaf range-size { type uint32; description "The SID range."; } uses sid-sub-tlv; } } } } grouping sr-algorithm { description "SR algorithm grouping."; container sr-algorithms { description "All SR algorithms."; leaf-list sr-algorithm { type identityref { base sr-cmn:prefix-sid-algorithm; } description "The Segment Routing (SR) algorithms that the router is currently using."; } } } grouping srlb { description "SR Local Block grouping."; container local-blocks { description "List of SRLBs."; list local-block { description "Segment Routing Local Block."; leaf range-size { type rt-types:uint24; description "The SID range."; } uses sid-sub-tlv; } } } grouping srms-preference { description "The SRMS preference TLV is used to advertise a preference associated with the node that acts as an SR Mapping Server."; container srms-preference { description "SRMS Preference TLV."; leaf preference { type uint8 { range "0 .. 255"; } description "SRMS preference TLV, value from 0 to 255."; } } } grouping adjacency-state { description "This group will extend adjacency state."; list adjacency-sid { key "value"; config false; leaf value { type uint32; description "Value of the Adj-SID."; } leaf af { type iana-rt-types:address-family; description "Address-family associated with the segment ID"; } leaf weight { type uint8; description "Weight associated with the adjacency SID."; } leaf protection-requested { type boolean; description "Describe if the adjacency SID must be protected."; } description "List of adjacency Segment IDs."; } } grouping prefix-segment-id { description "This group defines segment routing extensions for prefixes."; list sid-list { key "value"; leaf value { type uint32; description "Value of the prefix-SID."; } container prefix-sid-flags { leaf-list bits { type identityref { base prefix-sid-bit; } description "Prefix SID sub-TLV flag bits list."; } description "Describes flags associated with the segment ID."; } leaf algorithm { type identityref { base sr-cmn:prefix-sid-algorithm; } description "Algorithm to be used for path computation."; } description "List of segments."; } } grouping adjacency-segment-id { description "This group defines segment routing extensions for adjacencies."; list sid-list { key "value"; leaf value { type uint32; description "Value of the Adj-SID."; } container adj-sid-flags { leaf-list bits { type identityref { base adj-sid-bit; } description "Adj-SID sub-TLV flags list."; } description "Adj-SID sub-TLV flags."; } leaf weight { type uint8; description "The value represents the weight of the Adj-SID for the purpose of load balancing."; } leaf neighbor-id { type isis:system-id; description "Describes the system ID of the neighbor associated with the SID value. This is only used on LAN adjacencies."; } description "List of segments."; } } grouping segment-routing-binding-tlv { list segment-routing-bindings { key "prefix range"; leaf prefix { type inet:ip-prefix; description "The prefix represents the Forwarding Equivalence Class at the tail end of the advertised path."; } leaf range { type uint16; description "Describes number of elements to assign a binding to."; } container sid-binding-flags { leaf-list bits { type identityref { base sid-binding-bit; } description "SID Binding TLV flag bits list."; } description "Binding flags."; } container binding { container prefix-sid { uses prefix-segment-id; description "Binding prefix SID to the range."; } description "Bindings associated with the range."; } description "This container describes list of SID/Label bindings. ISIS reference is TLV 149."; } description "Defines binding TLV for database."; } /* Configuration */ augment "/rt:routing/" + "rt:control-plane-protocols/rt:control-plane-protocol" + "/isis:isis" { when "derived-from-or-self(../rt:type, 'isis:isis')" { description "This augments ISIS routing protocol when used"; } description "This augments ISIS protocol configuration with segment routing."; uses sr-mpls:sr-control-plane; container protocol-srgb { if-feature "sr-mpls:protocol-srgb"; uses sr-cmn:srgb; description "Per-protocol SRGB."; } } augment "/rt:routing/" + "rt:control-plane-protocols/rt:control-plane-protocol" + "/isis:isis/isis:interfaces/isis:interface" { when "derived-from-or-self(../../../rt:type, 'isis:isis')" { description "This augments ISIS routing protocol when used"; } description "This augments ISIS protocol configuration with segment routing."; uses sr-mpls:igp-interface; } augment "/rt:routing/" + "rt:control-plane-protocols/rt:control-plane-protocol" + "/isis:isis/isis:interfaces/isis:interface" + "/isis:fast-reroute/isis:lfa" { when "derived-from-or-self(../../../../../rt:type," + "'isis:isis')" { description "This augments ISIS routing protocol when used"; } description "This augments ISIS interface IP FRR with TILFA."; container ti-lfa { if-feature "ti-lfa"; leaf enable { type boolean; default false; description "Enables TI-LFA computation."; } container selection-tie-breakers { container node-protection { presence "Presence of container enables the node protection tie-breaker"; leaf priority { type uint8; default 128; description "Priority for node protection tie-breaker with a lower priority being more preferred."; } description "Enable node protection as a TI-LFA path selection tie-breaker. A path providing node protection will be selected over one that doesn't provide node protection."; } container srlg-disjoint { presence "Presence of container enables the SRLG disjoint tie-breaker"; leaf priority { type uint8; default 128; description "Priority for SRLG disjoint tie-breaker with a lower priority being more preferred."; } description "Enable SRLG (Shared Resource Link Group) disjoint as a TI-LFA path selection tie-breaker. A path providing node a disjoint path for SRLG links from the primary path will be selected over one that doesn't provide an SRLG disjoint path."; } description "Configure path selection tie-breakers and their respective priorities for the TI-LFA computation."; } description "Topology Independent Loop Free Alternate (TI-LFA) support."; } } augment "/rt:routing/" + "rt:control-plane-protocols/rt:control-plane-protocol" + "/isis:isis/isis:interfaces/isis:interface" + "/isis:fast-reroute/isis:lfa/isis:level-1" { when "derived-from-or-self(../../../../../../rt:type," + "'isis:isis')" { description "This augments ISIS routing protocol when used"; } description "This augments ISIS interface level-1 IP FRR with TILFA."; container ti-lfa { if-feature "ti-lfa"; leaf enable { type boolean; default false; description "Enables TI-LFA computation."; } description "TI-LFA configuration."; } } augment "/rt:routing/" + "rt:control-plane-protocols/rt:control-plane-protocol" + "/isis:isis/isis:interfaces/isis:interface" + "/isis:fast-reroute/isis:lfa/isis:level-2" { when "derived-from-or-self(../../../../../../rt:type," + "'isis:isis')" { description "This augments ISIS routing protocol when used"; } description "This augments ISIS IP interface level-2 FRR with TILFA."; container ti-lfa { if-feature "ti-lfa"; leaf enable { type boolean; default false; description "Enables TI-LFA computation."; } description "TI-LFA configuration."; } } augment "/rt:routing/" + "rt:control-plane-protocols/rt:control-plane-protocol" + "/isis:isis/isis:interfaces/isis:interface" + "/isis:fast-reroute/isis:lfa/isis:remote-lfa" { when "derived-from-or-self(../../../../../../rt:type," + "'isis:isis')" { description "This augments ISIS routing protocol when used"; } description "This augments ISIS remoteLFA config with use of segment-routing path."; leaf use-segment-routing-path { if-feature "remote-lfa-sr"; type boolean; default false; description "Force remote LFA to use segment routing path instead of LDP path. The value of this leaf is in effect only when remote-lfa is enabled."; } } /* Operational states */ augment "/rt:routing/" + "rt:control-plane-protocols/rt:control-plane-protocol" + "/isis:isis/isis:interfaces/isis:interface" + "/isis:adjacencies/isis:adjacency" { when "derived-from-or-self(../../../../../rt:type, 'isis:isis')" { description "This augments ISIS routing protocol when used"; } description "This augments ISIS protocol configuration with segment routing."; uses adjacency-state; } augment "/rt:routing/" + "rt:control-plane-protocols/rt:control-plane-protocol" + "/isis:isis/isis:database/isis:levels/isis:lsp" + "/isis:router-capabilities" { when "derived-from-or-self(../../../../../rt:type, 'isis:isis')" { description "This augments ISIS routing protocol when used"; } description "This augments ISIS protocol LSDB router capability."; uses sr-capability; uses sr-algorithm; uses srlb; uses srms-preference; } augment "/rt:routing/" + "rt:control-plane-protocols/rt:control-plane-protocol" + "/isis:isis/isis:database/isis:levels/isis:lsp" + "/isis:extended-is-neighbor/isis:neighbor" { when "derived-from-or-self(../../../../../../rt:type," + "'isis:isis')" { description "This augments ISIS routing protocol when used"; } description "This augments ISIS protocol LSDB neighbor."; uses adjacency-segment-id; } augment "/rt:routing/" + "rt:control-plane-protocols/rt:control-plane-protocol" + "/isis:isis/isis:database/isis:levels/isis:lsp" + "/isis:mt-is-neighbor/isis:neighbor" { when "derived-from-or-self(../../../../../../rt:type," + "'isis:isis')" { description "This augments ISIS routing protocol when used"; } description "This augments ISIS protocol LSDB neighbor."; uses adjacency-segment-id; } augment "/rt:routing/" + "rt:control-plane-protocols/rt:control-plane-protocol" + "/isis:isis/isis:database/isis:levels/isis:lsp" + "/isis:extended-ipv4-reachability/isis:prefixes" { when "derived-from-or-self(../../../../../../rt:type," + "'isis:isis')" { description "This augments ISIS routing protocol when used"; } description "This augments ISIS protocol LSDB prefix."; uses prefix-segment-id; } augment "/rt:routing/" + "rt:control-plane-protocols/rt:control-plane-protocol" + "/isis:isis/isis:database/isis:levels/isis:lsp" + "/isis:mt-extended-ipv4-reachability/isis:prefixes" { when "derived-from-or-self(../../../../../../rt:type," + "'isis:isis')" { description "This augments ISIS routing protocol when used"; } description "This augments ISIS protocol LSDB prefix."; uses prefix-segment-id; } augment "/rt:routing/" + "rt:control-plane-protocols/rt:control-plane-protocol" + "/isis:isis/isis:database/isis:levels/isis:lsp" + "/isis:ipv6-reachability/isis:prefixes" { when "derived-from-or-self(../../../../../../rt:type," + "'isis:isis')" { description "This augments ISIS routing protocol when used"; } description "This augments ISIS protocol LSDB prefix."; uses prefix-segment-id; } augment "/rt:routing/" + "rt:control-plane-protocols/rt:control-plane-protocol" + "/isis:isis/isis:database/isis:levels/isis:lsp" + "/isis:mt-ipv6-reachability/isis:prefixes" { when "derived-from-or-self(../../../../../../rt:type," + "'isis:isis')" { description "This augments ISIS routing protocol when used"; } description "This augments ISIS protocol LSDB prefix."; uses prefix-segment-id; } augment "/rt:routing/" + "rt:control-plane-protocols/rt:control-plane-protocol" + "/isis:isis/isis:database/isis:levels/isis:lsp" { when "derived-from-or-self(../../../../rt:type," + "'isis:isis')" { description "This augments ISIS routing protocol when used"; } description "This augments ISIS protocol LSDB."; uses segment-routing-binding-tlv; } } ]]>

Security Considerations The YANG module specified in this document defines a schema for data that is designed to be accessed via network management protocols such as NETCONF or RESTCONF . The lowest NETCONF layer is the secure transport layer, and the mandatory-to-implement secure transport is Secure Shell (SSH) . The lowest RESTCONF layer is HTTPS, and the mandatory-to-implement secure transport is TLS . The NETCONF Access Control Model (NACM) provides the means to restrict access for particular NETCONF or RESTCONF users to a pre-configured subset of all available NETCONF or RESTCONF protocol operations and content. There are a number of data nodes defined in this YANG module that are writable/creatable/deletable (i.e., config true, which is the default). These data nodes may be considered sensitive or vulnerable in some network environments. Write operations (e.g., edit-config) to these data nodes without proper protection can have a negative effect on network operations. These are the subtrees and data nodes and their sensitivity/vulnerability:

• /isis:isis/segment-routing
• /isis:isis/protocol-srgb
• /isis:isis/isis:interfaces/isis:interface/segment-routing
• /isis:isis/isis:interfaces/isis:interface/isis:fast-reroute/ti-lfa

Some of the readable data nodes in the modules may be considered sensitive or vulnerable in some network environments. It is thus important to control read access (e.g., via get, get-config, or notification) to these data nodes.

• /isis:router-capabilities/sr-capability
• /isis:router-capabilities/sr-algorithms
• /isis:router-capabilities/local-blocks
• /isis:router-capabilities/srms-preference
• /isis:router-capabilities/node-msd-tlv
• And the augmentations to the ISIS link state database.

Unauthorized access to any data node of these subtrees can disclose the operational state information of IS-IS protocol on this device.

Contributors Authors would like to thank Derek Yeung, Acee Lindem, Yi Yang for their major contributions to the draft.

Acknowledgements MITRE has approved this document for Public Release, Distribution Unlimited, with Public Release Case Number 19-3033.

IANA Considerations The IANA is requested to assign one new URI from the IETF XML registry (). Authors are suggesting the following URI: This document also requests one new YANG module name in the YANG Module Names registry () with the following suggestion :

References Normative References Informative References

A Configuration Example The following is an XML example using the ISIS SR MPLS YANG module defined in this document. Note: '\' line wrapping per . 1.1.1.1 \ isis:isis isis 1111.2222.3333 38888 true 4000 5000 ]]> The following is the same example using JSON format.