]> Futurewei Technologies

USA yingzhen.ietf@gmail.com

Huawei Technologies

Huawei Bld., No.156 Beiqing Rd. Beijing 100095 China huzhibo@huawei.com

Huawei Technologies

Huawei Bld., No.156 Beiqing Rd. Beijing 100095 China gengxuesong@huawei.com

Cisco Systems, Inc.

2000 Innovation Drive Kanata, ON K2K-3E8 CA skraza@cisco.com

LabN Consulting, L.L.C.

301 Midenhall Way Cary, NC 27513 USA acee.ietf@gmail.com

This document defines a YANG data model that can be used to configure and manage OSPFv3 Segment Routing over the IPv6 Data Plane. 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 RFC 2119.

Introduction 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 a YANG data model that can be used to configure and manage OSPFv3 SRv6 and it is an augmentation to the OSPF YANG data model .

Terminology and Notation 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. The following terms are defined in :

• client
• server
• configuration
• system state
• operational state
• intended configuration

The following terms are defined in :

• action
• augment
• container
• container with presence
• data model
• data node
• feature
• leaf
• list
• mandatory node
• module
• schema tree
• RPC (Remote Procedure Call) operation

Tree Diagrams Tree diagrams used in this document follow the notation defined in .

Prefixes in Data Node Names In this document, names of data nodes, actions, and other data model objects are often used without a prefix, as long as it is clear from the context in which YANG module each name is defined. Otherwise, names are prefixed using the standard prefix associated with the corresponding YANG module, as shown in Table 1.

Table 1: Prefixes and Corresponding YANG Modules

OSPFv3 SRv6 Configuration This document defines a YANG data model for OSPFv3 SRv6 feature. It is an augmentation of the OSPF base model. The OSPFv3 SRv6 YANG module requires support of OSPF base model which defines basic OSPF configuration and state and support of OSPFv3 Extended LSAs model .

SRv6 Activation Activation of OSPFv3 SRv6 is done by setting the "enable" leaf to true. This triggers advertisement of SRv6 extensions based on the configuration parameters that have been setup using the base SRv6 module .

Locator Setting The SRv6 base module [I-D.ietf-spring-srv6-yang] defines locators. When OSPFv6 SRv6 is enabled, the specified locators are used unless it is enabled to use the default locator. The default locator can be set by using two leafs, i.e.,"default-locator" leaf, "locator-name" leaf.

IP Fast Reroute The OSPFv3 SRv6 model augments the fast-reroute container in the OSPF base module with a leaf that enables TI-LFA (Topology Independent LFA) .

Micro-loop Avoidance OSPFv3 SRv6 model augments OSPF module with the micro-loop-avoidance container. This container includes the "srv6-enable" leaf, which activates SRv6 for microloop avoidance.

YANG Module and Tree

