<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.hardt-httpbis-signature-key" target="https://datatracker.ietf.org/doc/html/draft-hardt-httpbis-signature-key-07">
   <front>
      <title>HTTP Signature Keys</title>
      <author initials="D." surname="Hardt" fullname="Dick Hardt">
         <organization>Hellō</organization>
      </author>
      <author initials="T." surname="Meunier" fullname="Thibault Meunier">
         <organization>Cloudflare</organization>
      </author>
      <date month="July" day="4" year="2026" />
      <abstract>
	 <t>   This document defines two HTTP header fields and one Accept-Signature
   parameter for use with HTTP Message Signatures as defined in RFC
   9421.  The Signature-Key request header distributes public keys used
   to verify signatures, with six initial key distribution schemes:
   pseudonymous inline keys (hwk), self-issued key delegation via JWK
   Thumbprint JWTs (jkt-jwt), identified signers with JWKS URI discovery
   (jwks_uri), JWT-based delegation (jwt), self-issued JWTs (self-jwt),
   and X.509 certificate chains (x509).  The sigkey parameter extends
   Accept-Signature (RFC 9421 Section 5) to indicate the type of
   Signature-Key the server requires.  The Signature-Error response
   header provides structured error information when signature
   verification fails.  Together, these mechanisms enable flexible trust
   models ranging from privacy-preserving pseudonymous verification to
   horizontally-scalable delegated authentication and PKI-based identity
   chains.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-hardt-httpbis-signature-key-07" />
   
</reference>
