How a QUIC client gives itself away before any application data flows: the unencrypted Initial packet, the transport parameters in the TLS-in-QUIC ClientHello, version negotiation, and why server-side detection here is still near-greenfield.
A packet-level tour of the QUIC Initial: long header, version, connection IDs, the salt-derived initial keys, datagram padding, packet coalescing, and what stays observable on the wire for fingerprinting.
How QUIC went from a 2012 Google experiment in Chrome and YouTube to a standardized IETF transport, traced through gQUIC, the TLS 1.3 redesign, HTTP/3, and the May 2021 publication of RFC 9000.
