GQUIC Version 46 Packet Format

[Psyspy rambo]

Hello Everyone,

I am unable to dissect the latest quic version using wireshark. It follows the long header format. I tried reading the draft standards (20, 19...), but looks like v46 spec is a bit different. For example, in the initial packet structure, may I please know what fields come between the source connection id and frame type? This doesn't follow the structure given in ietf draft standard 20. I appreciate your help.

Thanks,
psyspy

[Nick Harper]

Version Q046 follows the invariants described in https://tools.ietf.org/html/draft-ietf-quic-invariants-04, but the rest of the header and packet format has some differences. The best resource that I know of for the packet format of Google QUIC versions is the source code: https://quiche.googlesource.com/quiche.git/+/HEAD/quic/core/quic_framer.cc. (There's a wire layout specification doc at https://docs.google.com/document/d/1WJvyZflAO2pq77yOLbp9NsGjC1CHetAXV8I0fQe-B_U/edit, but it's rather out of date.)

From reading through QuicFramer, it looks like the header format for Q046 is as follows (this is based on me reading the code - there may be errors in this):

1 byte public flags

8 byte connection ID (if bit 0x08 in public flags is set)

4 byte version field (if bit 0x01 in public flags is set)

32 byte diversification nonce (sent only by the server; only present if bit 0x04 in public flags is set)

packet number (length determined by bits 0x30 in public flags)

--
You received this message because you are subscribed to the Google Groups "QUIC Prototype Protocol Discussion group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to proto-quic+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/proto-quic/27248eb4-fe5a-4559-a23e-b80f93b414d2%40chromium.org.