%% You should probably cite draft-ietf-jose-json-web-proof-08 instead of this revision.
@techreport{ietf-jose-json-web-proof-07,
    number =    {draft-ietf-jose-json-web-proof-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-ietf-jose-json-web-proof/07/},
    author =    {David Waite and Michael B. Jones and Jeremie Miller},
    title =     {{JSON Web Proof}},
    pagetotal = 32,
    year =      ,
    month =     ,
    day =       ,
    abstract =  {The JOSE set of standards established JSON-based container formats for Keys, Signatures, and Encryption. They also established IANA registries to enable the algorithms and representations used for them to be extended. Since those were created, newer cryptographic algorithms that support selective disclosure and unlinkability have matured and started seeing early market adoption. The COSE set of standards likewise does this for CBOR-based containers, focusing on the needs of environments which are better served using CBOR, such as constrained devices and networks. This document defines a new container format similar in purpose and design to JSON Web Signature (JWS) and COSE Signed Messages called a \_JSON Web Proof (JWP)\_. Unlike JWS, which integrity-protects only a single payload, JWP can integrity-protect multiple payloads in one message. It also specifies a new presentation form that supports selective disclosure of individual payloads, enables additional proof computation, and adds a protected header to prevent replay.},
}