BGP Multipath in Inter-AS Option-B
draft-mohanty-bess-mutipath-interas-01

Document Type Expired Internet-Draft (individual)
Last updated 2018-04-19 (latest revision 2017-09-11)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
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
https://www.ietf.org/archive/id/draft-mohanty-bess-mutipath-interas-01.txt

Abstract

By default, The Border Gateway Protocol, BGP only installs the best- path to the IP Routing Table. BGP multi-path is a well known feature that enables installation of multiple paths to the IP Routing Table. This is done to achieve load balancing while forwarding traffic. For a path to be eligible as a multi-path, certain criteria need to be fulfilled. Inter-AS VPNs are commonly deployed to span organizations across Service Provider boundaries. In this draft, we describe an issue relating to multi-path load balancing that can arise in an Option B Inter-AS Deployment. With the help of a representative topology, we illustrate the problem and then present two simple schemes as the solution to the problem. We also note as a matter of independent interest that the same underlying issue is applicable to deployments that employ next-hop-self behavior (implicit or explicit) downstream and the multi-path feature upstream.

Authors

satyamoh@cisco.com (satyamoh@cisco.com)
Arjun Sreekantiah (asreekan@cisco.com)
Dhananjaya Rao (dhrao@cisco.com)
Keyur Patel (keyur@arrcus.com)

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