The problem we ran into is the following: We are just publishing the RFCs for the connection IDs for DTLS 1.2 and for DTLS 1.3. For the RRC work we need to define an extension. Using the flags extension makes a lot of sense for TLS 1.3 (to avoid wasting bytes sent over the wire). Should we do something entirely different for DTLS 1.2?
-----Original Message----- From: Sean Turner <s...@sn3rd.com> Sent: Thursday, November 4, 2021 2:27 PM To: Hannes Tschofenig <hannes.tschofe...@arm.com> Cc: TLS List <tls@ietf.org> Subject: Re: [TLS] Flags Extension: why only for TLS 1.3? Hannes, Sorry I forgot to answer this, but John pretty much answered it for me. The prevailing notion that the WG has been under is that extensions defined are for TLS 1.3. We put the following in the charter to make that clear: Changes or additions to older versions of (D)TLS whether via extensions or ciphersuites are discouraged and require significant justification to be taken on as work items. So ... do you have a significant justification? Cheers, spt > On Nov 4, 2021, at 09:11, 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. > > 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 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
