JSON Proof Token
draft-jmiller-jose-json-proof-token-00
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Replaced".
Expired & archived
|
|
|---|---|---|---|
| Authors | Jeremie Miller , Michael B. Jones | ||
| Last updated | 2023-01-25 (Latest revision 2022-07-24) | ||
| Replaced by | draft-ietf-jose-json-proof-token | ||
| RFC stream | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
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) (https://www.ietf.org/archive/id/draft-jmiller-jose-json-web-proof- 00.html) structure, enabling them to be digitally signed and selectively disclosed. JPTs also support reusability and unlinkability when using Zero-Knowledge Proofs (ZKPs).
Authors
Jeremie Miller
Michael B. Jones
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)