%% You should probably cite draft-ietf-idr-next-hop-capability instead of this I-D. @techreport{decraene-idr-next-hop-capability-03, number = {draft-decraene-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-decraene-idr-next-hop-capability/03/}, author = {Bruno Decraene and Kireeti Kompella and Wim Henderickx}, title = {{BGP Next-Hop dependant capabilities}}, pagetotal = 9, year = 2017, month = jan, day = 26, 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.}, }