Re: [quicwg/base-drafts] Remove handshake confirmed test for KeyUpdte (#3212)

Martin Thomson <> Mon, 11 November 2019 01:04 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 133A01200F4 for <>; Sun, 10 Nov 2019 17:04:56 -0800 (PST)
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 4PkghS06YSkO for <>; Sun, 10 Nov 2019 17:04:54 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 569381200E5 for <>; Sun, 10 Nov 2019 17:04:54 -0800 (PST)
Date: Sun, 10 Nov 2019 17:04:53 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1573434293; bh=Fcjsw+lYEfDUkPZ384oJWtE+hTLlOirCfqXEp6HqDSQ=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=hi09ESMTxUc/7PVtZNtwH5SmdRG6AH42AwW7O5y8KmatLSoGgCXU9gol+fNPMk1AT IigG2zw19X/SjaiUiK3JojIye2Lusay6VWOrpoOT1yLsfrh0CYTAug029i9FBmUdZ9 CAp9H+gLHEuA23gPwshMlTIeleUhaPe3FdPdm+3o=
From: Martin Thomson <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/3212/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] Remove handshake confirmed test for KeyUpdte (#3212)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5dc8b3b5717c6_18233f8dc6acd968118742f"; 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: Mon, 11 Nov 2019 01:04:56 -0000

Rather than get bogged down in the minutiae of the requirement and the nature of confirmation, let's just say that this was added when we added the definition of "confirmed".

But an endpoint that can accept 1-RTT in key phase 0 can also receive 1-RTT in key phase 1 equally well.  So there is no functional reason not to allow updates as soon as 1-RTT keys are available.  I think that we should just loosen this entirely.  It might not be a good idea to waste a key phase like that, but it certainly doesn't break anything.

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