RFC 7023: MPLS and Ethernet Operations, Administration, and Maintenance (OAM) Interworking
In plain English — editorial summary, not part of the RFC
This document specifies the mapping of defect states between Ethernet Attachment Circuits (ACs) and associated Ethernet pseudowires (PWs) connected in accordance with the Pseudowire Emulation Edge-to-Edge (PWE3) architecture to realize an end-to-end emulated Ethernet service. It standardizes the behavior of Provider Edges (PEs) with respect to Ethernet PW and AC defects.
Document record
- Document ID
- RFC7023
- Published
- October 2013
- Authors
- D. Mohan; N. Bitar; A. Sajassi; S. DeLord; P. Niger; R. Qiu
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 23
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7024Virtual Hub-and-Spoke in BGP/MPLS VPNsCurrent
October 2013
- RFC 7025Requirements for GMPLS Applications of PCECurrent
September 2013
- RFC 7026Retiring TLVs from the Associated Channel Header of the MPLS Generic Associated ChannelCurrent
September 2013
- RFC 7032LDP Downstream-on-Demand in Seamless MPLSCurrent
October 2013
- RFC 7038Use of OSPF-MDR in Single-Hop Broadcast NetworksCurrent
October 2013
- RFC 7041Extensions to the Virtual Private LAN Service (VPLS) Provider Edge (PE) Model for Provider Backbone BridgingCurrent
November 2013
- RFC 6998A Mechanism to Measure the Routing Metrics along a Point-to-Point Route in a Low-Power and Lossy NetworkCurrent
August 2013
- RFC 6997Reactive Discovery of Point-to-Point Routes in Low-Power and Lossy NetworksCurrent
August 2013
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?