> This email starts the working group last call for "Deprecating Obsolete Key > Exchange Methods in TLS 1.2” I-D, located here:
>. https://datatracker.ietf.org/doc/draft-ietf-tls-deprecate-obsolete-kex Three minor issues and a question. Consider saying once, early.in the document, that this does not address TLS 1.0 and TLS 1.1 as they were already deprecated. Are the appendices normative? I think so. That should be explicitly stated in each appendix. I would shuffle the appendices so that the order is B first (since it contains NEW information not in the registry) and then A C D. The rationale is that it puts all registry changes (mark as "not recommended" in one spot). The question might be more appropriate for the TLS chairs. About sync'ing this with the registry changes draft [1]. That document adds a DISCOURAGED value. Can we put this doc and [1] in the same cluster, so that the "discourage" use (currently in appendix B) gets reflected into the registries right away? [1] https://datatracker.ietf.org/doc/draft-ietf-tls-rfc8447bis/ _______________________________________________ TLS mailing list TLS@ietf.org https://www.ietf.org/mailman/listinfo/tls