OSPFv3 SRv6 Model Tree The figure below describes the overall structure of the ospfv3-srv6 YANG module: /rt:routing/srv6:srv6 | /srv6:locators/srv6:locator/srv6:name | +--rw persistent-end-x-sid? boolean +--rw micro-loop-avoidance +--rw srv6-enable? boolean +--rw srv6-rib-update-delay? uint16 augment /rt:routing/rt:control-plane-protocols /rt:control-plane-protocol/ospf:ospf /ospf:fast-reroute: +--rw srv6-ti-lfa {srv6-ti-lfa}? +--rw enable? boolean 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: +--ro srv6-localtor-lsas +--ro srv6-locator-lsa* [] +--ro link-state-id? uint32 +--ro adv-router? rt-types:router-id +--ro sr6-locator-tlv* [] +--ro srv6-locactor-tlvs | +--ro route-type? identityref | +--ro algorithm? uint8 | +--ro locator-length? uint8 | +--ro flags* identityref | +--ro metric? uint32 | +--ro locator* inet:ipv6-address-no-zone | +--ro srv6-end-sid | +--ro flags* identityref | +--ro endpoint-func | | +--ro flags* identityref | | +--ro endpoint-func? identityref | | +--ro undefined-endpoint-func? uint16 | +--ro sid? srv6-sid-value | +--ro srv6-sid-structure | +--ro lb-length? uint8 | +--ro ln-length? uint8 | +--ro fun-length? uint8 | +--ro arg-length? uint8 +--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/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: +--ro srv6-localtor-lsas +--ro srv6-locator-lsa* [] +--ro link-state-id? uint32 +--ro adv-router? rt-types:router-id +--ro sr6-locator-tlv* [] +--ro srv6-locactor-tlvs | +--ro route-type? identityref | +--ro algorithm? uint8 | +--ro locator-length? uint8 | +--ro flags* identityref | +--ro metric? uint32 | +--ro locator* inet:ipv6-address-no-zone | +--ro srv6-end-sid | +--ro flags* identityref | +--ro endpoint-func | | +--ro flags* identityref | | +--ro endpoint-func? identityref | | +--ro undefined-endpoint-func? uint16 | +--ro sid? srv6-sid-value | +--ro srv6-sid-structure | +--ro lb-length? uint8 | +--ro ln-length? uint8 | +--ro fun-length? uint8 | +--ro arg-length? uint8 +--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/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: +--ro srv6-localtor-lsas +--ro srv6-locator-lsa* [] +--ro link-state-id? uint32 +--ro adv-router? rt-types:router-id +--ro sr6-locator-tlv* [] +--ro srv6-locactor-tlvs | +--ro route-type? identityref | +--ro algorithm? uint8 | +--ro locator-length? uint8 | +--ro flags* identityref | +--ro metric? uint32 | +--ro locator* inet:ipv6-address-no-zone | +--ro srv6-end-sid | +--ro flags* identityref | +--ro endpoint-func | | +--ro flags* identityref | | +--ro endpoint-func? identityref | | +--ro undefined-endpoint-func? uint16 | +--ro sid? srv6-sid-value | +--ro srv6-sid-structure | +--ro lb-length? uint8 | +--ro ln-length? uint8 | +--ro fun-length? uint8 | +--ro arg-length? uint8 +--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/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: +--ro srv6-capability | +--ro flags* identityref +--ro msd +--ro max-sl? uint8 +--ro max-end-pop? uint8 +--ro max-h_encap? uint8 +--ro max-end_d? uint8 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: +--ro srv6-endx-sid | +--ro endpoint-func | | +--ro flags* identityref | | +--ro endpoint-func? identityref | | +--ro undefined-endpoint-func? uint16 | +--ro func-flags* identityref | +--ro algorithm? uint8 | +--ro weight? uint8 | +--ro sid* srv6-sid-value | +--ro neighbor-router-id? yang:dotted-quad | +--ro srv6-sid-structure | +--ro lb-length? uint8 | +--ro ln-length? uint8 | +--ro fun-length? uint8 | +--ro arg-length? uint8 +--ro msd +--ro max-sl? uint8 +--ro max-end-pop? uint8 +--ro max-h_encap? uint8 +--ro max-end_d? uint8 ]]>

