[TLS] Re: Working Group Last Call for TLS 1.2 is in Feature Freeze

[Yaron Sheffer]

For the second paragraph, I would prefer “no changes and no new extension values”. I don’t have a better idea for the title, so even if I think it’s not 100% precise, I’m good with keeping it.   From: Salz, Rich <rs...@akamai.com> Date: Tuesday, 10 December 2024 at 17:45 To: Yaron Sheffer <yaronf.i...@gmail.com>, Alicja Kario <hka...@redhat.com> Cc: TLS List <tls@ietf.org> Subject: Re: [TLS] Re: Working Group Last Call for TLS 1.2 is in Feature Freeze Does this diff address your concern? What about the title?  As I recall, the draft originally said “TLS 1.2 is frozen” but there were some who wanted it changed.   --- a/draft-ietf-tls-tls12-frozen.md +++ b/draft-ietf-tls-tls12-frozen.md @@ -70,7 +70,7 @@ Use of TLS 1.3 is growing and fixes some known deficiencies in TLS 1.2.  This document specifies that outside of  urgent security fixes, new TLS Exporter Labels, or new  Application-Layer Protocol Negotiation (ALPN) Protocol IDs, -no new features will be approved for TLS 1.2. +no changes will be approved for TLS 1.2.  This prescription does not pertain to DTLS (in any DTLS version); it pertains to  TLS only.   @@ -88,7 +88,7 @@ Both 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 {{iana}}, -no new features will be approved for TLS 1.2. +no changes will be approved for TLS 1.2.  This prescription does not pertain to DTLS (in any DTLS version); it pertains to  TLS only.

_______________________________________________
TLS mailing list -- tls@ietf.org
To unsubscribe send an email to tls-le...@ietf.org