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

Brian Campbell <> Mon, 30 March 2020 20:37 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id C6DF43A109E for <>; Mon, 30 Mar 2020 13:37:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -0.198
X-Spam-Status: No, score=-0.198 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id v85FPlbwDGlf for <>; Mon, 30 Mar 2020 13:37:40 -0700 (PDT)
Received: from ( [IPv6:2a00:1450:4864:20::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 308C23A10B8 for <>; Mon, 30 Mar 2020 13:37:13 -0700 (PDT)
Received: by with SMTP id n17so19633712lji.8 for <>; Mon, 30 Mar 2020 13:37:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ifHiOdNWRBWq2sLTvujDkjzrbtvDJl+7WMnc/ilvdXk=; b=ZKRIbmWZI9yGCJK1bHxFRFOer+k9dHXXASo7jeiGAePp62UbcuOoOCx5yS/J/SDVu2 iFacMBQfJvzYyWvzuExZnVSqA+J1sGuNRCbA6h2B6ThDXcmayPok2lQ8SbpDDlqltAcB GrXV6p60TmHHN15QgIfxxQA0vdTYnuOQQESoxkUVrjF4Dau1tPMY9pTp8LPx6omLD7zG SCfs7I8cuHbNDUbYovzeQEw1ylhkG1IknYLeXsCzqX4FI/FwUIHE69lgzY8Ly3RkXO2E CXUTrmbfi34JokmxvzEHpLaVYOMB92iCrTQMeF0SbU4crqTUjjg6cbbU9fIjSHhs+wag pxyw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ifHiOdNWRBWq2sLTvujDkjzrbtvDJl+7WMnc/ilvdXk=; b=KFf5FjfJk625nkB3BoAcYwYc+huQb5BK3BNTr8ink8gvsuiPvo1dRDGsKLNXqXbOQe ThxyykSfeXU+1mn8iRZuuEKA13IVIZOn+Sj3UlZid+VeIhz8f41kMMSUFDA/B2riM2Sy 76Jdf6GieIVI6xOa+gb/i/PcUcWK2Ty2TG3uPka96RpD2d8x+sG/WWv8lMybWlMO2nwc qUu7sCa0odiBh1VDjnccyoo425LVdRjCR6T1GfiL9hd28JM7NWcV3qQDEEJ7l8vLHutP bAqJLIa/MJFfvWxix6u5nKYN4m9s1xTyLEQpVQYWH7Uf+vK/zrM4VV6inBN/jWfjpYkl zt3A==
X-Gm-Message-State: AGi0PuZZtH0aPBIPDxjTIDyvxS6AeSeGkEFb/4j1uNaQjrt+M9Th0T6U DJr58+3DKsZJrzyjfSIpvqBSeWBPUg1ZJWvD3kYFaja8YY7xXEMsOKLqJ9kKSJlkG4zJoyseqYQ tE+XYowNHoWrU11U7bfn1YFqV
X-Google-Smtp-Source: APiQypKm+3rbfx93dvtfqfMe/xshEoOpcd1K7+vJd+Xs0iNWp13P45v9qPGiVtqmSfctV8XKk0msYyTU+G2CX1PCVbc=
X-Received: by 2002:a2e:2a03:: with SMTP id q3mr8099728ljq.216.1585600631327; Mon, 30 Mar 2020 13:37:11 -0700 (PDT)
MIME-Version: 1.0
References: <> <> <> <> <> <10060.1585597368@localhost> <>
In-Reply-To: <>
From: Brian Campbell <>
Date: Mon, 30 Mar 2020 14:36:44 -0600
Message-ID: <>
To: "Salz, Rich" <>
Cc: Michael Richardson <>, IETF SecDispatch <>
Content-Type: multipart/alternative; boundary="00000000000062e7f205a2186aba"
Archived-At: <>
Subject: Re: [Secdispatch] Request for secdispatch time slot in Vancouver IETF: Client-Cert HTTP Header
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Security Dispatch <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 30 Mar 2020 20:37:42 -0000

The outcome from SECDISPATCH last week, as I understand it, is that the
next step is to take the work to the HTTPbis WG and see if there's there's
sufficient interest there in taking it up. I plan to get that started soon
(for some value of soon anyway).

There was some discussion on mic and in jabber about spinning up or out a
new WG with a focus on proxy to backend type stuff. But I don't think it
rose to the level of being something actionable coming out of the meeting.

On Mon, Mar 30, 2020 at 1:52 PM Salz, Rich <rsalz=> wrote:

> It belong with HTTP, I don't care where.
> _______________________________________________
> Secdispatch mailing list

_CONFIDENTIALITY NOTICE: This email may contain confidential and privileged 
material for the sole use of the intended recipient(s). Any review, use, 
distribution or disclosure by others is strictly prohibited.  If you have 
received this communication in error, please notify the sender immediately 
by e-mail and delete the message and any file attachments from your 
computer. Thank you._