<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-jose-json-proof-token" target="https://datatracker.ietf.org/doc/html/draft-ietf-jose-json-proof-token-08">
   <front>
      <title>JSON Proof Token and CBOR Proof Token</title>
      <author initials="M. B." surname="Jones" fullname="Michael B. Jones">
         <organization>Self-Issued Consulting</organization>
      </author>
      <author initials="D." surname="Waite" fullname="David Waite">
         <organization>Ping Identity</organization>
      </author>
      <author initials="J." surname="Miller" fullname="Jeremie Miller">
         <organization>Ping Identity</organization>
      </author>
      <date month="March" day="17" year="2025" />
      <abstract>
	 <t>   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 of JPTs, but uses the
   JSON Web Proof (JWP) CBOR Serialization, rather than the JSON-based
   JWP Compact Serialization.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-jose-json-proof-token-08" />
   
</reference>
