Sign in
Version 5.13.0, 2015-03-25
Report a bug

Use Cases and Requirements for JSON Object Signing and Encryption (JOSE)

Document type: Replaced Internet-Draft (individual)
Document stream: No stream defined
Last updated: 2013-03-22 (latest revision 2013-02-25)
Intended RFC status: Unknown
Other versions: (expired, archived): plain text, pdf, html

Stream State:No stream defined
Document shepherd: No shepherd assigned

IESG State: Replaced by draft-ietf-jose-use-cases
Responsible AD: (None)
Send notices to: No addresses provided

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found here:


Many Internet applications have a need for object-based security mechanisms in addition to security mechanisms at the network layer or transport layer. In the past, the Cryptographic Message Syntax has provided a binary secure object format based on ASN.1. Over time, the use of binary object encodings such as ASN.1 has been overtaken by text-based encodings, for example JavaScript Object Notation. This document defines a set of use cases and requirements for a secure object format encoded using JavaScript Object Notation, drawn from a variety of application security mechanisms currently in development.


Richard Barnes <>

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