Hi Megan, I’m sorry, I should not have sent you 9622. Indeed there were no changes there.
Cheers, Michael Sent from my phone > Am 20.12.2024 um 10:48 schrieb Megan Ferguson <mfergu...@amsl.com>: > > Hi Michael, > > Thanks for the quick turnaround! > > We have adopted these versions and reposted (see below). > > Note that we did not see any changes to RFC-to-be 9622 when creating a diff > with our last version to the one you just sent. If this is in error, please > let us know. We will await your confirmation of this fact prior to marking > you as “Approved” for RFC-to-be 9622. > > It looks like everyone has approved at some point along the way except > Philipp and Anna. *We will assume those prior approvals stand unless we hear > otherwise at this time.* Once we have approvals from each party listed at > the AUTH48 status page, we will be ready to move this document set forward in > the publication process. > > The AUTH48 status page for the entire cluster is viewable here: > https://www.rfc-editor.org/auth48/C508 > > Each document’s updated files and diffs are available as listed below: > > The files have been posted here (please refresh): > https://www.rfc-editor.org/authors/rfc9621.txt > https://www.rfc-editor.org/authors/rfc9621.pdf > https://www.rfc-editor.org/authors/rfc9621.html > https://www.rfc-editor.org/authors/rfc9621.xml > > The relevant diff files have been posted here (please refresh): > https://www.rfc-editor.org/authors/rfc9621-diff.html (comprehensive diff) > https://www.rfc-editor.org/authors/rfc9621-auth48diff.html (AUTH48 changes > only) > https://www.rfc-editor.org/authors/rfc9621-lastdiff.html (last to current > version only) > https://www.rfc-editor.org/authors/rfc9621-lastrfcdiff.html (ditto but > rfcdiff) > > The following diff contains the capping changes from the last two rounds > together: > https://www.rfc-editor.org/authors/rfc9621caps-diff.html > > —— > > The files have been posted here (please refresh): > https://www.rfc-editor.org/authors/rfc9622.txt > https://www.rfc-editor.org/authors/rfc9622.pdf > https://www.rfc-editor.org/authors/rfc9622.html > https://www.rfc-editor.org/authors/rfc9622.xml > > The relevant diff files have been posted here (please refresh): > https://www.rfc-editor.org/authors/rfc9622-diff.html (comprehensive diff) > https://www.rfc-editor.org/authors/rfc9622-auth48diff.html (AUTH48 changes > only) > https://www.rfc-editor.org/authors/rfc9622-lastdiff.html (last to current > version only) > https://www.rfc-editor.org/authors/rfc9622-lastrfcdiff.html (ditto but > rfcdiff) > > > —— > > The files have been posted here (please refresh): > https://www.rfc-editor.org/authors/rfc9623.txt > https://www.rfc-editor.org/authors/rfc9623.pdf > https://www.rfc-editor.org/authors/rfc9623.html > https://www.rfc-editor.org/authors/rfc9623.xml > > The relevant diff files have been posted here (please refresh): > https://www.rfc-editor.org/authors/rfc9623-diff.html (comprehensive diff) > https://www.rfc-editor.org/authors/rfc9623-auth48diff.html (AUTH48 changes > only) > https://www.rfc-editor.org/authors/rfc9623-lastdiff.html (last to current > version only) > https://www.rfc-editor.org/authors/rfc9623-lastrfcdiff.html (ditto but > rfcdiff) > > The following diff contains the capping changes from the last two rounds > together: > https://www.rfc-editor.org/authors/rfc9623caps-diff.html > > Please review carefully and let us know if any further changes are necessary. > > Thank you. > > RFC Editor/mf > > >> On Dec 19, 2024, at 8:51 PM, Michael Welzl <mich...@ifi.uio.no> wrote: >> >> Hi ! >> >> Here come the new versions! >> >> Once these changes are incorporated, I approve publication wherever it’s >> missing (as a co-author: RFCs 9622 and 9623). >> >> Cheers, >> Michael >> >> >>>> On Dec 20, 2024, at 12:00 AM, Megan Ferguson <mfergu...@amsl.com> wrote: >>> >>> Hi Michael, >>> >>>> I will apply all of these changes to the XML files (the latest version you >>>> sent) and send them back to you. >>> >>> Excellent. We will await the files updated with all of the changes before >>> taking any action on our end. >>> >>> As to the get-together: thanks for the invite! You will have to reach out >>> to whoever ends up at the RFC Editor desk at IETF if you would like help >>> celebrating this accomplishment :). We were happy to do our part and very >>> much appreciate your time and attention in getting this cluster ready for >>> publication (no easy feat on Michael’s part)! >>> >>> RFC Editor/mf >> <rfc9621-NEW.xml><rfc9622-NEW.xml><rfc9623-NEW.xml> > -- auth48archive mailing list -- auth48archive@rfc-editor.org To unsubscribe send an email to auth48archive-le...@rfc-editor.org
