Hi Paul, Rich, and Nimrod,

Paul - Thanks for the reply. We noted your approval on the AUTH48 status page 
for this document: https://www.rfc-editor.org/auth48/rfc9852.

Rich and Nimrod - We have all needed approvals, so we will begin to prepare 
this document for publication at this time. Thank you for your prompt and clear 
responses during AUTH48! This was a very fast and smooth AUTH48.

Best regards,

Rebecca VanRheenen
RFC Production Center



> On Jan 7, 2026, at 12:46 PM, Paul Wouters <[email protected]> wrote:
> 
> 
> On Wed, Jan 7, 2026 at 3:15 PM Rebecca VanRheenen 
> <[email protected]> wrote:
> Hi Rich, Nimrod, and *Paul,
> 
> Rich, we did not make any changes to your entry in the Authors’ Addresses 
> section. Thanks for letting us know your preference about the street address.
> 
> Nimrod, we marked your approval on the AUTH48 status page for this document: 
> https://www.rfc-editor.org/auth48/rfc9852.
> 
> *Paul, as AD, please review the following question and let us know your 
> thoughts. Note that Rich and Nimrod are fine with the current assignment of 
> BCP 195 if you concur. Both authors have approved the document, so once you 
> have addressed this question, we will begin to prepare the document for 
> publication.
> 
> > 1) <!-- [rfced] Authors and *AD - We have marked this document as part of
> > BCP 195 because it updates RFC 9325, which is part of BCP 195. However,
> > please review and let us know if this document should be assigned a new
> > BCP number instead.
> 
> That makes sense. Approved.
> 
> Paul
>   
> > If needed, the complete list of BCPs is available here:
> > https://www.rfc-editor.org/bcps
> > -->
> 
> Best regards,
> 
> Rebecca VanRheenen
> RFC Production Center
> 
> 
> 
> 
> > On Jan 7, 2026, at 11:41 AM, Nimrod Aviram <[email protected]> wrote:
> > 
> > Hi Rebecca,
> > 
> > Looks good to me too.
> > I also approve, thanks a lot for your help!
> > 
> > best wishes,
> > Nimrod
> > 
> > 
> > On Wed, 7 Jan 2026 at 20:29, Rebecca VanRheenen 
> > <[email protected]> wrote:
> > Hi Rich and Nimrod,
> > 
> > Thank you for your replies! We made the change to the Introduction. All of 
> > our questions have now been addressed except for question #1. We are still 
> > waiting for Paul (AD) to comment on that one.
> > 
> > Please review the document carefully to ensure satisfaction as we do not 
> > make changes once it has been published as an RFC. Contact us with any 
> > further updates or with your approval of the document in its current form.  
> > We will await approvals from each author prior to moving forward in the 
> > publication process.
> > 
> > The files are listed below (please refresh).
> > 
> > Updated XML file:
> >   https://www.rfc-editor.org/authors/rfc9852.xml
> > 
> > Updated output files:
> >   https://www.rfc-editor.org/authors/rfc9852.txt
> >   https://www.rfc-editor.org/authors/rfc9852.pdf
> >   https://www.rfc-editor.org/authors/rfc9852.html
> > 
> > Diff files showing all changes made during AUTH48:
> >   https://www.rfc-editor.org/authors/rfc9852-auth48diff.html
> >   https://www.rfc-editor.org/authors/rfc9852-auth48rfcdiff.html (side by 
> > side)
> > 
> > Diff files showing all changes:
> >   https://www.rfc-editor.org/authors/rfc9852-diff.html
> >   https://www.rfc-editor.org/authors/rfc9852-rfcdiff.html (side by side)
> > 
> > For the AUTH48 status of this document, please see:
> >   https://www.rfc-editor.org/auth48/rfc9852
> > 
> > Best regards,
> > 
> > Rebecca VanRheenen
> > RFC Production Center
> > 
> > 
> > 
> > > On Jan 7, 2026, at 5:44 AM, Salz, Rich 
> > > <[email protected]> wrote:
> > > 
> > >     •  Perhaps (remove sentence in first paragraph and update the 
> > > sentence in the third paragraph as follows):
> > >     • This document updates [RFC9325]. It discusses post-quantum
> > >     • cryptography and the security and privacy improvements in TLS 1.3 as
> > >     • the rationale for the update. See Section 5.
> > > 
> > > Yes, please make that change.
> > 
> 

-- 
auth48archive mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to