RFC 6136: Layer 2 Virtual Private Network (L2VPN) Operations, Administration, and Maintenance (OAM) Requirements and Framework
In plain English — editorial summary, not part of the RFC
This document provides framework and requirements for Layer 2 Virtual Private Network (L2VPN) Operations, Administration, and Maintenance (OAM). The OAM framework is intended to provide OAM layering across L2VPN services, pseudowires (PWs), and Packet Switched Network (PSN) tunnels. This document is intended to identify OAM requirements for L2VPN services, i.e., Virtual Private LAN Service (VPLS), Virtual Private Wire Service (VPWS), and IP-only LAN Service (IPLS). Furthermore, if L2VPN service OAM requirements impose specific requirements on PW OAM and/or PSN OAM, those specific PW and/or PSN OAM requirements are also identified. This document is not an Internet Standards Track specification; it is published for informational purposes.
Document record
- Document ID
- RFC6136
- Published
- March 2011
- Authors
- A. Sajassi; D. Mohan
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 42
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6138LDP IGP Synchronization for Broadcast NetworksCurrent
February 2011
- RFC 6130Mobile Ad Hoc Network (MANET) Neighborhood Discovery Protocol (NHDP)Updated
April 2011
- RFC 6123Inclusion of Manageability Sections in Path Computation Element (PCE) Working Group DraftsCurrent
February 2011
- RFC 6119IPv6 Traffic Engineering in IS-ISCurrent
February 2011
- RFC 6163Framework for GMPLS and Path Computation Element (PCE) Control of Wavelength Switched Optical Networks (WSONs)Current
April 2011
- RFC 6107Procedures for Dynamically Signaled Hierarchical Label Switched PathsCurrent
February 2011
- RFC 6165Extensions to IS-IS for Layer-2 SystemsCurrent
April 2011
- RFC 6166A Registry for PIM Message TypesObsoleted
April 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?