Skip to main content

BGP best path next-hop selection enhancements
draft-vroonen-idr-bgp-bestpath-nh-selection-03

Document Type Replaced Internet-Draft (candidate for idr WG)
Expired & archived
Authors Olivier Vroonen , Stephane Litkowski , kandhla Chandi , Jie Dong , Israel Means
Last updated 2026-08-21 (Latest revision 2026-07-06)
Replaced by draft-ietf-idr-bgp-bestpath-nh-selection
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status (None)
Formats
Additional resources Mailing list discussion
Stream WG state Call For Adoption By WG Issued
Document shepherd (None)
IESG IESG state Replaced by draft-ietf-idr-bgp-bestpath-nh-selection
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:

Abstract

BGP [RFC4271] has originally been designed to carry IPv4 routing information over the Internet. IP routing being "hop-by-hop" in nature, NEXT_HOP which purpose is to carry the address of the next router to send the IP packet to. In BGP, the next-hop may not be a directly connected router, hence, when evaluating paths, a BGP speaker must determine if the next-hop is resolvable and, if so, determine the internal cost to reach it. The incremental use of tunneling technologies to carry traffic between routers (e.g.: GRE, MPLS, SR-MPLS, SRv6...) may violate the assumption that the address carried in the NEXT_HOP is representative of the actual forwarding next-hop. These technologies decouple the BGP control-plane's view of the next-hop from the data-plane's actual forwarding endpoint. This document describes the problems that arise from this decoupling. These problems include sub-optimal path selection, incorrect resolvability tracking of the forwarding path leading to traffic drop or misrouting, and others. This document specifies how BGP obtains resolvability, preference, metric, and tracking information from resolution of the forwarding path and uses those values as inputs to BGP path selection.

Authors

Olivier Vroonen
Stephane Litkowski
kandhla Chandi
Jie Dong
Israel Means

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