CBOR Object Signing and Encryption "typ" Header Parameter
RFC 9596, “CBOR Object Signing and Encryption "typ" Header Parameter”, is a Proposed Standard document published in June 2024 by M.B. Jones, O. Steele. The canonical text is published by the RFC Editor.
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.
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 9596 is hosted at rfc-editor.org. Available in HTML,TXT,PDF,XML.
- RFC 9595 YANG Schema Item iDentifier
- RFC 9597 CBOR Web Token Claims in COSE Headers
- RFC 9594 Key Provisioning for Group Communication Using Authentication and Authorization for Constrained Environments
- RFC 9598 Internationalized Email Addresses in X.509 Certificates
- RFC 9593 Announcing Supported Authentication Methods in the Internet Key Exchange Protocol Version 2
- RFC 9599 Guidelines for Adding Congestion Notification to Protocols that Encapsulate IP
- RFC 9592 Retiring the Tao of the IETF
- RFC 9600 TRansparent Interconnection of Lots of Links : Explicit Congestion Notification Support