BGP Next-Hop dependant capabilities
draft-decraene-idr-next-hop-capability-03

Document Type Replaced Internet-Draft (individual)
Last updated 2017-01-26
Replaced by draft-ietf-idr-next-hop-capability
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-idr-next-hop-capability
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-decraene-idr-next-hop-capability-03.txt

Abstract

RFC 5492 defines capabilities advertisement for the BGP peer. In addition, it is useful to be able to advertise BGP Next-Hop dependant capabilities, 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 dependant Capabilities. This document defines a new BGP non-transitive attribute to carry Next-Hop Capabilities. This attribute is deleted or possibly modified when the BGP Next Hop is changed. This document also defines a Next-Hop capability to advertise the ability to handle the MPLS Entropy Label defined in RFC 6790. It updates RFC 6790 with regard to this BGP signaling.

Authors

Bruno Decraene (bruno.decraene@orange.com)
Kireeti Kompella (kireeti.kompella@gmail.com)
Wim Henderickx (wim.henderickx@nokia.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)