Re: [quicwg/base-drafts] Include handshake anti-deadlock logic in pseudocode (#2281)

Martin Thomson <> Wed, 02 January 2019 00:09 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 55336128766 for <>; Tue, 1 Jan 2019 16:09:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -8.064
X-Spam-Status: No, score=-8.064 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.065, 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 gdZo7PvGERkx for <>; Tue, 1 Jan 2019 16:09:15 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id CDD101200B3 for <>; Tue, 1 Jan 2019 16:09:14 -0800 (PST)
Date: Tue, 01 Jan 2019 16:09:14 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1546387754; bh=t5fhYOw8RNhMYhG1NeVyvAqtqDPzN0EF/A0GREgZOQQ=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=FK5VPqJk6vZeNTTKmkgFVrh9ewmI+GsS7k53aZd9Wgzd05xd6jeT4QhSTo10nlc1i wQw9q+k5wqDgNbtLgEHqm1+FLmruHTewF1OAMJOIPLR1Ocq3Iddl9dxmWX44/q0+ly 3vjFt60o3dzZ5QoZ33UFz4IBjS7m1nnBI5aii5UA=
From: Martin Thomson <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/pull/2281/>
In-Reply-To: <quicwg/base-drafts/pull/>
References: <quicwg/base-drafts/pull/>
Subject: Re: [quicwg/base-drafts] Include handshake anti-deadlock logic in pseudocode (#2281)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c2c012a10eb8_4b113fe2eb6d45bc569634"; 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: Wed, 02 Jan 2019 00:09:16 -0000

Right, I had forgotten.  Handshake ACKs are sent earlier.  Either way, once that starts, the risk of deadlocking is gone.

> Ah, it wasn't clear to me that the client's second, ack-only, Initial packet qualified as "in flight"/"outstanding" here. 

Good point.  The current text says "When crypto packets are sent, the sender MUST set a timer for the crypto timeout period."  And crypto packets don't include ACK-only Initial packets.

That suggests a bigger problem with that text.  I would suggest then that the condition is "Initial packets outstanding and no packet from a higher encryption level ever sent".

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