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

Martin Thomson <> Thu, 24 October 2019 04:10 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id BA691120114 for <>; Wed, 23 Oct 2019 21:10:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.382
X-Spam-Status: No, score=-6.382 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_24=1.618, 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 yV1GD9mGcT1m for <>; Wed, 23 Oct 2019 21:10:40 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 6BE8212006E for <>; Wed, 23 Oct 2019 21:10:40 -0700 (PDT)
Date: Wed, 23 Oct 2019 21:10:39 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1571890239; bh=Y8mGfIOybw7WCej0p3s9ZcvEvkGGESb6BH7OYhyIWlw=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=w9E0QS9QU7F4pPQnYxJmtZ/Tj3qJc434g4v24J9ByweYP+AA5QbYdrx+QwL/AkxI2 pHCwyGE/NFUNt8BoXOEdWlKfTnS1aIGHeq2rogIcLsCR9j6+1wxlOmVCU958LiIiiz 9CXs2L0+lO35/uJNZ7rl1d+xsFG//WHw+7bW+60o=
From: Martin Thomson <>
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_5db1243fb39b2_45ff3fd3ececd95c30393"; 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: Thu, 24 Oct 2019 04:10:42 -0000

@kazuho, the problem I'm concerned about is asymmetry around this new proposed condition.

This doesn't work because you establish a discard point that is reliably "synchronized" between endpoints.  You require that the key update is initiated, but don't require that the endpoint keeps sending packets until they are acknowledged.  Without that, you can end up in a state where an endpoint can reach the point of key discard too far ahead of its peer.

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