RFC 6310: Pseudowire (PW) Operations, Administration, and Maintenance (OAM) Message Mapping
In plain English — editorial summary, not part of the RFC
This document specifies the mapping and notification of defect states between a pseudowire (PW) and the Attachment Circuits (ACs) of the end-to-end emulated service. It standardizes the behavior of Provider Edges (PEs) with respect to PW and AC defects. It addresses ATM, Frame Relay, Time Division Multiplexing (TDM), and Synchronous Optical Network / Synchronous Digital Hierarchy (SONET/SDH) PW services, carried over MPLS, MPLS/IP, and Layer 2 Tunneling Protocol version 3/IP (L2TPv3/IP) Packet Switched Networks (PSNs). [STANDARDS-TRACK]
Document record
- Document ID
- RFC6310
- Published
- July 2011
- Authors
- M. Aissaoui; P. Busschbach; L. Martini; M. Morrow; T. Nadeau; Y(J). Stein
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 40
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6428Proactive Connectivity Verification, Continuity Check, and Remote Defect Indication for the MPLS Transport ProfileUpdated
November 2011
- RFC 6435MPLS Transport Profile Lock Instruct and Loopback FunctionsCurrent
November 2011
- RFC 5921A Framework for MPLS in Transport NetworksUpdated
July 2010
- RFC 5885Bidirectional Forwarding Detection (BFD) for the Pseudowire Virtual Circuit Connectivity Verification (VCCV)Updated
June 2010
- RFC 5860Requirements for Operations, Administration, and Maintenance (OAM) in MPLS Transport NetworksCurrent
May 2010
- RFC 7026Retiring TLVs from the Associated Channel Header of the MPLS Generic Associated ChannelCurrent
September 2013
- RFC 5586MPLS Generic Associated ChannelUpdated
June 2009
- RFC 5542Definitions of Textual Conventions for Pseudowire (PW) ManagementCurrent
May 2009
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?