Google Git
Sign in
quiche/quiche/1eb9b26af7a84f13ee208803c4704306b2ceec9a
commit
1eb9b26af7a84f13ee208803c4704306b2ceec9a
[log]
author
QUICHE team <quiche-dev@google.com>
Wed Jan 07 01:22:06 2026 -0800
committer
Copybara-Service <copybara-worker@google.com>
Wed Jan 07 01:22:58 2026 -0800
tree
7c28b2fec8833eafa47c714b8f007b6a6fe1fed5
parent
b02b83c63e16e288ff98dc3992fa26dda25da35f [diff]
Fix gap filling ACK logic in QuicReceivedPacketManager.

Updates the logic for sending immediate ACKs when receiving out-of-order packets. Previously, any packet smaller than last_sent_largest_acked_ would trigger an immediate ACK, regardless of the threshold.

This CL ensures compliance with draft-ietf-quic-ack-frequency-13 Section 6.2 by respecting the reordering_threshold: immediate ACKs are now only triggered if the received packet is outside the reordering window (i.e., less than or equal to last_sent_largest_acked_ - reordering_threshold_).

This reduces the number of immediate ACKs sent on networks with packet reordering, improving efficiency.

Handles underflow scenarios: if last_sent_largest_acked_ is smaller than the reordering_threshold_, no immediate ACK is sent, preventing incorrect immediate ACKs when the reordering threshold exceeds the largest acked packet.

Protected by default disabled --quic_reloadable_flag_quic_fix_gap_filling_ack_logic.

PiperOrigin-RevId: 853138944
3 files changed
tree: 7c28b2fec8833eafa47c714b8f007b6a6fe1fed5
  1. build/
  2. depstool/
  3. quiche/
  4. .bazelrc
  5. .bazelversion
  6. BUILD.bazel
  7. CONTRIBUTING.md
  8. LICENSE
  9. MODULE.bazel
  10. MODULE.bazel.lock
  11. README.md
  12. WHITESPACE
README.md

QUICHE

QUICHE stands for QUIC, Http, Etc. It is Google‘s production-ready implementation of QUIC, HTTP/2, HTTP/3, and related protocols and tools. It powers Google’s servers, Chromium, Envoy, and other projects. It is actively developed and maintained.

There are two public QUICHE repositories. Either one may be used by embedders, as they are automatically kept in sync:

To embed QUICHE in your project, platform APIs need to be implemented and build files need to be created. Note that it is on the QUICHE team's roadmap to include default implementation for all platform APIs and to open-source build files. In the meanwhile, take a look at open source embedders like Chromium and Envoy to get started:

To contribute to QUICHE, follow instructions at CONTRIBUTING.md.

QUICHE is only supported on little-endian platforms.

Build and run standalone QUICHE

QUICHE has binaries that can run on Linux platforms.

Follow the instructions to install Bazel.

sudo apt install libicu-dev clang lld
cd <directory that will be the root of your quiche implmentation>
git clone https://github.com/google/quiche.git
cd quiche
CC=clang bazel build -c opt //...
./bazel-bin/quiche/<target_name> <arguments>

There are several targets that can be built and then run. Full usage instructions are available using the --helpfull flag on any binary.

  • quic_packet_printer: from a provided packet, parses and prints out the contents that are accessible without decryption.

Usage: quic_packet_printer server|client <hex dump of packet>

  • crypto_message_printer: dumps the contents of a QUIC crypto handshake message in a human readable format.

Usage: crypto_message_printer_bin <hex of message>

  • quic_client: connects to a host using QUIC and HTTP/3, sends a request to the provided URL, and displays the response.

Usage: quic_client <URL>

  • quic_server: listens forever on --port (default 6121) until halted via ctrl-c.

  • masque_client: tunnels to a URL via an identified proxy (See RFC 9298).

Usage: masque_client [options] <proxy-url> <urls>

  • masque_server: a MASQUE tunnel proxy that defaults to port 9661.

Usage: masque_server

  • web_transport_test_server: a server that clients can connect to via WebTransport.

  • moqt_relay: a relay for the Media Over QUIC transport for publishers and subscribers can connect to.

Usage: moqt_relay