.
Professional copy editors are paid to do it.
Brian
-Original Message-
From: Brian E Carpenter
Sent: Wednesday, August 9, 2023 22:40
To: Esko Dijk ; Toerless Eckert ;
Michael Richardson
Cc: anima@ietf.org
Subject: Re: [Anima] Esko: Re: Moving draft-ietf-anima-brski-cloud-06 forward
(we
If someone can tell me when the document is ready technically, I
volunteer to do an editing pass for "typos and word omissions", and
anything else that I catch.
Either I will need a txt/pdf version of the document (for which I will
produce a separate text file containing my suggested
Esko Dijk wrote:
> I did check just now - the review comments were addressed. I added a
> few new text issues in the issue tracker #42 to #46
> (https://github.com/anima-wg/brski-cloud/issues) and a request to
> change one more item for #32. This is based on reading the new text
rom: Brian E Carpenter
Sent: Wednesday, August 9, 2023 22:40
To: Esko Dijk ; Toerless Eckert ;
Michael Richardson
Cc: anima@ietf.org
Subject: Re: [Anima] Esko: Re: Moving draft-ietf-anima-brski-cloud-06 forward
> (we can apply the lazy-fix policy and let IESG find them ;-) )
A bit off
(we can apply the lazy-fix policy and let IESG find them ;-) )
A bit off topic, but that is *not* the IESG's job. Unfortunately the IESG often
wastes time on this rather than sending it on to the RFC Editor, whose job it
is. I believe it's better for everybody if this is done by the authors.
I did check just now - the review comments were addressed. I added a few new
text issues in the issue tracker #42 to #46
(https://github.com/anima-wg/brski-cloud/issues) and a request to change one
more item for #32.
This is based on reading the new text and re-reading the old. These are
Esko: I was just checking -07, it looks as if your open review concerns should
have been
successfully answered. Would you mind acknowledging, please ?!
Thanks
Toerless
On Wed, Jul 26, 2023 at 01:58:22PM -0400, Michael Richardson wrote:
>
> Owen Friel \(ofriel\) wrote:
> > Thanks Esko,
