RFC 7916: Operational Management of Loop-Free Alternates
In plain English — editorial summary, not part of the RFC
Loop-Free Alternates (LFAs), as defined in RFC 5286, constitute an IP Fast Reroute (IP FRR) mechanism enabling traffic protection for IP traffic (and, by extension, MPLS LDP traffic). Following early deployment experiences, this document provides operational feedback on LFAs, highlights some limitations, and proposes a set of refinements to address those limitations. It also proposes required management specifications. This proposal is also applicable to remote-LFA solutions.
Document record
- Document ID
- RFC7916
- Published
- July 2016
- Authors
- S. Litkowski; B. Decraene; C. Filsfils; K. Raza; M. Horneffer; P. Sarkar
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 31
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9855Topology Independent Fast Reroute Using Segment RoutingCurrent
October 2025
- RFC 7812An Architecture for IP/LDP Fast Reroute Using Maximally Redundant Trees (MRT-FRR)Current
June 2016
- RFC 7811An Algorithm for Computing IP/LDP Fast Reroute Using Maximally Redundant Trees (MRT-FRR)Current
June 2016
- RFC 8102Remote-LFA Node Protection and ManageabilityCurrent
March 2017
- RFC 8400Extensions to RSVP-TE for Label Switched Path (LSP) Egress ProtectionCurrent
June 2018
- RFC 8518Selection of Loop-Free Alternates for Multi-Homed PrefixesCurrent
March 2019
- RFC 5286Basic Specification for IP Fast Reroute: Loop-Free AlternatesUpdated
September 2008
- RFC 7917Advertising Node Administrative Tags in IS-ISCurrent
July 2016
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?