On Dec 30, 2022, at 10:21 AM, John Mattsson <john.mattsson=40ericsson....@dmarc.ietf.org> wrote: > > Hi, > > >This document replaces RFC 7170. > Use the IETF term obsoletes and add that to the header.
Done. > - Use the new RFC 8174 text. Done. > > - I think we are past the time when it is acceptable to publish standards > track based on the obsolete TLS 1.2. NIST is requiring TLS 1.3 support > everywhere by January 2024. This document would be ready for deprecation > before its even is published. The only reasonable thing for a 2023 document > is to do TLS 1.3 only. If TLS 1.2 is supported at all the currently listed > cipher suites needs to be forbidden and replaced with a profile like that in > RFC 9113. I don't think the current document can be published as standard > track in 2023. If draft-ietf-emu-tls-eap-types is published in 2023, then I think it addresses your concerns. I have previously suggested bringing the text about TLS 1.3 from draft-ietf-emu-tls-eap-types into this document, and didn't get much feedback. So I agree, if we're fixing TEAP, it does make sense to bring all of the TEAP issues into this document. It's also important for implementors to write and test the TLS 1.3 key derivations. Alan DeKok. _______________________________________________ Emu mailing list Emu@ietf.org https://www.ietf.org/mailman/listinfo/emu
