%% You should probably cite draft-hardt-httpbis-signature-key-08 instead of this revision.
@techreport{hardt-httpbis-signature-key-07,
    number =    {draft-hardt-httpbis-signature-key-07},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-hardt-httpbis-signature-key/07/},
    author =    {Dick Hardt and Thibault Meunier},
    title =     {{HTTP Signature Keys}},
    pagetotal = 39,
    year =      ,
    month =     ,
    day =       ,
    abstract =  {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.},
}