HTTP/3 and QUIC: the details

Robin Marx's deep dive from curl up 2019.

[pcbona]

Best reference to QUIC out there so far. Am a network engineer and am very interested in how Quic handles maximum segment size, has global synchronisation been handled, how does it handle congestion, how does it slow-start/ramp up, will it be affected by traffic shaping (delaying packets instead of dropping them), how does quic prioritise certain traffic? Hope there is a Part2 where it goes even deper into these topics.

[programmingart]

Small correction for the "Packet Number Spaces" discussion around 11:45 and after: apparently the LitespeedTech implementation (lsquic) also uses a single PN space, so it's not just Microsoft.

[kapsterio]

Very good and comprehensive explanation for QUIC internals, one question about the connection setup still confused me: what do the key for client initial packet comes from? it sounds like QUIC doesn't encrypt the initial packet (just like tls1.3 does), and authenticate the packet by using method like computing a HMAC over the packet. If the key was derived from some value that client chosen and sent over the wire to server, the attacker can also derived that key, so the attacker can modify the packet and recompute the HMAC without being detected, So, what am I missed

[carlossantillana]

Too technical, Please try to make it more relatable. Maybe making some connections to comic book heroes can help! :)

[microcolonel]

And another one on my nope list, I'll just read the RFC when you're done.