ZTE Corporation

Nanjing China chen.ran@zte.com.cn

ZTE Corporation

Nanjing China zhao.detao@zte.com.cn

Cisco Systems

ppsenak@cisco.com

Cisco Systems

ketant.ietf@gmail.com

New H3C Technologies

Beijing China linchangwang.04414@h3c.com

RTG lsr An IP prefix may be configured as anycast and, as such, the same value can be advertised by multiple routers. It is useful for other routers to know that the advertisement is for an anycast prefix. This document defines a new flag in the OSPFv2 Extended Prefix TLV Flags to advertise the anycast property. The document also specifies a companion YANG module for managing this function.

Status of This Memo This is an Internet Standards Track document. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 7841. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at .

Copyright Notice Copyright (c) 2026 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents () in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.

Table of Contents

• .  Introduction
  • .  Requirements Language
• .  OSPFv2 Anycast Property Advertisement
• .  BGP-LS Advertisement
• .  YANG Data Model
  • .  Tree for the YANG Data Model
  • .  YANG Data Model for OSPFv2 Anycast Property Advertisement
• .  IANA Considerations
  • .  OSPFv2 Extended Prefix TLV Flags Registry
  • .  OSPFv2 Anycast Flag YANG Module Registration
• .  Security Considerations
  • .  Protocol Security Considerations
  • .  YANG Security Considerations
• .  References
  • .  Normative References
  • .  Informative References
• Acknowledgements
• Contributors
• Authors' Addresses

Introduction An IP prefix may be configured as anycast and, as such, the same value can be advertised by multiple routers. It is useful for other routers to know that the advertisement is for an anycast prefix. defines OSPFv2 Opaque Link State Advertisements (LSAs) based on Type-Length-Value (TLV) tuples that can be used to associate additional attributes with prefixes or links. The OSPFv2 Extended Prefix TLV that is contained in the OSPFv2 Extended Prefix Opaque LSA is used to advertise additional attributes associated with a prefix. Extensions related to the anycast property of prefixes have been specified for IS-IS and OSPFv3 , even though those documents are related to Segment Routing over IPv6, the anycast property applies to any IP prefix advertisement. This document defines a flag to advertise the anycast property for a prefix advertisement in OSPFv2 in the Flags field of the OSPFv2 Extended Prefix TLV Flags (). The document also specifies a companion YANG module for managing this function.

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.

OSPFv2 Anycast Property Advertisement An IP prefix may be configured as anycast; it is useful for other routers to know that the advertisement is for an anycast prefix. In the context of the flags defined in this document, the term "set" means the bit is set to 1; "clear" means the bit is set to 0. A flag is introduced in the "OSPFv2 Extended Prefix TLV Flags" IANA registry (see ) to advertise the anycast property:

Value:

0x10

Description:

Anycast Flag (AC-Flag)

The only meaning of the AC-Flag is that the prefix is intended to be advertised by multiple nodes. When a prefix is configured as anycast, the AC-Flag MUST be set. Otherwise, this flag MUST be clear. The AC-Flag and the N-flag () MUST NOT both be set. The reception of an advertisement with both the N-flag and AC-Flag set MUST be considered a configuration anomaly, and the N-flag MUST be ignored. Additionally, the detection of such a conflicting advertisement SHOULD be logged as an operational error (subject to rate-limiting). The AC-Flag MUST be preserved when the OSPFv2 Extended Prefix Opaque LSA is re-advertised into other areas. The same prefix can be advertised by multiple routers, and, if at least one of them sets the AC-Flag in its advertisement, the prefix is considered to be anycast. A prefix that is advertised by a single node and without an AC-Flag is considered to be a node-specific prefix. Anycast prefixes SHOULD be consistently managed throughout the network. Since an AC-Flag set takes precedence in identifying the anycast property, stale configurations should be strictly monitored.

BGP-LS Advertisement defines the Prefix Attribute Flags TLV for Border Gateway Protocol - Link State (BGP-LS) that carries prefix attribute flags information. The Flags field of this TLV is interpreted according to OSPFv2 . Thus, the Flags field of the BGP-LS Prefix Attribute Flags TLV also conveys the anycast property introduced by this document.

YANG Data Model YANG is a data definition language used to define the contents of a conceptual data store that allows networked devices to be managed using Network Configuration Protocol (NETCONF) or RESTCONF . This section defines a YANG data model that can be used to manage the usage of the OSPFv2 Anycast Property as defined in this document, which augments the OSPF YANG data model and the YANG Data Model for Routing Management .

Tree for the YANG Data Model This document uses the graphical representation of data models per . The following shows the tree diagram of the module: module: ietf-ospf-anycast-flag augment /rt:routing/rt:control-plane-protocols /rt:control-plane-protocol/ospf:ospf/ospf:areas/ospf:area /ospf:interfaces/ospf:interface: +--rw anycast-flag? boolean

