I think the draft is confusing to the point of almost being misleading, in particular with its use of the word “feature”. Based on the words “feature freeze” people on this list have interpreted it as merely “the TLS WG will no longer work on TLS 1.2”. But by blocking IANA registrations, this has much broader implications on real-world use of TLS 1.2. This confusion is true for the document’s title, as well as the introduction, quoting: Both [TLS] versions have several extension points, so items like new cryptographic algorithms, new supported groups (formerly "named curves"), etc., can be added without defining a new protocol. This document specifies that outside of urgent security fixes, and the exceptions listed in Section 4, no new features will be approved for TLS 1.2. Most people would read it to mean that no new *features* (e.g. new TLS messages) will be added, but that the “extension points” (e.g. new ciphersuites) continue to be available. Thanks, Yaron On 09/12/2024, 21:01, "Alicja Kario" <hka...@redhat.com> wrote: I think it's ready for publication. On Tuesday, 3 December 2024 22:26:30 CET, Sean Turner wrote: > This is the working group last call for TLS 1.2 is in Feature > Freeze. Please review draft-ietf-tls-tls12-frozen [1] and reply > to this thread indicating if you think it is ready for > publication or not. If you do not think it is ready please > indicate why. This call will end on December 17, 2024. > > Cheers, > spt > -- Regards, Alicja (nee Hubert) Kario Principal Quality Engineer, RHEL Crypto team Web: www.cz.redhat.com Red Hat Czech s.r.o., Purkyňova 115, 612 00, Brno, Czech Republic _______________________________________________ TLS mailing list -- tls@ietf.org To unsubscribe send an email to tls-le...@ietf.org |
_______________________________________________ TLS mailing list -- tls@ietf.org To unsubscribe send an email to tls-le...@ietf.org
