On Friday, February 19, 2016 07:47:31 pm Martin Thomson wrote: > This really only helps on the first connection attempt. Browsers > already pre-warm connections to subresource hosts.
The first connect is important, as are new connections after a cache clear (think also, private browsing modes). Providing this capability to TLS 1.3 clients (likely also requiring HTTP/2) would allow for browsers to explicitly have a way to do this, rather than speculatively "pre-warm" connections. Additionally, servers could push a cached config for links on pages if they wanted to. Servers supporting this could effectively chain together to give 0RTT for virtually all normal user connections. Clients would not have to open connections to arbitrary link destinations in order to optimize away this 1RTT. (yes, there's the TCP 1RTT too, but that's a separate issue) Dave _______________________________________________ TLS mailing list [email protected] https://www.ietf.org/mailman/listinfo/tls
