BCP 161

RFC 6291

Guidelines for the Use of the "OAM" Acronym in the IETF, June 2011

File formats:
icon for text file icon for PDF icon for HTML
L. Andersson
H. van Helvoort
R. Bonica
D. Romascanu
S. Mansfield
opsawg (ops)

Cite this RFC: TXT  |  XML  |   BibTeX

DOI:  https://doi.org/10.17487/RFC6291

Discuss this RFC: Send questions or comments to the mailing list opsawg@ietf.org

Other actions: Submit Errata  |  Find IPR Disclosures from the IETF  |  View History of RFC 6291


At first glance, the acronym "OAM" seems to be well-known and well-understood. Looking at the acronym a bit more closely reveals a set of recurring problems that are revisited time and again.

This document provides a definition of the acronym "OAM" (Operations, Administration, and Maintenance) for use in all future IETF documents that refer to OAM. There are other definitions and acronyms that will be discussed while exploring the definition of the constituent parts of the "OAM" term. This memo documents an Internet Best Current Practice.

For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 8729.

Advanced Search