RFC 4665: Service Requirements for Layer 2 Provider-Provisioned Virtual Private Networks
In plain English — editorial summary, not part of the RFC
This document provides requirements for Layer 2 Provider-Provisioned Virtual Private Networks (L2VPNs). It first provides taxonomy and terminology and states generic and general service requirements. It covers point-to-point VPNs, referred to as Virtual Private Wire Service (VPWS), as well as multipoint-to-multipoint VPNs, also known as Virtual Private LAN Service (VPLS). Detailed requirements are expressed from both a customer as well as a service provider perspectives. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4665
- Published
- September 2006
- Authors
- W. Augustyn; Y. Serbest
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 32
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6718Pseudowire RedundancyCurrent
August 2012
- RFC 7152Requirements for Metro Ethernet Forum (MEF) Ethernet-Tree (E-Tree) Support in Layer 2 Virtual Private Network (L2VPN)Current
March 2014
- RFC 4667Layer 2 Virtual Private Network (L2VPN) Extensions for Layer 2 Tunneling Protocol (L2TP)Current
September 2006
- RFC 4026Provider Provisioned Virtual Private Network (VPN) TerminologyCurrent
March 2005
- RFC 5501Requirements for Multicast Support in Virtual Private LAN ServicesCurrent
March 2009
- RFC 7439Gap Analysis for Operating IPv6-Only MPLS NetworksCurrent
January 2015
- RFC 8385Transparent Interconnection of Lots of Links (TRILL) Transparent Transport over MPLSCurrent
June 2018
- RFC 8560Seamless Integration of Ethernet VPN (EVPN) with Virtual Private LAN Service (VPLS) and Their Provider Backbone Bridge (PBB) EquivalentsCurrent
May 2019
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?