Re: [quicwg/base-drafts] use key update for confirming the handshake (#3141)

Kazuho Oku <> Thu, 24 October 2019 03:46 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id B2276120219 for <>; Wed, 23 Oct 2019 20:46:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.595
X-Spam-Status: No, score=-6.595 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_28=1.404, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 nntiHusAH68B for <>; Wed, 23 Oct 2019 20:45:59 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id C2039120152 for <>; Wed, 23 Oct 2019 20:45:59 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id CFEAC5203B2 for <>; Wed, 23 Oct 2019 20:45:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1571888757; bh=ohqbW2njE1QYgwOVRSxbIpkwFYDH5vqpIPIGfoNngho=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=aGt8HSNneZKh/kx7IJa23i3SSaORrExiT0ao9oon0G2LgzCx+4TZjne8vhaTYvKqz thHVjmMb6V+GcaXs9aSkz89uP8rxTHtfWzOZiJG1fIsuLOgPMayR8WSDM/38e9dtix WcQU4UdQdLhmj+OO/oJmU8dX1OnzvnGrPp8RH62o=
Date: Wed, 23 Oct 2019 20:45:57 -0700
From: Kazuho Oku <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/pull/3141/>
In-Reply-To: <quicwg/base-drafts/pull/>
References: <quicwg/base-drafts/pull/>
Subject: Re: [quicwg/base-drafts] use key update for confirming the handshake (#3141)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5db11e75befbf_7f163f9b470cd95c703db"; 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: Thu, 24 Oct 2019 03:46:02 -0000

@martinthomson I agree with the observation. However, I do not think that's a problem.

Current spec does not mandate endpoints to reach handshake confirmation. It is something an endpoint might do. Quoting from [section 4.10.2]( _endpoints that do not have reason to send immediately after completing the handshake MAY send ack-eliciting frames, such as PING, which will cause the handshake to be confirmed when they are acknowledged._

This PR retains that property. We can change the property, but I do not think that there is a need to.

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