Best Practices for Advertisement of Multiple Paths in BGP
draft-uttaro-idr-add-paths-guidelines-03
Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Jim Uttaro , Place Barbe , Pierre Francois , Roberto Fragassi , Adam Simpson , Prodosh Mohapatra | ||
Last updated | 2011-01-10 (Latest revision 2010-10-24) | ||
Replaced by | draft-ietf-idr-add-paths-guidelines | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Replaced by draft-ietf-idr-add-paths-guidelines | |
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
Add-Paths is a BGP enhancement that allows a BGP router to advertise multiple distinct paths for the same prefix/NLRI. This provides a number of potential benefits, including reduced routing churn, faster convergence and better loadsharing. This document provides recommendations to implementers of Add-Paths so that network operators have the tools needed to address their specific applications and to manage the scalability impact of Add- Paths. A router implementing Add-Paths may learn many paths for a prefix and must decide which of these to advertise to peers. This document analyses different algorithms for making this selection and provides recommendations based on the target application.
Authors
Jim Uttaro
Place Barbe
Pierre Francois
Roberto Fragassi
Adam Simpson
Prodosh Mohapatra
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)