IP Fast Re-Route with Fast Notification
draft-csaszar-rtgwg-ipfrr-fn-01

 
Document Type Expired Internet-Draft (individual)
Last updated 2013-08-29 (latest revision 2013-02-25)
Replaces draft-csaszar-ipfrr-fn
Stream IETF
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html
Stream WG state (None)
Document shepherd No shepherd assigned
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-csaszar-rtgwg-ipfrr-fn-01.txt

Abstract

This document describes the benefits and main applications of sending explicit fast notification (FN) packets to routers in an area. FN packets are generated and processed in the dataplane, and a single FN service can substitute existing OAM methods for remote failure detection, such as a full mesh of multi-hop BFD session. The FN service, therefore, decreases network overhead considerable. The main application is fast reroute in pure IP and in IP/LDP-MPLS networks called IPFRR-FN. The detour 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; moreover it is an efficient solution to protect against BGP ASBR failures as well as VPN PE router failures. IPFRR-FN can be a supplemental tool to provide FRR when LFA cannot repair a failure case, while it can be a replacement of existing ASBR/PE protection mechanisms by overcoming their scalability and complexity issues.

Authors

Andras Csaszar (Andras.Csaszar@ericsson.com)
Gabor Envedi (Gabor.Sandor.Enyedi@ericsson.com)
Jeff Tantsura (jeff.tantsura@ericsson.com)
Sriganesh Kini (sriganesh.kini@ericsson.com)
John Sucec (sucecj@telcordia.com)
Subir Das (sdas2@telcordia.com)

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