Updates to Anycast Property advertisement for OSPF
draft-chen-lsr-anycast-flag-01
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Replaced".
Expired & archived
|
|
|---|---|---|---|
| Authors | Ran Chen , Detao Zhao , Peter Psenak , Ketan Talaulikar | ||
| Last updated | 2022-05-11 (Latest revision 2021-11-07) | ||
| Replaced by | draft-ietf-lsr-anycast-flag, draft-ietf-lsr-anycast-flag | ||
| RFC stream | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
Each prefix is advertised along with an 8-bit field of capabilities,by using the Prefix Options[RFC8362] and the flag flield in the OSPFv2 Extended Prefix TLV [RFC7684], but the definition of anycast flag to identify the prefix as anycast has not yet been defined. However, Almost all bits of the Flag field has been assigned already. Thus, it is also required to extend the flag field for future use. This document updates [RFC7684] and [RFC8362], by defining a new variable length Prefix attributes Sub-TLVs for OSPFv2 and OSPFv3 and a new flag in the Prefix attributes Sub-TLV to advertise the anycast property.
Authors
Ran Chen
Detao Zhao
Peter Psenak
Ketan Talaulikar
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)