I read the HTML (and am totally digging the boldness of the section headers, 
etc.) and it looks good. Do you want a more complete street address for me?  If 
so, it’s
      Akamai Technologies
      145 Boadway
      Cambridge, MA 02142

Either way, I approve and thanks for all your fixes!
      
From: Rebecca VanRheenen <[email protected]>
Date: Wednesday, January 7, 2026 at 1:30 PM
To: Salz, Rich <[email protected]>, [email protected] 
<[email protected]>, [email protected] <[email protected]>, 
[email protected] <[email protected]>
Cc: RFC Editor <[email protected]>, [email protected] 
<[email protected]>, [email protected] <[email protected]>, 
[email protected] <[email protected]>
Subject: Re: [AD] AUTH48: RFC-to-be 9852 <draft-ietf-uta-require-tls13-12> for 
your review

!-------------------------------------------------------------------|
  This Message Is From an External Sender
  This message came from outside your organization.
|-------------------------------------------------------------------!

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://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9852.xml__;!!GjvTz_vk!Unf1DRhcqbxzGm7FRwLhNcK8fFRY-eEDcAAHKGaGkpGaGmg98c0LZhoryHGg_XcF3ToV7U8GTQIUYAcWTQoUi2WgCKQ$

Updated output files:
  
https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9852.txt__;!!GjvTz_vk!Unf1DRhcqbxzGm7FRwLhNcK8fFRY-eEDcAAHKGaGkpGaGmg98c0LZhoryHGg_XcF3ToV7U8GTQIUYAcWTQoU-44Vir8$
  
https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9852.pdf__;!!GjvTz_vk!Unf1DRhcqbxzGm7FRwLhNcK8fFRY-eEDcAAHKGaGkpGaGmg98c0LZhoryHGg_XcF3ToV7U8GTQIUYAcWTQoUFeYQ9V8$
  
https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9852.html__;!!GjvTz_vk!Unf1DRhcqbxzGm7FRwLhNcK8fFRY-eEDcAAHKGaGkpGaGmg98c0LZhoryHGg_XcF3ToV7U8GTQIUYAcWTQoUc6LfYv0$

Diff files showing all changes made during AUTH48:
  
https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9852-auth48diff.html__;!!GjvTz_vk!Unf1DRhcqbxzGm7FRwLhNcK8fFRY-eEDcAAHKGaGkpGaGmg98c0LZhoryHGg_XcF3ToV7U8GTQIUYAcWTQoUes41O5g$
  
https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9852-auth48rfcdiff.html__;!!GjvTz_vk!Unf1DRhcqbxzGm7FRwLhNcK8fFRY-eEDcAAHKGaGkpGaGmg98c0LZhoryHGg_XcF3ToV7U8GTQIUYAcWTQoU_FlYlWY$
  (side by side)

Diff files showing all changes:
  
https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9852-diff.html__;!!GjvTz_vk!Unf1DRhcqbxzGm7FRwLhNcK8fFRY-eEDcAAHKGaGkpGaGmg98c0LZhoryHGg_XcF3ToV7U8GTQIUYAcWTQoUNdNn4sU$
  
https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9852-rfcdiff.html__;!!GjvTz_vk!Unf1DRhcqbxzGm7FRwLhNcK8fFRY-eEDcAAHKGaGkpGaGmg98c0LZhoryHGg_XcF3ToV7U8GTQIUYAcWTQoUvZGxz_g$
  (side by side)

For the AUTH48 status of this document, please see:
  
https://urldefense.com/v3/__https://www.rfc-editor.org/auth48/rfc9852__;!!GjvTz_vk!Unf1DRhcqbxzGm7FRwLhNcK8fFRY-eEDcAAHKGaGkpGaGmg98c0LZhoryHGg_XcF3ToV7U8GTQIUYAcWTQoU4TQ068I$

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