OOPS, one more issue: 9. References: Move [I-D.draft-ietf-tls-deprecate-obsolete-kex] to Informative references.
> Hi authors, > > before requesting publication of draft-ietf-uta-require-tls13, I'd like you > to fix some > minor issues. > > 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. > 2. Abstract: s/[RFC9325]/RFC9325 (no square brackets) > 3. Section 1. Add few words mentioning that this document updates RFC 9325 and > then reference Section 5 for details. > 4. Section 3. I believe IPSECME WG can also be mentioned as a WG that is > working on drafts to support hybrid algorithms. > 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")? > 6. Section 5. Add some introductory words what RFC9325 is all about. > 7. Section 8. Move [RFC5746] and [RFC7465] to Informative references. > 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. > > Regards and Merry Christmas, > Valery. > > > > > _______________________________________________ > Uta mailing list -- uta@ietf.org > To unsubscribe send an email to uta-le...@ietf.org _______________________________________________ Uta mailing list -- uta@ietf.org To unsubscribe send an email to uta-le...@ietf.org
