Re: [Secdispatch] Request for secdispatch time slot in Vancouver IETF: Client-Cert HTTP Header

Michael Richardson <mcr+ietf@sandelman.ca> Mon, 30 March 2020 19:42 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: secdispatch@ietfa.amsl.com
Delivered-To: secdispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 323D43A0FC5 for <secdispatch@ietfa.amsl.com>; Mon, 30 Mar 2020 12:42:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level:
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
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 PfuxTDhYT1Hu for <secdispatch@ietfa.amsl.com>; Mon, 30 Mar 2020 12:42:52 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E79AD3A0FDC for <secdispatch@ietf.org>; Mon, 30 Mar 2020 12:42:51 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id E748F3897A; Mon, 30 Mar 2020 15:41:19 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 742B1451; Mon, 30 Mar 2020 15:42:48 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "Salz\, Rich" <rsalz=40akamai.com@dmarc.ietf.org>
cc: IETF SecDispatch <secdispatch@ietf.org>
In-Reply-To: <7FE4FEF8-AA30-44D8-BED8-2578B307FCD4@akamai.com>
References: <CA+k3eCTPisEFnxecjzpNAssSbTuUbUxQ+Hm+m+sjq__2Cpy9pg@mail.gmail.com> <CABcZeBPJO4j0KZk=zjopN2oEWLN-NrYRtKO=GuQ2e5CzH7=iPA@mail.gmail.com> <CA+k3eCQ9hd6rOkxLjS3hACMT3=eC+ojq3DS_XgkcRHRrJc7xdA@mail.gmail.com> <CABcZeBNroHGFdRXJE1X3PxF__SNeH_X3FAjJDVRgCTwGaORDLg@mail.gmail.com> <7FE4FEF8-AA30-44D8-BED8-2578B307FCD4@akamai.com>
X-Mailer: MH-E 8.6; nmh 1.7+dev; GNU Emacs 25.1.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature"
Date: Mon, 30 Mar 2020 15:42:48 -0400
Message-ID: <10060.1585597368@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdispatch/4OJirZ__L3eO1aca5PYOVrrUSJk>
Subject: Re: [Secdispatch] Request for secdispatch time slot in Vancouver IETF: Client-Cert HTTP Header
X-BeenThere: secdispatch@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Security Dispatch <secdispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/secdispatch>, <mailto:secdispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/secdispatch/>
List-Post: <mailto:secdispatch@ietf.org>
List-Help: <mailto:secdispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdispatch>, <mailto:secdispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Mar 2020 19:42:56 -0000

Salz, Rich <rsalz=40akamai.com@dmarc.ietf.org> wrote:
    > I support this document. A standardized place for a TLS-terminating
    > intermediary to present the certificate to an origin is a good thing.
    > It will make CDN customers more portable.

    > Maybe this is a point solution that most of the Internet doesn’t care
    > about.  But measurable portion should care and would benefit.

Do you want a new WG, HTTPBIS, the proposed HTTPSBIS-offshoot, TLS, or ???

I concur with how important it is.
Is there an email chain about the HTTPSBIS offshoot, btw?

--
Michael Richardson <mcr+IETF@sandelman.ca>ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-