RFC 7024: Virtual Hub-and-Spoke in BGP/MPLS VPNs
In plain English — editorial summary, not part of the RFC
With BGP/MPLS Virtual Private Networks (VPNs), providing any-to-any connectivity among sites of a given VPN would require each Provider Edge (PE) router connected to one or more of these sites to hold all the routes of that VPN. The approach described in this document allows the VPN service provider to reduce the number of PE routers that have to maintain all these routes by requiring only a subset of these routers to maintain all these routes. Furthermore, when PE routers use ingress replication to carry the multicast traffic of VPN customers, the approach described in this document may, under certain circumstances, reduce bandwidth inefficiency associated with ingress replication and redistribute the replication load among PE routers.
Document record
- Document ID
- RFC7024
- Published
- October 2013
- Authors
- H. Jeng; J. Uttaro; L. Jalil; B. Decraene; Y. Rekhter; R. Aggarwal
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 25
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7023MPLS and Ethernet Operations, Administration, and Maintenance (OAM) InterworkingCurrent
October 2013
- RFC 7025Requirements for GMPLS Applications of PCECurrent
September 2013
- RFC 7026Retiring TLVs from the Associated Channel Header of the MPLS Generic Associated ChannelCurrent
September 2013
- RFC 7032LDP Downstream-on-Demand in Seamless MPLSCurrent
October 2013
- RFC 7038Use of OSPF-MDR in Single-Hop Broadcast NetworksCurrent
October 2013
- RFC 7041Extensions to the Virtual Private LAN Service (VPLS) Provider Edge (PE) Model for Provider Backbone BridgingCurrent
November 2013
- RFC 6998A Mechanism to Measure the Routing Metrics along a Point-to-Point Route in a Low-Power and Lossy NetworkCurrent
August 2013
- RFC 6997Reactive Discovery of Point-to-Point Routes in Low-Power and Lossy NetworksCurrent
August 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?