Re: [quicwg/base-drafts] use a HANDSHAKE_DONE frame to drive the handshake to confirmation (#3145)

Kazuho Oku <> Fri, 25 October 2019 06:16 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id C54DB1200F6 for <>; Thu, 24 Oct 2019 23:16:08 -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_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 aQujsmG5hIq2 for <>; Thu, 24 Oct 2019 23:16:07 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 3965512006F for <>; Thu, 24 Oct 2019 23:16:07 -0700 (PDT)
Date: Thu, 24 Oct 2019 23:16:06 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1571984166; bh=n/Bs6CZeOjKX7ABLQtUn6k4u4lG6Y+y/4X1QWkOWbvw=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=hpfep/j7Iv/WGRjS8w83f2R78Jxcz+P2gwTLsWh1G1dpKpicjNOBRwo10F9BOVnSM KkyLf4NXy+u7h2sG2WW67oeX9NnDMOrZ1Fgb03ZDmpsh/hPBoGoFCy8kRXPKESSJ+R ORaVWhjFRAUA8obwun2aw6jXb3a3HiIiQ9rE/ICA=
From: Kazuho Oku <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/pull/3145/>
In-Reply-To: <quicwg/base-drafts/pull/>
References: <quicwg/base-drafts/pull/>
Subject: Re: [quicwg/base-drafts] use a HANDSHAKE_DONE frame to drive the handshake to confirmation (#3145)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5db29326557e7_e2a3fb8754cd96c1094be"; 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: Fri, 25 Oct 2019 06:16:09 -0000

PS. The approach proposed in this PR has the following two properties:
* sending one-way signal from to the client, when the server reaches handshake complete
* use a frame as the conveyor of the signal

It's good to see emerging consensus, but it seems to me that some  are concerned about the second point. Specifically, I see suggestions to use a continuous signal (, or an ACK as a signal too (see

**If** we are in fact unhappy with using a frame, then I might suggest using Key Update as the conveyor of the one-way signal. We can require the server to initiate a Key Update when the handshake is complete and to repeatedly send PINGs until it receives an ACK for one of them.

That'd give us an continuous signal, and also removes the need for an alternative signal. And also the need to have a different frame.

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