Link-Local Next Hop Capability for BGP
draft-white-linklocal-capability-06
| Document | Type |
Replaced Internet-Draft
(candidate for idr WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Russ White , Jeff Tantsura , Donatas Abraitis | ||
| Last updated | 2025-03-14 (Latest revision 2025-03-02) | ||
| Replaced by | draft-ietf-idr-linklocal-capability | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | Call For Adoption By WG Issued | |
| Document shepherd | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-idr-linklocal-capability | |
| 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
BGP [RFC4271], was originally designed to provide reachability between domains and between the edges of a domain. As such, BGP assumes the next hop towards any reachable destination may not reside on the advertising speaker, but rather may either be through a router connected to the same subnet as the speaker, or through a router only reachable by traversing multiple hops through the network. Because of this, as per [RFC4291] - BGP does not recognize IPv6 link-local addresses, as a valid next hop for the forwarding purposes. This draft standardizes the operation of BGP over a point-to-point link using link-local IPv6 addressing only.
Authors
Russ White
Jeff Tantsura
Donatas Abraitis
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)