%% You should probably cite draft-ietf-idr-entropy-label instead of this I-D. @techreport{ietf-idr-next-hop-capability-03, number = {draft-ietf-idr-next-hop-capability-03}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-ietf-idr-next-hop-capability/03/}, author = {Bruno Decraene and Kireeti Kompella and Wim Henderickx}, title = {{BGP Next-Hop dependent capabilities}}, pagetotal = 12, year = 2018, month = jun, day = 27, abstract = {RFC 5492 advertises the capabilities of the BGP peer. When the BGP peer is not the same as the BGP Next-Hop, it is useful to also be able to advertise the capability of the BGP Next-Hop, in particular to advertise forwarding plane features. This document defines a mechanism to advertise such BGP Next Hop dependent Capabilities. This document defines a new BGP non-transitive attribute to carry Next-Hop Capabilities. This attribute is guaranteed to be deleted or updated when the BGP Next Hop is changed, in order to reflect the capabilities of the new BGP Next-Hop. This document also defines a Next-Hop capability to advertise the ability to process the MPLS Entropy Label as an egress LSR for all NLRI advertised in the BGP UPDATE. It updates RFC 6790 with regard to this BGP signaling.}, }