Cite this RFC:TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC6624
Discuss this RFC: Send questions or comments to the mailing listiesg@ietf.org
Other actions:Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 6624
Layer 2 Virtual Private Networks (L2VPNs) based on Frame Relay or ATMcircuits 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 Providerinfrastructure for each type and yet another for the Internet and IPVPNs. In addition, L2VPN provisioning was cumbersome. This documentpresents a new approach to the problem of offering L2VPN serviceswhere the L2VPN customer's experience is virtually identical to thatoffered by traditional L2VPNs, but such that a Service Provider canmaintain a single network for L2VPNs, IP VPNs, and the Internet, aswell as a common provisioning methodology for all services.This document is not an Internet Standards Track specification; it ispublished for informational purposes.
For the definition ofStatus,seeRFC 2026.
For the definition ofStream, seeRFC 8729.