Re:QUIC File Transfer Service, a CLI and srv for transferrin...
by 01HNNWZ0MV43FF on Sunday July 14, 2024 @05:46PM
(#40963429)
Hm. Wikipedia tells me that a UDP headers has 4 parts: Source port, dest port, length, and checksum.
I suppose with a new protocol you could ditch the length and checksum, which (I don't know much about networking) might be redundant with the IP header and with TLS respectively. That would save you 4 bytes per packet. Nothing huge.
The reason it uses UDP is that the Internet is full of middleboxes built 10 years ago that won't get any firmware updates for another 10 years, and those boxes love TCP and we're lucky if they even pass UDP and ICMP packets. Anything else might just get dropped, and then you have to fall back. Is UDP underneath QUIC really hurting much?
Re:QUIC File Transfer Service, a CLI and srv for transferrin...
by foresto on Sunday July 14, 2024 @09:09PM
(#40964516)
I'm under the impression that UDP is what makes QUIC valuable, by keeping it compatible with the world's existing network hardware and firewall configurations.
If that issue didn't exist, SCTP would surely see a lot more use.
Re:QUIC File Transfer Service, a CLI and srv for transferrin...
by AndrewDucker on Monday July 15, 2024 @04:37AM
(#40966171)
The problem is that most routers don't support anything other than UDP and TCP.
https://www.iana.org/assignments/protocol-numbers/protocol-n...