IETF Logo Mail Archive

Re: Report on preliminary decision on TLS 1.3 and client auth

Martin Thomson <martin.thomson@gmail.com> Thu, 24 September 2015 03:45 UTC

Return-Path: <ietf-http-wg-request+bounce-httpbisa-archive-bis2juki=lists.ie@listhub.w3.org>
X-Original-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Delivered-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 475181B2C85 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Wed, 23 Sep 2015 20:45:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.012
X-Spam-Level:
X-Spam-Status: No, score=-7.012 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ldsMyHtEwCHt for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Wed, 23 Sep 2015 20:45:27 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 62E211AD2DF for <httpbisa-archive-bis2Juki@lists.ietf.org>; Wed, 23 Sep 2015 20:45:27 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.80) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1ZexQ2-0008BM-4u for ietf-http-wg-dist@listhub.w3.org; Thu, 24 Sep 2015 03:42:02 +0000
Resent-Date: Thu, 24 Sep 2015 03:42:02 +0000
Resent-Message-Id: <E1ZexQ2-0008BM-4u@frink.w3.org>
Received: from lisa.w3.org ([128.30.52.41]) by frink.w3.org with esmtps (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <martin.thomson@gmail.com>) id 1ZexPv-00089u-Rp for ietf-http-wg@listhub.w3.org; Thu, 24 Sep 2015 03:41:55 +0000
Received: from mail-yk0-f178.google.com ([209.85.160.178]) by lisa.w3.org with esmtps (TLS1.2:RSA_ARCFOUR_SHA1:128) (Exim 4.80) (envelope-from <martin.thomson@gmail.com>) id 1ZexPq-0006lz-0d for ietf-http-wg@w3.org; Thu, 24 Sep 2015 03:41:54 +0000
Received: by ykdt18 with SMTP id t18so61932000ykd.3 for <ietf-http-wg@w3.org>; Wed, 23 Sep 2015 20:41:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=uR+d7t/i5nF+nr9wN8G8KxVidn+UZI5NJtpEwArekAg=; b=v11wOH0paiBP/OTZbmHD3aCZt64jZRHic+9gQUVKL/F1DU1GUpMWsqBI6rqMkSakTx 4JLF5b2BeaBnZECms3oYbYciJMQweeN/ZsSIME+e+mDtK67xyBjrDRqmY0TbMndHdKzS WhAVgAsZE6FYzzo23o0U4PbExgfVbDroWiizh1HlsXBgypRm+eYfb12xxhc5tT1EdzyX 4rYzvJHWfdsVcxc4u4QJ/HhQ/dj9Hhgt1GmIPLUm2xAE4qbVNFxrCSNOalI0a4RLsOqa Sy3aXhJvkZBXtQDZne6T4xkoIjvGUxLjy03mVNhKJkB/LzB+xbpHTzqaDDsK584aHTr1 AuFA==
MIME-Version: 1.0
X-Received: by 10.170.110.210 with SMTP id c201mr29368060ykb.1.1443066084186; Wed, 23 Sep 2015 20:41:24 -0700 (PDT)
Received: by 10.129.133.130 with HTTP; Wed, 23 Sep 2015 20:41:24 -0700 (PDT)
In-Reply-To: <5603599F.8090303@treenet.co.nz>
References: <CABkgnnWREq6X+chcvookChGAZGxkJ6Zs_7FGwz7Mbn12XMxewQ@mail.gmail.com> <5603599F.8090303@treenet.co.nz>
Date: Wed, 23 Sep 2015 20:41:24 -0700
Message-ID: <CABkgnnVq9FDeGf_=JF0m0AkgfO1G3DVV2QN_aPrbYnFtfRLFrw@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Amos Jeffries <squid3@treenet.co.nz>
Cc: HTTP Working Group <ietf-http-wg@w3.org>
Content-Type: text/plain; charset="UTF-8"
Received-SPF: pass client-ip=209.85.160.178; envelope-from=martin.thomson@gmail.com; helo=mail-yk0-f178.google.com
X-W3C-Hub-Spam-Status: No, score=-7.9
X-W3C-Hub-Spam-Report: AWL=1.841, BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, W3C_AA=-1, W3C_DB=-1, W3C_IRA=-1, W3C_IRR=-3, W3C_WL=-1
X-W3C-Scan-Sig: lisa.w3.org 1ZexPq-0006lz-0d 28298a2f370244a17cfdb696f16001cd
X-Original-To: ietf-http-wg@w3.org
Subject: Re: Report on preliminary decision on TLS 1.3 and client auth
Archived-At: <http://www.w3.org/mid/CABkgnnVq9FDeGf_=JF0m0AkgfO1G3DVV2QN_aPrbYnFtfRLFrw@mail.gmail.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/30268
X-Loop: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list
List-Id: <ietf-http-wg.w3.org>
List-Help: <http://www.w3.org/Mail/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>

On 23 September 2015 at 19:02, Amos Jeffries <squid3@treenet.co.nz> wrote:
>
> Option 2 risks the same mess if the AUTH frame is defined end-to-end.
> But a per-hop frame would work nicely as long as it is clear to server
> implementers that intermediaries may be the source of the certificate.
> Not some "user".

This would naturally be hop-by-hop, by virtue of extensions being
hop-by-hop and by virtue of the setting that enables it also being
hop-by-hop.

> An option 3 might be to use a SETTINGS instead of dedicated AUTH frame.
> So that the per-hop nature is made extra clear. That would also be more
> backward compatible with older h2 implementations and work in with
> clearing dynamic compression contexts at the same time as authenticating.

SETTINGS wouldn't allow the server to correlate the CertificateRequest
with a specific request/response exchange.

Also, while I think of it, we should probably forbid the use of this
on server-initiated streams (i.e., with server push).  That could
cause problems.

v2.23.0 | Report a Bug | By Email