OSPF 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 OSPF YANG model , which itself augments , to provide support for configuration and operational state for the following OSPF features:

RFC5329:: Traffic Engineering Extensions to OSPF Version 3 .
RFC5392:: OSPF Extensions in Support of Inter-Autonomous System (AS) MPLS and GMPLS Traffic Engineering .
RFC8042:: OSPF Two-Part Metric .
RFC8379:: OSPF Graceful Link Shutdown .
RFC8476:: Signaling Maximum SID Depth (MSD) Using OSPF.
RFC8510:: OSPF Link-Local Signaling (LLS) Extensions for Local Interface ID Advertisement .
RFC9356:: Advertising Layer 2 Bundle Member Link Attributes in OSPF .
RFC9843:: IGP Flexible Algorithms: Bandwidth, Delay, Metrics and Constraints .

The augmentations defined in this document requires support for the OSPF base model which defines basic OSPF configuration and state. The OSPF 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", "MAY", and "OPTIONAL" in this document are to be interpreted as described in .

YANG Module for Traffic Engineering Extensions to OSPF This document defines a YANG module for Traffic Engineering Extensions to OSPF as defined in and . It is an augmentation of the OSPF base model. WG List: Author: Yingzhen Qu Author: Acee Lindem "; description "This YANG module defines the configuration and operational state for Traffic Engineering (TE) Extensions to OSPF Version 2 as defined in RFC 3630 and OSPFv3 extensions to support intra-area Traffic Engineering (TE) as defined in RFC 5329. Copyright (c) 2025 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."; reference "RFC XXXX"; revision 2025-02-27 { description "Initial version"; reference "RFC XXXX: OSPF YANG Model Augmentations for Additional Features - Version 1"; } identity ospfv3-intra-area-te-lsa { base ospf:ospfv3-lsa-type; description "OSPFv3 Intrea-area TE LSA."; } grouping ospfv3-intra-area-te { description "Grouping for OSPFv3 intra-area-te-lsa."; container ospfv3-intra-area-te { container router-address-tlv { description "The router IPv6 address tlv advertises a reachable IPv6 address."; leaf router-address { type inet:ipv6-address; description "Router IPv6 address."; } } container link-tlv { description "Describes a single link, and it is constructed of a set of Sub-TLVs."; leaf link-type { type ospf:router-link-type; mandatory true; description "Link type."; } container local-if-ipv6-addrs { description "All local interface IPv6 addresses."; leaf-list local-if-ipv6-addr { type inet:ipv6-address; description "List of local interface IPv6 addresses."; } } container remote-if-ipv6-addrs { description "All remote interface IPv6 addresses."; leaf-list remote-if-ipv6-addr { type inet:ipv6-address; description "List of remote interface IPv6 addresses."; } } leaf te-metric { type uint32; description "TE metric."; } leaf max-bandwidth { type rt-types:bandwidth-ieee-float32; description "Maximum bandwidth."; } leaf max-reservable-bandwidth { type rt-types:bandwidth-ieee-float32; description "Maximum reservable bandwidth."; } container unreserved-bandwidths { description "All unreserved bandwidths."; list unreserved-bandwidth { leaf priority { type uint8 { range "0 .. 7"; } description "Priority from 0 to 7."; } leaf unreserved-bandwidth { type rt-types:bandwidth-ieee-float32; description "Unreserved bandwidth."; } description "List of unreserved bandwidths for different priorities."; } } leaf admin-group { type uint32; description "Administrative group/Resource Class/Color."; } container neighbor-id { description "Neighbor link identification."; leaf nbr-interface-id { type uint32; mandatory true; description "The neighbor's interface ID."; } leaf nbr-router-id { type rt-types:router-id; mandatory true; description "The neighbor's router ID."; } } uses ospf:unknown-tlvs; } description "OSPFv3 Intra-Area-TE-LSA."; reference "RFC 5329: Traffic Engineering Extensions to OSPF Version 3"; } } /* Configuration */ augment "/rt:routing/" + "rt:control-plane-protocols/rt:control-plane-protocol" + "/ospf:ospf/ospf:mpls" { when "derived-from(/rt:routing/rt:control-plane-protocols/" + "rt:control-plane-protocol/rt:type, 'ospf:ospf')" { description "This augments the OSPF routing protocol when used."; } description "This augments OSPF protocol configuration with MPLS TE configuration."; container traffic-eng { description "OSPF MPLS TE configuration."; leaf enable { type boolean; default "false"; description "Enables traffic engineering advertisement in OSPF."; } reference "RFC 3630: Traffic Engineering (TE) Extensions to OSPF Version 2 RFC 5329: Traffic Engineering Extensions to OSPF Version 3"; } } augment "/rt:routing/rt:control-plane-protocols/" + "rt:control-plane-protocol/ospf:ospf/" + "ospf:areas/ospf:area/ospf:interfaces/ospf:interface" { when "derived-from(/rt:routing/rt:control-plane-protocols/" + "rt:control-plane-protocol/rt:type, 'ospf:ospf')" { description "This augments the OSPF routing protocol interface configuration."; } description "This augments OSPF interface with MPLS TE configuration."; container traffic-eng { description "OSPF interface MPLS TE configuration."; leaf enable { type boolean; default "false"; description "Enables OSPF MPLS traffic engineering functionality on the interface."; } } } /* Database */ augment "/rt:routing/" + "rt:control-plane-protocols/rt:control-plane-protocol/" + "ospf:ospf/ospf:areas/" + "ospf:area/ospf:database/" + "ospf:area-scope-lsa-type/ospf:area-scope-lsas/" + "ospf:area-scope-lsa/ospf:version/ospf:ospfv3/" + "ospf:ospfv3/ospf:body" { when "../../../../../../../../../" + "rt:type = 'ospf:ospfv3'" { description "This augmentation is only valid for OSPFv3."; } description "OSPFv3 Intra-Area-TE-LSA."; uses ospfv3-intra-area-te; } } ]]>

