RFC 7715: Multipoint LDP (mLDP) Node Protection
In plain English — editorial summary, not part of the RFC
This document describes procedures to support node protection for Point-to-Multipoint and Multipoint-to-Multipoint Label Switched Paths (P2MP and MP2MP LSPs) that have been built by the Multipoint Label Distribution Protocol (mLDP). In order to protect a node N, the Point of Local Repair (PLR) Label Switching Router (LSR) of N must learn the Merge Point (MPT) LSR(s) of node N such that traffic can be redirected to them in case node N fails. Redirecting the traffic around the failed node N depends on existing Point-to-Point (P2P) Label Switched Paths (LSPs). The pre-established LSPs originate from the PLR LSR and terminate on the MPT LSRs while bypassing LSR N.
Document record
- Document ID
- RFC7715
- Published
- January 2016
- Authors
- IJ. Wijnands; K. Raza; A. Atlas; J. Tantsura; Q. Zhao
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 19
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7716Global Table Multicast with BGP Multicast VPN (BGP-MVPN) ProceduresCurrent
December 2015
- RFC 7709Requirements for Very Fast Setup of GMPLS Label Switched Paths (LSPs)Current
November 2015
- RFC 7708Using a Generic Associated Channel Label as a Virtual Circuit Connectivity Verification Channel IndicatorCurrent
November 2015
- RFC 7722Multi-Topology Extension for the Optimized Link State Routing Protocol Version 2 (OLSRv2)Current
December 2015
- RFC 7705Autonomous System Migration Mechanisms and Their Effects on the BGP AS_PATH AttributeCurrent
November 2015
- RFC 7726Clarifying Procedures for Establishing BFD Sessions for MPLS Label Switched Paths (LSPs)Current
January 2016
- RFC 7727Spanning Tree Protocol (STP) Application of the Inter-Chassis Communication Protocol (ICCP)Current
January 2016
- RFC 7730Resource Public Key Infrastructure (RPKI) Trust Anchor LocatorObsoleted
January 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?