Re: [quicwg/base-drafts] Clarify why post-handshake client auth is banned (#3044)

David Schinazi <> Tue, 17 September 2019 08:28 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 5354F12021C for <>; Tue, 17 Sep 2019 01:28:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.596
X-Spam-Status: No, score=-6.596 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] 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 1zVQbjej9191 for <>; Tue, 17 Sep 2019 01:28:17 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id A7D901201EF for <>; Tue, 17 Sep 2019 01:28:17 -0700 (PDT)
Date: Tue, 17 Sep 2019 01:28:16 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1568708896; bh=bSj9FHIxg8xDE+aDrGYnNSk+nq3WJ/brR1t9FAIGFtI=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=NY//jGQNGp9up7NgYil7P10gig/brqeHHLKCx/Mw1VLqjsp3g/WlsfCi/xo3diQyQ 380dPDQc265WEFxbqD7zdReh4On0MfZpgrShR6MKDIOWXoB/NzWLSPQrNpzEyYrxA9 x/387cgQLAUzPRQYNqoSdJozvmTK2/niHoObh+64=
From: David Schinazi <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/pull/3044/review/>
In-Reply-To: <quicwg/base-drafts/pull/>
References: <quicwg/base-drafts/pull/>
Subject: Re: [quicwg/base-drafts] Clarify why post-handshake client auth is banned (#3044)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5d80992061eab_5bfc3facae8cd9689613"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: DavidSchinazi
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: Tue, 17 Sep 2019 08:28:19 -0000

DavidSchinazi commented on this pull request.

> @@ -612,8 +612,13 @@ MAY refuse a connection if the client is unable to authenticate when requested.
 The requirements for client authentication vary based on application protocol
 and deployment.
-A server MUST NOT use post-handshake client authentication (see Section 4.6.2 of
+A server MUST NOT use post-handshake client authentication (as defined in
+Section 4.6.2 of {{!TLS13}}), because the multiplexing offered by QUIC prevents
+clients from correlating the certificate request with the application-level
+event which triggered it (see {{?HTTP2-TLS13=I-D.ietf-httpbis-http2-tls13}}).

I'm honored to have been confused with @davidben.

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