Skip to main content

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

Document Type Replaced Internet-Draft (individual)
Expired & archived
Author Richard Barnes
Last updated 2013-03-22 (Latest revision 2013-02-25)
Replaced by RFC 7165
RFC stream (None)
Intended RFC status (None)
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-jose-use-cases
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:


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.)