Internet Protocols · Cluster
QUIC and HTTP/3
UDP-based transport and stream multiplexing.
- 01 Head-of-Line Blocking and the Transport Gap QUIC Was Built to Fill Why one lost TCP segment stalls every multiplexed request on a connection, and which parts of that coupling a UDP-based transport can actually remove.
- 02 Stream Identifiers and the State Machine That Makes Closing Cheap How the low two bits of a QUIC stream ID encode direction and initiator, why IDs are never reused, and how reset and stop-sending terminate a stream without waiting for a FIN.
- 03 Reading a QUIC Packet: Header Protection, Varints, and Frame Types The byte layout of long and short headers, how header protection hides the packet number, and how the frame type space is partitioned between transport and extension use.
- 04 Connection IDs, Migration, and Validating a New Path Why QUIC addresses packets by connection rather than by four-tuple, how NEW_CONNECTION_ID hands out routable identifiers, and what PATH_CHALLENGE proves about a peer that has moved.
- 05 The QUIC Handshake: TLS 1.3 Without a Record Layer How CRYPTO frames carry the TLS handshake inside the transport, why encryption levels change mid-handshake, and how Retry forces address validation before a certificate is sent.
- 06 Loss Detection Without Retransmitted Packets How QUIC infers loss from packet-number gaps and time thresholds, why frames rather than packets are retransmitted, and how probe timeouts keep a connection from stalling.
- 07 Two-Level Flow Control and Why Credit Must Be Advertised How stream and connection limits interact, why a receiver cannot simply stop reading, and what happens to credit when a stream is reset.
- 08 Congestion Control and Pacing in a Transport That Owns the Socket How a QUIC sender turns acknowledgements into a window, why the window must be spread into a packet schedule, and what changes when the controller is not in the kernel.
- 09 HTTP/3 Framing: Request Streams, Control Streams, and the Settings Exchange How HTTP semantics are carried over QUIC streams, which unidirectional streams the connection requires, and why the control channel is a stream rather than a frame type.
- 10 QPACK and the Cost of a Shared Header Table Why HTTP/3 could not reuse HPACK unchanged, how absolute and relative indices decouple encoding from delivery order, and what a blocked stream actually waits for.