metasystema.org
UpdatedBEST CURRENT PRACTICEIETF streamBCP161

RFC 6291: Guidelines for the Use of the "OAM" Acronym in the IETF

Still current, but amended. Parts of this document are changed or extended by RFC 10014. Read both.

In plain English — editorial summary, not part of the RFC

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.

Document record

Document ID
RFC6291
Published
June 2011
Authors
L. Andersson; H. van Helvoort; R. Bonica; D. Romascanu; S. Mansfield
Status
BEST CURRENT PRACTICE
Stream
IETF
Area
ops
Pages
9
Also known as
BCP161
Updated by:
RFC 10014

Referenced by

One later RFC formally updates or obsoletes part of this document.

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

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?

canonical URL: /rfc/6291-guidelines-for-the-use-of-the-oam-acronym-in-the-ietf