RFC 8518: Selection of Loop-Free Alternates for Multi-Homed Prefixes
In plain English — editorial summary, not part of the RFC
Deployment experience gained from implementing algorithms to determine Loop-Free Alternates (LFAs) for multi-homed prefixes (MHPs) has revealed some avenues for potential improvement. This document provides explicit inequalities that can be used to evaluate neighbors as potential alternates for MHPs. It also provides detailed criteria for evaluating potential alternates for external prefixes advertised by OSPF ASBRs. This document updates Section 6 of RFC 5286 by expanding some of the routing aspects.
Document record
- Document ID
- RFC8518
- Published
- March 2019
- Authors
- P. Sarkar; U. Chunduri; S. Hegde; J. Tantsura; H. Gredler
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 20
- Also known as
- —
- Updates:
- RFC 5286
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8102Remote-LFA Node Protection and ManageabilityCurrent
March 2017
- RFC 7916Operational Management of Loop-Free AlternatesCurrent
July 2016
- RFC 8510OSPF Link-Local Signaling (LLS) Extensions for Local Interface ID AdvertisementCurrent
January 2019
- RFC 8500IS-IS Routing with Reverse MetricCurrent
February 2019
- RFC 8570IS-IS Traffic Engineering (TE) Metric ExtensionsCurrent
March 2019
- RFC 8379OSPF Graceful Link ShutdownCurrent
May 2018
- RFC 8665OSPF Extensions for Segment RoutingCurrent
December 2019
- RFC 8666OSPFv3 Extensions for Segment RoutingCurrent
December 2019
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?