And given that it’s the next evolution of TCP and a requirement for HTTP/3 it seems like the opposite direction of better QUIC compatibility is likely.
Allowing bypassing it breaks their policy.
If you own your own network then you don’t need to worry about middle boxes interfering with quic or http.
> Companies don’t put these things inline for fun, they do it because they want to block traffic. Allowing bypassing it breaks their policy
Right. And QUIC is a technical response to say "no - you have to control the actual endpoint to enforce the policy, you can only control endpoint access to your network but you have to be a common carrier once you allow that access". A telephone equivalent would be the telephone company discontinued your call because they didn't like what you were saying to the other person on the end of the line (& this is ignoring the fact that QUIC also improves request errors, tail latency and other quantifiable metrics by excluding the kinds of actions that carriers can take on that traffic).
[1] https://docs.google.com/document/d/1RNHkx_VvKWyWg6Lr8SZ-saqs...
[2] https://engineering.fb.com/2020/10/21/networking-traffic/how...
Over bonded networks bitrate are typically under 40mbit, and usually under 20
Of course none of this uses tcp.
When you're using TCP, you can enable MPTCP for free and make your connections faster and more stable. If you're not using TCP, there are alternatives, but then MPTCP is completely irrelevant anyway. You can use QUIC if you want to bypass shitty middleboxes, for instance, as that has similar features but smuggles itself past shitty middleboxes by being marked as UDP (which also makes it more likely to get dropped when the network is congested, unfortunately).
and the other comments on lack of MPTCP support from middleboxes, my guess is even for Apple first party apps, out in the wild, might not see much MPTCP use?
Once a session establishes a route, maintain it. Add logic to prioritize routes by session importance.
Doing it at the packet level in theory gives you the ability to exploit the aggregate bandwidth for any session but as OP noted you still have all the latency problems and middleboxes getting in the way.
QUIC by the way solves the middlebox problem and you could put individual QUIC streams on separate connections to solve the head of line blocking that can appear but I feel like that’s closer to the TCP session thing where you only benefit the use cases that set up multiple streams. HTTP3 where this does happen may not benefit though because bandwidth tends to not be a problem if your rich enough to afford multiple links in the first place (ie more latency sensitive). This could be useful in places if you build a custom end to end solution for video streaming where you put the time-sensitive parts of the video on the lowest latency link and let the rest of the video buffer across all links. It’s a very niche use case though and not worth the effort I think.
Initially I was amazed by MPTCP and wondered why it had so little adoption. As I looked into the papers I slowly figured out why. With different links (WLAN, LAN, LTE) their real world characteristics are too different for efficient aggregation. It is the head of line blocking problem times ten.
It might be fine as a back up link, but there are other problems like the limit to TCP and middelboxes dropping unknowns packets. The challenges outnumber the benefits for consumers and in data centers there are other technologies to aggregate links that operate on a level below TCP.