Basic Specification for IP Fast Reroute: Loop-Free Alternates
RFC 5286, “Basic Specification for IP Fast Reroute: Loop-Free Alternates”, is a Proposed Standard document published in September 2008 by A. Atlas, A. Zinin. It has since been updated by RFC 8518. The canonical text is published by the RFC Editor.
Abstract
This document describes the use of loop-free alternates to provide local protection for unicast traffic in pure IP and MPLS/LDP networks in the event of a single failure, whether link, node, or shared risk link group (SRLG). The goal of this technology is to reduce the packet loss that happens while routers converge after a topology change due to a failure. Rapid failure repair is achieved through use of precalculated backup next-hops that are loop-free and safe to use until the distributed network convergence process completes. This simple approach does not require any support from other routers. The extent to which this goal can be met by this specification is dependent on the topology of the network. [STANDARDS-TRACK]
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 5286 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 5285 A General Mechanism for RTP Header Extensions
- RFC 5287 Control Protocol Extensions for the Setup of Time-Division Multiplexing Pseudowires in MPLS Networks
- RFC 5284 User-Defined Errors for RSVP
- RFC 5288 AES Galois Counter Mode Cipher Suites for TLS
- RFC 5283 LDP Extension for Inter-Area Label Switched Paths
- RFC 5289 TLS Elliptic Curve Cipher Suites with SHA-256/384 and AES Galois Counter Mode
- RFC 5282 Using Authenticated Encryption Algorithms with the Encrypted Payload of the Internet Key Exchange version 2 Protocol
- RFC 5290 Comments on the Usefulness of Simple Best-Effort Traffic