RFC 6981: A Framework for IP and MPLS Fast Reroute Using Not-Via Addresses
In plain English — editorial summary, not part of the RFC
This document presents an illustrative framework for providing fast reroute in an IP or MPLS network through encapsulation and forwarding to "not-via" addresses. The general approach described here uses a single level of encapsulation and could be used to protect unicast, multicast, and LDP traffic against link, router, and shared risk group failure, regardless of network topology and metrics. The mechanisms presented in this document are purely illustrative of the general approach and do not constitute a protocol specification. The document represents a snapshot of the work of the Routing Area Working Group at the time of publication and is published as a document of record. Further work is needed before implementation or deployment.
Document record
- Document ID
- RFC6981
- Published
- August 2013
- Authors
- S. Bryant; S. Previdi; M. Shand
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 34
- 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 6984Interoperability Report for Forwarding and Control Element Separation (ForCES)Current
August 2013
- RFC 6976Framework for Loop-Free Convergence Using the Ordered Forwarding Information Base (oFIB) ApproachCurrent
July 2013
- RFC 6987OSPF Stub Router AdvertisementUpdated
September 2013
- RFC 6974Applicability of MPLS Transport Profile for Ring TopologiesCurrent
July 2013
- RFC 6992Routing for IPv4-Embedded IPv6 PacketsCurrent
July 2013
- RFC 6969OSPFv3 Instance ID Registry UpdateCurrent
July 2013
- RFC 6996Autonomous System (AS) Reservation for Private UseCurrent
July 2013
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?