RFC 7024

Virtual Hub-and-Spoke in BGP/MPLS VPNs, October 2013

File formats:
icon for text file icon for PDF icon for HTML
H. Jeng
J. Uttaro
L. Jalil
B. Decraene
Y. Rekhter
R. Aggarwal
l3vpn (rtg)

Cite this RFC: TXT  |  XML  |   BibTeX

DOI:  https://doi.org/10.17487/RFC7024

Discuss this RFC: Send questions or comments to the mailing list l3vpn@ietf.org

Other actions: Submit Errata  |  Find IPR Disclosures from the IETF  |  View History of RFC 7024


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.

For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 8729.

Advanced Search