The IESG has received a request from the Operations and Management Area Working Group WG (opsawg) to consider the following document: - 'Guidelines for Characterizing "OAM"' <draft-ietf-opsawg-oam-characterization-14.txt> as Best Current Practice
The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the [email protected] mailing lists by 2026-01-06. Exceptionally, comments may be sent to [email protected] instead. In either case, please retain the beginning of the Subject line to allow automated sorting. 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 abbreviation. 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 recommends not to use these two terms when referring to OAM. This document considers some common qualifiers and modifiers that are prepended, within the context of packet networks, to the OAM abbreviation and lays out guidelines for their use in future IETF work. This document updates RFC6291 by adding to the guidelines for the use of the term "OAM". It does not modify any other part of RFC6291. The file can be obtained via https://datatracker.ietf.org/doc/draft-ietf-opsawg-oam-characterization/ No IPR declarations have been submitted directly on this I-D. The document contains these normative downward references. See RFC 3967 for additional information: rfc7799: Active and Passive Metrics and Methods (with Hybrid Types In-Between) (Informational - Internet Engineering Task Force (IETF) stream) _______________________________________________ OPSAWG mailing list -- [email protected] To unsubscribe send an email to [email protected]
