Skip to main content

Virtual Hub-and-Spoke in BGP/MPLS VPNs
RFC 7024

Revision differences

Document history

Date By Action
2018-12-20
(System)
Received changes through RFC Editor sync (changed abstract to 'With BGP/MPLS Virtual Private Networks (VPNs), providing any-to-any connectivity among sites of a given VPN would …
Received changes through RFC Editor sync (changed abstract to '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.')
2015-10-14
(System) Notify list changed from l3vpn-chairs@ietf.org, draft-ietf-l3vpn-virtual-hub@ietf.org to (None)
2014-08-08
(System) Posted related IPR disclosure: Huawei Technologies Co.,Ltd's Statement about IPR related to RFC 7024
2013-10-09
(System) RFC published