YANG Module for OSPF Extensions in Support of Inter-Autonomous System (AS) MPLS and GMPLS Traffic Engineering This document defines a YANG module for OSPF Extensions in Support of Inter-Autonomous System (AS) MPLS and GMPLS Traffic Engineering as defined in . file "ietf-ospf-inter-as-te@2025-02-27.yang" module ietf-ospf-inter-as-te { yang-version 1.1; namespace "urn:ietf:params:xml:ns:yang:ietf-ospf-inter-as-te"; prefix ospf-inter-as-te; import ietf-inet-types { prefix inet; reference "RFC 6991: Common YANG Data Types"; } import ietf-routing-types { prefix rt-types; reference "RFC 8294: Common YANG Data Types for the Routing Area"; } import ietf-routing { prefix rt; reference "RFC 8349: A YANG Data Model for Routing Management (NMDA Version)"; } import ietf-ospf { prefix ospf; reference "RFC 9129: YANG Data Model for the OSPF Protocol"; } import ietf-ospf-te { prefix ospf-te; reference "RFC 3630: Traffic Engineering (TE) Extensions to OSPF Version 2 RFC 5329: Traffic Engineering Extensions to OSPF Version 3"; } organization "IETF LSR - Link State Routing Working Group"; contact "WG Web: WG List: Author: Yingzhen Qu Author: Acee Lindem "; description "This YANG module defines the configuration and operational state for OSPF Extensions in Support of Inter-Autonomous System (AS) MPLS and GMPLS Traffic Engineering as defined in RFC 5392. Copyright (c) 2025 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."; reference "RFC XXXX"; revision 2025-02-27 { description "Initial version"; reference "RFC XXXX: OSPF YANG Model Augmentations for Additional Features - Version 1"; } identity ospfv3-intra-area-te-lsa { base ospf:ospfv3-lsa-type; description "OSPFv3 Intrea-area TE LSA."; } grouping inter-as-te-v2-lsa { description "Grouping for OSPF Inter-AS-TE-2 LSA."; container inter-as-te-v2 { description "The Inter-AS-TE-v2 LSA."; container link-tlv { description "Describes a single link. It is constructed from a set of sub-TLVs."; leaf link-type { type ospf:router-link-type; mandatory true; description "Link type."; } container local-if-ipv4-addrs { description "All local interface IPv4 addresses."; leaf-list local-if-ipv4-addr { type inet:ipv4-address; description "List of local interface IPv4 addresses."; } } container remote-if-ipv4-addrs { description "All remote interface IPv4 addresses."; leaf-list remote-if-ipv4-addr { type inet:ipv4-address; description "List of remote interface IPv4 addresses."; } } leaf te-metric { type uint32; description "TE metric."; } leaf max-bandwidth { type rt-types:bandwidth-ieee-float32; description "Maximum bandwidth."; } leaf max-reservable-bandwidth { type rt-types:bandwidth-ieee-float32; description "Maximum reservable bandwidth."; } container unreserved-bandwidths { description "All unreserved bandwidths."; list unreserved-bandwidth { leaf priority { type uint8 { range "0 .. 7"; } description "Priority from 0 to 7."; } leaf unreserved-bandwidth { type rt-types:bandwidth-ieee-float32; description "Unreserved bandwidth."; } description "List of unreserved bandwidths for different priorities."; } } leaf admin-group { type uint32; description "Administrative Group / Resource Class/Color."; } leaf remote-as-number { type uint32; mandatory true; description "Remote AS number."; } leaf ipv4-remote-asbr-id { type inet:ipv4-address; description "The neighboring ASBR IPv4 address."; } leaf ipv6-remote-asbr-id { type inet:ipv6-address; description "The neighboring ASBR IPv6 address."; } uses ospf:unknown-tlvs; } } } grouping inter-as-te-v3 { description "Grouping for OSPFv3 inter-as-te-v3 lsa."; container inter-as-te-v3 { container link-tlv { description "Describes a single link, and it is constructed of a set of Sub-TLVs."; leaf link-type { type ospf:router-link-type; mandatory true; description "Link type."; } container local-if-ipv6-addrs { description "All local interface IPv6 addresses."; leaf-list local-if-ipv6-addr { type inet:ipv6-address; description "List of local interface IPv6 addresses."; } } container remote-if-ipv6-addrs { description "All remote interface IPv6 addresses."; leaf-list remote-if-ipv6-addr { type inet:ipv6-address; description "List of remote interface IPv6 addresses."; } } leaf te-metric { type uint32; description "TE metric."; } leaf max-bandwidth { type rt-types:bandwidth-ieee-float32; description "Maximum bandwidth."; } leaf max-reservable-bandwidth { type rt-types:bandwidth-ieee-float32; description "Maximum reservable bandwidth."; } container unreserved-bandwidths { description "All unreserved bandwidths."; list unreserved-bandwidth { leaf priority { type uint8 { range "0 .. 7"; } description "Priority from 0 to 7."; } leaf unreserved-bandwidth { type rt-types:bandwidth-ieee-float32; description "Unreserved bandwidth."; } description "List of unreserved bandwidths for different priorities."; } } leaf admin-group { type uint32; description "Administrative group/Resource Class/Color."; } leaf remote-as-number { type uint32; mandatory true; description "Remote AS number."; } leaf ipv4-remote-asbr-id { type inet:ipv4-address; description "The neighboring ASBR IPv4 address."; } leaf ipv6-remote-asbr-id { type inet:ipv6-address; description "The neighboring ASBR IPv6 address."; } uses ospf:unknown-tlvs; } description "OSPFv3 Inter-AS-TE-v3 LSA."; reference "RFC 5392: TOSPF Extensions in Support of Inter-Autonomous System (AS) MPLS and GMPLS Traffic Engineering"; } } /* Configuration */ augment "/rt:routing/" + "rt:control-plane-protocols/rt:control-plane-protocol/" + "ospf:ospf/ospf:mpls/ospf-te:traffic-eng" { when "derived-from(/rt:routing/rt:control-plane-protocols/" + "rt:control-plane-protocol/rt:type, 'ospf:ospf')" { description "This augment OSPF routing protocol when used"; } description "This augments OSPF protocol traffic engineering configuration with Inter-AS-TE configuration."; container inter-as-te { presence "Enable Inter-AS-TE"; description "OSPFv3 MPLS TE configuration."; leaf flood-as-wide { type boolean; default "false"; description "Enables as-scoped traffic engineering advertisement. By default, the inter-as TE link advertisement is limited to within the single area."; } reference "RFC 5392: OSPF Extensions in Support of Inter-Autonomous System (AS) MPLS and GMPLS Traffic Engineering"; } } /* Database */ augment "/rt:routing/" + "rt:control-plane-protocols/rt:control-plane-protocol/" + "ospf:ospf/ospf:areas/" + "ospf:area/ospf:database/" + "ospf:area-scope-lsa-type/ospf:area-scope-lsas/" + "ospf:area-scope-lsa/ospf:version/ospf:ospfv2/" + "ospf:ospfv2/ospf:body/ospf:opaque" { when "derived-from(/rt:routing/rt:control-plane-protocols/" + "rt:control-plane-protocol/rt:type, 'ospf:ospfv2')" { description "This augments OSPFv2 routing protocol when used"; } description "OSPFv2 type 10 Opaque LSA."; uses inter-as-te-v2-lsa; } augment "/rt:routing/" + "rt:control-plane-protocols/rt:control-plane-protocol/" + "ospf:ospf/ospf:database/" + "ospf:as-scope-lsa-type/ospf:as-scope-lsas/" + "ospf:as-scope-lsa/ospf:version/ospf:ospfv2/" + "ospf:ospfv2/ospf:body/ospf:opaque" { when "derived-from(/rt:routing/rt:control-plane-protocols/" + "rt:control-plane-protocol/rt:type, 'ospf:ospfv2')" { description "This augments OSPFv2 routing protocol when used"; } description "OSPFv2 type 11 Opaque LSA."; uses inter-as-te-v2-lsa; } augment "/rt:routing/" + "rt:control-plane-protocols/rt:control-plane-protocol/" + "ospf:ospf/ospf:areas/" + "ospf:area/ospf:database/" + "ospf:area-scope-lsa-type/ospf:area-scope-lsas/" + "ospf:area-scope-lsa/ospf:version/ospf:ospfv3/" + "ospf:ospfv3/ospf:body" { when "derived-from(/rt:routing/rt:control-plane-protocols/" + "rt:control-plane-protocol/rt:type, 'ospf:ospfv3')" { description "This augmentation is only valid for OSPFv3."; } description "OSPFv3 Intra-Area-TE-LSA."; uses inter-as-te-v3; } augment "/rt:routing/" + "rt:control-plane-protocols/rt:control-plane-protocol/" + "ospf:ospf/ospf:database/" + "ospf:as-scope-lsa-type/ospf:as-scope-lsas/" + "ospf:as-scope-lsa/ospf:version/ospf:ospfv3/" + "ospf:ospfv3/ospf:body" { when "derived-from(/rt:routing/rt:control-plane-protocols/" + "rt:control-plane-protocol/rt:type, 'ospf:ospfv3')" { description "This augmentation is only valid for OSPFv3."; } description "OSPFv3 Intra-Area-TE-LSA."; uses inter-as-te-v3; } } ]]>

