Re: [quicwg/base-drafts] use max_ack_delay = 0 before receving the TPs (#2646)

Kazuho Oku <> Wed, 24 April 2019 03:04 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 69806120318 for <>; Tue, 23 Apr 2019 20:04:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -8
X-Spam-Status: No, score=-8 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_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, 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 hTOLaawOJtkA for <>; Tue, 23 Apr 2019 20:04:26 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id BED221203C3 for <>; Tue, 23 Apr 2019 20:04:25 -0700 (PDT)
Date: Tue, 23 Apr 2019 20:04:25 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1556075065; bh=EQYWd1Xaz//6mZxH7aExKxjEb5RI2IvpWUP3vTHZtWg=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=NUEH9H33P2XX2WtKuhvq1Ct9A42g0eiBtSTaCHYvlt10Hs2I6e7kKTMpP+3borLfE thGClOUVrk3YFOPRB+xnSg+nyqoLoHpwyFc61KknkHMrLByBGsv/lUGNIVH2OnN+1s ghasF//xmsAdu7QdRuPdFRBf+rqEV4yxi+HDjuWo=
From: Kazuho Oku <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/pull/2646/review/>
In-Reply-To: <quicwg/base-drafts/pull/>
References: <quicwg/base-drafts/pull/>
Subject: Re: [quicwg/base-drafts] use max_ack_delay = 0 before receving the TPs (#2646)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5cbfd2399aba_39983ff8476cd96c3720ad"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: kazuho
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, 24 Apr 2019 03:04:30 -0000

kazuho commented on this pull request.

> @@ -1028,9 +1029,9 @@ min_rtt:
 : The maximum amount of time by which the receiver intends to delay
-  acknowledgments, in milliseconds.  The actual ack_delay in a
-  received ACK frame may be larger due to late timers, reordering,
-  or lost ACKs.
+  acknowledgments. The value is initialized to 0, and updated when the peer's
+  transport parameters are received. The actual ACK Delay in a received ACK
+  frame may be larger due to late timers, reordering, or lost ACKs.

How about clarifying tha the value is zero for "crypto packets".

Some reasons:
* endpoints are expected to send ACKs immediately for crypto packets, even after TP.max_ack_delay is known.
* Retransmissions of 0-RTT packets should respect max_ack_delay obtained in the previous connection.

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