<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-opsawg-oam-characterization" target="https://datatracker.ietf.org/doc/html/draft-ietf-opsawg-oam-characterization-16">
   <front>
      <title>Guidelines for Characterizing &quot;OAM&quot;</title>
      <author initials="C." surname="Pignataro" fullname="Carlos Pignataro">
         <organization>Blue Fern
      Consulting</organization>
      </author>
      <author initials="A." surname="Farrel" fullname="Adrian Farrel">
         <organization>Old Dog Consulting</organization>
      </author>
      <author initials="T." surname="Mizrahi" fullname="Tal Mizrahi">
         <organization>Huawei</organization>
      </author>
      <date month="January" day="26" year="2026" />
      <abstract>
	 <t>   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 &quot;in-band&quot; and
   &quot;out-of-band&quot; 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 IETF documents.

   This document updates RFC 6291 by adding to the guidelines for the
   use of the term &quot;OAM&quot; with qualifiers.  It does not modify any other
   part of RFC 6291.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-opsawg-oam-characterization-16" />
   
</reference>
