TL;DR. I addressed all your comments (and one additional one). Please see if https://github.com/richsalz/draft-use-tls13/pull/3 is okay; if so, I will merge and publish a new draft.
Thanks for the careful review! > 1. Abstract: can you rephrase "the existence of TLS 1.3 existence" to avoid > double > use of "existence"? > To my (non-native) ear it sounds a bit weird and creates suspects of some > typo. Yes it's weird. Deleting the second instance seems to wrok. > 2. Abstract: s/[RFC9325]/RFC9325 (no square brackets) Done. > 3. Section 1. Add few words mentioning that this document updates RFC 9325 and > then reference Section 5 for details. Done. > 4. Section 3. I believe IPSECME WG can also be mentioned as a WG that is > working on drafts to support hybrid algorithms. Added, s/notably/including/ > 5. Section 3. "WILL NOT" is not an RFC 2119 keyword. Giving that it is in > uppercase, I suspect that readers can be confused. > Perhaps convert it to lowercase and emphasize (like "will never be")? Too bad the IETF claims all use of UPPERCASE :). I hesitate to make claims like "never" so I just made words lowercase. > 6. Section 5. Add some introductory words what RFC9325 is all about. Done. > 7. Section 8. Move [RFC5746] and [RFC7465] to Informative references. Done. > 8. Section 8. Change [TLS13] to reference draft-ietf-tls-rfc8446bis, so that > this > document references the most recent TLS 1.3 RFC when published. Good catch! >9. References: Move [I-D.draft-ietf-tls-deprecate-obsolete-kex] to Informative >references. Done. I also changed a reference to the empty "IANA Considerations" section to the "tls1.2-frozen" draft. (Let it snow, let it snow) _______________________________________________ Uta mailing list -- uta@ietf.org To unsubscribe send an email to uta-le...@ietf.org
