RFC 7165

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

Canonical URL:
File formats:
Plain TextPDF
R. Barnes
jose (sec)

Cite this RFC: TXT  |  XML

DOI:  10.17487/RFC7165

Discuss this RFC: Send questions or comments to jose@ietf.org

Other actions: Submit Errata  |  Find IPR Disclosures from the IETF


Many Internet applications have a need for object-based security mechanisms in addition to security mechanisms at the network layer or transport layer. For many years, the Cryptographic Message Syntax (CMS) has provided a binary secure object format based on ASN.1. Over time, binary object encodings such as ASN.1 have become less common than text-based encodings, such as the JavaScript Object Notation (JSON). This document defines a set of use cases and requirements for a secure object format encoded using JSON, drawn from a variety of application security mechanisms currently in development.

For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 4844.

Download PDF Reader

Search RFCs
Advanced Search