Ask Your Question

Revision history [back]

Wireshark has reasonable support (dissection and decryption) for the QUIC version that is in development by the IETF working group, its status can be tracked at https://github.com/quicwg/base-drafts/wiki/Tools#wireshark

You seem to be looking for Google's version of QUIC which is referred to by Wireshark as "gQUIC" with display filter gquic. It has no RFC since it is a proprietary protocol. Google will eventually replace their version of QUIC with the IETF version, similar to what they did with Google's SPDY protocol which got replaced by HTTP/2. Wireshark's gQUIC support lags behind and is not fully up-to-date. We may eventually tackle it, but right now my priority is implementing HTTP/3 support on top of IETF QUIC in Wireshark. Alexis La Goutte worked on gQUIC in the past, maybe he could make it compatible with newer gQUIC versions.

Some resources about Google's QUIC version:

  • https://github.com/Lekensteyn/chromium-quic - a subset of the QUIC code from Chromium, the opensource project behind Google Chrome. Since the official Chromium code is enormous, I have extracted a subset of it such that its sources and commit history can be easier studied.
  • https://www.chromium.org/quic - The main documentation from the Chromium project on QUIC.
  • Packet header wire format for Google QUIC (Q046)

Wireshark has reasonable support (dissection and decryption) for the QUIC version that is in development by the IETF working group, its status can be tracked at https://github.com/quicwg/base-drafts/wiki/Tools#wireshark

You seem to be looking for Google's version of QUIC which is referred to by Wireshark as "gQUIC" with display filter gquic. It has no RFC since it is a proprietary protocol. Google will eventually replace their version of QUIC with the IETF version, similar to what they did with Google's SPDY protocol which got replaced by HTTP/2. Wireshark's gQUIC support lags behind and is not fully up-to-date. We may eventually tackle it, but right now my priority is implementing HTTP/3 support on top of IETF QUIC in Wireshark. Alexis La Goutte worked on gQUIC in the past, maybe he could make it compatible with newer gQUIC versions.

Some resources about Google's QUIC version:

  • https://github.com/Lekensteyn/chromium-quic https://github.com/Lekensteyn/chromium-quic - a subset of the QUIC code from Chromium, the opensource project behind Google Chrome. Since the official Chromium code is enormous, I have extracted a subset of it such that its sources and commit history can be easier studied.
  • https://www.chromium.org/quic - The main documentation from the Chromium project on QUIC.
  • Packet header wire format for Google QUIC (Q046)

Wireshark has reasonable support (dissection and decryption) for the QUIC version that is in development by the IETF working group, its status can be tracked at https://github.com/quicwg/base-drafts/wiki/Tools#wireshark.

You seem to be looking for Google's version of QUIC which is referred to by Wireshark as "gQUIC" with display filter gquic. It has no RFC since it is a proprietary protocol. Google will eventually replace their version of QUIC with the IETF version, similar to what they did with Google's SPDY protocol which got replaced by HTTP/2. Wireshark's gQUIC support lags behind and is not fully up-to-date. We may eventually tackle it, but right now my priority is implementing HTTP/3 support on top of IETF QUIC in Wireshark. Alexis La Goutte worked on gQUIC in the past, maybe he could make it compatible with newer gQUIC versions.

Some resources about Google's QUIC version: