IS-IS YANG Model Augmentations for Additional Features

Overview YANG is a data definition language used to define the contents of a conceptual data store that allows networked devices to be managed using NETCONF . YANG is proving relevant beyond its initial confines, as bindings to other interfaces (e.g., ReST) and encodings other than XML (e.g., JSON) are being defined. Furthermore, YANG data models can be used as the basis for implementation of other interfaces, such as CLI and programmatic APIs. This document defines YANG data modules augmenting the IETF IS-IS YANG model , which itself augments , to provide support for configuration and operational state for the following IS-IS features:

RFC7987:: IS-IS Minimum Remaining Lifetime.
RFC8919:: IS-IS Application-Specific Link Attributes.
RFCxxxx:: IGP Flexible Algorithm .

The augmentations defined in this document requires support for the IS-IS base model which defines basic IS-IS configuration and state. The IS-IS YANG model augments the ietf-routing YANG model defined in .

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 diagram Tree diagrams used in this document follow the notation defined in .

YANG Module for IS-IS Minimum Remaining Lifetime This document defines a YANG module for IS-IS Minimum Remaining Lifetime as defined in . It is an augmentation of the IS-IS base model. /rt:routing /control-plane-protocols /control-plane-protocol/name +--ro isis-level? level +--ro lsp-id? isis:lsp-id ]]> WG List: Author: Yingzhen Qu Author: Acee Lindem Author: Stephane Litkowski "; description "This YANG module defines the configuration and operational state for IS-IS Minimum Remaining Lifetime feature as defined in RFC 7987. Copyright (c) 2021 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 (http://trustee.ietf.org/license-info). This version of this YANG module is part of RFC XXXX; see the RFC itself for full legal notices."; reference "RFC XXXX"; revision 2021-12-22 { description "Initial version"; reference "RFC XXXX: A YANG Data Model for IS-IS Minimum Remaining Lifetime"; } notification corrupt-remaining-lifetime { uses isis:notification-instance-hdr; leaf lsp-id { type isis:lsp-id; description "LSP ID"; } description "This notification is sent when the system detects corrupted lifetime of an LSP."; reference "RFC 7987: IS-IS Minimum Remaining Lifetime"; } } ]]>

YANG Module for IS-IS Application-Specific Link Attributes This document defines a YANG module for IS-IS Application-Specific Link Attributes . It is an augmentation of the IS-IS base model. WG List: Author: Yingzhen Qu Author: Acee Lindem Author: Stephane Litkowski "; description "This YANG module defines the configuration and operational state for IS-IS application specific link attributes feature as defined in RFC 8919. This YANG model conforms to the Network Management Datastore Architecture (NMDA) as described in RFC 8342. Copyright (c) 2022 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 (http://trustee.ietf.org/license-info). This version of this YANG module is part of RFC XXXX; 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."; reference "RFC XXXX"; revision 2022-03-06 { description "Initial version"; reference "RFC XXXX: A YANG Data Model for IS-IS Application-Specific Link Attributes."; } identity sabm-bit { description "Base identity for sabm bits."; reference "RFC 8919: IS-IS Application-Specific Link Attributes"; } identity rsvp-te-bit { base sabm-bit; description "R bit, RSVP-TE."; } identity sr-policy-bit { base sabm-bit; description "S bit, Segment Routing Policy."; } identity lfa-bit { base sabm-bit; description "F bit, Loop Free Alternate (LFA). Includes all LFA types."; } grouping application-identifier-bit-mask { description "Identification of the set of applications associated with link attribute advertisements"; leaf l-flag { type boolean; description "Legacy Flag. When set, all of the applications specified in the bit mask MUST use the legacy advertisements."; } leaf sabm-length { type uint8; description "Standard Application Identifier Bit Mask Length in octets."; } leaf r-flag { type boolean; default false; description "Reserved."; } leaf udabm-length { type uint8; description "User Defined Application Identifier Bit Mask Length in octets."; } container sabm { leaf-list sabm-bits { type identityref { base sabm-bit; } description "SABM bits list. This list will contain identities for the bits which are set in the SABA bits."; } description "Standard Application Identifier Bit Mask."; } container udabm { description "User Defined Application Identifier Bit Mask. This container is to be augmented by user defined applications."; } } grouping application-specific-link-attributes-sub-tlv { description "Grouping for specification of the applications and application-specific attribute values."; container application-specific-link-attributes-sub-tlvs { list asla-sub-tlvs { uses application-identifier-bit-mask; uses isis:unknown-tlvs; description "List of application specific link attributes sub-tlvs."; } description "Application specific link attributes sub-tlv."; } } grouping application-specific-srlg-tlv { description "Grouping of a TLV to advertise application-specific SRLGs for a given link."; container application-specific-srlg-tlv { list as-srlg-tlvs { leaf neighbor-system-id { type isis:system-id; description "Neighbor System-ID."; } leaf pseudo-node-id { type uint8; description "Pseudo-node ID."; } uses application-identifier-bit-mask; leaf length-of-sub-tlvs { type uint8; description "Length of sub-tlvs."; } container link-id-sub-tlvs { description "Link Identifier sub-TLVs."; container link-local-remote-ids { description "Link local/remote identifier sub-tlv."; leaf link-local-id { type union { type inet:ipv4-address; type uint32; } description "Local identifier of the link. It could be an IPv4 address or a local identifier."; } leaf link-remote-id { type union { type inet:ipv4-address; type uint32; } description "Remote identifier of the link. It could be an IPv4 address or a remotely learned identifier."; } } container ipv4-interface-addr { leaf ipv4-int-addr { type inet:ipv4-address; description "IPv4 address for the interface."; } description "IPv4 interface address sub-tlv."; } container ipv4-neighbor-addr { leaf ipv4-neighbor-addr { type inet:ipv4-address; description "IPv4 address for a neighboring router on this link."; } description "IPv4 neighbor address sub-tlv."; } container ipv6-interface-addr { leaf ipv6-int-addr { type inet:ipv6-address; description "IPv6 address for the interface."; } description "IPv6 interface address sub-tlv."; } container ipv6-neighbor-addr { leaf ipv6-neighbor-addr { type inet:ipv6-address; description "IPv6 address for a neighboring router on this link."; } description "IPv6 neighbor address sub-tlv."; } } container srlgs { description "List of SRLGs."; leaf-list srlg { type uint32; description "SRLG value of the link."; } } description "List of application specific SRLG tlvs."; } description "Application specific SRLG tlv."; } } augment "/rt:routing/" + "rt:control-plane-protocols/rt:control-plane-protocol"+ "/isis:isis/isis:interfaces/isis:interface" { when "/rt:routing/rt:control-plane-protocols/"+ "rt:control-plane-protocol/rt:type = 'isis:isis'" { description "This augment ISIS routing protocol when used."; } description "This augments ISIS protocol configuration with TE attributes per application."; container isis-link-attr { choice link-attr-op-mode { mandatory "true"; leaf legacy { type empty; description "Only send legacy advertisements."; } leaf transition { type empty; description "Send both application-specific and legacy advertisements."; } leaf app-specific{ type empty; description "Only send application-specific advertisements."; } description "Link attributes mode"; } description "Link attributes operation mode."; } } /* TLV 22 */ 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"+ "/isis:instances/isis:instance" { when "/rt:routing/rt:control-plane-protocols/"+ "rt:control-plane-protocol/rt:type = 'isis:isis'" { description "This augment ISIS routing protocol when used"; } description "This augments ISIS protocol LSDB TLV22."; uses application-specific-link-attributes-sub-tlv; } /* TLV 223 */ 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"+ "/isis:instances/isis:instance" { when "/rt:routing/rt:control-plane-protocols/"+ "rt:control-plane-protocol/rt:type = 'isis:isis'" { description "This augment ISIS routing protocol when used"; } description "This augments ISIS protocol LSDB TLV223."; uses application-specific-link-attributes-sub-tlv; } /* application-specific SRLG TLV 238 */ augment "/rt:routing/" + "rt:control-plane-protocols/rt:control-plane-protocol"+ "/isis:isis/isis:database/isis:levels/isis:lsp" { when "/rt:routing/rt:control-plane-protocols/"+ "rt:control-plane-protocol/rt:type = 'isis:isis'" { description "This augment ISIS routing protocol when used"; } description "This augments ISIS protocol LSDB."; uses application-specific-srlg-tlv; } } ]]>

YANG Module for IS-IS Flexible Algorithm This document defines a YANG module for IS-IS Flexible Algorithm . It is an augmentation of the IS-IS base model. /te:te/globals /named-admin-groups /named-admin-group/name | +--rw include-any-admin-groups* -> /te:te/globals /named-admin-groups /named-admin-group/name | +--rw include-all-admin-groups* -> /te:te/globals /named-admin-groups /named-admin-group/name +--rw exclude-srlgs* -> /te:te/globals /named-srlgs/named-srlg/name {te-types:named-srlg-groups}? +--rw fast-reroute? boolean +--rw metric-type? identityref +--rw microloop-avoidance? boolean +--rw prefix-metric! +--rw priority? uint8 augment /rt:routing/rt:control-plane-protocols /rt:control-plane-protocol/isis:isis/isis:database /isis:levels/isis:lsp/isis:router-capabilities: +--ro fad-tlvs +--ro fad-tlv* [] +--ro flex-algo? uint8 +--ro metric-type? identityref +--ro calc-type? uint8 +--ro priority? uint8 +--ro fa-ex-ag-sub-tlv | +--ro extended-admin-groups* uint64 +--ro fa-in-any-ag-sub-tlv | +--ro extended-admin-groups* uint64 +--ro fa-in-all-ag-sub-tlv | +--ro extended-admin-groups* uint64 +--ro fad-flags-sub-tlv | +--ro fad-flags* identityref +--ro fa-ex-srlg-sub-tlv | +--ro srlgs* uint32 +--ro unknown-tlvs +--ro unknown-tlv* [] +--ro type? uint16 +--ro length? uint16 +--ro value? yang:hex-string 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 fapm-sub-tlvs +--ro fapm-sub-tlv* [] +--ro flex-algo? uint8 +--ro metric? uint32 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 fapm-sub-tlvs +--ro fapm-sub-tlv* [] +--ro flex-algo? uint8 +--ro metric? uint32 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 fapm-sub-tlvs +--ro fapm-sub-tlv* [] +--ro flex-algo? uint8 +--ro metric? uint32 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 fapm-sub-tlvs +--ro fapm-sub-tlv* [] +--ro flex-algo? uint8 +--ro metric? uint32 notifications: +---n flex-algo-not-supported +--ro routing-protocol-name? -> /rt:routing /control-plane-protocols /control-plane-protocol/name +--ro isis-level? level +--ro flex-algo-number? uint8 ]]> WG List: Author: Yingzhen Qu Author: Acee Lindem Author: Stephane Litkowski "; description "The YANG module defines the configuration and operational state for ISIS Flexible Algorithm as defined in RFC xxxx. This YANG model conforms to the Network Management Datastore Architecture (NMDA) as described in RFC 8342. Copyright (c) 2022 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; 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."; reference "RFC XXXX: YANG Data Model for ISIS Flexible Algorithm."; revision 2022-03-06 { description "Initial Version"; reference "RFC XXXX: YANG Data Model for ISIS Flexible Algorithm."; } /* Identities */ identity metric-type { description "Base identity for route metric types."; } identity igp-metric { base metric-type; description "Identity for the IGP metric type."; } identity min-uni-delay { base metric-type; description "Min unidirectional link delay metric type."; reference "RFC 8570 - IS-IS Traffic Engineering (TE) Metric Extensions"; } identity te-metric { base metric-type; description "Traffic engineering metric type."; reference "RFC 5305 - IS-IS Extensions for Traffic Engineering (TE)"; } identity fad-flags { description "Base identity for ISIS FAD flags."; } identity m-bit { base fad-flags; description "M bit, when set, the flex-algo specific prefix and ASBR metric MUST be used for inter-area and external prefix calculation."; } /* Identity augmentation */ identity flex-algo-bit { base isis-link-attr:sabm-bit; description "X bit, flexible algorithm."; } /* Groupings */ grouping fa-ex-ag-sub-tlv { container fa-ex-ag-sub-tlv { leaf-list extended-admin-groups { type uint64; description "Extended administrative group as defined in RFC 7308."; } description "The flex-algo exclude admin group sub-tlv."; } description "The flex-algo exclude admin group sub-tlv."; } grouping fa-in-any-ag-sub-tlv { container fa-in-any-ag-sub-tlv { leaf-list extended-admin-groups { type uint64; description "Extended administrative group as defined in RFC 7308."; } description "The flex-algo include-any admin group sub-tlv."; } description "The flex-algo include-any admin group sub-tlv."; } grouping fa-in-all-ag-sub-tlv { container fa-in-all-ag-sub-tlv { leaf-list extended-admin-groups { type uint64; description "Extended administrative group as defined in RFC 7308."; } description "The flex-algo include-all admin group sub-tlv."; } description "The flex-algo include-all admin group sub-tlv."; } grouping fad-flags-sub-tlv { container fad-flags-sub-tlv { leaf-list fad-flags { type identityref { base fad-flags; } description "Flex-algo definition flags list."; } description "ISIS flex-algo definition flags."; } description "The flex-algo definition flags sub-tlv."; } grouping fa-ex-srlg-sub-tlv { container fa-ex-srlg-sub-tlv { leaf-list srlgs { type uint32; description "SRLG value as defined in RFC 4203."; } description "The flex-algo exclude SRLG sub-tlv."; } description "The flex-algo exclude SRLG sub-tlv."; } grouping fad-tlvs { container fad-tlvs { list fad-tlv { leaf flex-algo { type uint8; description "Flex-algo number, value between 128 and 255 inclusive."; } leaf metric-type { type identityref { base metric-type; } description "Type of metric to be used during the calculation."; } leaf calc-type { type uint8 { range "0..127"; } description "IGP algorithm types, value from 0 to 127 as defined under 'Interior Gateway Protocol (IGP) Parameter' by IANA."; } leaf priority { type uint8; description "Priority of the advertisement."; } uses fa-ex-ag-sub-tlv; uses fa-in-any-ag-sub-tlv; uses fa-in-all-ag-sub-tlv; uses fad-flags-sub-tlv; uses fa-ex-srlg-sub-tlv; uses isis:unknown-tlvs; description "List of flex-algo definition TLVs."; } description "ISIS Flexible Algorithm Definition TLV."; } description "ISIS Flexible Algorithm Definition (FAD) TLV."; } grouping fapm-sub-tlvs { container fapm-sub-tlvs { list fapm-sub-tlv { leaf flex-algo { type uint8; description "Flex-algo number, value between 128 and 255 inclusive."; } leaf metric { type uint32; description "Prefix metric."; } description "List of flex-algo prefix sub-tlvs."; } description "Flex-algo prefix metric sub-tlvs."; } description "Flexible Algorithm Prefix Metric (FAPM) sub TLVs."; } /* Configurations */ augment "/rt:routing/" + "rt:control-plane-protocols/rt:control-plane-protocol"+ "/isis:isis" { when "/rt:routing/rt:control-plane-protocols/"+ "rt:control-plane-protocol/rt:type = 'isis:isis'" { description "This augment ISIS routing protocol when used"; } description "This augments ISIS protocol configuration with flexible algorithm."; container isis-flex-algo { list flex-algo { key "algo-number"; leaf algo-number { type uint8 { range "128..255"; } description "An identifier in the range 128-255 that's associated with the Flexible Algorithm Definition."; } leaf advertise-definition { type boolean; default true; description "Enable to advertise the flex-algo definition."; } container admin-groups { if-feature "te-types:extended-admin-groups"; if-feature "te-types:named-extended-admin-groups"; leaf-list exclude-admin-groups { type leafref { path "/te:te/te:globals/te:named-admin-groups/" + "te:named-admin-group/te:name"; } description "Exclude rule used during the flex-algo path computation."; } leaf-list include-any-admin-groups { type leafref { path "/te:te/te:globals/te:named-admin-groups/" + "te:named-admin-group/te:name"; } description "Include-any rule used during the flex-algo path computation."; } leaf-list include-all-admin-groups { type leafref { path "/te:te/te:globals/te:named-admin-groups/" + "te:named-admin-group/te:name"; } description "Include-all rule used during the flex-algo path computation."; } description "Specify links for the flex-algo path computation."; } leaf-list exclude-srlgs { if-feature "te-types:named-srlg-groups"; type leafref { path "/te:te/te:globals/te:named-srlgs/te:named-srlg/" + "te:name"; } description "Shared Risk Link Groups (SRLGs) to be excluded during the flex-algo path computation."; } leaf fast-reroute { type boolean; default true; description "Enable fast reroute."; } leaf metric-type { type identityref { base metric-type; } description "Type of metric to be used during the calculation."; } leaf microloop-avoidance { type boolean; default true; description "Enable microloop avoidance."; } container prefix-metric { presence "Use flex-algo specific prefix metric."; description "Use flex-algo prefix metric."; } leaf priority { type uint8; description "Priority of the advertisement."; } description "List of flex-algo configurations."; } description "Flexible Algorithm configuration."; } } /* Database */ augment "/rt:routing/" + "rt:control-plane-protocols/rt:control-plane-protocol"+ "/isis:isis/isis:database/isis:levels/isis:lsp"+ "/isis:router-capabilities" { when "/rt:routing/rt:control-plane-protocols/"+ "rt:control-plane-protocol/rt:type = 'isis:isis'" { description "This augment ISIS routing protocol when used"; } description "This augments ISIS protocol LSDB router capability."; uses fad-tlvs; } 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 "/rt:routing/rt:control-plane-protocols/"+ "rt:control-plane-protocol/rt:type = 'isis:isis'" { description "This augment ISIS routing protocol when used"; } description "This augments ISIS protocol LSDB prefix."; uses fapm-sub-tlvs; } 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 "/rt:routing/rt:control-plane-protocols/"+ "rt:control-plane-protocol/rt:type = 'isis:isis'" { description "This augment ISIS routing protocol when used"; } description "This augments ISIS protocol LSDB prefix."; uses fapm-sub-tlvs; } 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 "/rt:routing/rt:control-plane-protocols/"+ "rt:control-plane-protocol/rt:type = 'isis:isis'" { description "This augment ISIS routing protocol when used"; } description "This augments ISIS protocol LSDB prefix."; uses fapm-sub-tlvs; } 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 "/rt:routing/rt:control-plane-protocols/"+ "rt:control-plane-protocol/rt:type = 'isis:isis'" { description "This augment ISIS routing protocol when used"; } description "This augments ISIS protocol LSDB prefix."; uses fapm-sub-tlvs; } /* notification */ notification flex-algo-not-supported { uses isis:notification-instance-hdr; leaf flex-algo-number { type uint8 { range "128..255"; } description "Flex-algo identifier which is not supported by the IS-IS instance."; } description "This notification is sent when an IS-IS instance does not support this flex-algo."; } } ]]>

