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 list cose@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 and Encryption (JOSE) "typ" (type) header parameter to CBOR Object Signing and Encryption (COSE). This enables the benefits of explicit typing (as defined in RFC 8725, "JSON Web Token Best Current Practices") to be brought to COSE objects. The syntax of the COSE type header parameter value is the same as the existing COSE content type header parameter.

For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 8729.