RFC 7490: Remote Loop-Free Alternate (LFA) Fast Reroute (FRR)
In plain English — editorial summary, not part of the RFC
This document describes an extension to the basic IP fast reroute mechanism, described in RFC 5286, that provides additional backup connectivity for point-to-point link failures when none can be provided by the basic mechanisms.
Document record
- Document ID
- RFC7490
- Published
- April 2015
- Authors
- S. Bryant; C. Filsfils; S. Previdi; M. Shand; N. So
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 29
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7487Configuration of Proactive Operations, Administration, and Maintenance (OAM) Functions for MPLS-Based Transport Networks Using RSVP-TECurrent
March 2015
- RFC 7498Problem Statement for Service Function ChainingCurrent
April 2015
- RFC 7503OSPFv3 AutoconfigurationCurrent
April 2015
- RFC 7506IPv6 Router Alert Option for MPLS Operations, Administration, and Maintenance (OAM)Current
April 2015
- RFC 7474Security Extension for OSPFv2 When Using Manual Key ManagementCurrent
April 2015
- RFC 7473Controlling State Advertisements of Non-negotiated LDP ApplicationsUpdated
March 2015
- RFC 7471OSPF Traffic Engineering (TE) Metric ExtensionsCurrent
March 2015
- RFC 7470Conveying Vendor-Specific Constraints in the Path Computation Element Communication ProtocolUpdated
March 2015
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?