Re: [quicwg/base-drafts] Fixed handshake key deadlock issue (#3093)

Martin Thomson <> Tue, 22 October 2019 02:46 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id A24D4120AEC for <>; Mon, 21 Oct 2019 19:46:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.454
X-Spam-Status: No, score=-6.454 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_20=1.546, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, 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 P-AkkrXXTh5p for <>; Mon, 21 Oct 2019 19:46:48 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 5264112006F for <>; Mon, 21 Oct 2019 19:46:48 -0700 (PDT)
Date: Mon, 21 Oct 2019 19:46:47 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1571712407; bh=LMX/mfX+xFEWZhnqIF9iEum9fsBdv9s4qiw+TUtPCPY=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=v6008cBfXZGe35uChDE2iNPgAaRCwRVhkC1Ni0BGMqFnN3AM+VozBs1h2iFF4V6DU aUQh1rBhdqMCxDFYiXclvhvbTvRxiCCDBe9RvxWQMkcrR5nUNBESqgxzAPShFDImj5 7jfantI4mOSKyly5N13juIpXcoe4CY8g394rx/lk=
From: Martin Thomson <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/pull/3093/>
In-Reply-To: <quicwg/base-drafts/pull/>
References: <quicwg/base-drafts/pull/>
Subject: Re: [quicwg/base-drafts] Fixed handshake key deadlock issue (#3093)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5dae6d979ad28_1993ff3298cd96011673a"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: martinthomson
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: Tue, 22 Oct 2019 02:46:49 -0000

@martinduke, the diagram is correct.  There is no ack-eliciting packet in 0.5-RTT.  The ACK of the 0.5-RTT data is bundled with the other ack-eliciting frames in the packet, that's all.

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