IP Fast Re-Route with Fast Notification
draft-csaszar-ipfrr-fn-02
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Replaced".
Expired & archived
|
|
|---|---|---|---|
| Authors | Andras Csaszar , Jeff Tantsura , Sriganesh Kini , John Sucec , Subir Das | ||
| Last updated | 2012-05-03 (Latest revision 2011-10-31) | ||
| Replaced by | draft-csaszar-rtgwg-ipfrr-fn | ||
| RFC stream | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document describes a mechanism that provides IP fast reroute (IPFRR) by using a failure notification (FN) to nodes beyond the ones that first detect the failure (i.e. nodes that are directly connected to the failure point). The paths used when IPFRR-FN is active are in most cases identical to those used after Interior Gateway Protocol (IGP) convergence. The proposed mechanism can address all single link, node, and SRLG failures in an area and has been designed to allow traffic recovery traffic to happen quickly (The goal being to keep traffic loss under 50msec). IPFRR-FN can be a supplemental tool to provide FRR when LFA cannot repair a failure case.
Authors
Andras Csaszar
Jeff Tantsura
Sriganesh Kini
John Sucec
Subir Das
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)