Hiya, On 01/10/2019 11:50, Kathleen Moriarty wrote: > On Tue, Oct 1, 2019 at 4:04 AM John Mattsson <john.mattsson= > 40ericsson....@dmarc.ietf.org> wrote: > >> Hi, >> >> I think draft-ietf-tls-oldversions-deprecate needs to update >> draft-ietf-rtcweb-security-arch as well. >> >> draft-ietf-rtcweb-security-arch-20 uses DTLS and even talks about support >> of DTLS 1.0. >> >> "Earlier drafts of this specification required DTLS >> 1.0 with the cipher suite TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA, and >> at the time of this writing some implementations do not support DTLS >> 1.2; endpoints which support only DTLS 1.2 might encounter >> interoperability issues." >> > Good catch.
I'm not sure what that'd mean for our draft (meaning draft-ietf-tls-oldversions-deprecate) as we can't "UPDATE" an I-D. draft-ietf-rtcweb-security-arch-20 is in the RFC editor queue, but is part of a giant cluster IIRC so I suspect nobody will want to touch anything there:-) I think something like this (or maybe exactly this) did come up before and the answer was that it was best to leave it as-is for now. (But I'm open to correction on that and/or maybe things have changed.) Cheers, S.
0x5AB2FAF17B172BEA.asc
Description: application/pgp-keys
signature.asc
Description: OpenPGP digital signature
_______________________________________________ TLS mailing list TLS@ietf.org https://www.ietf.org/mailman/listinfo/tls