OSPFv3 SRv6 YANG Module WG List: Author: Yingzhen Qu Author: Zhibo Hu Author: Xuesong Geng Author: Kamran Raza Author: Acee Lindem "; description "The YANG module defines the configuration and operational state for OSPFv3 extensions to support Segment Routing over IPv6 data plane as defined in RFC9513. This YANG model conforms to the Network Management Datastore Architecture (NDMA) 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 (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."; revision 2025-03-01 { description "Initial revision."; reference "RFC XXXX: YANG Data Model for OSPF SRv6"; } /* Identities */ identity SRV6_END_FUNC_TYPE { description "Base identity type for srv6 endpoint function code points."; } identity SRV6_END_FUNC_NO_PSP_USP { base SRV6_END_FUNC_TYPE; description "End (no PSP, no USP)."; } identity SRV6_END_FUNC_PSP { base SRV6_END_FUNC_TYPE; description "End with PSP."; } identity SRV6_END_FUNC_USP { base SRV6_END_FUNC_TYPE; description "END with USP."; } identity SRV6_END_FUNC_PSP_USP { base SRV6_END_FUNC_TYPE; description "END with PSP & USP."; } identity SRV6_END_T_FUNC_NO_PSP_USP { base SRV6_END_FUNC_TYPE; description "End.T (no PSP, no USP)."; } identity SRV6_END_T_FUNC_PSP { base SRV6_END_FUNC_TYPE; description "End.T with PSP."; } identity SRV6_END_T_FUNC_USP { base SRV6_END_FUNC_TYPE; description "End.T with USP."; } identity SRV6_END_T_FUNC_PSP_USP { base SRV6_END_FUNC_TYPE; description "End.T with PSP & USP."; } identity SRV6_END_X_FUNC_NO_PSP_USP { base SRV6_END_FUNC_TYPE; description "End.x (no PSP, no USP)."; } identity SRV6_END_X_FUNC_PSP { base SRV6_END_FUNC_TYPE; description "End.x with PSP."; } identity SRV6_END_X_FUNC_USP { base SRV6_END_FUNC_TYPE; description "End.x with USP."; } identity SRV6_END_X_FUNC_PSP_USP { base SRV6_END_FUNC_TYPE; description "End.x with PSP & USP."; } identity SRV6_END_FUNC_DX6 { base SRV6_END_FUNC_TYPE; description "End.DX6 function."; } identity SRV6_END_FUNC_DT6 { base SRV6_END_FUNC_TYPE; description "End.DT6 function."; } identity SRV6_END_FUNC_OTP { base SRV6_END_FUNC_TYPE; description "END.OTP."; } identity s1-bit { base ospf:ospfv3-lsa-option; description "The S1/S2 bits are dependent on the desired flooding scope for the LSA."; } identity s2-bit { base ospf:ospfv3-lsa-option; description "The S1/S2 bits are dependent on the desired flooding scope for the LSA."; } identity srv6-locator-lsa { base ospf:ospfv3-lsa-type; description "SRv6 Locator LSA - Type TBD"; } identity LOCATOR-ROUTE-TYPE { description "The type of the locator route."; } identity INTRA-AREA-LOCATOR { base LOCATOR-ROUTE-TYPE; description "Intra-Area"; } identity INTER-AREA-LOCATOR { base LOCATOR-ROUTE-TYPE; description "Inter-Area"; } identity AS-EXTERNAL-LOCATOR { base LOCATOR-ROUTE-TYPE; description "AS External"; } identity NSSA-EXTERNAL-LOCATOR { base LOCATOR-ROUTE-TYPE; description "NSSA External"; } identity srv6-capability-bit { description "Base identity for SRv6 capability TLV bits."; } identity o-bit { base srv6-capability-bit; description "O-flag."; reference "RFC 9259: Operations, Administration, and Maintenance (OAM) in Segment Routing over IPv6 (SRv6)"; } identity srv6-end-sid-bit { description "Base identity for SRv6 End SID sub-TLV bits."; } identity srv6-endx-sid-bit { description "Base identity for SRv6 End.X SID sub-TLV bits."; } identity b-bit { base srv6-endx-sid-bit; description "B-flag. Backup flag. If set, the End.X sid is eligible for protection."; } identity s-bit { base srv6-endx-sid-bit; description "S-flag. Set flag. When set, the End.X sid refers to a set of adjacencies (and therefore May be assigned to other adjacencies as well."; } identity p-bit { base srv6-endx-sid-bit; description "P-flag. Persistent flag. When set, the End.X sid is persistently allocated, i.e., the End.x sid value remains consistent across router restart and/or interface flap."; } identity ac-bit { base ospfv3-e-lsa:ospfv3-e-prefix-option; description "When the prefix/SRv6 Locator is configured as anycast, the AC-bit MUST be set. Otherwise, this flag MUST be clear."; reference "draft-ietf-lsr-ospfv3-srv6-extensions"; } /* typedef */ typedef srv6-sid-value { type inet:ipv6-address-no-zone; description "16 Octets encoded sid value."; } /* Features */ feature srv6-ti-lfa { description "Enhance SRv6 FRR with ti-lfa support"; } /* Groupings */ grouping srv6-capabilities { description "SRV6 capability grouping."; container srv6-capability { description "SRv6 capability."; leaf-list flags { type identityref { base srv6-capability-bit; } description "SRv6 Capability TLV flag bits list."; } } } grouping srv6-endpoint-func { description "This group defines srv6 endpoint function"; container endpoint-func { description "SRv6 Endpoint function Descriptor."; leaf-list flags { type identityref { base srv6-end-sid-bit; } description "SRv6 End SID sub-TLV flag bits list. No flags are currently being defined."; } leaf endpoint-func { type identityref { base SRV6_END_FUNC_TYPE; } description "The endpoint function."; } leaf undefined-endpoint-func { type uint16; description "Unknown endpoint func value."; } } } grouping srv6-end-sids { description "This group defines srv6 end sid"; container srv6-end-sid { description "SRv6 Segment Identifier(SID) with Endpoint functions."; leaf-list flags { type identityref { base srv6-end-sid-bit; } description "SRv6 end sid flags."; } uses srv6-endpoint-func; leaf sid { type srv6-sid-value; description "SRV6 sid value."; } uses srv6-sid-structures; } } grouping srv6-sid-structures { description "This group defines SRv6 SID Structure sub-TLV."; container srv6-sid-structure { description "SRv6 SID Structure sub-TLV is used to advertise the length of each individual part of the SRv6 SID as defined in [I-D.ietf-spring-srv6-network-programming]"; leaf lb-length { type uint8; description "SRv6 SID Locator Block length in bits."; } leaf ln-length { type uint8; description "SRv6 SID Locator Node length in bits."; } leaf fun-length { type uint8; description "SRv6 SID Function length in bits."; } leaf arg-length { type uint8; description "SRv6 SID Argument length in bits."; } } } grouping srv6-endx-sids { description "This group defines SRv6 SIDs Associated with Adjacencies including SRv6 End.X SID Sub-TLV and SRv6 LAN End.X SID Sub-TLV."; container srv6-endx-sid { description "SRv6 sids associated with an adjacency."; uses srv6-endpoint-func; leaf-list func-flags { type identityref { base srv6-endx-sid-bit; } description "Flags for SRv6 end x SID."; } leaf algorithm { type uint8; description "Associated algorithm."; } leaf weight { type uint8; description "8 bit field whose value represents the weight of the End.X SID for the purpose of load balancing"; } leaf-list sid { type srv6-sid-value; description "SRV6 sid value."; } leaf neighbor-router-id { type yang:dotted-quad; description "Neighbor router ID.This is only used on LAN adjacencies."; } uses srv6-sid-structures; } } grouping srv6-locator-lsas { description "Grouping for SRv6 locator lsas."; container srv6-localtor-lsas { description "SRv6 locator lsas."; list srv6-locator-lsa { description "List of SRv6 locator lsa."; leaf link-state-id { type uint32; description "Link State ID."; } leaf adv-router { type rt-types:router-id; description "Advertising router id."; } list sr6-locator-tlv { description "List of tlvs in SRv6 locator lsa."; container srv6-locactor-tlvs { description "This contains a SRv6 locator tlv."; leaf route-type { type identityref { base LOCATOR-ROUTE-TYPE; } description "The type of the locator route"; } leaf algorithm { type uint8; description "Associated algorithm."; } leaf locator-length { type uint8; description "Carries the length of the Locator prefix as number of bits (1-128)"; } leaf-list flags { type identityref { base ospfv3-e-lsa:ospfv3-e-prefix-option; } description "Flags for srv6 locator tlv."; } leaf metric { type uint32; description "Metric value."; } leaf-list locator { type inet:ipv6-address-no-zone; description "Advertised SRV6 locator."; } uses srv6-end-sids; } container unknown-tlv { uses ospf:tlv; description "Unknow tlv."; } } } } } /* Cfg */ augment "/rt:routing/" + "rt:control-plane-protocols/rt:control-plane-protocol" + "/ospf:ospf" { when "../rt:type = 'ospf:ospfv3'" { description "This augment OSPFv3 routing protocol when used"; } description "This augments OSPFv3 protocol configuration with SRv6."; container srv6 { leaf enable { type boolean; default "false"; description "Enables SRv6 protocol extensions."; } leaf default-locator { type boolean; default "false"; description "Enable OSPFv3 segment-routing IPv6 with default Locator."; } leaf-list locator-name { when "not(../default-locator='true')" { description "Only applies to non default locator."; } type leafref { path "/rt:routing/sr:segment-routing/srv6:srv6" + "/srv6:locators/srv6:locator/srv6:name"; } description "Enable OSPFv3 segment-routing IPv6 with specified locator."; } leaf persistent-end-x-sid { type boolean; default "false"; description "Enable the persistent nature of End.X sid"; } description "Configuration about OSPFv3 segment-routing IPv6."; } container micro-loop-avoidance { leaf srv6-enable { type boolean; default "false"; description "Enable SRv6 avoid-microloop.Depend on SR IPv6 Enable."; } leaf srv6-rib-update-delay { type uint16 { range "1000..10000"; } units "ms"; default "5000"; description "Set the route delivery delay for SRv6 avoid-microloop. Depend on SR IPv6 Enable."; } description "Enable OSPFv3 avoid-microloop."; } } augment "/rt:routing/" + "rt:control-plane-protocols/rt:control-plane-protocol" + "/ospf:ospf/ospf:fast-reroute" { when "../../rt:type = 'ospf:ospfv3'" { description "This augment OSPFv3 routing protocol when used"; } description "This augments OSPFv3 IP FRR with IPV6 TILFA."; container srv6-ti-lfa { if-feature "srv6-ti-lfa"; leaf enable { type boolean; description "Enables SRv6 TI-LFA computation."; } description "SRv6 TILFA configuration."; } } /* 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:ospfv3/" + "ospf:ospfv3/ospf:body" { when "../../../../../../../../../../../rt:type = 'ospf:ospfv3'" { description "This augment OSPFv3 routing protocol when used"; } description "This augments OSPFv3 database with link scope SRv6 locator lsas."; uses srv6-locator-lsas; } 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 augment OSPFv3 routing protocol when used"; } description "This augments OSPFv3 database with area scope SRv6 locator lsas."; uses srv6-locator-lsas; } 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 "../../../../../../../rt:type = 'ospf:ospfv3'" { description "This augment OSPFv3 routing protocol when used"; } description "This augments OSPFv3 database with as scope SRv6 locator lsas."; uses srv6-locator-lsas; } 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 "Area scope OSPFv3 Router Information LSA."; uses srv6-capabilities; uses srv6:srv6-msd-signaled; } 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 augment OSPFv3 routing protocol when used"; } description "This augments OSPFv3 protocol router capability."; uses srv6-capabilities; uses srv6:srv6-msd-signaled; } 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 "../../../../../../../../../../../../rt:type" + "= 'ospf:ospfv3'" { description "This augment OSPFv3 routing protocol when used"; } description "This augments OSPFv3 protocol neighbor."; uses srv6-endx-sids; uses srv6:srv6-msd-signaled; } /* Notifications */ } ]]>

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 [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF layer is the secure transport layer, and the mandatory-to-implement secure transport is Secure Shell (SSH) [RFC6242]. The lowest RESTCONF layer is HTTPS, and the mandatory-to-implement secure transport is TLS [RFC8446]. The Network Configuration Access Control Model provides the means to restrict access for particular NETCONF or RESTCONF users to a preconfigured 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 are the subtrees and data nodes and their sensitivity/vulnerability:

• srv6
• micro-loop-avoidance
• srv6-ti-lfa

The ability to disable or enable OSPF Segment Routing support and/or change Segment Routing configurations can result in a Denail-of-Service (DoS) attack, as this may cause traffic to be dropped or misrouted. 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 are the subtrees and data nodes and their sensitivity/vulnerability:

• srv6-locator
• srv6-capability
• srv6-msd
• srv6-endx-sid

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

Contributors

Acknowledgements TBD.

IANA Considerations The IANA is requested to assign two new URIs 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 :

Normative References Huawei Technologies Huawei Technologies Arrcus Inc Cisco Systems The Segment Routing (SR) architecture allows a flexible definition of the end-to-end path by encoding it as a sequence of topological elements called segments. It can be implemented over an MPLS or IPv6 data plane. This document describes the OSPFv3 extensions required to support SR over the IPv6 data plane. Cisco Systems Individual Cisco Systems INSA Lyon Orange Bell Canada This document presents Topology Independent Loop-free Alternate Fast Re-route (TI-LFA), aimed at providing protection of node and adjacency segments within the Segment Routing (SR) framework. This Fast Re-route (FRR) behavior builds on proven IP-FRR concepts being LFAs, remote LFAs (RLFA), and remote LFAs with directed forwarding (DLFA). It extends these concepts to provide guaranteed coverage in any two connected network using a link-state IGP. A key aspect of TI-LFA is the FRR path selection approach establishing protection over the expected post-convergence paths from the point of local repair, reducing the operational need to control the tie-breaks among various FRR options. Cisco Systems Cisco Systems Volta Networks Huawei Technologies Infinera Corporation Ciena Corporation Bell Canada SoftBank SoftBank Cisco Systems Cisco Systems This document describes a YANG data model for Segment Routing IPv6 (SRv6) base. The model serves as a base framework for configuring and managing an SRv6 subsystem and expected to be augmented by other SRv6 technology models accordingly. Additionally, this document also specifies the model for the SRv6 Static application. The YANG modules in this document conform to the Network Management Datastore Architecture (NMDA). LabN Consulting, L.L.C. Microsoft Futurewei Technologies This document defines a YANG data model augmenting the IETF OSPF YANG data model (RFC 9129) to provide support for OSPFv3 Link State Advertisement (LSA) Extensibility as defined in RFC 8362. OSPFv3 Extended LSAs provide extensible TLV-based LSAs for the base LSA types defined in RFC 5340. In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. YANG is a data modeling language used to model configuration and state data manipulated by the Network Configuration Protocol (NETCONF), NETCONF remote procedure calls, and NETCONF notifications. [STANDARDS-TRACK] YANG is a data modeling language used to model configuration data, state data, Remote Procedure Calls, and notifications for network management protocols. This document describes the syntax and semantics of version 1.1 of the YANG language. YANG version 1.1 is a maintenance release of the YANG language, addressing ambiguities and defects in the original specification. There are a small number of backward incompatibilities from YANG version 1. This document also specifies the YANG mappings to the Network Configuration Protocol (NETCONF). The Network Configuration Protocol (NETCONF) defined in this document provides mechanisms to install, manipulate, and delete the configuration of network devices. It uses an Extensible Markup Language (XML)-based data encoding for the configuration data as well as the protocol messages. The NETCONF protocol operations are realized as remote procedure calls (RPCs). This document obsoletes RFC 4741. [STANDARDS-TRACK] Arrcus Futurewei Juniper Networks The MITRE Corporation Cisco Systems This document defines a YANG data model that can be used to configure and manage OSPF. The model is based on YANG 1.1 as defined in RFC 7950 and conforms to the Network Management Datastore Architecture (NMDA) as described in RFC 8342. The standardization of network configuration interfaces for use with the Network Configuration Protocol (NETCONF) or the RESTCONF protocol requires a structured and secure operating environment that promotes human usability and multi-vendor interoperability. There is a need for standard mechanisms to restrict NETCONF or RESTCONF protocol access for particular users to a preconfigured subset of all available NETCONF or RESTCONF protocol operations and content. This document defines such an access control model. This document describes an IANA maintained registry for IETF standards which use Extensible Markup Language (XML) related items such as Namespaces, Document Type Declarations (DTDs), Schemas, and Resource Description Framework (RDF) Schemas. This document captures the current syntax used in YANG module tree diagrams. The purpose of this document is to provide a single location for this definition. This syntax may be updated from time to time based on the evolution of the YANG language. Datastores are a fundamental concept binding the data models written in the YANG data modeling language to network management protocols such as the Network Configuration Protocol (NETCONF) and RESTCONF. This document defines an architectural framework for datastores based on the experience gained with the initial simpler model, addressing requirements that were not well supported in the initial model. This document updates RFC 7950. RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings. This document defines three YANG data models. The first is for Segment Routing (SR) configuration and operation, which is to be augmented by different Segment Routing data planes. The next is a YANG data model that defines a collection of generic types and groupings for SR. The third module defines the configuration and operational states for the Segment Routing MPLS data plane.