The main value propositions of QUIC for me are in the encryption earlier in the connection and in the reduced infrastructure usage on the server side.
The main value propositions of QUIC for me are in the encryption earlier in the connection and in the reduced infrastructure usage on the server side.
You give no reasoning for it being less and less relevant. It is very relevant to me, where every connection to the US has 300ms RTT.
> that problem is intractable because it's a consequence of the speed of light.
The problem does seem to be quite "tractable"/managable with quic then, which it seems like you agree on.
If a device is dropping the ball on connection tracking, it's almost certainly in your own network.
Your ISP may have carrier-grade NAT. The content provider network probably has stateful load balancers. Those devices need to keep state, but they would need to do so with QUIC and UDP quasi-connections too.
But that's not my point - most cases where things /are/ keeping state need to worry about keeping state on UDP-oriented protocols as well.
However most routers don't do connection tracking at all. That is way too expensive at scale for zero benefits. Take your transit provider, it has tens of terabits of data per second, and those can be handled by a single router. That's a buttload of different stream for a single device, and connection tracking is expensive to do. I can say for experience that connection tracking tables for a single hypervisor with VMs can reach gigabytes. For a single node. Now extrapolate that to a backbone router. It's not happening.
That doesn't help for a phone bouncing between wifi and cellular.