database logo graphic

BCP 161

RFC 6291

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

Canonical URL:
http://www.rfc-editor.org/rfc/rfc6291.txt
This document is also available in this non-normative format: PDF.
Status:
BEST CURRENT PRACTICE
Authors:
L. Andersson
H. van Helvoort
R. Bonica
D. Romascanu
S. Mansfield
Stream:
IETF
Source:
opsawg (ops)

Cite this RFC: TXT  |  XML

Other actions: Find Errata (if any)  |  Submit Errata  |  Find IPR Disclosures from the IETF


Abstract

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 4844.


Go to the RFC Editor Homepage.