IS-IS MSD This document defines a module for Signaling Maximum SID Depth (MSD) using IS-IS . It is an augmentation of the IS-IS base model. The figure below describes the overall structure of the isis-msd YANG module:

module: ietf-isis-msd augment /rt:routing/rt:control-plane-protocols /rt:control-plane-protocol/isis:isis/isis:database /isis:levels/isis:lsp/isis:router-capabilities: +--ro node-msd-tlv +--ro node-msds* [msd-type] +--ro msd-type identityref +--ro msd-value? 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 link-msd-sub-tlv +--ro link-msds* [msd-type] +--ro msd-type identityref +--ro msd-value? uint8 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 link-msd-sub-tlv +--ro link-msds* [msd-type] +--ro msd-type identityref +--ro msd-value? uint8

file "ietf-isis-msd@2022-09-05.yang" module ietf-isis-msd { yang-version 1.1; namespace "urn:ietf:params:xml:ns:yang:ietf-isis-msd"; prefix isis-msd; import ietf-routing { prefix rt; reference "RFC 8349: A YANG Data Model for Routing Management (NMDA Version)"; } import ietf-isis { prefix isis; } import ietf-mpls-msd { prefix mpls-msd; } organization "IETF LSR - LSR Working Group"; contact "WG Web: WG List: Author: Yingzhen Qu Author: Acee Lindem Author: Stephane Litkowski Author: Jeff Tantsura "; description "The YANG module augments the base ISIS model to manage different types of MSDs. This YANG model conforms to the Network Management Datastore Architecture (NMDA) as described in RFC 8342. Copyright (c) 2022 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."; reference "RFC XXXX: YANG Data Model for ISIS MSD"; revision 2022-09-05 { description "Initial Version"; reference "RFC XXXX: YANG Data Model for ISIS MSD."; } grouping link-msd-sub-tlv { description "Link Maximum SID Depth (MSD) grouping for an interface."; container link-msd-sub-tlv { list link-msds { key "msd-type"; leaf msd-type { type identityref { base mpls-msd:msd-base-type; } description "MSD-Types"; } leaf msd-value { type uint8; description "MSD value, in the range of 0-255."; } description "List of link MSDs"; } description "Link MSD sub-tlvs."; } } /* Node MSD TLV */ 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 augment ISIS routing protocol when used"; } description "This augments ISIS protocol LSDB router capability."; container node-msd-tlv { list node-msds { key "msd-type"; leaf msd-type { type identityref { base mpls-msd:msd-base-type; } description "MSD-Types"; } leaf msd-value { type uint8; description "MSD value, in the range of 0-255."; } description "Node MSD is the smallest link MSD supported by the node."; } description "Node MSD is the number of SIDs supported by a node."; reference "RFC 8491: Signaling Maximum SID Depth (MSD) Using IS-IS"; } } /* link MSD sub-tlv */ 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 augment ISIS routing protocol when used"; } description "This augments ISIS protocol LSDB neighbor with Link MSD sub-TLV."; uses link-msd-sub-tlv; } 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 augment ISIS routing protocol when used"; } description "This augments ISIS protocol LSDB neighbor."; uses link-msd-sub-tlv; } }

]]>


    
      Security Considerations
      The YANG modules specified in this document define 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  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 the modules
      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 correspond
      to the following schema nodes:
      
      
        /isis:isis/isis:interfaces/isis:interface/isis-link-attr - Modification 
          of link attributes operation mode could result in traffic being 
          redirected or DoS attack.
      
      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. The exposure of the Link State Database (LSDB) will
      expose the detailed topology of the network. This may be undesirable since
      both due to the fact that exposure may facilitate other attacks. Additionally, 
      network operators may consider their topologies to be sensitive confidential
      data.These correspond to the following schema nodes:
      
      
        /isis:isis/isis:database/isis:levels/isis:lsp/isis:mt-is-neighbor/isis:neighbor/isis:instances/isis:instance/application-specific-link-attributes-sub-tlvs 
        /isis:isis/isis:database/isis:levels/isis:lsp/application-specific-srlg-tlv 
        /isis:router-capabilities/node-msd-tlv
        /isis:isis/isis:database/isis:levels/isis:lsp//isis:extended-is-neighbor/isis:neighbor/link-msd-sub-tlv
        /isis:isis/isis:database/isis:levels/isis:lsp//isis:mt-is-neighbor/isis:neighbor/link-msd-sub-tlv
      
    
    
      IANA Considerations
      This document registers URIs in the IETF XML registry 
   .  Following the format in , 
   the following registrations is requested to be made:
      
      
      
      
     
      This document registers the YANG modules in the YANG Module Names
   registry .
      
      
      
      
     
    
    
      Acknowledgements
      This document was produced using Marshall Rose's xml2rfc tool.
      The YANG model was developed using the suite of YANG tools written 
         and maintained by numerous authors.