Search RFCs

RFC Editor

File formats:

Also available:XML file for editing

 

Status:

PROPOSED STANDARD

Authors:

M.B. Jones
O. Steele

Stream:

IETF

Source:

cose (sec)

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC9596

Discuss this RFC: Send questions or comments to the mailing listcose@ietf.org

Other actions:Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 9596

Abstract

This specification adds the equivalent of the JSON Object Signing andEncryption (JOSE) "typ" (type) header parameter to CBOR ObjectSigning and Encryption (COSE). This enables the benefits of explicittyping (as defined in RFC 8725, "JSON Web Token Best CurrentPractices") to be brought to COSE objects. The syntax of the COSEtype header parameter value is the same as the existing COSE contenttype header parameter.

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.