QUIC works hand-in-hand with HTTP/3’s multiplexed connections, allowing multiple streams of data to reach all the endpoints independently, and hence independent of packet losses involving other streams. In contrast, HTTP/2, which is carried over TCP, can suffer head-of-line-blocking delays if multiple streams are multiplexed on a TCP connection and any of the TCP packets on that connection are delayed or lost.
SCTP was going to do that too. It hasn’t seen much uptake.
https://en.wikipedia.org/wiki/Stream_Control_Transmission_Protocol
Features of SCTP include:
- Delivery of chunks within independent streams eliminates unnecessary head-of-line blocking, as opposed to TCP byte-stream delivery.













I don’t have a YouTube account, and have no interest in getting one. I hid shorts with this browser add-on:
https://github.com/Vulpelo/hide-youtube-shorts