Hi, Following the discussions in IETF 122, the draft has been significantly revised in order to address the comments from the three main reviewers (Tim Chown, Benoit Claise, Greg Mirsky).
https://datatracker.ietf.org/doc/draft-ietf-opsawg-oam-characterization The main changes compared to version 04: - New co-author: Tal. - The document has been trimmed to focus on the in/out-of-band and alternative terms. - Removed: extended abbreviation text, processing of OAM packets, "compound OAM". - Integrated the active/passive/hybrid terminology into Section 2, making in-packet OAM a special case of hybrid OAM, and removed dedicated-packet OAM. - Removed the term "combined OAM" while leaving the clarifying text. - Some additional clarifications based on comments from the reviewers. We will continue the discussion with the reviewers to see that their comments have been resolved. Any additional comments will be welcome. Thanks, The authors. On Thu, May 15, 2025 at 6:22 PM <[email protected]> wrote: > > Internet-Draft draft-ietf-opsawg-oam-characterization-06.txt is now available. > It is a work item of the Operations and Management Area Working Group (OPSAWG) > WG of the IETF. > > Title: Guidelines for Characterizing "OAM" > Authors: Carlos Pignataro > Adrian Farrel > Tal Mizrahi > Name: draft-ietf-opsawg-oam-characterization-06.txt > Pages: 9 > Dates: 2025-05-15 > > 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 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 RFC 6291 by adding to the guidelines for the > use of the term "OAM". It does not modify any other part of RFC > 6291. > > The IETF datatracker status page for this Internet-Draft is: > https://datatracker.ietf.org/doc/draft-ietf-opsawg-oam-characterization/ > > There is also an HTMLized version available at: > https://datatracker.ietf.org/doc/html/draft-ietf-opsawg-oam-characterization-06 > > A diff from the previous version is available at: > https://author-tools.ietf.org/iddiff?url2=draft-ietf-opsawg-oam-characterization-06 > > Internet-Drafts are also available by rsync at: > rsync.ietf.org::internet-drafts > > > _______________________________________________ > OPSAWG mailing list -- [email protected] > To unsubscribe send an email to [email protected] _______________________________________________ OPSAWG mailing list -- [email protected] To unsubscribe send an email to [email protected]
