Learn / Field guide

QUIC: the transport behind HTTP/3

QUIC runs over UDP port 443 and combines the connection and encryption handshakes into one, so pages start faster. Almost everything is encrypted, including most of QUIC's own headers; only the first handshake packets reveal the server name.

19 QUIC fields, explained

Field names are the ones Wireshark and TShark use, so you can search for them or use them in display filters.

quic.header_form

Whether this packet has a long header (used during the handshake) or a short header (used after).

Why it matters: Long-header packets carry version and connection IDs in the clear; short-header packets reveal almost nothing.

quic.fixed_bit

A bit that is always 1 in QUIC packets, so middleboxes can tell QUIC apart from other UDP traffic.

quic.long.packet_type

The kind of long-header packet: Initial, 0-RTT, Handshake, or Retry.

Why it matters: Initial packets carry the TLS ClientHello and ServerHello, protected with keys anyone can derive.

quic.version

The QUIC version. 0x00000001 is QUIC version 1 (RFC 9000).

Why it matters: A version of 0 is a Version Negotiation packet: the server doesn't speak the client's version.

quic.dcil

The length of the destination connection ID.

quic.dcid

The destination connection ID: identifies the connection to the receiver.

Why it matters: Connection IDs let a QUIC connection survive a change of address, like moving from Wi-Fi to mobile data.

quic.scil

The length of the source connection ID.

quic.scid

The source connection ID: the ID the sender wants the other side to use.

quic.token_length

The length of the address-validation token. Usually 0 on a client's first Initial packet.

quic.token

A token from the server's Retry packet, proving the client's address is real.

quic.length

The length of the rest of the packet: packet number plus encrypted payload.

quic.packet_number

The packet number, which only ever goes up. It is encrypted on the wire.

Why it matters: Unlike TCP, QUIC never reuses a number, so a resent packet gets a new one and timing is unambiguous.

quic.payload

The encrypted frames: handshake data, acknowledgements, and stream data.

quic.frame

A QUIC frame. Several frames can share one packet.

quic.frame_type

The kind of frame: CRYPTO (handshake), ACK, STREAM (data), PADDING, and so on.

quic.short

A short-header packet, used once the handshake is done. Only the connection ID is visible.

quic.remaining_payload

Bytes Wireshark can't decrypt without the session keys.

Why it matters: Browsers can export keys (SSLKEYLOGFILE) to let Wireshark decrypt QUIC and TLS.

quic.connection.number

Wireshark's number for this QUIC connection, like a stream index.

quic.padding_length

Padding that brings the client's first packet up to 1200 bytes, as QUIC requires.

Why it matters: The minimum size stops attackers from using QUIC servers to amplify traffic.