YANG Module for OSPF Two-Part Metric This document defines a YANG module for OSPF Two-Part Metric feature as defined in . It is an augmentation of the OSPF base model. WG List: Author: Yingzhen Qu Author: Acee Lindem "; description "This YANG module defines the configuration and operational state for OSPF Two-Part Metric feature as defined in RFC 8042. 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; see the RFC itself for full legal notices."; reference "RFC XXXX"; revision 2023-06-27 { description "Initial version"; reference "RFC XXXX: A YANG Data Model for OSPF Two-Part Metric."; } identity two-part-metric { base ospf:informational-capability; description "When set, the router is capable of supporting OSPF two-part metrics."; reference "RFC 8042: OSPF Two-Part Metric"; } /* RFC 8042 */ augment "/rt:routing/rt:control-plane-protocols/" + "rt:control-plane-protocol/ospf:ospf/" + "ospf:areas/ospf:area/ospf:interfaces/ospf:interface" { when "../../../../../rt:type = 'ospf:ospfv2' or " + "../../../../../rt:type = 'ospf:ospfv3'" { description "This augments the OSPF interface configuration when used."; } description "This augments the OSPF protocol interface configuration with two-part metric."; container two-part-metric { when "enum-value(../ospf:interface-type) = 2" { description "Two-part metric when link type is multi-access."; } leaf enable { type boolean; default false; description "Enable two-part metric."; } leaf int-input-cost { type ospf:ospf-link-metric; description "Link state metric from the two-part-metric network to this router."; } description "Interface two part metric configuration."; } } augment "/rt:routing/" + "rt:control-plane-protocols/rt:control-plane-protocol/" + "ospf:ospf/ospf:areas/" + "ospf:area/ospf:database/" + "ospf:area-scope-lsa-type/ospf:area-scope-lsas/" + "ospf:area-scope-lsa/ospf:version/ospf:ospfv2/" + "ospf:ospfv2/ospf:body/ospf:opaque/" + "ospf:extended-link-opaque/ospf:extended-link-tlv" { when "../../../../../../../../../../../../" + "rt:type = 'ospf:ospfv2'" { description "This augmentation is only valid for OSPFv2."; } description "Network-to-Router metric sub tlv for OSPFv2 extended link TLV in type 10 opaque LSA."; container network-to-router-metric-sub-tlvs { description "Network-to-Router metric sub TLV."; list net-to-rtr-sub-tlv { leaf mt-id { type uint8; description "Multi-Topology Identifier (MT-ID)."; } leaf mt-metric { type uint16; description "Network-to-router metric."; } description "Network-to-Router metric sub-TLV."; } } } augment "/rt:routing/" + "rt:control-plane-protocols/rt:control-plane-protocol/" + "ospf:ospf/ospf:areas/" + "ospf:area/ospf:database/" + "ospf:area-scope-lsa-type/ospf:area-scope-lsas/" + "ospf:area-scope-lsa/ospf:version/ospf:ospfv2/" + "ospf:ospfv2/ospf:body/ospf:opaque/ospf:te-opaque/" + "ospf:link-tlv" { when "../../../../../../../../../../../../" + "rt:type = 'ospf:ospfv2'" { description "This augmentation is only valid for OSPFv2."; } description "Traffic Engineering Network-to-Router Sub-TLV."; leaf network-to-router-te-metric { type uint32; description "Network to Router TE metric."; reference "RFC 8042 - OSPF Two-Part Metric"; } } augment "/rt:routing/" + "rt:control-plane-protocols/rt:control-plane-protocol/" + "ospf:ospf/ospf:areas/" + "ospf:area/ospf:database/" + "ospf:area-scope-lsa-type/ospf:area-scope-lsas/" + "ospf:area-scope-lsa/ospf:version/ospf:ospfv3/" + "ospf:ospfv3/ospf:body/ospfv3-te:ospfv3-intra-area-te/" + "ospfv3-te:link-tlv" { when "../../../../../../../../../../../" + "rt:type = 'ospf:ospfv3'" { description "This augmentation is only valid for OSPFv3."; } description "Traffic Engineering Network-to-Router Sub-TLV."; leaf network-to-router-te-metric { type uint32; description "Network to Router TE metric."; reference "RFC 8042 - OSPF Two-Part Metric"; } } } ]]>

YANG Module for OSPF Graceful Link Shutdown This document defines a YANG module for OSPF Graceful Link Shutdown feature as defined in . It is an augmentation of the OSPF base model. WG List: Author: Yingzhen Qu Author: Acee Lindem "; description "This YANG module defines the configuration and operational state for OSPF Graceful Link Shutdown feature as defined in RFC 8379. This YANG model conforms to the Network Management Datastore Architecture (NDMA) as described in RFC 8342. Copyright (c) 2024 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."; reference "RFC XXXX"; revision 2024-07-01 { description "Initial version"; reference "RFC XXXX: OSPF YANG Model Augmentations for Additional Features - Version 1."; } /* RFC 8379 */ augment "/rt:routing/rt:control-plane-protocols/" + "rt:control-plane-protocol/ospf:ospf/" + "ospf:areas/ospf:area/ospf:interfaces/ospf:interface" { when "../../../../../rt:type = 'ospf:ospfv2' or " + "../../../../../rt:type = 'ospf:ospfv3'" { description "This augments the OSPF interface configuration when used."; } description "This augments the OSPF protocol interface configuration with segment routing."; container graceful-link-shutdown { leaf enable { type boolean; default false; description "Enable OSPF graceful link shutdown."; } description "OSPF Graceful Link Shutdown."; } } /* Database */ augment "/rt:routing/" + "rt:control-plane-protocols/rt:control-plane-protocol/" + "ospf:ospf/ospf:areas/" + "ospf:area/ospf:database/" + "ospf:area-scope-lsa-type/ospf:area-scope-lsas/" + "ospf:area-scope-lsa/ospf:version/ospf:ospfv2/" + "ospf:ospfv2/ospf:body/ospf:opaque/" + "ospf:extended-link-opaque/ospf:extended-link-tlv" { when "../../../../../../../../../../../../" + "rt:type = 'ospf:ospfv2'" { description "This augmentation is only valid for OSPFv2."; } description "OSPF graceful link shutdown for OSPFv2 extended link TLV in type 10 opaque LSA."; container graceful-link-shutdown-sub-tlv { presence "Enable graceful link shutdown"; description "Graceful-Link-Shutdown sub-TLV identifies the link as being gracefully shutdown."; } container remote-address-sub-tlv { leaf remote-address { type inet:ipv4-address; description "Remote IPv4 address used to identify a particular link on the remote side."; } description "This sub-TLV specifies the IPv4 address of the remote endpoint on the link."; } container local-remote-int-id-sub-tlv { leaf local-int-id { type uint32; description "Local interface ID."; } leaf remote-int-id { type uint32; description "Remote interface ID."; } description "This sub-TLV specifies Local and Remote Interface IDs."; } } augment "/rt:routing/" + "rt:control-plane-protocols/rt:control-plane-protocol/" + "ospf:ospf/ospf:areas/ospf:area/ospf:database/" + "ospf:area-scope-lsa-type/ospf:area-scope-lsas/" + "ospf:area-scope-lsa/ospf:version/ospf:ospfv3/" + "ospf:ospfv3/ospf:body/ospfv3-e-lsa:e-router" + "/ospfv3-e-lsa:e-router-tlvs/ospfv3-e-lsa:link-tlv" { when "'ospf:../../../../../../../../../" + "rt:type' = 'ospf:ospfv3'" { description "This augmentation is only valid for OSPFv3 E-Router LSAs"; } container graceful-link-shutdown-sub-tlv { presence "Enable graceful link shutdown"; description "Graceful-Link-Shutdown sub-TLV identifies the link as being gracefully shutdown."; } description "Augment OSPFv3 Area scope router-link TLV."; } } ]]>

