Authors and contributors, please respond on-list as to whether or not you are
aware of any IPR that pertains to this work.
Please state either:
"No, I'm not aware of any IPR that applies to this draft"
or
"Yes, I'm aware of IPR that applies to this draft"
If you are aware of IPR, indicate
Hello, Opsawg. The last round of comments on this draft have been
discussed/resolved, and we'd like to kick off a three-week WG LC for
this work. Please provide any and all feedback on list before the end
of the day May 13, 2022.
Authors, if you have suggestions for a good shepherd for this
Hi,
I'm the document shepherd for this document as it moves beyond the WG
for requested publication as an RFC.
I reviewed the draft at -03 during WG last call, so my comments here
are basically editorial with only a few small questions.
If the authors could produce a new revision, I will start
From: Jean Quilbeuf
Sent: 22 April 2022 14:14
> -Original Message-
> From: tom petch [mailto:ie...@btconnect.com]
> Sent: Thursday 21 April 2022 17:04
> To: Jean Quilbeuf ; Joe Clarke (jclarke)
> ; mohamed.boucad...@orange.com;
> Benoit Claise ; opsawg@ietf.org
> Subject: Re: [OPSAWG]
> -Original Message-
> From: tom petch [mailto:ie...@btconnect.com]
> Sent: Thursday 21 April 2022 17:04
> To: Jean Quilbeuf ; Joe Clarke (jclarke)
> ; mohamed.boucad...@orange.com;
> Benoit Claise ; opsawg@ietf.org
> Subject: Re: [OPSAWG] Comments on draft-ietf-opsawg-service-assurance-
