RFC 6624: Layer 2 Virtual Private Networks Using BGP for Auto-Discovery and Signaling
In plain English — editorial summary, not part of the RFC
Layer 2 Virtual Private Networks (L2VPNs) based on Frame Relay or ATM circuits have been around a long time; more recently, Ethernet VPNs, including Virtual Private LAN Service, have become popular. Traditional L2VPNs often required a separate Service Provider infrastructure for each type and yet another for the Internet and IP VPNs. In addition, L2VPN provisioning was cumbersome. This document presents a new approach to the problem of offering L2VPN services where the L2VPN customer's experience is virtually identical to that offered by traditional L2VPNs, but such that a Service Provider can maintain a single network for L2VPNs, IP VPNs, and the Internet, as well as a common provisioning methodology for all services. This document is not an Internet Standards Track specification; it is published for informational purposes.
Document record
- Document ID
- RFC6624
- Published
- May 2012
- Authors
- K. Kompella; B. Kothari; R. Cherukuri
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- —
- Pages
- 26
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4667Layer 2 Virtual Private Network (L2VPN) Extensions for Layer 2 Tunneling Protocol (L2TP)Current
September 2006
- RFC 6517Mandatory Features in a Layer 3 Multicast BGP/MPLS VPN SolutionCurrent
February 2012
- RFC 6483Validation of Route Origination Using the Resource Certificate Public Key Infrastructure (PKI) and Route Origin Authorizations (ROAs)Current
February 2012
- RFC 6482A Profile for Route Origin Authorizations (ROAs)Obsoleted
February 2012
- RFC 6480An Infrastructure to Support Secure Internet RoutingCurrent
February 2012
- RFC 6769Simple Virtual Aggregation (S-VA)Current
October 2012
- RFC 6440The EAP Re-authentication Protocol (ERP) Local Domain Name DHCPv6 OptionCurrent
December 2011
- RFC 6382Unique Origin Autonomous System Numbers (ASNs) per Node for Globally Anycasted ServicesCurrent
October 2011
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?