hi John,

On Thu, Nov 4, 2021 at 1:11 PM John Mattsson <john.mattsson=
40ericsson....@dmarc.ietf.org> wrote:

> TLS 1.2 has been obsolete for over three years. Oxford dictionary defines
> obsolete as "no longer produced or used; out of date." NIST requires
> support of TLS 1.3 everywhere no later than Jan 2024, which at least in
> theory means no negotiation of TLS 1.2.
>
>
>
> I think IETF, TLS WG, and TLS libraries should spend their time on TLS
> 1.3 rather than giving the false idea it is ok to stay on TLS 1.2.
>

Whilst I agree on the general sentiment, let me point out that the specific
extension we wanted to register (RRC) would be DTLS-only.

And while deprecating TLS 1.2 is certainly OK since 8446 has been around
for 3+ years, the deprecation of DTLS 1.2 would seem a tad premature absent
a published RFC for 1.3 (*)

cheers!

(*) This is going to change soon, but it'll take time for implementations
to catch up (**)

(**) IoT is a vastly different space compared to telco and web.  It is very
fragmented with no real incumbents that could orchestrate a quick
switchover.  Also, because of the heterogeneity of platforms there is a
very high number of purpose built stacks.  So we need to be a bit more
patient (***)

(***) Nothing, just checking if you are still following me in this meander
of recursive footnotes ;-)



> John
>
>
>
> *From: *TLS <tls-boun...@ietf.org> on behalf of Hannes Tschofenig <
> hannes.tschofe...@arm.com>
> *Date: *Monday, 25 October 2021 at 19:12
> *To: *IETF TLS <tls@ietf.org>
> *Subject: *[TLS] Flags Extension: why only for TLS 1.3?
>
> Hi all,
>
>
>
> why is the flags extension only defined for TLS 1.3?
>
>
>
> There is nothing in this extension that prevents us from using it also in
> TLS 1.2.
>
>
>
> Could we make it also available to TLS 1.2?
>
>
>
> Ciao
>
> Hannes
>
>
>
> IMPORTANT NOTICE: The contents of this email and any attachments are
> confidential and may also be privileged. If you are not the intended
> recipient, please notify the sender immediately and do not disclose the
> contents to any other person, use it for any purpose, or store or copy the
> information in any medium. Thank you.
> _______________________________________________
> TLS mailing list
> TLS@ietf.org
> https://www.ietf.org/mailman/listinfo/tls
>


-- 
Thomas
_______________________________________________
TLS mailing list
TLS@ietf.org
https://www.ietf.org/mailman/listinfo/tls

Reply via email to