Skip to main content

JSON Web Signatures (JWS) Multiple Payload Option

Document Type Expired Internet-Draft (individual)
Expired & archived
Authors David Waite , Jeremie Miller , Michael B. Jones
Last updated 2024-01-11 (Latest revision 2023-07-10)
RFC stream (None)
Intended RFC status (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 signatures ( over a content payload using established algorithms ( Newer algorithms are emerging which allow for additional operations on content, such as a party (other than the signer) choosing not to disclose some of the integrity-protected content. However, these algorithms often support granularity at the individual message level, creating a need to define a way to support expressing multiple content payloads as part of a single message. This document defines a new operational mode for JSON Web Signatures that operates on a protected header and multiple binary content payloads to provide the expressivity needed for this class of algorithm. It also describes how multiple content payloads can be expressed in a manner compatible with pre-existing algorithms, albeit without the operational capabilities of newer algorithms.


David Waite
Jeremie Miller
Michael B. Jones

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