RFC 6246: Virtual Private LAN Service (VPLS) Interoperability with Customer Edge (CE) Bridges
In plain English — editorial summary, not part of the RFC
One of the main motivations behind Virtual Private LAN Service (VPLS) is its ability to provide connectivity not only among customer routers and servers/hosts but also among customer IEEE bridges. VPLS is expected to deliver the same level of service that current enterprise users are accustomed to from their own enterprise bridged networks or their Ethernet Service Providers. When customer edge (CE) devices are IEEE bridges, then there are certain issues and challenges that need to be accounted for in a VPLS network. The majority of these issues have been addressed in the IEEE 802.1ad standard for provider bridges and they can be leveraged for VPLS networks. This document extends the provider edge (PE) model described in RFC 4664 based on IEEE 802.1ad bridge module, and it illustrates a clear demarcation between the IEEE bridge module and IETF LAN emulation module. By doing so, it shows that the majority of interoperability issues with CE bridges can be delegated to the 802.1ad bridge module, thus removing the burden on the IETF LAN emulation module within a VPLS PE. This document is not an Internet Standards Track specification; it is published for informational purposes.
Document record
- Document ID
- RFC6246
- Published
- June 2011
- Authors
- A. Sajassi; F. Brockners; D. Mohan; Y. Serbest
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 20
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6240Synchronous Optical Network/Synchronous Digital Hierarchy (SONET/SDH) Circuit Emulation over Packet (CEP) MIB Using SMIv2Current
May 2011
- RFC 6233IS-IS Registry Extension for PurgesCurrent
May 2011
- RFC 6232Purge Originator Identification TLV for IS-ISUpdated
May 2011
- RFC 6226PIM Group-to-Rendezvous-Point MappingCurrent
May 2011
- RFC 6215MPLS Transport Profile User-to-Network and Network-to-Network InterfacesCurrent
April 2011
- RFC 6213IS-IS BFD-Enabled TLVCurrent
April 2011
- RFC 6206The Trickle AlgorithmCurrent
March 2011
- RFC 6286Autonomous-System-Wide Unique BGP Identifier for BGP-4Current
June 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?