Re: [quicwg/base-drafts] ACK generation recommendation (#3304)

Ryan Hamilton <> Tue, 17 December 2019 15:47 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 4177B120856 for <>; Tue, 17 Dec 2019 07:47:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.382
X-Spam-Status: No, score=-6.382 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id OxuFLOiV3II8 for <>; Tue, 17 Dec 2019 07:47:07 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id DFC941209F1 for <>; Tue, 17 Dec 2019 07:47:06 -0800 (PST)
Date: Tue, 17 Dec 2019 07:47:05 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1576597626; bh=0DxB8My8XyHiqrUpXMGWxyTd5+aRjyEx2GC4pmd8l7o=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=TXR4t9af+tL8LlzcwrTDmg9Vp/asx5Mt54DrycGBUEd4g7/FuNg9gLBMrgdyO+WNE 1FidKxdKvC0GcjQN6r3+XYSkFYcRJrnyNptm/9nVy+qfRz59Syv4skoeLeZ1RkncG7 TWrHk+S8SwGVDspNjqNPSQdBSZBYsohIbiQ2k5L8=
From: Ryan Hamilton <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/3304/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] ACK generation recommendation (#3304)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5df8f879f1872_30fc3fd984ecd96415452"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: RyanAtGoogle
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
Archived-At: <>
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 17 Dec 2019 15:47:11 -0000

> It can happen to either endpoint. Consider an HTTP/3 download.

Oh, and of course this can happen in the other direction too. In an HTTP/3 upload the sender is the client which is less likely to have hardware offload so the CPU concerns can be quite accute.

> I think a QUIC sender which sends ACKs of every 2 packets without and further limits will be unable to take full advantage of the network

Err, a QUIC sender obvious isn't the ACK sender. *sigh*. My point remains, though. Senders my not be able to take full advantage of the network if every two packets are ACKd.

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub: