Guidelines for the Use of the "OAM" Acronym in the IETF
Metadata
- Publisher
- IETF
- Doc Type
- Best Practice
- Pages
- 9
- 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.
- Publication Date
- 2011-06-01
- Status Note
- Best Current Practice
- DOI
10.17487/RFC6291- Link
- https://doi.org/10.17487/RFC6291
- Author(s)
- Loa AnderssonHuub van HelvoortRon BonicaDan RomascanuScott Mansfield
Latest version of IETF RFC 6291
Document Versions — IETF RFC 6291
-
▶ IETF RFC 6291 (2011-06-01)THIS DOC [ACTIVE] [LATEST VERSION]
Bibliographic Reference(s)
- IEEE.STD802.3.2008 — IEEE802.3 EXTERNAL
- Metro Ethernet Forum, "Service OAM Requirements & Framework - Phase 1", MEF Technical Specification MEF 17, April 2007. EXTERNAL
- Mizrahi, T., Sprecher, N., Bellagamba, E., and Y. Weingarten, "An Overview of Operations, Administration, and Maintenance (OAM) Mechanisms", Work in Progress, March 2011. EXTERNAL
- IETF RFC 1812 [Active*]
- IETF RFC 3429 [Active*]
- IETF RFC 4377 [Active*]
- IETF RFC 4594 [Active*]
- IETF RFC 5586 [Active*]
- T-REC-I.610.1999 — I610 EXTERNAL
- T-REC-M.20.1992 — M.20 EXTERNAL
- T-REC-M.60.1993 — ITU-T-M.60 EXTERNAL
- T-REC-M.3010.2000 — 35 EXTERNAL
- T-REC-Y.1731.2008 — Y.1731 EXTERNAL
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC6291.json
Amended by:
RFC10014 NOT IN REGISTRY
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 6291, Guidelines for the Use of the "OAM" Acronym in the IETF. Available at https://doi.org/10.17487/RFC6291
Snippet:
IETF RFC 6291, Guidelines for the Use of the "OAM" Acronym in the IETF. Available at https://doi.org/10.17487/RFC6291
HTML (ISO 690 compliant)
Preview:
IETF RFC 6291, Guidelines for the Use of the "OAM" Acronym in the IETF. Available at https://doi.org/10.17487/RFC6291
Snippet:
<span class="citation"><cite>IETF RFC 6291</cite>, Guidelines for the Use of the "OAM" Acronym in the IETF. Available at <a href="https://doi.org/10.17487/RFC6291" target="_blank" rel="noopener">https://doi.org/10.17487/RFC6291</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 6291, Guidelines for the Use of the "OAM" Acronym in the IETF
doi: 10.17487/RFC6291
url: https://doi.org/10.17487/RFC6291
doi: 10.17487/RFC6291
url: https://doi.org/10.17487/RFC6291
Snippet:
<li> <cite id="bib-rfc6291">IETF RFC 6291</cite>, Guidelines for the Use of the "OAM" Acronym in the IETF <span class="doi">10.17487/RFC6291</span> </li>
Referenced By
- IETF RFC 6372 [Active*]
- IETF RFC 6428 [Active*]
- IETF RFC 7149 [Active*]
- IETF RFC 7319 [Active*]
- IETF RFC 7325 [Active*]