Guidelines for the Use of the "OAM" Acronym in the IETF
RFC 6291, “Guidelines for the Use of the "OAM" Acronym in the IETF”, is a Best Current Practice document published in June 2011 by L. Andersson, H. van Helvoort, R. Bonica, D. Romascanu, S. Mansfield. The canonical text is published by the RFC Editor.
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.
What “Best Current Practice” means
Documents the IETF community's recommended operational or procedural practice rather than a protocol specification.
The canonical text of RFC 6291 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 6290 A Quick Crash Detection Method for the Internet Key Exchange Protocol
- RFC 6292 Requirements for a Working Group Charter Tool
- RFC 6289 A Uniform Resource Name Namespace for CableLabs
- RFC 6293 Requirements for Internet-Draft Tracking by the IETF Community in the Datatracker
- RFC 6288 URN Namespace for the Defence Geospatial Information Working Group
- RFC 6294 Survey of Proposed Use Cases for the IPv6 Flow Label
- RFC 6287 OCRA: OATH Challenge-Response Algorithm
- RFC 6295 RTP Payload Format for MIDI