Use Cases and Requirements for JSON Object Signing and Encryption
RFC 7165, “Use Cases and Requirements for JSON Object Signing and Encryption”, is an Informational document published in April 2014 by R. Barnes. The canonical text is published by the RFC Editor.
Abstract
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.
What “Informational” means
Published for the general information of the community. It does not define an IETF standard and carries no standards-track status.
The canonical text of RFC 7165 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 7164 RTP and Leap Seconds
- RFC 7166 Supporting Authentication Trailer for OSPFv3
- RFC 7163 URN for Country-Specific Emergency Services
- RFC 7167 A Framework for Point-to-Multipoint MPLS in Transport Networks
- RFC 7168 The Hyper Text Coffee Pot Control Protocol for Tea Efflux Appliances
- RFC 7162 IMAP Extensions: Quick Flag Changes Resynchronization and Quick Mailbox Resynchronization
- RFC 7169 The NSA Certificate Extension
- RFC 7161 Proxy Mobile IPv6 Multicast Handover Optimization by the Subscription Information Acquisition through the LMA