BGP/MPLS IP Virtual Private Networks (VPNs)
Embed This Widget
Add the script tag and a data attribute to embed this widget.
Embed via iframe for maximum compatibility.
<iframe src="https://ipfyi.com/iframe/entity//" width="420" height="400" frameborder="0" style="border:0;border-radius:10px;max-width:100%" loading="lazy"></iframe>Paste this URL in WordPress, Medium, or any oEmbed-compatible platform.
https://ipfyi.com/entity//Add a dynamic SVG badge to your README or docs.
[](https://ipfyi.com/entity//)Use the native HTML custom element.
E. Rosen, Y. Rekhter · 2006-02
Abstract
RFC 4364 specifies how BGP and MPLS are combined to build Layer 3 VPNs across a provider backbone. Provider Edge (PE) routers maintain per-VPN routing and forwarding tables (VRFs), redistribute customer routes as VPN-IPv4 prefixes via MP-BGP, and forward customer packets through MPLS Label Switched Paths. The architecture supports overlapping address spaces across different VPN customers.
Why This RFC Matters
BGP/MPLS L3VPN (often called RFC 2547bis or simply L3VPN) is the dominant enterprise WAN connectivity service offered by carriers worldwide. It allows service providers to deliver private IP connectivity to thousands of enterprise customers over a shared backbone while maintaining full routing isolation per customer. The use of Route Distinguishers (RDs) and Route Targets (RTs) to partition and share VPN routes became a model for subsequent overlay technologies.