YANG Module for OSPF LLS Extenstion for Local Interface ID Advertisement This document defines a YANG module for OSPF Link-Local Signaling (LLS) Extensions for Local Interface ID Advertisement feature as defined in . It is an augmentation of the OSPF base model. WG List: Author: Yingzhen Qu Author: Acee Lindem "; description "This YANG module defines the configuration and operational state for OSPF Link-Local Signaling (LLS) Extensions for Local Interface ID Advertisement feature as defined in RFC 8510. Copyright (c) 2024 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."; revision 2024-07-01 { description "Initial version"; reference "RFC XXXX: OSPF YANG Model Augmentations for Additional Features - Version 1."; } augment "/rt:routing/rt:control-plane-protocols" + "/rt:control-plane-protocol/ospf:ospf" { when "../rt:type = 'ospf:ospfv2' or " + "../rt:type = 'ospf:ospfv3'" { description "This augments the OSPF routing protocol when used."; } description "This augments the OSPF protocol configuration to support LLS extesnions for interfacde ID as defined in RFC 8510."; container lls-int-id { leaf enable { type boolean; default false; description "Enable LLS to advertise local interface ID."; } description "OSPF LLS Extensions for interface ID."; } } } ]]>

YANG Module for OSPF Maximum SID Depth (MSD) This document defines a model for Signaling Maximum SID Depth (MSD) Using OSPF . It is an augmentation of the OSPF base model. WG List: Author: Yingzhen Qu Author: Acee Lindem Author: Stephane Litkowski Author: Jeff Tantsura "; description "The YANG module augments the base OSPF 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) 2025 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 OSPF MSD."; revision 2025-03-01 { description "Initial Version"; reference "RFC XXXX: OSPF YANG Model Augmentations for Additional Features - Version 1."; } grouping node-msd-tlv { description "Grouping for node MSD."; container node-msd-tlv { list node-msds { key "msd-type"; leaf msd-type { type identityref { base iana-msd-types:msd-base-mpls; } 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 8476: Signaling Maximum SID Depth (MSD) Using OSPF"; } } 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 iana-msd-types:msd-base-mpls; } 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/" + "ospf:ospf/ospf:areas/" + "ospf:area/ospf:database/" + "ospf:area-scope-lsa-type/ospf:area-scope-lsas/" + "ospf:area-scope-lsa/ospf:version/ospf:ospfv2/" + "ospf:ospfv2/ospf:body/ospf:opaque/" + "ospf:ri-opaque" { when "../../../../../../../../../../../" + "rt:type = 'ospf:ospfv2'" { description "This augmentation is only valid for OSPFv2."; } description "Node MSD TLV is an optional TLV of OSPFv2 RI Opaque LSA (RFC7770) and has a type of 12."; uses node-msd-tlv; } augment "/rt:routing/" + "rt:control-plane-protocols/rt:control-plane-protocol/" + "ospf:ospf/ospf:database/" + "ospf:as-scope-lsa-type/ospf:as-scope-lsas/" + "ospf:as-scope-lsa/ospf:version/ospf:ospfv2/" + "ospf:ospfv2/ospf:body/ospf:opaque/" + "ospf:ri-opaque" { when "../../../../../../../../../" + "rt:type = 'ospf:ospfv2'" { description "This augmentation is only valid for OSPFv2."; } description "Node MSD TLV is an optional TLV of OSPFv2 RI Opaque LSA (RFC7770) and has a type of 12."; uses node-msd-tlv; } augment "/rt:routing/" + "rt:control-plane-protocols/rt:control-plane-protocol/" + "ospf:ospf/ospf:areas/" + "ospf:area/ospf:database/" + "ospf:area-scope-lsa-type/ospf:area-scope-lsas/" + "ospf:area-scope-lsa/ospf:version/ospf:ospfv3/" + "ospf:ospfv3/ospf:body/ospf:router-information" { when "../../../../../../../../../../" + "rt:type = 'ospf:ospfv3'" { description "This augmentation is only valid for OSPFv3."; } description "Node MSD TLV is an optional TLV of OSPFv3 RI Opaque LSA (RFC7770) and has a type of 12."; uses node-msd-tlv; } augment "/rt:routing/" + "rt:control-plane-protocols/rt:control-plane-protocol/" + "ospf:ospf/ospf:database/" + "ospf:as-scope-lsa-type/ospf:as-scope-lsas/" + "ospf:as-scope-lsa/ospf:version/ospf:ospfv3/" + "ospf:ospfv3/ospf:body/ospf:router-information" { when "../../../../../../../../" + "rt:type = 'ospf:ospfv3'" { description "This augmentation is only valid for OSPFv3."; } description "Node MSD TLV is an optional TLV of OSPFv3 RI Opaque LSA (RFC7770) and has a type of 12."; uses node-msd-tlv; } /* link MSD sub-tlv */ augment "/rt:routing/" + "rt:control-plane-protocols/rt:control-plane-protocol/" + "ospf:ospf/ospf:areas/" + "ospf:area/ospf:database/" + "ospf:area-scope-lsa-type/ospf:area-scope-lsas/" + "ospf:area-scope-lsa/ospf:version/ospf:ospfv2/" + "ospf:ospfv2/ospf:body/ospf:opaque/" + "ospf:extended-link-opaque/ospf:extended-link-tlv" { when "../../../../../../../../../../../../" + "rt:type = 'ospf:ospfv2'" { description "This augmentation is only valid for OSPFv2."; } description "Link MSD sub-TLV is an optional sub-TLV of OSPFv2 extended link TLV as defined in RFC 7684 and has a type of 6."; uses link-msd-sub-tlv; } augment "/rt:routing/" + "rt:control-plane-protocols/rt:control-plane-protocol/" + "ospf:ospf/ospf:areas/ospf:area/ospf:database/" + "ospf:area-scope-lsa-type/ospf:area-scope-lsas/" + "ospf:area-scope-lsa/ospf:version/ospf:ospfv3/" + "ospf:ospfv3/ospf:body/ospfv3-e-lsa:e-router/" + "ospfv3-e-lsa:e-router-tlvs/ospfv3-e-lsa:link-tlv" { when "'ospf:../../../../../../../../" + "rt:type' = 'ospf:ospfv3'" { description "This augmentation is only valid for OSPFv3 E-Router LSAs"; } description "Augment OSPFv3 Area scope router-link TLV."; uses link-msd-sub-tlv; } } ]]>

