Re: [quicwg/base-drafts] Describe inputs to TLS more clearly (#4011)

Martin Thomson <> Wed, 02 September 2020 01:01 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 4D8153A08EC for <>; Tue, 1 Sep 2020 18:01:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.694
X-Spam-Status: No, score=-1.694 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, DKIM_VALID_EF=-0.1, HTML_IMAGE_ONLY_28=1.404, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, 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 cgI8AZtRsUR0 for <>; Tue, 1 Sep 2020 18:01:53 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id B65B53A08EB for <>; Tue, 1 Sep 2020 18:01:53 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 104AB7A002C for <>; Tue, 1 Sep 2020 18:01:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1599008513; bh=vECtmizAgx/yrLjGc4VlROyChpHQqpIb1etE87D6vjY=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=WT+QkJkeVky39FYG1LeCQPmrgnWQYq3pX0Q99PtPbD1bspSL4MHVR3mA/Zdw+To8j l+4hZs9BL/2t8wzGD4175i7zNNXcl6kHaoHVkAk4wRT5hjbUBs6teGOLBDu1FluqzN 6iTKRvWlhmB5sQY3wlZS1+U7KcY5n2tSXFfWL7Eo=
Date: Tue, 01 Sep 2020 18:01:52 -0700
From: Martin Thomson <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/pull/4011/review/>
In-Reply-To: <quicwg/base-drafts/pull/>
References: <quicwg/base-drafts/pull/>
Subject: Re: [quicwg/base-drafts] Describe inputs to TLS more clearly (#4011)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5f4eef00bfae4_495c1964513775"; 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 Sep 2020 01:01:55 -0000

@martinthomson commented on this pull request.

> @@ -499,12 +499,24 @@ handshake, new data is requested from TLS after providing received data.
 ### Encryption Level Changes
 As keys at a given encryption level become available to TLS, TLS indicates to
-QUIC that reading or writing keys at that encryption level are available.  While
-generating these keys, an endpoint SHOULD buffer received packets marked as
-protected by the keys being generated, and process them once those keys become
-available.  If the keys are generated asynchronously, an endpoint MAY continue
-responding to the received packets that were processable while waiting for TLS
-to provide these keys.
+QUIC that reading or writing keys at that encryption level are available.
+The events that cause new keys to be available are not asynchronous; they
+always occur immediately after TLS is provided with inputs. Inputs are either
+new handshake bytes or new instructions. The two instructions that this
+document relies upon are the initial signal to start the handshake and - if the
+TLS implementation depends on certificate validation being performed externally
+- an indication that the certificate chain of a peer has been accepted or

Thanks for persisting @kazuho, I think that worked out better.

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