Hi authors,

This is a friendly reminder that we have yet to hear back from some of you 
regarding this document’s readiness for publication.  

Please review the AUTH48 status page 
(https://www.rfc-editor.org/auth48/rfc9853) for further information and the 
previous messages in this thread for pertinent communication.

Thank you,

Rebecca VanRheenen
RFC Production Center



> On Feb 24, 2026, at 11:16 AM, Rebecca VanRheenen 
> <[email protected]> wrote:
> 
> Hi Thomas,
> 
> I updated the sentence in Section 7.2 as you suggest. Thanks for catching 
> that!
> 
> I have also marked your approval on the AUTH48 status page for this document 
> (see https://www.rfc-editor.org/auth48/rfc9853). 
> 
> We will wait for any further updates and/or approval from Hannes and Achim 
> before moving forward in the publication process.
> 
> Best regards,
> 
> Rebecca VanRheenen
> RFC Production Center
> 
> 
>> On Feb 24, 2026, at 7:09 AM, Thomas Fossati <[email protected]> 
>> wrote:
>> 
>> Hi Rebecca,
>> 
>> On Tue, 24 Feb 2026 at 02:12, Rebecca VanRheenen
>> <[email protected]> wrote:
>>> 
>>> Hi Thomas,
>>> 
>>> Thanks for the quick reply! All of our questions have now been addressed. 
>>> We’ll leave the current references to [RFC8446] and [RFC8447] as is.
>>> 
>>> 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.
>> 
>> I have re-read the document and am happy to approve it.
>> 
>> The only nit I fnoud is in §7.2: "[...] when RRC in DTLS 1.2 is used",
>> which sounds slightly odd to my non-native ears.
>> 
>> Wouldn't it be more natural to say "[...] when RRC is used in DTLS 1.2"?
>> 
>> Anyway, not a big deal... I'll defer to your superior understanding of
>> the nuances of the English language :-)
>> 
>> cheers, t
> 

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

Reply via email to