RFC 6571: Loop-Free Alternate (LFA) Applicability in Service Provider (SP) Networks
In plain English — editorial summary, not part of the RFC
In this document, we analyze the applicability of the Loop-Free Alternate (LFA) method of providing IP fast reroute in both the core and access parts of Service Provider networks. We consider both the link and node failure cases, and provide guidance on the applicability of LFAs to different network topologies, with special emphasis on the access parts of the network. This document is not an Internet Standards Track specification; it is published for informational purposes.
Document record
- Document ID
- RFC6571
- Published
- June 2012
- Authors
- C. Filsfils; P. Francois; M. Shand; B. Decraene; J. Uttaro; N. Leymann; M. Horneffer
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 35
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5715A Framework for Loop-Free ConvergenceCurrent
January 2010
- RFC 5714IP Fast Reroute FrameworkCurrent
January 2010
- RFC 4972Routing Extensions for Discovery of Multiprotocol (MPLS) Label Switch Router (LSR) Traffic Engineering (TE) Mesh MembershipCurrent
July 2007
- RFC 8541Impact of Shortest Path First (SPF) Trigger and Delay Strategies on IGP Micro-loopsCurrent
March 2019
- RFC 9085Border Gateway Protocol - Link State (BGP-LS) Extensions for Segment RoutingUpdated
August 2021
- RFC 9127YANG Data Model for Bidirectional Forwarding Detection (BFD)Updated
October 2021
- RFC 9247BGP - Link State (BGP-LS) Extensions for Seamless Bidirectional Forwarding Detection (S-BFD)Current
June 2022
- RFC 9294Application-Specific Link Attributes Advertisement Using the Border Gateway Protocol - Link State (BGP-LS)Current
August 2022
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?