RFC 9062: Framework and Requirements for Ethernet VPN (EVPN) Operations, Administration, and Maintenance (OAM)
In plain English — editorial summary, not part of the RFC
This document specifies the requirements and reference framework for Ethernet VPN (EVPN) Operations, Administration, and Maintenance (OAM). The requirements cover the OAM aspects of EVPN and Provider Backbone Bridge EVPN (PBB-EVPN). The framework defines the layered OAM model encompassing the EVPN service layer, network layer, underlying Packet Switched Network (PSN) transport layer, and link layer but focuses on the service and network layers.
Document record
- Document ID
- RFC9062
- Published
- June 2021
- Authors
- S. Salam; A. Sajassi; S. Aldrin; J. Drake; D. Eastlake 3rd
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 16
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8632A YANG Data Model for Alarm ManagementCurrent
September 2019
- RFC 8560Seamless Integration of Ethernet VPN (EVPN) with Virtual Private LAN Service (VPLS) and Their Provider Backbone Bridge (PBB) EquivalentsCurrent
May 2019
- RFC 7784Transparent Interconnection of Lots of Links (TRILL) Operations, Administration, and Maintenance (OAM) MIBCurrent
February 2016
- RFC 7734Support for Shortest Path Bridging MAC Mode over Ethernet VPN (EVPN)Current
January 2016
- RFC 4207Synchronous Optical Network (SONET)/Synchronous Digital Hierarchy (SDH) Encoding for Link Management Protocol (LMP) Test MessagesUpdated
October 2005
- RFC 9059Path Computation Element Communication Protocol (PCEP) Extensions for Associated Bidirectional Label Switched Paths (LSPs)Updated
June 2021
- RFC 9067A YANG Data Model for Routing PolicyCurrent
October 2021
- RFC 9056Deterministic Networking (DetNet) Data Plane: IP over MPLSCurrent
October 2021
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?