Updates to Anycast Property advertisement for OSPFv2
draft-ietf-lsr-anycast-flag-00
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Active".
Expired & archived
|
|
|---|---|---|---|
| Authors | Ran Chen , Detao Zhao , Peter Psenak , Ketan Talaulikar , Changwang Lin | ||
| Last updated | 2024-10-12 (Latest revision 2024-04-10) | ||
| Replaces | draft-chen-lsr-anycast-flag | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| 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
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. Each prefix is advertised along with an 8-bit field of capabilities,by using the flag flield in the OSPFv2 Extended Prefix TLV, but the definition of anycast flag to identify the prefix as anycast has not yet been defined. This document defines a new flag in the OSPFv2 Extended Prefix TLV Flags to advertise the anycast property.
Authors
Ran Chen
Detao Zhao
Peter Psenak
Ketan Talaulikar
Changwang Lin
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)