Re: [auth48] [AD] AUTH48: RFC-to-be 9325 <draft-ietf-uta-rfc7525bis-11> for your review

[Thomas Fossati <[e-mail]>]

Hi Karen, all,

I approve publication.

To everyone involved in the production of this document: thank you very much!

Cheers, t

On 22/11/2022, 21:17, "Karen Moore" <[e-mail]> wrote:

Peter and Yaron,

We have noted your approvals on the AUTH48 status page for this document (https://www.rfc-editor.org/auth48/rfc9325).

Thank you for the nice note! Likewise, it has been great working with all of the authors (congrats in advance on the publication of this spec!).

Once we have received approvals from Francesca and Thomas, we will move forward in the publication process.

Best regards,

RFC Editor/kc


> On Nov 22, 2022, at 12:37 PM, Peter Saint-Andre <[e-mail]> wrote:
>
> I approve, too.
>
> Karen, you've been great to work with on this document!
>
> Peter
>
> On 11/22/22 1:26 PM, Yaron Sheffer wrote:
>> Thank you Karen! I approve publication.
>>       Yaron
>> On 22/11/2022, 21:41, "Karen Moore" <[e-mail]> wrote:
>>     Peter and Yaron,
>>     Thanks for your comments.  We have updated our files to reflect the changes outlined in the thread below.
>>     (Please refresh)
>>     The updated XML file is here:
>>      https://www.rfc-editor.org/authors/rfc9325.xml
>>     The updated output files are here:
>>      https://www.rfc-editor.org/authors/rfc9325.txt
>>      https://www.rfc-editor.org/authors/rfc9325.pdf
>>      https://www.rfc-editor.org/authors/rfc9325.html
>>     This diff file shows all changes made during AUTH48:
>>      https://www.rfc-editor.org/authors/rfc9325-auth48diff.html
>>     This diff file shows all changes made to date:
>>      https://www.rfc-editor.org/authors/rfc9325-diff.html
>>     Please contact us with any further updates or with your approval of the document in its current form.  We will await approvals from the AD and each author prior to moving forward in the publication process.
>>     For the AUTH48 status of this document, please see:
>>      https://www.rfc-editor.org/auth48/rfc9325
>>     Thank you,
>>     RFC Editor/kc
>>     > On Nov 22, 2022, at 12:35 AM, Thomas Fossati <[e-mail]> wrote:
>>     >
>>     > Hi all,
>>     >
>>     > +1 for the changes below and on moving the reference tags to RFC numbers where possible.
>>     >
>>     > Modulo that, I approve publication.
>>     >
>>     > Thanks a lot for the great work!
>>     >
>>     > On 21/11/2022, 23:55, "Peter Saint-Andre" <[e-mail]> wrote:
>>     >
>>     > On 11/21/22 4:37 PM, Peter Saint-Andre wrote:
>>     >
>>     > > I'll double-check the files now.
>>     >
>>     > I see only three small fixes...
>>     >
>>     > 3.3.  Compression
>>     >
>>     > OLD
>>     >
>>     >     compression-related attacks.  (Note: this recommendation applies to
>>     >     TLS 1.2 only, because compression has been removed from TLS 1.3.)
>>     >
>>     > NEW
>>     >
>>     >     compression-related attacks.  (This recommendation applies to TLS 1.2
>>     >     only, because compression has been removed from TLS 1.3.)
>>     >
>>     > Acknowledgements
>>     >
>>     > OLD
>>     >
>>     >     The authors gratefully acknowledge the contribution of Ralph Holz,
>>     >     who was a coauthor of RFC 7525, the previous version of this
>>     >     document.
>>     >
>>     > NEW
>>     >
>>     >     The authors gratefully acknowledge the contributions of Ralph Holz,
>>     >     who was a coauthor of RFC 7525, the previous version of the TLS
>>     >     recommendations.
>>     >
>>     > OLD
>>     >
>>     >     See RFC 7525 for additional acknowledgments for the previous version
>>     >     of this document.
>>     >
>>     > NEW
>>     >
>>     >     See RFC 7525 for additional acknowledgments specific to the previous
>>     >     version of the TLS recommendations.
>>     >
>>     > Peter
>>     >
>>     >
>>     > IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
>
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.