%% You should probably cite draft-ietf-jose-json-proof-token-12 instead of this revision.
@techreport{ietf-jose-json-proof-token-10,
    number =    {draft-ietf-jose-json-proof-token-10},
    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-proof-token/10/},
    author =    {Michael B. Jones and David Waite and Jeremie Miller},
    title =     {{JSON Proof Token and CBOR Proof Token}},
    pagetotal = 14,
    year =      ,
    month =     ,
    day =       ,
    abstract =  {JSON Proof Token (JPT) is a compact, URL-safe, privacy-preserving representation of claims to be transferred between three parties. The claims in a JPT are encoded as base64url-encoded JSON objects that are used as the payloads of a JSON Web Proof (JWP) structure, enabling them to be digitally signed and selectively disclosed. JPTs also support reusability and unlinkability when using Zero-Knowledge Proofs (ZKPs). A CBOR-based representation of JPTs is also defined, called a CBOR Proof Token (CPT). It has the same properties as JPTs, but uses the JSON Web Proof (JWP) CBOR Serialization, rather than the JSON-based JWP Compact Serialization.},
}