Abstract
draft-bashandy-rtgwg-bgp-pic-02

Document Type Replaced Internet-Draft (individual)
Last updated 2015-11-09
Replaced by draft-ietf-rtgwg-bgp-pic
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 Replaced by draft-ietf-rtgwg-bgp-pic
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-bashandy-rtgwg-bgp-pic-02.txt

Abstract

In the network comprising thousands of iBGP peers exchanging millions of routes, many routes are reachable via more than one path. 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 chains 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 transparency and 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 (bashandy@cisco.com)
Clarence Filsfils (cfilsfil@cisco.com)
Prodosh Mohapatra (mpradosh@yahoo.com)

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