RFC 7140: LDP Extensions for Hub and Spoke Multipoint Label Switched Path
In plain English — editorial summary, not part of the RFC
This document introduces a hub and spoke multipoint (HSMP) Label Switched Path (LSP), which allows traffic from root to leaf through point-to-multipoint (P2MP) LSPs and also leaf to root along the reverse path. That means traffic entering the HSMP LSP from the application/customer at the root node travels downstream to each leaf node, exactly as if it were traveling downstream along a P2MP LSP to each leaf node. Upstream traffic entering the HSMP LSP at any leaf node travels upstream along the tree to the root, as if it were unicast to the root. Direct communication among the leaf nodes is not allowed.
Document record
- Document ID
- RFC7140
- Published
- March 2014
- Authors
- L. Jin; F. Jounay; IJ. Wijnands; N. Leymann
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 15
- Also known as
- —
- Updated by:
- RFC 7358
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7139GMPLS Signaling Extensions for Control of Evolving G.709 Optical Transport NetworksUpdated
March 2014
- RFC 7138Traffic Engineering Extensions to OSPF for GMPLS Control of Evolving G.709 Optical Transport NetworksCurrent
March 2014
- RFC 7142Reclassification of RFC 1142 to HistoricCurrent
February 2014
- RFC 7137Use of the OSPF-MANET Interface in Single-Hop Broadcast NetworksCurrent
February 2014
- RFC 7132Threat Model for BGP Path SecurityCurrent
February 2014
- RFC 7130Bidirectional Forwarding Detection (BFD) on Link Aggregation Group (LAG) InterfacesCurrent
February 2014
- RFC 7150Conveying Vendor-Specific Constraints in the Path Computation Element Communication ProtocolObsoleted
March 2014
- RFC 7128Resource Public Key Infrastructure (RPKI) Router Implementation ReportCurrent
February 2014
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?