OSPFv2 Anycast Property Advertisement
RFC 9983
Revision differences
Document history
| Date | By | Action |
|---|---|---|
|
2026-05-20
|
(System) | Changed metadata: changed keywords to '['Extended Prefix TLV', 'AC‑flag', 'YANG']' from '[]' |
|
2026-05-20
|
(System) | Metadata update from RFC Editor |
|
2026-05-20
|
(System) | Changed author "C. Lin": changed name from "Changwang Lin" to "C. Lin", cleared country (was "China") |
|
2026-05-20
|
(System) | Changed author "K. Talaulikar": changed name from "Ketan Talaulikar" to "K. Talaulikar" |
|
2026-05-20
|
(System) | Changed author "P. Psenak": changed name from "Peter Psenak" to "P. Psenak" |
|
2026-05-20
|
(System) | Changed author "D. Zhao": changed name from "Detao Zhao" to "D. Zhao", cleared country (was "China") |
|
2026-05-20
|
(System) | Changed author "R. Chen": changed name from "Ran Chen" to "R. Chen", cleared country (was "China") |
|
2026-05-20
|
(System) | Metadata update from RFC Editor |
|
2026-05-19
|
(System) | Received changes through RFC Editor sync (created document RFC 9983, created became rfc relationship between draft-ietf-lsr-anycast-flag and RFC 9983, set abstract to 'An … Received changes through RFC Editor sync (created document RFC 9983, created became rfc relationship between draft-ietf-lsr-anycast-flag and RFC 9983, set abstract to '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.', set pages to 11, set standardization level to Proposed Standard, added RFC published event at 2026-05-19) |
|
2026-05-19
|
(System) | RFC published |