Equal-Cost Multipath Considerations for BGP

The information below is for an old version of the document
Document Type Expired Internet-Draft (individual)
Author Petr Lapukhov 
Last updated 2018-05-03 (latest revision 2017-10-30)
Stream (None)
Expired & archived
pdf htmlized bibtex
Additional Resources
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


BGP routing protocol defined in ([RFC4271]) employs tie-breaking logic to elect single best path among multiple possible. At the same time, it has been common in all practical BGP implementations to allow for "equal-cost multipath" (ECMP) path election and programming of multiple next-hops in routing tables. This documents provides some common considerations for the ECMP logic, with the intent of providing common reference on otherwise unstandardized feature.


Petr Lapukhov (petr@fb.com)

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