RFC 7060: Using LDP Multipoint Extensions on Targeted LDP Sessions
In plain English — editorial summary, not part of the RFC
Label Distribution Protocol (LDP) can be used to set up Point-to-Multipoint (P2MP) and Multipoint-to-Multipoint (MP2MP) Label Switched Paths. However, the specification for the Multipoint Extensions to LDP presupposes that the two endpoints of an LDP session are directly connected. The LDP base specification allows for the case where the two endpoints of an LDP session are not directly connected; such a session is known as a "Targeted LDP" session. This document provides the specification for using the LDP Multipoint Extensions over a Targeted LDP session.
Document record
- Document ID
- RFC7060
- Published
- November 2013
- Authors
- M. Napierala; E. Rosen; IJ. Wijnands
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 9
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7062Framework for GMPLS and PCE Control of G.709 Optical Transport NetworksCurrent
November 2013
- RFC 7063Survey Report on Protocol Independent Multicast - Sparse Mode (PIM-SM) Implementations and DeploymentsCurrent
December 2013
- RFC 7054Addressing Requirements and Design Considerations for Per-Interface Maintenance Entity Group Intermediate Points (MIPs)Current
November 2013
- RFC 7067Directory Assistance Problem and High-Level Design ProposalCurrent
November 2013
- RFC 7052Locator/ID Separation Protocol (LISP) MIBCurrent
October 2013
- RFC 7074Revised Definition of the GMPLS Switching Capability and Type FieldsCurrent
November 2013
- RFC 7041Extensions to the Virtual Private LAN Service (VPLS) Provider Edge (PE) Model for Provider Backbone BridgingCurrent
November 2013
- RFC 7079The Pseudowire (PW) and Virtual Circuit Connectivity Verification (VCCV) Implementation Survey ResultsCurrent
November 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?