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

Michael Richardson <mcr+ietf@sandelman.ca> Mon, 02 March 2020 23:54 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 6167D3A1425 for <secdispatch@ietfa.amsl.com>; Mon, 2 Mar 2020 15:54:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 3mR9B8eUtB2C for <secdispatch@ietfa.amsl.com>; Mon, 2 Mar 2020 15:54:18 -0800 (PST)
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 2FF3A3A092E for <secdispatch@ietf.org>; Mon, 2 Mar 2020 15:54:18 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 4F7ED3897F for <secdispatch@ietf.org>; Mon, 2 Mar 2020 18:53:11 -0500 (EST)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id DBB6EE6 for <secdispatch@ietf.org>; Mon, 2 Mar 2020 18:54:16 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: secdispatch@ietf.org
In-Reply-To: <CA+k3eCTPisEFnxecjzpNAssSbTuUbUxQ+Hm+m+sjq__2Cpy9pg@mail.gmail.com>
References: <CA+k3eCTPisEFnxecjzpNAssSbTuUbUxQ+Hm+m+sjq__2Cpy9pg@mail.gmail.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, 02 Mar 2020 18:54:16 -0500
Message-ID: <13758.1583193256@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdispatch/Phd-138y7T68AufVUCqr2ANB_a4>
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, 02 Mar 2020 23:54:23 -0000

Brian Campbell <bcampbell=40pingidentity.com@dmarc.ietf.org> wrote:
    > Hello SecDispatchers and Chairs thereof,

    > I'd like to request some time on the agenda in Vancouver to present on
    > https://datatracker.ietf.org/doc/draft-bdc-something-something-certificate/
    > in an effort to gauge interest and potentially find an appropriate venue
    > for the work to proceed (or just put it and its ridiculously long title out
    > of its misery).

    > Client-Cert HTTP Header: Conveying Client Certificate Information from
    > TLS Terminating Reverse Proxies to Origin Server Applications

    > Abstract

I have previously read this document.
I was surprised it wasn't already a thing actually.

I can't see why it would any place other than HTTPbis.

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