RFC 8532: Generic YANG Data Model for the Management of Operations, Administration, and Maintenance (OAM) Protocols That Use Connectionless Communications
In plain English — editorial summary, not part of the RFC
This document presents a base YANG Data model for the management of Operations, Administration, and Maintenance (OAM) protocols that use connectionless communications. The data model is defined using the YANG data modeling language, as specified in RFC 7950. It provides a technology-independent abstraction of key OAM constructs for OAM protocols that use connectionless communication. The base model presented here can be extended to include technology-specific details. There are two key benefits of this approach: First, it leads to uniformity between OAM protocols. Second, it supports both nested OAM workflows (i.e., performing OAM functions at the same level or different levels through a unified interface) as well as interactive OAM workflows (i.e., performing OAM functions at the same level through a unified interface).
Document record
- Document ID
- RFC8532
- Published
- April 2019
- Authors
- D. Kumar; Z. Wang; Q. Wu; R. Rahman; S. Raghavan
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 59
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8533A YANG Data Model for Retrieval Methods for the Management of Operations, Administration, and Maintenance (OAM) Protocols That Use Connectionless CommunicationsCurrent
April 2019
- RFC 8531Generic YANG Data Model for Connection-Oriented Operations, Administration, and Maintenance (OAM) ProtocolsCurrent
April 2019
- RFC 8528YANG Schema MountCurrent
March 2019
- RFC 8527RESTCONF Extensions to Support the Network Management Datastore ArchitectureCurrent
March 2019
- RFC 8526NETCONF Extensions to Support the Network Management Datastore ArchitectureCurrent
March 2019
- RFC 8525YANG LibraryCurrent
March 2019
- RFC 8521Registration Data Access Protocol (RDAP) Object TaggingCurrent
November 2018
- RFC 8543Extensible Provisioning Protocol (EPP) Organization MappingCurrent
March 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?