YANG Module for Advertising Layer 2 Bundle Member Link Attributes in OSPF This document defines a YANG Moduel for Advertising Layer 2 Bundle Member Link Attributes in OSPF as defined in . file "ietf-ospf-l2-bundle@2025-02-27.yang" module ietf-ospf-l2-bundle { yang-version 1.1; namespace "urn:ietf:params:xml:ns:yang:ietf-ospf-l2-bundle"; prefix ospf-l2-bundle; import ietf-routing-types { prefix rt-types; reference "RFC 8294: Common YANG Data Types for the Routing Area"; } import ietf-routing { prefix rt; reference "RFC 8349: A YANG Data Model for Routing Management (NMDA Version)"; } import ietf-ospf { prefix ospf; reference "RFC 9129: YANG Data Model for the OSPF Protocol"; } import ietf-ospf-link-attr { prefix ospf-link-attr; } import ietf-ospfv3-extended-lsa { prefix ospfv3-e-lsa; reference "RFC 9587 - YANG Data Model for OSPFv3 Extended LSAs"; } import ietf-ospf-sr-mpls { prefix ospf-sr-mpls; } organization "IETF LSR - Link State Routing Working Group"; contact "WG Web: WG List: Author: Yingzhen Qu Author: Acee Lindem "; description "This YANG module defines the configuration and operational state for Advertising Layer 2 Bundle Member Link Attributes in OSPF as defined in RFC 9356. Copyright (c) 2025 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."; reference "RFC XXXX"; revision 2025-02-27 { description "Initial version"; reference "RFC XXXX: OSPF YANG Model Augmentations for Additional Features - Version 1"; } /* Groupings */ grouping ospfv2-member-link-attr-sub-tlvs { description "OSPFv2 L2 Bundle Member Attributes sub-TLV (RFC 9356)."; container adj-sid-sub-tlvs { list adj-sid-sub-tlv { description "List of adj-sid sub-tlvs."; container adj-sid-flags { leaf-list flags { type identityref { base ospf-sr-mpls:adj-sid-flag; } description "Adj-SID sub-TLV flags."; } description "Adj-sid sub-TLV flags."; } leaf mt-id { type uint8; description "Multi-topology ID. Topologies range from 0-127 and return of any other value would indicate an error."; reference "RFC 4915 - Multi-Topology (MT) Routing in OSPF"; } leaf weight { type uint8; description "Weight used for load-balancing."; } leaf sid { type uint32; description "Segment Identifier (SID) - A 20 bit label or an index into the SID/Label space."; } } description "Adjacency SID sub-tlvs."; } container lan-adj-sid-sub-tlv { description "LAN Adj-SID optional sub-TLVs."; list lan-adj-sid-sub-tlv { description "List of LAN Adj-SID sub-TLVs."; container lan-adj-sid-flags { leaf-list flags { type identityref { base ospf-sr-mpls:adj-sid-flag; } description "LAN Adj-SID sub-TLV flags."; } description "LAN Adj-SID sub-TLV flags."; } leaf mt-id { type uint8; description "Multi-topology ID. Topologies range from 0-127 and return of any other value would indicate an error."; reference "RFC 4915 - Multi-Topology (MT) Routing in OSPF"; } leaf weight { type uint8; description "Weight used for load-balancing."; } leaf neighbor-router-id { type rt-types:router-id; description "Neighbor router ID."; } leaf sid { type uint32; description "Segment Identifier (SID) - A 20 bit label or an index into the SID/Label space. If the V-Flag is set to 0 and L-Flag is set to 0: The SID/Index/Label field is a 4-octet index defining the offset in the SID/Label space advertised by this router. If V-Flag is set to 1 and L-Flag is set to 1: The SID/Index/Label field is a 3-octet local label where the 20 rightmost bits are used for encoding the label value."; } } } uses ospf-link-attr:app-specific-link-attr-sub-tlvs; } grouping ospfv3-member-link-attr-sub-tlvs { description "OSPFv3 L2 Bundle Member Attributes sub-TLV (RFC 9356)."; uses ospf-sr-mpls:ospfv3-adj-sid-sub-tlvs; uses ospf-sr-mpls:ospfv3-lan-adj-sid-sub-tlvs; uses ospf-link-attr:app-specific-link-attr-sub-tlvs; } /* Configuration */ augment "/rt:routing/rt:control-plane-protocols/" + "rt:control-plane-protocol/ospf:ospf/" + "ospf:areas/ospf:area/ospf:interfaces/ospf:interface" { when "derived-from(/rt:routing/rt:control-plane-protocols/" + "rt:control-plane-protocol/rt:type, 'ospf:ospf')" { description "This augments the OSPF routing protocol when used."; } description "This augments the OSPF interface configuration with L2 Bundle Member Attributes."; container l2-mbr-attrs { description "L2 member attributes configuration."; list l2-mbr-attr { key l2-bdl-mbr-dscpr; leaf l2-bdl-mbr-dscpr { type uint32; description "L2 bundle member descriptor: a 4-octet link-local identifier for the member link."; } leaf adj-sid { type uint32; description "Value of the Adj-SID."; } leaf lan-adj-sid { type uint32; description "Value of the LAN-Adj-SID."; } /* More configuration can be added here */ description "List of L2 bundle members."; } } } /* Database */ augment "/rt:routing/" + "rt:control-plane-protocols/rt:control-plane-protocol/" + "ospf:ospf/ospf:areas/" + "ospf:area/ospf:database/" + "ospf:area-scope-lsa-type/ospf:area-scope-lsas/" + "ospf:area-scope-lsa/ospf:version/ospf:ospfv2/" + "ospf:ospfv2/ospf:body/ospf:opaque/" + "ospf:extended-link-opaque/ospf:extended-link-tlv" { when "derived-from(/rt:routing/rt:control-plane-protocols/" + "rt:control-plane-protocol/rt:type, 'ospf:ospfv2')" { description "This augmentation is only valid for OSPFv2."; } description "OSPFv2 L2 Bundle Member Attributes sub-TLV is a sub-TLV of OSPFv2 Extended Link TLV (RFC7684)."; container l2-bdl-mbr-attr { list l2-bdl-mbrs { description "List of L2 bundle members."; leaf l2-bdl-mbr-dscpr { type uint32; description "L2 bundle member descriptor: a 4-octet link-local identifier for the member link."; } uses ospfv2-member-link-attr-sub-tlvs; } description "OSPFv2 L2 Bundle Member Attributes sub-TLV."; } } augment "/rt:routing/" + "rt:control-plane-protocols/rt:control-plane-protocol/" + "ospf:ospf/ospf:areas/ospf:area/ospf:database/" + "ospf:area-scope-lsa-type/ospf:area-scope-lsas/" + "ospf:area-scope-lsa/ospf:version/ospf:ospfv3/" + "ospf:ospfv3/ospf:body/ospfv3-e-lsa:e-router/" + "ospfv3-e-lsa:e-router-tlvs/ospfv3-e-lsa:link-tlv" { when "derived-from(/rt:routing/rt:control-plane-protocols/" + "rt:control-plane-protocol/rt:type, 'ospf:ospfv3')" { description "This augmentation is only valid for OSPFv3 E-Router LSAs"; } description "Augment OSPFv3 Area scope router-link TLV."; container l2-bdl-mbr-attr { list l2-bdl-mbrs { description "List of L2 bundle members."; leaf l2-bdl-mbr-dscpr { type uint32; description "L2 bundle member descriptor: a 4-octet link-local identifier for the member link."; } uses ospfv3-member-link-attr-sub-tlvs; } description "OSPFv3 L2 Bundle Member Attributes sub-TLV."; } } } ]]>

