3 ms·
> TCP will waste roundtrips on handshakes. And then some extra on MTU discovery. This is especially true when using TLS (which is at least a major use case now
by saghm 2y ago
> TCP will waste roundtrips on handshakes. And then some extra on MTU discovery.
This is especially true when using TLS (which is at least a major use case nowadays if not the default assumption); the TCP handshake has to complete before the TLS handshake can occur, whereas QUIC has protocol-level support for doing TLS negotiation as part of the initial handshake. Having the network protocol and the encryption be composable rather than tightly coupled feels more elegant, it's hard for me to convince myself that being able to save a round trip per connection isn't a more practical benefit in a world where we now expect pretty much everything to be encrypted in transit.
- marcosdumay 2y ago> feels more elegant Yet, it's not. That kind of elegance ends up in application level implementations like STARTTLS and socket data becoming unusable on the middle of a connection while both parties scramble to decide what to throw away and what to interpret. It does really look like the real thing, but it's decoupling things that are very coupled by definition.
- markhahn 2y agomaybe the lesson is that "composable" shouldn't mean "just nested".