Sign in
Version 5.13.0, 2015-03-25
Report a bug

IP Fast Re-Route with Fast Notification

Document type: Expired Internet-Draft (individual)
Document stream: IETF
Last updated: 2013-08-29 (latest revision 2013-02-25)
Intended RFC status: Unknown
Other versions: (expired, archived): plain text, pdf, html

IETF State: (None)
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:


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.


Andras Csaszar <>
Gabor Envedi <>
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)