YANG Module for OSPF Flexible Algorithms: Bandwidth, Delay, Metrics and Constraints This document defines a YANG module for OSPF Flexible Algorithms: Bandwidth, Delay, Metrics and Constraints . It is an augmentation of the OSPF base model and the Flexible Algorithm YANG module . file "ietf-ospf-flex-algo-bw-con@2026-01-08.yang" module ietf-ospf-flex-algo-bw-con { yang-version 1.1; namespace "urn:ietf:params:xml:ns:yang:ietf-ospf-flex-algo-bw-con"; prefix ospf-flex-algo-bw-con; import ietf-routing { prefix rt; reference "RFC 8349: A YANG Data Model for Routing Management (NMDA Version)"; } import ietf-routing-types { prefix rt-types; reference "RFC 8294: Common YANG Data Types for the Routing Area"; } import ietf-te-types { prefix te-types; reference "RFC8776: Common YANG Data Types for Traffic Engineering."; } import ietf-ospf { prefix ospf; reference "RFC 9129: YANG Data Model for the OSPF Protocol"; } import ietf-ospfv3-extended-lsa { prefix ospfv3-e-lsa; reference "RFC 9587: YANG Data Model for OSPFv3 Extended Link State Advertisements (LSAs)"; } import ietf-ospf-te { prefix ospf-te; } import ietf-ospf-flex-algo { prefix ospf-flex-algo; reference "RFC XXXX"; } import ietf-ospf-link-attr { prefix ospf-link-attr; } import ietf-ospf-inter-as-te { prefix ospf-inter-as-te; } import ietf-ospf-l2-bundle { prefix ospf-l2-bundle; } import iana-igp-metric-types { prefix iana-metric-type; } organization "IETF LSR - Link State Routing Working Group"; contact "WG Web: WG List: Author: Yingzhen Qu Author: Acee Lindem "; description "The YANG module defines the configuration and operational state for OSPF protocol as defined in RFC 9843, IGP Flexible Algorithms: Bandwidth, Delay, Metrics and Constraints This YANG model conforms to the Network Management Datastore Architecture (NMDA) as described in RFC 8342. Copyright (c) 2025 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 OSPF Flexible Algorithm."; revision 2025-07-06 { description "Initial Version"; reference "RFC XXXX: OSPF YANG Model Augmentations for Additional Features - Version 1."; } /* Identities */ identity bandwidth-constraint-type { description "Base identity for bandwidth constraint types."; } identity min-bw { base bandwidth-constraint-type; description "Minimum bandwidth constraint."; } identity max-bw { base bandwidth-constraint-type; description "Maximum bandwidth constraint."; } identity fadrb-flags { description "Base identity for OSPF Flexible Algorithm Definition Reference Bandwidth sub-tlv flags."; } identity g-bit { base fadrb-flags; description "G bit, when set, interface group mode MUST be used to derive total link bandwidth."; } identity fadbt-flags { description "Base identity for OSPF Flexible Algorithm Definition Reference Bandwidth sub-tlv flags."; } identity gp-bit { base fadbt-flags; description "G bit, when set, interface group mode MUST be used to derive total link bandwidth."; } /* Groupings */ grouping bandwidth-constraint { description "Grouping for bandwidth constraints in Flex-Algo."; container bandwidth-constraints { list constraint { key "constraint-type"; description "List of bandwidth constraints for the Flex-Algo."; leaf constraint-type { type identityref { base bandwidth-constraint-type; } description "Type of bandwidth constraint (e.g., min-bw, max-bw)."; } leaf bandwidth-value { type te-types:te-bandwidth; description "Bandwidth value for the constraint."; } leaf threshold { type uint8 { range "1..100"; } units "percent"; description "Threshold percentage for triggering re-optimization."; } } description "Bandwidth constraints configuration for flex-algo."; } } grouping generic-metric-sub-tlv { container generic-metric-sub-tlvs { list generic-metric-sub-tlv { leaf metric-type { type identityref { base iana-metric-type:metric-type; } description "Type of metric to be used during the calculation."; } leaf value { type uint32; description "A 32-bit unsigned integer representing the metric value."; } description "The list of generic metric sub-tlvs."; } description "The generic metric sub-tlv."; } description "The grouping for generic metric sub-tlv."; } grouping faemb-sub-tlv { container faemb-sub-tlv { leaf min-bandwidth { type rt-types:bandwidth-ieee-float32; description "A 32-bit field specifying the link bandwidth in IEEE floating point format (IEEE754). The units are bytes-per-second."; } description "Flex-algo Exclude Minimum Bandwidth sub-tlv (FAEMB)."; } description "Grouping for FAEMB sub-tlv."; } grouping faemd-sub-tlv { container faemd-sub-tlv { leaf max-link-delay { type rt-types:uint24; description "A 24-bit field specifying the maximum link delay in microseconds."; } description "The Flex-algo Exclude Maximum Delay sub-tlv (FAEMD)."; } description "Grouping for FAEMD sub-tlv."; } grouping fadrb-sub-tlv { container fadrb-sub-tlv { leaf-list fadrb-flags { type identityref { base fadrb-flags; } description "Flex-algo definition reference bandwidth sub-tlv flags list."; } leaf reference-bandwidth { type rt-types:bandwidth-ieee-float32; description "A 32-bit field specifying the link bandwidth in IEEE floating point format (IEEE754). The units are bytes-per-second."; } leaf granularity-bandwidth { type rt-types:bandwidth-ieee-float32; description "A 32-bit field specifying the link bandwidth in IEEE floating point format (IEEE754). The units are bytes-per-second."; } description "The Flex-algo Reference Bandwidth sub-tlv (FAEMD)."; } description "Grouping for FADRB sub-tlv."; } grouping fadbt-sub-tlv { container fadbt-sub-tlv { leaf-list fadbt-flags { type identityref { base fadbt-flags; } description "Flex-algo definition bandwidth thresholds sub-tlv flags list."; } list bandwidth-threshold { leaf bandwidth-threshold { type rt-types:bandwidth-ieee-float32; description "Maximum link bandwidth. A 32-bit field specifying the link bandwidth in IEEE floating point format (IEEE754). The units are bytes-per-second."; } leaf threshold-metric { type uint32; description "Metric value range 1 - 4,294,967,296 (0xFFFFFFFF)."; } description "List of bandwidth thresholds and metrics."; } description "The Flex-algo Bandwidth Thresholds sub-tlv (FADBT)."; } description "Grouping for FADBT sub-tlv."; } /* Configurations */ augment "/rt:routing/rt:control-plane-protocols/" + "rt:control-plane-protocol/ospf:ospf/" + "ospf:areas/ospf:area/ospf:interfaces/ospf:interface" { when "derived-from(/rt:routing/rt:control-plane-protocols/" + "rt:control-plane-protocol/rt:type, 'ospf:ospf')" { description "This augments the OSPF interface configuration when used."; } description "This augments the OSPF protocol interface configuration with generic metric configuration."; container generic-metrics { list generic-metric { key "metric-type"; leaf metric-type { type identityref { base iana-metric-type:metric-type; } description "Type of metric to be used during the calculation."; } leaf metric-value { type uint32; description "Metric value, range is from 0 to 0xFFFFFFFF."; } description "Interface generic metric configuration per metric-type."; } description "Interface generic metric configuration."; } } augment "/rt:routing/rt:control-plane-protocols/" + "rt:control-plane-protocol/ospf:ospf/" + "ospf-flex-algo:ospf-flex-algo/ospf-flex-algo:flex-algo" { when "derived-from(/rt:routing/rt:control-plane-protocols/" + "rt:control-plane-protocol/rt:type, 'ospf:ospf')" { description "This augments the OSPF routing protocol when used."; } description "This augments OSPF protocol Flexible Algorithm with bandwidth constraints."; uses bandwidth-constraint; choice metric-derivation-method { description "Choice of automatic metric derivation methods."; container reference-bandwidth { description "Metric is inversely proportional to the link bandwidth."; leaf reference-bandwidth { type rt-types:bandwidth-ieee-float32; description "A 32-bit field specifying the link bandwidth in IEEE floating point format (IEEE754). The units are bytes-per-second."; } leaf granularity-bandwidth { type rt-types:bandwidth-ieee-float32; description "A 32-bit field specifying the link bandwidth in IEEE floating point format (IEEE754). The units are bytes-per-second."; } } container bandwidth-thresholds { description "Pre-define non-proportional metric values from the varying ranges of link bandwidth."; list bandwidth-threshold { key bandwidth-threshold; leaf bandwidth-threshold { type rt-types:bandwidth-ieee-float32; description "Maximum link bandwidth. A 32-bit field specifying the link bandwidth in IEEE floating point format (IEEE754). The units are bytes-per-second."; } leaf threshold-metric { type uint32; description "Metric value range 1 - 4,294,967,296 (0xFFFFFFFF)."; } description "List of bandwidth thresholds and metrics."; } } } leaf exclude-min-bw { type rt-types:bandwidth-ieee-float32; description "A 32-bit field specifying the link bandwidth in IEEE floating point format (IEEE754). The units are bytes-per-second."; } leaf exclude-max-delay { type rt-types:uint24; description "A 24-bit field specifying the maximum link delay in microseconds."; } } /* Database */ augment "/rt:routing/" + "rt:control-plane-protocols/rt:control-plane-protocol/" + "ospf:ospf/ospf:areas/ospf:area/" + "ospf:interfaces/ospf:interface/ospf:database/" + "ospf:link-scope-lsa-type/ospf:link-scope-lsas/" + "ospf:link-scope-lsa/ospf:version/ospf:ospfv2/" + "ospf:ospfv2/ospf:body/ospf:opaque/ospf:te-opaque/" + "ospf:link-tlv" { when "derived-from(/rt:routing/rt:control-plane-protocols/" + "rt:control-plane-protocol/rt:type, 'ospf:ospfv2')" { description "This augmentation is only valid for OSPFv2."; } description "TE link TLV of OSPF TE LSA."; uses generic-metric-sub-tlv; } augment "/rt:routing/" + "rt:control-plane-protocols/rt:control-plane-protocol/" + "ospf:ospf/ospf:areas/ospf:area/ospf:database/" + "ospf:area-scope-lsa-type/ospf:area-scope-lsas/" + "ospf:area-scope-lsa/ospf:version/ospf:ospfv2/" + "ospf:ospfv2/ospf:body/ospf:opaque/" + "ospf-inter-as-te:inter-as-te-v2/" + "ospf-inter-as-te:link-tlv" { when "derived-from(/rt:routing/rt:control-plane-protocols/" + "rt:control-plane-protocol/rt:type, 'ospf:ospfv2')" { description "This augmentation is only valid for OSPFv2."; } description "Area scope TE link TLV of OSPFv2 Inter-AS-TE-v2 LSA."; uses generic-metric-sub-tlv; } augment "/rt:routing/" + "rt:control-plane-protocols/rt:control-plane-protocol/" + "ospf:ospf/ospf:database/" + "ospf:as-scope-lsa-type/ospf:as-scope-lsas/" + "ospf:as-scope-lsa/ospf:version/ospf:ospfv2/" + "ospf:ospfv2/ospf:body/ospf:opaque/" + "ospf-inter-as-te:inter-as-te-v2/" + "ospf-inter-as-te:link-tlv" { when "derived-from(/rt:routing/rt:control-plane-protocols/" + "rt:control-plane-protocol/rt:type, 'ospf:ospfv2')" { description "This augment OSPFv2 routing protocol when used"; } description "AS scope TE link TLV of OSPFv2 Inter-AS-TE-v2 LSA."; uses generic-metric-sub-tlv; } augment "/rt:routing/" + "rt:control-plane-protocols/rt:control-plane-protocol/" + "ospf:ospf/ospf:areas/" + "ospf:area/ospf:database/" + "ospf:area-scope-lsa-type/ospf:area-scope-lsas/" + "ospf:area-scope-lsa/ospf:version/ospf:ospfv3/" + "ospf:ospfv3/ospf:body/ospf-te:ospfv3-intra-area-te/" + "ospf-te:link-tlv" { when "derived-from(/rt:routing/rt:control-plane-protocols/" + "rt:control-plane-protocol/rt:type, 'ospf:ospfv3')" { description "This augmentation is only valid for OSPFv3."; } description "TE Link TLV of OSPFv3 Intra-Area-TE-LSA."; uses generic-metric-sub-tlv; } augment "/rt:routing/" + "rt:control-plane-protocols/rt:control-plane-protocol/" + "ospf:ospf/ospf:areas/" + "ospf:area/ospf:database/" + "ospf:area-scope-lsa-type/ospf:area-scope-lsas/" + "ospf:area-scope-lsa/ospf:version/ospf:ospfv3/" + "ospf:ospfv3/ospf:body/ospf-inter-as-te:inter-as-te-v3/" + "ospf-inter-as-te:link-tlv" { when "derived-from(/rt:routing/rt:control-plane-protocols/" + "rt:control-plane-protocol/rt:type, 'ospf:ospfv3')" { description "This augmentation is only valid for OSPFv3."; } description "Area scope TE Link TLV of OSPFv3 Inter-AS-TE-v3 LSA."; uses generic-metric-sub-tlv; } augment "/rt:routing/" + "rt:control-plane-protocols/rt:control-plane-protocol/" + "ospf:ospf/ospf:database/" + "ospf:as-scope-lsa-type/ospf:as-scope-lsas/" + "ospf:as-scope-lsa/ospf:version/ospf:ospfv3/" + "ospf:ospfv3/ospf:body/ospf-inter-as-te:inter-as-te-v3/" + "ospf-inter-as-te:link-tlv" { when "derived-from(/rt:routing/rt:control-plane-protocols/" + "rt:control-plane-protocol/rt:type, 'ospf:ospfv3')" { description "This augmentation is only valid for OSPFv3."; } description "AS scope TE Link TLV of OSPFv3 Inter-AS-TE-v3 LSA."; uses generic-metric-sub-tlv; } augment "/rt:routing/" + "rt:control-plane-protocols/rt:control-plane-protocol/" + "ospf:ospf/ospf:areas/" + "ospf:area/ospf:database/" + "ospf:area-scope-lsa-type/ospf:area-scope-lsas/" + "ospf:area-scope-lsa/ospf:version/ospf:ospfv2/" + "ospf:ospfv2/ospf:body/ospf:opaque/" + "ospf:extended-link-opaque/ospf:extended-link-tlv/" + "ospf-link-attr:app-specific-link-attr-sub-tlvs" { when "derived-from(/rt:routing/rt:control-plane-protocols/" + "rt:control-plane-protocol/rt:type, 'ospf:ospfv2')" { description "This augmentation is only valid for OSPFv2."; } description "OSPF Application-Specific Link Attributes (ASLA) sub-TLV is a sub-TLV of OSPFv2 Extended Link TLV (RFC7684)."; uses generic-metric-sub-tlv; } augment "/rt:routing/" + "rt:control-plane-protocols/rt:control-plane-protocol/" + "ospf:ospf/ospf:areas/ospf:area/ospf:database/" + "ospf:area-scope-lsa-type/ospf:area-scope-lsas/" + "ospf:area-scope-lsa/ospf:version/ospf:ospfv3/" + "ospf:ospfv3/ospf:body/ospfv3-e-lsa:e-router/" + "ospfv3-e-lsa:e-router-tlvs/ospfv3-e-lsa:link-tlv/" + "ospf-link-attr:app-specific-link-attr-sub-tlvs" { when "derived-from(/rt:routing/rt:control-plane-protocols/" + "rt:control-plane-protocol/rt:type, 'ospf:ospfv3')" { description "This augmentation is only valid for OSPFv3 E-Router LSAs"; } description "Application-Specific Link Attributes (ASLA) sub-TLV (RFC9492) of the OSPFv3 Router-Link TLV (RFC8362)."; uses generic-metric-sub-tlv; } augment "/rt:routing/" + "rt:control-plane-protocols/rt:control-plane-protocol/" + "ospf:ospf/ospf:areas/" + "ospf:area/ospf:database/" + "ospf:area-scope-lsa-type/ospf:area-scope-lsas/" + "ospf:area-scope-lsa/ospf:version/ospf:ospfv2/" + "ospf:ospfv2/ospf:body/ospf:opaque/" + "ospf:extended-link-opaque/ospf:extended-link-tlv/" + "ospf-l2-bundle:l2-bdl-mbr-attr/" + "ospf-l2-bundle:l2-bdl-mbrs" { when "derived-from(/rt:routing/rt:control-plane-protocols/" + "rt:control-plane-protocol/rt:type, 'ospf:ospfv2')" { description "This augmentation is only valid for OSPFv2."; } description "OSPFv2 L2 Bundle Member Attributes sub-TLV is a sub-TLV of OSPFv2 Extended Link TLV (RFC7684)."; uses generic-metric-sub-tlv; } augment "/rt:routing/" + "rt:control-plane-protocols/rt:control-plane-protocol/" + "ospf:ospf/ospf:areas/ospf:area/ospf:database/" + "ospf:area-scope-lsa-type/ospf:area-scope-lsas/" + "ospf:area-scope-lsa/ospf:version/ospf:ospfv3/" + "ospf:ospfv3/ospf:body/ospfv3-e-lsa:e-router/" + "ospfv3-e-lsa:e-router-tlvs/ospfv3-e-lsa:link-tlv/" + "ospf-l2-bundle:l2-bdl-mbr-attr/" + "ospf-l2-bundle:l2-bdl-mbrs" { when "derived-from(/rt:routing/rt:control-plane-protocols/" + "rt:control-plane-protocol/rt:type, 'ospf:ospfv3')" { description "This augmentation is only valid for OSPFv3 E-Router LSAs"; } description "OSPFv3 L2 Bundle Member Attributes sub-TLV in OSPFv3 Area scope router-link TLV."; uses generic-metric-sub-tlv; } augment "/rt:routing/" + "rt:control-plane-protocols/rt:control-plane-protocol/" + "ospf:ospf/ospf:areas/ospf:area/" + "ospf:interfaces/ospf:interface/ospf:database/" + "ospf:link-scope-lsa-type/ospf:link-scope-lsas/" + "ospf:link-scope-lsa/ospf:version/ospf:ospfv2/" + "ospf:ospfv2/ospf:body/ospf:opaque/ospf:ri-opaque/" + "ospf-flex-algo:fad-tlvs/ospf-flex-algo:fad-tlv" { when "derived-from(/rt:routing/rt:control-plane-protocols/" + "rt:control-plane-protocol/rt:type, 'ospf:ospfv2')" { description "This augmentation is only valid for OSPFv2."; } description "Flex-algo definition TLVs for OSPFv2 type 9 opaque RI LSA."; uses faemb-sub-tlv; uses faemd-sub-tlv; uses fadrb-sub-tlv; uses fadbt-sub-tlv; } augment "/rt:routing/" + "rt:control-plane-protocols/rt:control-plane-protocol/" + "ospf:ospf/ospf:areas/" + "ospf:area/ospf:database/" + "ospf:area-scope-lsa-type/ospf:area-scope-lsas/" + "ospf:area-scope-lsa/ospf:version/ospf:ospfv2/" + "ospf:ospfv2/ospf:body/ospf:opaque/ospf:ri-opaque/" + "ospf-flex-algo:fad-tlvs/ospf-flex-algo:fad-tlv" { when "derived-from(/rt:routing/rt:control-plane-protocols/" + "rt:control-plane-protocol/rt:type, 'ospf:ospfv2')" { description "This augmentation is only valid for OSPFv2."; } description "Flex-algo definition TLVs for OSPFv2 type 10 opaque RI LSA."; uses faemb-sub-tlv; uses faemd-sub-tlv; uses fadrb-sub-tlv; uses fadbt-sub-tlv; } augment "/rt:routing/" + "rt:control-plane-protocols/rt:control-plane-protocol/" + "ospf:ospf/ospf:database/" + "ospf:as-scope-lsa-type/ospf:as-scope-lsas/" + "ospf:as-scope-lsa/ospf:version/ospf:ospfv2/" + "ospf:ospfv2/ospf:body/ospf:opaque/ospf:ri-opaque/" + "ospf-flex-algo:fad-tlvs/ospf-flex-algo:fad-tlv" { when "derived-from(/rt:routing/rt:control-plane-protocols/" + "rt:control-plane-protocol/rt:type, 'ospf:ospfv2')" { description "This augmentation is only valid for OSPFv2."; } description "Flex-algo definition TLVs for OSPFv2 type 11 opaque RI LSA."; uses faemb-sub-tlv; uses faemd-sub-tlv; uses fadrb-sub-tlv; uses fadbt-sub-tlv; } augment "/rt:routing/" + "rt:control-plane-protocols/rt:control-plane-protocol/" + "ospf:ospf/ospf:areas/ospf:area/" + "ospf:interfaces/ospf:interface/ospf:database/" + "ospf:link-scope-lsa-type/ospf:link-scope-lsas/" + "ospf:link-scope-lsa/ospf:version/ospf:ospfv3/" + "ospf:ospfv3/ospf:body/ospf:router-information/" + "ospf-flex-algo:fad-tlvs/ospf-flex-algo:fad-tlv" { when "derived-from(/rt:routing/rt:control-plane-protocols/" + "rt:control-plane-protocol/rt:type, 'ospf:ospfv3')" { description "This augmentation is only valid for OSPFv3."; } description "Flex-algo definition TLVs for OSPFv3 Router Information (RI) LSA."; uses faemb-sub-tlv; uses faemd-sub-tlv; uses fadrb-sub-tlv; uses fadbt-sub-tlv; } augment "/rt:routing/" + "rt:control-plane-protocols/rt:control-plane-protocol/" + "ospf:ospf/ospf:areas/" + "ospf:area/ospf:database/" + "ospf:area-scope-lsa-type/ospf:area-scope-lsas/" + "ospf:area-scope-lsa/ospf:version/ospf:ospfv3/" + "ospf:ospfv3/ospf:body/ospf:router-information/" + "ospf-flex-algo:fad-tlvs/ospf-flex-algo:fad-tlv" { when "derived-from(/rt:routing/rt:control-plane-protocols/" + "rt:control-plane-protocol/rt:type, 'ospf:ospfv3')" { description "This augmentation is only valid for OSPFv3."; } description "Flex-algo definition TLVs for OSPFv3 Router Information (RI) LSA."; uses faemb-sub-tlv; uses faemd-sub-tlv; uses fadrb-sub-tlv; uses fadbt-sub-tlv; } augment "/rt:routing/" + "rt:control-plane-protocols/rt:control-plane-protocol/" + "ospf:ospf/ospf:database/" + "ospf:as-scope-lsa-type/ospf:as-scope-lsas/" + "ospf:as-scope-lsa/ospf:version/ospf:ospfv3/" + "ospf:ospfv3/ospf:body/ospf:router-information/" + "ospf-flex-algo:fad-tlvs/ospf-flex-algo:fad-tlv" { when "derived-from(/rt:routing/rt:control-plane-protocols/" + "rt:control-plane-protocol/rt:type, 'ospf:ospfv3')" { description "This augmentation is only valid for OSPFv3."; } description "Flex-algo definition TLVs for OSPFv3 Router Information LSA."; uses faemb-sub-tlv; uses faemd-sub-tlv; uses fadrb-sub-tlv; uses fadbt-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. 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.

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.