Skip to main content

JSON Web Proof

The information below is for an old version of the document.
Document Type
This is an older version of an Internet-Draft whose latest revision state is "Replaced".
Expired & archived
Authors Jeremie Miller , David Waite , Michael B. Jones
Last updated 2023-01-25 (Latest revision 2022-07-24)
Replaced by draft-ietf-jose-json-web-proof
RFC stream (None)
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:


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. This document defines a new container format similar in purpose and design to JSON Web Signature (JWS) 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 and support binding mechanisms.


Jeremie Miller
David Waite
Michael B. Jones

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)