Peter has said it more colorfully than I have:
> Not necessarily. Since TLS 1.3 has forked TLS into two protocols, 1.0-1.2
> and
1.3 (lets call them TLS family A and TLS family B), there are a large number
of users who will be sticking with the TLS A rather than TLS B family for an
But he is right. At least Amazon, CloudFlare, and Facebook have had
implementations of TLS 1.3 that handed off the connection to "legacy code" if
it was an earlier version. (Of course, I don't know if they still do that.)
To repeat myself from yesterday: "I agree that if you have supported_versions
than you probably also have a 1.3-capable stack. But it is also possible to
have the first without the second." And to be more direct: the draft SHOULD
separate those two cases.
_______________________________________________
TLS mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/tls
