SCTP has 2 flaws:
- Lack of a good incremental adoption given ASIC middlewares
- Lack of real world data (whcoh QUIC had thanks to SPDY thanks to Google and Google Chrome)
Comment on QUIC will soon be as important as TCP
tal@lemmy.today 3 weeks ago
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.
en.wikipedia.org/…/Stream_Control_Transmission_Pr…
Features of SCTP include:
- Delivery of chunks within independent streams eliminates unnecessary head-of-line blocking, as opposed to TCP byte-stream delivery.
kunaltyagi@programming.dev 3 weeks ago
who@feddit.org 3 weeks ago
SCTP has a major obstacle in that the internet is full of middleboxes that will never support it, because it’s not TCP or UDP. QUIC deliberately addresses that by being plain old UDP.