RFC 9983: OSPFv2 Anycast Property Advertisement

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…

Read RFC 9983 on the RFC Editor

Outgoing relationships (19 related RFCs)

Normative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
Normative reference — RFC 8174: Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
Normative reference — RFC 3688: The IETF XML Registry
Normative reference — RFC 6020: YANG - A Data Modeling Language for the Network Configuration Protocol (NETCONF)
Normative reference — RFC 7950: The YANG 1.1 Data Modeling Language
Normative reference — RFC 8341: Network Configuration Access Control Model
Normative reference — RFC 8349: A YANG Data Model for Routing Management (NMDA Version)
Normative reference — RFC 7684: OSPFv2 Prefix/Link Attribute Advertisement
Normative reference — RFC 9085: Border Gateway Protocol - Link State (BGP-LS) Extensions for Segment Routing
Normative reference — RFC 9129: YANG Data Model for the OSPF Protocol
Informative reference — RFC 8446: The Transport Layer Security (TLS) Protocol Version 1.3
Informative reference — RFC 6241: Network Configuration Protocol (NETCONF)
Informative reference — RFC 8040: RESTCONF Protocol
Informative reference — RFC 9000: QUIC: A UDP-Based Multiplexed and Secure Transport
Informative reference — RFC 8340: YANG Tree Diagrams
Informative reference — RFC 4252: The Secure Shell (SSH) Authentication Protocol
Informative reference — RFC 9352: IS-IS Extensions to Support Segment Routing over the IPv6 Data Plane
Informative reference — RFC 9513: OSPFv3 Extensions for Segment Routing over IPv6 (SRv6)
Informative reference — RFC 9907: Guidelines for Authors and Reviewers of Documents Containing YANG Data Models