So, the fix you're looking for is
Guidelines for Charactering OED
?
:-)
On 23/10/2024 12:57 BST Joe Clarke (jclarke) <jclarke=40cisco....@dmarc.ietf.org> wrote:Heh. Yeah, I caught that, too. Sometimes the low hanging fruit is on the ground.Joe—PGP Key : https://www.marcuscom.com/pgp.ascOn Oct 23, 2024, at 07:48, tom petch <ie...@btconnect.com> wrote:Guidelines for Charactering "OAM"-------------Not a word I can see in my OED:-)Tom Petch________________________________________From: Joe Clarke (jclarke) <jclarke=40cisco....@dmarc.ietf.org>Sent: 21 October 2024 17:21To: opsawg@ietf.orgSubject: [OPSAWG]WG LAST CALL: Guidelines for Charactering "OAM"This starts a two week WG LC https://datatracker.ietf.org/doc/draft-ietf-opsawg-oam-characterization/. The authors have been polled and there is no known IPR on this work that has been disclosed at this time.Please post comments and thoughts on this document’s readiness to the list. We ultimately want to run publication of this in conjunction with the on-path telemetry document. Thanks to Greg Mirsky who agreed to shepherd this draft.The WG LC will run until November 4.Thanks.Joe_______________________________________________OPSAWG mailing list -- opsawg@ietf.orgTo unsubscribe send an email to opsawg-le...@ietf.org
_______________________________________________ OPSAWG mailing list -- opsawg@ietf.org To unsubscribe send an email to opsawg-le...@ietf.org