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

Gorry Fairhurst <> Wed, 29 January 2020 17:07 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 2489C120884 for <>; Wed, 29 Jan 2020 09:07:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.381
X-Spam-Status: No, score=-6.381 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, URIBL_BLOCKED=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 FSxNCSkbiEEu for <>; Wed, 29 Jan 2020 09:07:31 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 32789120869 for <>; Wed, 29 Jan 2020 09:07:30 -0800 (PST)
Date: Wed, 29 Jan 2020 09:07:29 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1580317649; bh=LVwhnvY3z5oZHuq67cZuPknh8x/6Mdh9KZdh5Pz3Ggk=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=GGiCZDJCA7nyDXtAkcGFkFeSB9MDHnZS9ceJoFsSnNZfZiUUvLCPF266cJrc0EVqM lSz+YDwmtdpPGuRTQPmqLI33tlj4vWtRLsnwwQL/Yn4UKDCzsWxoC2I6pI+PVevzE/ kTUcIJuTjI+x3MYqmvvnG2vdAbl6oV5Nlh6MpLtA=
From: Gorry Fairhurst <>
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_5e31bbd11338_680c3f87730cd96c13062e"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: gorryfair
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: Wed, 29 Jan 2020 17:07:33 -0000

To me the problem is in two parts ... The first part is "what is the default?" - I still think we shouldn't be designing a QUIC default with significantly worse performance than TCP - simply because TCP can take advantage of an in-network device to Thin ACKs - we should think carefully about setting an appropriate default. To avoid a long "issue" we wrote a draft on this and can present results if there is interest, with a proposal to change the default in the spec:

draft-iyengar-quic-delayed-ack provides opportunities to tune the ACK policy for a server and CC algorithm.  I don't see the two drafts in competition. Both could proceed?

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