Dear all,
Small correction: the responsible AD is Med and not Mahesh.
Regards, Benoit
Dear all,
Now that the dust has settled on the
draft-ietf-opsawg-oam-characterization, it's time to draw the
conclusions.
The (second) WGLC has concluded.
Some feedback was received; thanks Giuseppe, Greg, Thomas, Min,
Justin, Qin, Chongfeng.
This feedback was taken into account and addressed into the latest
draft version 13.
Special thanks to Tal for helping out & progressing this draft since
the first WGLC.
The next steps are:
- shepherd write up
- send this document to Mahesh
Regards, Benoit (as document shepherd)
Subject: WG Last Call: draft-ietf-opsawg-oam-characterization-12 (Ends
2025-09-30)
This message starts a 2-week WG Last Call for this document.
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].
File can be retrieved from:
https://datatracker.ietf.org/doc/draft-ietf-opsawg-oam-characterization/
Please review and indicate your support or objection to proceed with the
publication of this document by replying to this email keeping
[email protected] in copy. Objections should be motivated and
suggestions to
resolve them are highly appreciated.
Authors, and WG participants in general, are reminded again of the
Intellectual Property Rights (IPR) disclosure obligations described
in BCP 79
[1]. Appropriate IPR disclosures required for full conformance with the
provisions of BCP 78 [1] and BCP 79 [2] must be filed, if you are
aware of
any. Sanctions available for application to violators of IETF IPR
Policy can
be found at [3].
Thank you.
[1] https://datatracker.ietf.org/doc/bcp78/
[2] https://datatracker.ietf.org/doc/bcp79/
[3] https://datatracker.ietf.org/doc/rfc6701/
_______________________________________________
OPSAWG mailing list -- [email protected]
To unsubscribe send an email to [email protected]
