BGP/MPLS IP Virtual Private Networks
RFC 4364, “BGP/MPLS IP Virtual Private Networks”, is a Proposed Standard document published in February 2006 by E. Rosen, Y. Rekhter. It obsoletes RFC 2547. It has since been updated by RFC 4577, RFC 4684, RFC 5462. The canonical text is published by the RFC Editor.
Abstract
This document describes a method by which a Service Provider may use an IP backbone to provide IP Virtual Private Networks (VPNs) for its customers. This method uses a "peer model", in which the customers' edge routers (CE routers) send their routes to the Service Provider's edge routers (PE routers); there is no "overlay" visible to the customer's routing algorithm, and CE routers at different sites do not peer with each other. Data packets are tunneled through the backbone, so that the core routers do not need to know the VPN routes. [STANDARDS-TRACK]
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 4364 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 4363 Definitions of Managed Objects for Bridges with Traffic Classes, Multicast Filtering, and Virtual LAN Extensions
- RFC 4365 Applicability Statement for BGP/MPLS IP Virtual Private Networks
- RFC 4362 RObust Header Compression : A Link-Layer Assisted Profile for IP/UDP/RTP
- RFC 4366 Transport Layer Security Extensions
- RFC 4361 Node-specific Client Identifiers for Dynamic Host Configuration Protocol Version Four
- RFC 4367 What's in a Name: False Assumptions about DNS Names
- RFC 4360 BGP Extended Communities Attribute
- RFC 4368 Multiprotocol Label Switching Label-Controlled Asynchronous Transfer Mode and Frame-Relay Management Interface Definition