Hi Murray,

We marked your AD approval on the AUTH48 status page for this document (see 
https://www.rfc-editor.org/auth48/rfc9725).

We now need the following: 1) your approval for Alexandre and 2) Sergio’s 
approval. It seems that there may be a chance to wrap up approvals before the 
changeover on Wednesday, but if that isn’t possible, we’ll reach out to Andy as 
the incoming AD.

After receiving these approvals, we’ll ask IANA to make some updates to the 
registries to match the edited document before publishing.

For your convenience, here are the files:

Updated XML file:
https://www.rfc-editor.org/authors/rfc9725.xml

Updated output files:
https://www.rfc-editor.org/authors/rfc9725.txt
https://www.rfc-editor.org/authors/rfc9725.pdf
https://www.rfc-editor.org/authors/rfc9725.html

Diff files showing all changes made during AUTH48:
https://www.rfc-editor.org/authors/rfc9725-auth48diff.html
https://www.rfc-editor.org/authors/rfc9725-auth48rfcdiff.html (side by side)

Diff files showing all changes:
https://www.rfc-editor.org/authors/rfc9725-diff.html
https://www.rfc-editor.org/authors/rfc9725-rfcdiff.html (side by side)
https://www.rfc-editor.org/authors/rfc9725-alt-diff.html (shows changes where 
text is moved or deleted)

Thank you,
RFC Editor/rv



> On Mar 15, 2025, at 7:50 PM, Murray S. Kucherawy <superu...@gmail.com> wrote:
> 
> On Sun, Mar 16, 2025 at 8:24 AM Sean Turner <s...@sn3rd.com> wrote:
> Just so it’s clear you are giving approval both as an AD and for Alexandre?
> 
> My understanding is that I just approved the stuff Rebecca asked me to 
> approve as an AD because they're possibly substantive changes since the IESG 
> approved.  The "approve on behalf of Alexandre" step happens separately; I've 
> said I would do that when asked, but I don't think it's been asked yet.  My 
> answer there is unchanged (I will be happy to do so), but becomes meaningless 
> sometime on Wednesday.
> 
> -MSK

-- 
auth48archive mailing list -- auth48archive@rfc-editor.org
To unsubscribe send an email to auth48archive-le...@rfc-editor.org

Reply via email to