YANG Data Model for OSPFv2 Anycast Property Advertisement The "ietf-ospf-anycast-flag" module defined in this document imports typedefs from and . module ietf-ospf-anycast-flag { yang-version 1.1; namespace "urn:ietf:params:xml:ns:yang:ietf-ospf-anycast-flag"; prefix ospf-anycast-flag; 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"; } organization "IETF LSR - Link State Routing Working Group"; contact "WG Web: <https://datatracker.ietf.org/wg/lsr/> WG List: <mailto:lsr@ietf.org> Author: Ran Chen <mailto:chen.ran@zte.com.cn> Author: Detao Zhao <mailto:zhao.detao@zte.com.cn> Author: Peter Psenak <mailto:ppsenak@cisco.com> Author: Ketan Talaulikar <mailto:ketant.ietf@gmail.com> Author: Changwang Lin <mailto:linchangwang.04414@h3c.com>"; description "This YANG module adds the support of managing an OSPFv2 prefix as anycast. 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. Copyright (c) 2026 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). All revisions of IETF and IANA published modules can be found at the YANG Parameters registry group (https://www.iana.org/assignments/yang-parameters); This version of this YANG module is part of RFC 9983; see the RFC itself for full legal notices."; revision 2026-05-19 { description "Initial version"; reference "RFC 9983: OSPFv2 Anycast Property Advertisement"; } identity ac-flag { base ospf:ospfv2-extended-prefix-flag; description "Indicates that the prefix is configured as anycast."; } 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:ospfv2')" { description "This augments the OSPFv2 interface."; } description "This augments OSPFv2 interface with anycast property advertisement."; leaf anycast-flag { type boolean; must "not(../anycast-flag = 'true' and " + "/rt:routing/rt:control-plane-protocols/" + "rt:control-plane-protocol/ospf:ospf/" + "ospf:areas/ospf:area/ospf:interfaces/" + "ospf:interface/ospf:node-flag = 'true')" { error-message "The anycast-flag and the node-flag MUST " + "NOT both be set to 1 (true)."; description "Ensures architectural consistency by preventing a prefix from being marked as both anycast and node-specific."; } default "false"; description "Indicates that the prefix is an anycast address, if set to 1 (true)."; } } }

IANA Considerations IANA has allocated and/or registered the following values in their respective registries.

OSPFv2 Extended Prefix TLV Flags Registry IANA has allocated the following value in the "OSPFv2 Extended Prefix TLV Flags" registry: 0x10: AC-Flag (Anycast Flag)

OSPFv2 Anycast Flag YANG Module Registration IANA has registered the following URI in the "ns" registry within the "IETF XML Registry" registry group (see ):

ID:

yang:ietf-ospf-anycast-flag

URI:

urn:ietf:params:xml:ns:yang:ietf-ospf-anycast-flag

Registrant Contact:

The IESG

XML:

N/A; the requested URI is an XML namespace

IANA has registered the following YANG module in the "YANG Module Names" registry () within the "YANG Parameters" registry group.

Name:

ietf-ospf-anycast-flag

Maintained by IANA?

N

Namespace:

urn:ietf:params:xml:ns:yang:ietf-ospf-anycast-flag

Prefix:

ospf-anycast-flag

Reference:

RFC 9983

Security Considerations

Protocol Security Considerations Procedures and protocol extensions defined in this document do not affect the OSPFv2 security model. See the "Security Considerations" section of for a discussion of OSPFv2 security. The newly introduced AC-Flag, which MUST be either set or clear, introduces operational dependencies that impact the semantic validity of the advertised prefix. The correct semantic interpretation of the AC-Flag relies on both router implementation support for the flag and accurate operator configuration of the anycast route. Consequently, receivers MUST consider the possibility of misconfiguration or inconsistent implementation when relying on the AC-Flag for forwarding or security decisions.

YANG Security Considerations This section is modeled after the template described in . The "ietf-ospf-anycast-flag" YANG module defines a data model that is designed to be accessed via YANG-based management protocols, such as Network Configuration Protocol (NETCONF) and RESTCONF . These YANG-based management protocols (1) have to use a secure transport layer (e.g., SSH , TLS , and QUIC ) and (2) have to use mutual authentication. The Network Configuration Access Control Model (NACM) 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 is a data node defined in this YANG module that is writable/creatable/deletable (i.e., config true, which is the default). This data node can be considered sensitive or vulnerable in some network environments. Write operations (e.g., edit-config) and delete operations to this data node without proper protection or authentication can have a negative effect on network operations. Specifically, the following subtree and data node have particular sensitivities/vulnerabilities: /ospf:ospf/ospf:areas/ospf:area/ospf:interfaces/ospf:interface/ospf-anycast-flag:anycast-flag As specified in , the AC-Flag and the N-flag MUST NOT both be set to 1. This rule is enforced by a "must" constraint in the YANG module to prevent configuration anomalies. The handling of such anomalies is defined in . Modifications to this data node without proper protection could prevent interpreting the IPv4 prefix as anycast or node-specific. The readable data node in this YANG module 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 this data node. Specifically, the following subtree and data node have particular sensitivities/vulnerabilities: /ospf:ospf/ospf:areas/ospf:area/ospf:interfaces/ospf:interface/ospf-anycast-flag:anycast-flag Unauthorized access to the data node of this subtree can disclose specific anycast property information for OSPF prefixes on a device. There are no particularly sensitive RPC or action operations.

References Normative References 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. 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. 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] OSPFv2 requires functional extension beyond what can readily be done with the fixed-format Link State Advertisements (LSAs) as described in RFC 2328. This document defines OSPFv2 Opaque LSAs based on Type-Length-Value (TLV) tuples that can be used to associate additional attributes with prefixes or links. Depending on the application, these prefixes and links may or may not be advertised in the fixed-format LSAs. The OSPFv2 Opaque LSAs are optional and fully backward compatible. 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). 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. 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 obsoletes RFC 6536. This document specifies three YANG modules and one submodule. Together, they form the core routing data model that serves as a framework for configuring and managing a routing subsystem. It is expected that these modules will be augmented by additional YANG modules defining data models for control-plane protocols, route filters, and other functions. The core routing data model provides common building blocks for such extensions -- routes, Routing Information Bases (RIBs), and control-plane protocols. The YANG modules in this document conform to the Network Management Datastore Architecture (NMDA). This document obsoletes RFC 8022. Segment Routing (SR) allows for a flexible definition of end-to-end paths by encoding paths as sequences of topological subpaths, called "segments". These segments are advertised by routing protocols, e.g., by the link-state routing protocols (IS-IS, OSPFv2, and OSPFv3) within IGP topologies. This document defines extensions to the Border Gateway Protocol - Link State (BGP-LS) address family in order to carry SR information via BGP. 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. Informative References The Secure Shell Protocol (SSH) is a protocol for secure remote login and other secure network services over an insecure network. This document describes the SSH authentication protocol framework and public key, password, and host-based client authentication methods. Additional authentication methods are described in separate documents. The SSH authentication protocol runs on top of the SSH transport layer protocol and provides a single authenticated tunnel for the SSH connection protocol. [STANDARDS-TRACK] 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] This document describes an HTTP-based protocol that provides a programmatic interface for accessing data defined in YANG, using the datastore concepts defined in the Network Configuration Protocol (NETCONF). 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. This document specifies version 1.3 of the Transport Layer Security (TLS) protocol. TLS allows client/server applications to communicate over the Internet in a way that is designed to prevent eavesdropping, tampering, and message forgery. This document updates RFCs 5705 and 6066, and obsoletes RFCs 5077, 5246, and 6961. This document also specifies new requirements for TLS 1.2 implementations. This document defines the core of the QUIC transport protocol. QUIC provides applications with flow-controlled streams for structured communication, low-latency connection establishment, and network path migration. QUIC includes security measures that ensure confidentiality, integrity, and availability in a range of deployment circumstances. Accompanying documents describe the integration of TLS for key negotiation, loss detection, and an exemplary congestion control algorithm. 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 the MPLS or the IPv6 data plane. This document describes the IS-IS extensions required to support SR over the IPv6 data plane. This document updates RFC 7370 by modifying an existing registry. 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. This document provides guidelines for authors and reviewers of specifications containing YANG data models, including IANA-maintained YANG modules. Recommendations and procedures are defined, which are intended to increase interoperability and usability of Network Configuration Protocol (NETCONF) and RESTCONF protocol implementations that utilize YANG modules. This document obsoletes RFC 8407; it also updates RFC 8126 by providing additional guidelines for writing the IANA considerations for RFCs that specify IANA-maintained YANG modules.

Acknowledgements The authors would like to thank for aligning the terminology with existing OSPF documents and for editorial improvements.

Contributors This document has the following contributor: Futurewei Technologies

yingzhen.ietf@gmail.com

Authors' Addresses ZTE Corporation

Nanjing China chen.ran@zte.com.cn

ZTE Corporation

Nanjing China zhao.detao@zte.com.cn

Cisco Systems

ppsenak@cisco.com

Cisco Systems

ketant.ietf@gmail.com

New H3C Technologies

Beijing China linchangwang.04414@h3c.com