Re: [quicwg/base-drafts] SHOULD NOT include platform delay in ack delay (#2786)

ianswett <> Fri, 14 June 2019 16:14 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 25AE5120441 for <>; Fri, 14 Jun 2019 09:14:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.391
X-Spam-Status: No, score=-6.391 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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, T_DKIMWL_WL_HIGH=-0.01] 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 AipqewugkQ7F for <>; Fri, 14 Jun 2019 09:14:38 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 2D90112035F for <>; Fri, 14 Jun 2019 09:14:38 -0700 (PDT)
Date: Fri, 14 Jun 2019 09:14:36 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1560528876; bh=e1RMw7bNaf3O7ZtoUk/SsD0dnNELXlkvZTXIdhDO2CA=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=rCYhdv6/UsgmGMABuZ41/7KrJSqK5FD9x4rr4MYGPshvNMZUqISNCp5H6EqhBcn07 AfaNBRITTLZthaw0rKrkK1WVNnZdX+M86T5HeuhZfO/437M5BHBQ6OVwh6vaCTdnUy 2eR2UQwLWOaFrkBiaOjuwxFrjzjcPakdoaLehLUQ=
From: ianswett <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/pull/2786/>
In-Reply-To: <quicwg/base-drafts/pull/>
References: <quicwg/base-drafts/pull/>
Subject: Re: [quicwg/base-drafts] SHOULD NOT include platform delay in ack delay (#2786)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5d03c7ec74368_25d73ff52facd960134767"; 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: Fri, 14 Jun 2019 16:14:40 -0000

Our implementation includes TLS and decrypt delay in ack delay.  I think that's the right thing to do, but given it's a relatively fixed cost, I'm not sure it matters that much either way.  Queueing delays of any sort are much more concerning, since you want to include those in the path RTT.

If one was doing async handshakes, then if the delayed ack timer went off before the handshake completed, you should still send an ACK frame and not wait for the handshake to complete.

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