Re: [quicwg/base-drafts] congestion window increase on every ACKed packet could result in bursty sends (#3094)

Tommy Pauly <> Tue, 21 January 2020 18:44 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 67A6C12095B for <>; Tue, 21 Jan 2020 10:44:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.596
X-Spam-Status: No, score=-6.596 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_28=1.404, 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 gBVzG0KuA_qO for <>; Tue, 21 Jan 2020 10:44:15 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 9BD7F12008A for <>; Tue, 21 Jan 2020 10:44:15 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id 77713C602FF for <>; Tue, 21 Jan 2020 10:44:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1579632254; bh=j7WjkaLJ+clJsOwp0rO9P0fWrPV8wa81bvGUscic5Tk=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=HLN+GSM2Rn2Um3SYQuT0tsI9KLWXrqLyzC/5H3hkLkQkd8UyuzhvmeJrfRtDfNXV/ CLqPW1a2xU+mW5M3pRVfXKMzMx7C+/8AXgLH24TaSmKzjIeupKPSauT2yAvUZUxPwK TouJJonDtB1e9I4neqfGN6YbKmhLEgMdKOcBCcG8=
Date: Tue, 21 Jan 2020 10:44:14 -0800
From: Tommy Pauly <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/3094/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] congestion window increase on every ACKed packet could result in bursty sends (#3094)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5e27467e688ed_4abd3fe72c2cd96014417d"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: tfpauly
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, 21 Jan 2020 18:44:17 -0000

@martinthomson Yes, it does largely reduce to "implementations MUST pace" (even if the pacing algorithm isn't very nuanced, in which case you'll perform poorly).

The formalization of the rate, one option for which was specified in #3351, I think is the heart of what should be done here.

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