The CBOR Object Signing and Encryption (COSE) “typ” (type) Header Parameter
specification has been published as RFC
9596<https://www.rfc-editor.org/rfc/rfc9596.html>! This closes a gap for COSE
relative to JOSE, adding the ability to use media types to declare the content
of the complete COSE object.
The specification abstract is:
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.
Special thanks to my co-author Orie Steele, who pointed out the gap and
proposed that we close it. He was an active participant and insightful partner
in making this RFC happen (his first!). The CBOR and COSE ecosystems are better
for it.
-- Mike
P.S. This note was also published at https://self-issued.info/?p=2548 and
referenced from https://x.com/selfissued/status/1800659034070192418 and
https://www.linkedin.com/posts/selfissued_ietf-cose-jose-activity-7206425687249866752-vVmB/.
_______________________________________________
COSE mailing list -- [email protected]
To unsubscribe send an email to [email protected]
