RFC 9596: CBOR Object Signing and Encryption (COSE) "typ" (type) Header Parameter
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC9596
- Published
- June 2024
- Authors
- M.B. Jones; O. Steele
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 5
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9597CBOR Web Token (CWT) Claims in COSE HeadersCurrent
June 2024
- RFC 9598Internationalized Email Addresses in X.509 CertificatesCurrent
May 2024
- RFC 9594Key Provisioning for Group Communication Using Authentication and Authorization for Constrained Environments (ACE)Current
September 2024
- RFC 9593Announcing Supported Authentication Methods in the Internet Key Exchange Protocol Version 2 (IKEv2)Current
July 2024
- RFC 9588Kerberos Simple Password-Authenticated Key Exchange (SPAKE) Pre-authenticationCurrent
August 2024
- RFC 9608No Revocation Available for X.509 Public Key CertificatesCurrent
June 2024
- RFC 9611Internet Key Exchange Protocol Version 2 (IKEv2) Support for Per-Resource Child Security Associations (SAs)Current
July 2024
- RFC 9580OpenPGPCurrent
July 2024
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?