BGP Next-Hop Capabilities
draft-decraene-idr-next-hop-capability-01
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Replaced".
Expired & archived
|
|
|---|---|---|---|
| Authors | Bruno Decraene , Kireeti Kompella , Wim Henderickx | ||
| Last updated | 2016-01-07 (Latest revision 2015-07-06) | ||
| Replaced by | draft-ietf-idr-next-hop-capability | ||
| RFC stream | (None) | ||
| Formats | |||
| Additional resources | |||
| 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
RFC 5492 defines capabilities advertisement for the BGP peer. In addition, it is useful to know the capabilities of the BGP Next-Hop, in particular for forwarding plane features. RFC 5492 is not applicable because the BGP peer may be different from the BGP Next- Hop, in particular when BGP Route Reflection is used. This document defines a mechanism to advertise such BGP Next Hop Capabilities. This document defines a new BGP non-transitive attribute to carry Next-Hop Capabilities. This attribute is deleted when the BGP Next Hop is changed. This document also defines a Next-Hop capability to advertise the ability to handle the Entropy Label defined in RFC 6790.
Authors
Bruno Decraene
Kireeti Kompella
Wim Henderickx
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)