Why doesn't QUIC work well for machine-to-machine traffic ? Is it due to the lack of offloads/optimizations for TCP and machine-to-machine traffic tend to me high volume/high rate ?
QUIC would work okay, but not really have many advantages for machine-to-machine traffic. Machine-to-machine you tend to have long-lived connections over a pretty good network. In this situation TCP already works well and is currently handled better in the kernel. Eventually QUIC will probably be just as good for TCP in this use case, but we're not there yet.
The NAT firewalls do not like P2P UDP traffic.
Majoritoy of the routers lack the smarts to passtrough QUIC correctly, they need to treat it the same as TCP essentially.
I think basically there is currently a lot of overhead and, when you control the network more and everything is more reliable, you can make tcp work better.
Encryption gets you data integrity "for free". If a bit is flipped by faulty hardware, the packet won't decrypt. TCP checksums are not good enough for catching corruption in many cases.
Because any random machine in the same datacenter and network segment might be compromised and do stuff like running ARP spoofing attacks. Cisco alone has had so many vendor-provided backdoors cropping up that I wouldn't trust anything in a data center with Cisco gear.
yello_downunder|7 months ago
jabart|7 months ago
extropy|7 months ago
beeflet|7 months ago
johncolanduoni|7 months ago
dan-robertson|7 months ago
m00x|7 months ago
exabrial|7 months ago
sleepydog|7 months ago
mschuster91|7 months ago
lll-o-lll|7 months ago
20k|7 months ago
switchbak|7 months ago