4 ms·
Interesting. Google has been pushing TLS on the world, with its additional 750ms round-trip time to clients on the other side of the world, while taking advant
by rebelde 8y ago
Interesting. Google has been pushing TLS on the world, with its additional 750ms round-trip time to clients on the other side of the world, while taking advantage of their ownership of Chrome to use QUIC to deliver very fast connectivity for their users. That is a sweet competitive advantage that they have over competing services. EDIT: Am I misunderstanding this?
- tialaramex 8y agoIf you are False Start compatible (allow modern ECDHE, etcetera and speak HTTP/2, don't use crappy middleboxes from Cisco, Palo Alto) you get 1RTT with TLS 1.2. If you do TLS 1.3 you always get 1RTT. You can't avoid the one round trip on first connections, you pay that in QUIC too.
- xfs 8y agoThere's 0RTT but once the connection setup cost is amortized by preconnects and multiplexing being 0 or 1 RTT is not that important to justify its engineering ugliness.
- the_clarence 8y agoIsn't QUIC mixing the tcp handshake with the tls handshake? That should make it faster
- londons_explore 8y agoIf you trust people like cloudflare to do CDN termination for you, that time penalty is far lower. There is also a proposal to allow connection sharing for different domains, which would reduce the connection time to 0-rtt even if the user has never visited your site.