RFC 4761: Virtual Private LAN Service (VPLS) Using BGP for Auto-Discovery and Signaling
In plain English — editorial summary, not part of the RFC
Virtual Private LAN Service (VPLS), also known as Transparent LAN Service and Virtual Private Switched Network service, is a useful Service Provider offering. The service offers a Layer 2 Virtual Private Network (VPN); however, in the case of VPLS, the customers in the VPN are connected by a multipoint Ethernet LAN, in contrast to the usual Layer 2 VPNs, which are point-to-point in nature. This document describes the functions required to offer VPLS, a mechanism for signaling a VPLS, and rules for forwarding VPLS frames across a packet switched network. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4761
- Published
- January 2007
- Authors
- K. Kompella; Y. Rekhter
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 28
- Also known as
- —
Topics
Referenced by
3 later RFCs formally update or obsolete part of this document.
- RFC 5462Multiprotocol Label Switching (MPLS) Label Stack Entry: "EXP" Field Renamed to "Traffic Class" FieldCurrent
February 2009
- RFC 8395Extensions to BGP-Signaled Pseudowires to Support Flow-Aware Transport LabelsCurrent
June 2018
- RFC 8614Updated Processing of Control Flags for BGP Virtual Private LAN Service (VPLS)Current
June 2019
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4659BGP-MPLS IP Virtual Private Network (VPN) Extension for IPv6 VPNCurrent
September 2006
- RFC 4762Virtual Private LAN Service (VPLS) Using Label Distribution Protocol (LDP) SignalingCurrent
January 2007
- RFC 4760Multiprotocol Extensions for BGP-4Updated
January 2007
- RFC 4781Graceful Restart Mechanism for BGP with MPLSCurrent
January 2007
- RFC 4724Graceful Restart Mechanism for BGPUpdated
January 2007
- RFC 4893BGP Support for Four-octet AS Number SpaceObsoleted
May 2007
- RFC 4576Using a Link State Advertisement (LSA) Options Bit to Prevent Looping in BGP/MPLS IP Virtual Private Networks (VPNs)Current
June 2006
- RFC 5004Avoid BGP Best Path Transitions from One External to AnotherCurrent
September 2007
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?