Updates to Anycast Property advertisement for OSPFv2

Introduction Both SR-MPLS prefix-SID and IPv4 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 identifier. defines OSPFv2 Opaque 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 the prefix, but the definition of anycast flag to identify the prefix as anycast has not yet been defined. This document updates , by defining a new flag in the OSPFv2 Extended Prefix TLV Flags to advertise the anycast property.

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.

Use-case In the absence of the N-flag, the node specific prefixes need to be identified from the anycast prefixs. A prefix that is advertised by a single node and without an AC-flag MUST be considered node specific.

Updates to Anycast Property advertisement for OSPFv2 The prefix may be configured as anycast and it is useful for other routers to know that the advertisement is for an anycast identifier. defines one-octet field contains flags applicable to the prefix, and it has been defines the below flags: OSPFv2 Extended Prefix TLV Flags

Value	Description	Reference
0x80	A
0x40	N
0x02	E-Flag

A new bit in OSPFv2 Extended Prefix TLV Flags is defined to advertise the anycast property: Value: TBD Description:Anycast (AC-Flag) When the prefix is configured as anycast, the AC-Flag SHOULD be set. Otherwise, this flag MUST be clear. The AC-Flag and the N-bit MUST NOT both be set. If both N-flag and AC-Flag are set, the receiving routers MUST ignore the N-flag. The AC-Flag MUST be preserved when re-advertising the prefix across areas. The same prefix can be advertised by multiple routers, and that if at least one of them sets the AC-Flag in its advertisement, the prefix SHOULD be considered as anycast. A prefix that is advertised by a single node and without an AC-flag MUST be considered node specific prefix.

Updates to Anycast Property advertisement for BGP-LS defines the Prefix Attribute Flags TLV carries IPv4 prefix attribute flags information, and the Flags field of this TLV is interpreted according to OSPFv2 . This section extends the interpretation of the Flags field of the Prefix Attribute Flags TLV. Flags:

OSPFv2 flags correspond to the Flags field of the OSPFv2 Extended Prefix TLV defined in and extended in this draft.

Acknowledgements TBD.

IANA Considerations This document requests allocation for the following registry.

OSPFv2 Extended Prefix TLV Flags Registry This document adds a new bit in the "OSPFv2 Extended Prefix TLV Flags"registry: AC-Flag (Anycast Flag).

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.