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

Kazuho Oku <> Wed, 24 April 2019 05:08 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id DDAC11200D7 for <>; Tue, 23 Apr 2019 22:08:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -8.002
X-Spam-Status: No, score=-8.002 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_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-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 5gTWQXs07RDb for <>; Tue, 23 Apr 2019 22:08:55 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 2FA5D12069B for <>; Tue, 23 Apr 2019 22:08:55 -0700 (PDT)
Date: Tue, 23 Apr 2019 22:08:53 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1556082533; bh=Lo68VOfAXxRC8HN4r7hT0sTFvcuujGVEc1uoXOYYtD4=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=oAqmJ8mkfZ9n1Ds6BpIT3G6KxsI+UL+5jpnZhHSLF2g5ZUM0N2dFFGb4Wn9x2ZvtD /7K3iyqXWm4ccuZkT9vZg+1fQkIQpOunLAMkZQ4IZ6N+P6pNsyuWs0s3a0Ig4z3Vb3 8HOe72MI2dTyQXTk90ilDemLu3zzGa057p7R8fns=
From: Kazuho Oku <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/pull/2646/>
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_5cbfef65de50e_94d3fa890ccd9686563f3"; 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 05:08:57 -0000

> Let's do this right and set the value to 0 initially in the transport doc. The "crypto packet" hack is cute, but it's another special case, where this doesn't need a special case, just an initial value.

I think that using max-ack-delay 0 for crypto packets (to be precise, Initial and Hanshake packets)  is _not_ a hack. It's preferable.

The problem of respecting TP.max_ack_delay for Initial and Handshake packets, once receiving TP from the peer, is that loss recovery would kick in `TP.max_ack_delay` seconds later than they can (note: peer is required to send ACK ASAP).

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