BGP Prefix Independent Convergence
draft-ietf-rtgwg-bgp-pic-12
Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Active".
Expired & archived
|
|
---|---|---|---|
Authors | Ahmed Bashandy , Clarence Filsfils , Prodosh Mohapatra | ||
Last updated | 2021-02-13 (Latest revision 2020-08-12) | ||
Replaces | draft-bashandy-rtgwg-bgp-pic | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Formats | |||
Reviews |
RTGDIR Last Call review
by Bruno Decraene
Has issues
IOTDIR Last Call review
by Ines Robles
Ready w/nits
GENART Last Call review
by Reese Enghardt
Ready w/issues
|
||
Additional resources | Mailing list discussion | ||
Stream | WG state | In WG Last Call | |
Document shepherd | Yingzhen Qu | ||
Shepherd write-up | Show Last changed 2020-07-26 | ||
IESG | IESG state | Expired | |
Consensus boilerplate | Unknown | ||
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | Yingzhen Qu <yingzhen.ietf@gmail.com> |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
In the network comprising thousands of iBGP peers exchanging millions of routes, many routes are reachable via more than one next-hop. Given the large scaling targets, it is desirable to restore traffic after failure in a time period that does not depend on the number of BGP prefixes. In this document we proposed an architecture by which traffic can be re-routed to ECMP or pre-calculated backup paths in a timeframe that does not depend on the number of BGP prefixes. The objective is achieved through organizing the forwarding data structures in a hierarchical manner and sharing forwarding elements among the maximum possible number of routes. The proposed technique achieves prefix independent convergence while ensuring incremental deployment, complete automation, and zero management and provisioning effort. It is noteworthy to mention that the benefits of BGP-PIC are hinged on the existence of more than one path whether as ECMP or primary-backup.
Authors
Ahmed Bashandy
Clarence Filsfils
Prodosh Mohapatra
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)