datatracker.ietf.org
Sign in
Version 5.6.2.p5, 2014-08-04
Report a bug

IS-IS Extension for BGP FRR Protection against Edge Node Failure
draft-bashandy-isis-bgp-edge-node-frr-01

Document type: Expired Internet-Draft (individual)
Document stream: No stream defined
Last updated: 2013-03-14 (latest revision 2012-09-10)
Intended RFC status: Unknown
Other versions: (expired, archived): plain text, pdf, html

Stream State:No stream defined
Document shepherd: No shepherd assigned

IESG State: Expired
Responsible AD: (None)
Send notices to: No addresses provided

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found here:
http://www.ietf.org/archive/id/draft-bashandy-isis-bgp-edge-node-frr-01.txt

Abstract

Consider a BGP free core scenario where traffic is tunneled between edge routers. 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 desirable for a core router "P" that is carrying traffic to the failed edge router PEi to immediately restore traffic by re- routing 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. If the packets originally flowing to the failed edge router PEi are labeled, then the repairing core router P router may need to swap, push, or pop the label advertised by the failed edge router PEi with another label before re-routing the packet through an LSP terminating PEj so that PEj can correctly forward the packet. The document proposes an extension to IS-IS protocol to inform core routers about the repair edge router PEj and, for labeled packets, the label that needs to be pushed/swapped before sending the packet into the tunnel terminating on PEj

Authors

Ahmed Bashandy <bashandy@cisco.com>

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