Best Practices for Advertisement of Multiple Paths in IBGP
draft-ietf-idr-add-paths-guidelines-07
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
|---|---|---|---|
| Authors | Jim Uttaro , Pierre Francois , Keyur Patel , Prodosh Mohapatra , Jeffrey Haas , Adam Simpson , Roberto Fragassi | ||
| Last updated | 2015-10-14 (Latest revision 2014-12-04) | ||
| Replaces | draft-uttaro-idr-add-paths-guidelines | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Formats | |||
| Reviews |
RTGDIR Early review
by Stewart Bryant
Not ready
|
||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Consensus: Waiting for Write-Up | |
| Document shepherd | Susan Hares | ||
| IESG | IESG state | Expired | |
| 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
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
Pierre Francois
Keyur Patel
Prodosh Mohapatra
Jeffrey Haas
Adam Simpson
Roberto Fragassi
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)