Thomas Pornin <por...@bolet.org> writes: >TLS 1.3 is moving away from the IoT/embedded world, and more toward a Web >world. This is not necessarily _bad_, but it is likely to leave some people >unsatisfied (and, in practice, people clinging to TLS 1.2).
I would go slightly further and say that TLS 1.3 could end up forking TLS in the same way that HTTP/2 has forked HTTP. There's HTTP/2 for web content providers and HTTP 1.1 for the rest of us/them (depending on your point of view). Similarly, there are sizeable groups of users who will take a decade or more to get to TLS 1.3 (they're still years away from 1.2 at the moment), or who may never move to TLS 1.3 because too much of their existing infrastructure is dependent on how TLS 1.x, x = 0...2, works. So as with HTTP/2 we may end up with TLS 1.3 for web content providers and TLS 1.0/1.2 for everything else. Peter. _______________________________________________ TLS mailing list TLS@ietf.org https://www.ietf.org/mailman/listinfo/tls
