Client-Cert Header draft

[Brian Campbell <[e-mail]>]

Hello HTTP Working Group,

I've somewhat inadvertently found myself working on this draft
https://datatracker.ietf.org/doc/draft-bdc-something-something-certificate/,
which aspires to define a "Client-Cert" HTTP header field that allows a TLS
terminating reverse proxy to convey information about the client
certificate of a mutually-authenticated TLS connection to an origin server
in a common and predictable manner.

I presented the concept
<https://datatracker.ietf.org/meeting/107/materials/slides-107-secdispatch-client-cert-http-header-00>
at the recent virtual IETF 107 secdispatch meeting
<https://datatracker.ietf.org/meeting/107/materials/minutes-107-secdispatch-00>
and the outcome from that was basically that there seems to be some
interest in pursuing the work and the suggestion that the conversation be
taken to the HTTPbis WG (and also keep TLS WG involved - presumably if the
work progresses). And that's what brings me here. I also hope to get a
little bit of time at one of the upcoming virtual interims to
present/discuss the draft.

Thanks,
Brian

-- 
_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._