Cite this RFC:TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC7165
Discuss this RFC: Send questions or comments to the mailing listjose@ietf.org
Other actions:Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 7165
Many Internet applications have a need for object-based securitymechanisms in addition to security mechanisms at the network layer ortransport 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 lesscommon than text-based encodings, such as the JavaScript ObjectNotation (JSON). This document defines a set of use cases andrequirements for a secure object format encoded using JSON, drawnfrom a variety of application security mechanisms currently indevelopment.
For the definition ofStatus,seeRFC 2026.
For the definition ofStream, seeRFC 8729.