Advertisement of Multiple Paths in BGP
Embed This Widget
Add the script tag and a data attribute to embed this widget.
Embed via iframe for maximum compatibility.
<iframe src="https://ipfyi.com/iframe/entity//" width="420" height="400" frameborder="0" style="border:0;border-radius:10px;max-width:100%" loading="lazy"></iframe>
Paste this URL in WordPress, Medium, or any oEmbed-compatible platform.
https://ipfyi.com/entity//
Add a dynamic SVG badge to your README or docs.
[](https://ipfyi.com/entity//)
Use the native HTML custom element.
D. Walton, A. Retana, E. Chen, J. Scudder · 2016-07
Abstract
RFC 7911 defines the ADD-PATH capability for BGP, allowing a BGP speaker to advertise multiple paths for the same prefix to a peer instead of only the single best path. Each path is distinguished by a Path Identifier field prepended to the NLRI. ADD-PATH enables better route diversity for BGP-based Fast Reroute and improves path distribution in route-reflector topologies.
Why This RFC Matters
Traditional BGP advertises only the best path per prefix, which can cause suboptimal convergence and hidden path problems in route-reflector clusters. ADD-PATH allows route reflectors to advertise all viable paths to clients, enabling clients to perform their own best-path selection and maintain backup paths for instant failover. It is widely deployed in carrier and data-center networks to improve resilience and eliminate route oscillation caused by information hiding in reflector hierarchies.