Re: [quicwg/base-drafts] Update ACK generation policy (#3501)

ianswett <> Sun, 22 March 2020 19:53 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id EA2083A087C for <>; Sun, 22 Mar 2020 12:53:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.554
X-Spam-Status: No, score=-1.554 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, DKIM_VALID_EF=-0.1, HTML_IMAGE_ONLY_20=1.546, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, 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 D7U6UKiBVZGu for <>; Sun, 22 Mar 2020 12:53:23 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 927873A0891 for <>; Sun, 22 Mar 2020 12:53:23 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 5BB3DA0B7E for <>; Sun, 22 Mar 2020 12:53:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1584906802; bh=TzTRSmi6+UNg0wbsi36/wnpayqpz66rT5o3hAcyBGBU=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=k+/1uNmlh7pUW9/4yVdzYizGzfKNsyj/05uG0BNxVJsflIsHvghuFuQwQpCHOaohJ Tdz9ZeWgE69zbPeex3RHceFSnWlhIZf6DcecZ2JrxjEHjdemHJqvr2wXBMSvd6drVz Jw96jWvH+mzgTLDiS+MUKHLcyFvsn3zVRzjW5ReU=
Date: Sun, 22 Mar 2020 12:53:22 -0700
From: ianswett <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/pull/3501/review/>
In-Reply-To: <quicwg/base-drafts/pull/>
References: <quicwg/base-drafts/pull/>
Subject: Re: [quicwg/base-drafts] Update ACK generation policy (#3501)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5e77c2324b5a0_31b93fe7856cd96c1196f5"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ianswett
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: Sun, 22 Mar 2020 19:53:25 -0000

ianswett commented on this pull request.

> @@ -3170,11 +3170,21 @@ delayed retransmissions from the peer. For Initial and Handshake packets,
 a max_ack_delay of 0 is used. The sender uses the receiver's `max_ack_delay`
 value in determining timeouts for timer-based retransmission, as detailed in
 Section 5.2.1 of {{QUIC-RECOVERY}}.
+The max_ack_delay needs to be set so that at least several samples can

max_ack_delay is used in the PTO timeout, and there's no guarantee the two peers have a similar view of RTT(in fact, it's pretty much guaranteed they're not quite identical), so an explicit signal is necessary.

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