Skip to main content

Guidelines for Charactering "OAM"
draft-pignataro-opsawg-oam-whaaat-question-mark-05

Document Type Replaced Internet-Draft (candidate for opsawg WG)
Expired & archived
Authors Carlos Pignataro , Adrian Farrel
Last updated 2024-05-08
Replaced by draft-ietf-opsawg-oam-characterization
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status Best Current Practice
Formats
Additional resources Mailing list discussion
Stream WG state Call For Adoption By WG Issued
Document shepherd (None)
IESG IESG state Replaced by draft-ietf-opsawg-oam-characterization
Consensus boilerplate Yes
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:

Abstract

As the IETF continues to produce and standardize different Operations, Administration, and Maintenance (OAM) protocols and technologies, various qualifiers and modifiers are prepended to the OAM acronym. While, at first glance, the most used appear to be well understood, the same qualifier may be interpreted differently in different contexts. A case in point is the qualifiers "in-band" and "out-of-band" which have their origins in the radio lexicon and which have been extrapolated into other communication networks. This document considers some common qualifiers and modifiers that are prepended, within the context of packet networks, to the OAM acronym, and lays out guidelines for their use in future IETF work. This document updates RFC 6291 by adding to the guidelines for the use of the term "OAM".

Authors

Carlos Pignataro
Adrian Farrel

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)