RFC 7811: An Algorithm for Computing IP/LDP Fast Reroute Using Maximally Redundant Trees (MRT-FRR)
In plain English — editorial summary, not part of the RFC
This document supports the solution put forth in "An Architecture for IP/LDP Fast Reroute Using Maximally Redundant Trees (MRT-FRR)" (RFC 7812) by defining the associated MRT Lowpoint algorithm that is used in the Default MRT Profile to compute both the necessary Maximally Redundant Trees with their associated next hops and the alternates to select for MRT-FRR.
Document record
- Document ID
- RFC7811
- Published
- June 2016
- Authors
- G. Enyedi; A. Csaszar; A. Atlas; C. Bowers; A. Gopalan
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 118
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7812An Architecture for IP/LDP Fast Reroute Using Maximally Redundant Trees (MRT-FRR)Current
June 2016
- RFC 5286Basic Specification for IP Fast Reroute: Loop-Free AlternatesUpdated
September 2008
- RFC 9855Topology Independent Fast Reroute Using Segment RoutingCurrent
October 2025
- RFC 7916Operational Management of Loop-Free AlternatesCurrent
July 2016
- RFC 7779Directional Airtime Metric Based on Packet Sequence Numbers for Optimized Link State Routing Version 2 (OLSRv2)Current
April 2016
- RFC 7733Applicability Statement: The Use of the Routing Protocol for Low-Power and Lossy Networks (RPL) Protocol Suite in Home Automation and Building ControlCurrent
February 2016
- RFC 7732Forwarder Policy for Multicast with Admin-Local Scope in the Multicast Protocol for Low-Power and Lossy Networks (MPL)Current
February 2016
- RFC 7939Definition of Managed Objects for the Neighborhood Discovery ProtocolCurrent
August 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?