News for hackers. Stuff that matters.
Re:The Status of HTTP/3 by tyingq on Monday January 13, 2020 @02:36PM (#22037767)
Because QIC is UDP based, Chrome first runs a race with TCP just in case you're sitting behind some device that blocks UDP.

I wonder how much bandwidth this will waste globally.

Re:The Status of HTTP/3 by eximius on Monday January 13, 2020 @02:52PM (#22037924)
Most global bandwidth is from video streaming, so most of the data isn't in the first couple packets.

So the number would probably be surprisingly large but also a very small fraction of overall traffic.

Re:The Status of HTTP/3 by xfalcox on Monday January 13, 2020 @02:41PM (#22037814)
I wonder if Happy Eyeballs means that there are 4 races in total for systems under dual-stack...
Re:The Status of HTTP/3 by derefr on Monday January 13, 2020 @07:21PM (#22040373)
Or, a more interesting measure: how much more full will all our NAT connection-state tables be because of this?
Re:The Status of HTTP/3 by microcolonel on Monday January 13, 2020 @04:53PM (#22039124)
> I wonder how much bandwidth this will waste globally.

One or two packets? A handful of bytes per initial connection. The Connection ID mechanism and QPACK are likely to save a lot more data than is lost on initial TCP races.

Re:The Status of HTTP/3 by tyingq on Monday January 13, 2020 @06:21PM (#22039885)
I could have worded it better. I understand it's small in any single area.

Just interesting to contemplate the total effect when you have a userbase like Chrome's.

Re:The Status of HTTP/3 by antpls on Friday January 17, 2020 @03:11AM (#22072807)
Or how many "visitor" statistics will it flaw ?
Re:The Status of HTTP/3 by sebazzz on Monday January 13, 2020 @03:29PM (#22038245)
Isn't that like any device behind NAT?
Re:The Status of HTTP/3 by stephenjudkins on Monday January 13, 2020 @04:50PM (#22039090)
No. Most NATs handle UDP sessions trivially as long as one end of the connection is not behind a NAT itself. Tricks like UDP hole punching are necessary only between two endpoints that are both behind NATs.
Re:The Status of HTTP/3 by iso947 on Monday January 13, 2020 @05:06PM (#22039242)
And assuming the protocol can cope with changing source ports. I’ve seem some udp protocols that only work if the source port is not translated.
Re:The Status of HTTP/3 by big_chungus on Monday January 13, 2020 @04:05PM (#22038568)
Most NAT still allows UDP hole-punching (STUN/TURN/ICE) unless specifically blocked (which a depressing number still do).
Re:The Status of HTTP/3 by tyingq on Monday January 13, 2020 @04:01PM (#22038531)
Yes. NAT, firewalls with admins that don't know what QUIC is, various corporate MITM boxes, etc.