BGP FRR Protection against Edge Node Failure Using Table Mirroring with Context Labels
draft-bashandy-bgp-frr-mirror-table-00

Document Type Expired Internet-Draft (individual)
Last updated 2013-04-11 (latest revision 2012-10-08)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized 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-bashandy-bgp-frr-mirror-table-00.txt

Abstract

Consider a BGP free core scenario. Suppose the edge BGP speakers PE1, PE2,..., PEn know about a prefix P/m via the external routers CE1, CE2,..., CEm. If the edge router PEi crashes or becomes totally disconnected from the core, it is desirable for a core router "P" carrying traffic to the failed edge router PEi to immediately restore traffic by re-tunneling packets originally tunneled to PEi and destined to the prefix P/m to one of the other edge routers that advertised P/m, say PEj, until BGP re-converges. This draft proposes a BGP FRR scheme that relies on having the repairing edge router mirror the protected edge router forwarding table. The repairing edge router uses a locally allocated context label to identify the correct mirrored table.

Authors

Ahmed Bashandy (bashandy@cisco.com)
Maciek Konstantynowicz (mkonstan@cisco.com)
Nagendra Kumar (naikumar@cisco.com)

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