Fast Connectivity Restoration Using BGP Add-path
draft-pmohapat-idr-fast-conn-restore-03

Document Type Expired Internet-Draft (individual)
Last updated 2013-07-29 (latest revision 2013-01-22)
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-pmohapat-idr-fast-conn-restore-03.txt

Abstract

A BGP route defines an association of an address prefix with an "exit point" from the current Autonomous System (AS). If the exit point becomes unreachable due to a failure, the route becomes invalid. This usually triggers an exchange of BGP control messages after which a new BGP route for the given prefix is installed. However, connectivity can be restored more quickly if the router maintains precomputed BGP backup routes. It can then switch to a backup route immediately upon learning that an exit point is unreachable, without needing to wait for the BGP control messages exchange. This document specifies the procedures to be used by BGP to maintain and distribute the precomputed backup routes. Maintaining these additional routes is also useful in promoting load balancing, performing maintenance without causing traffic loss, and in reducing churn in the BGP control plane.

Authors

Prodosh Mohapatra (pmohapat@cisco.com)
Rex Fernando (rex@cisco.com)
Clarence Filsfils (cfilsfil@cisco.com)
Robert Raszuk (robert@raszuk.net)

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