Skip to main content

Carrying next-hop cost information in BGP

Document Type Expired Internet-Draft (idr WG)
Expired & archived
Authors Ilya Varlashkin , Robert Raszuk , Keyur Patel , Manish Bhardwaj , Serpil Bayraktar
Last updated 2022-06-03 (Latest revision 2021-11-30)
Replaces draft-varlashkin-bgp-nh-cost
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status (None)
Additional resources Mailing list discussion
Stream WG state WG Document
Document shepherd (None)
IESG IESG state Expired
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:


BGPLS provides a mechanism by which Link state and traffic engineering information can be collected from internal networks and shared with external network routers using BGP. BGPLS defines a new Address Family to exchange this information using BGP. BGP Optimal Route Reflection [BGP-ORR] [RFC9107] provides a mechanism for a centralized BGP Route Reflector to acheive requirements of a Hot Potato Routing as described in Section 11 of [RFC4456]. Optimal Route Reflection requires BGP ORR to overwrite the default IGP location placement of the route reflector; which is used for determining cost to the nexthop contained in the path. This draft augments BGPLS and defines a new extensions to exchange cost information to next-hops for the purpose of calculating best path from a peer perspective rather than local BGP speaker own perspective.


Ilya Varlashkin
Robert Raszuk
Keyur Patel
Manish Bhardwaj
Serpil Bayraktar

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