A new Request for Comments is now available in online RFC libraries.

        
        RFC 9596

        Title:      CBOR Object Signing and Encryption (COSE)
                    "typ" (type) Header Parameter 
        Author:     M.B. Jones,
                    O. Steele
        Status:     Standards Track
        Stream:     IETF
        Date:       June 2024
        Mailbox:    michael_b_jo...@hotmail.com,
                    orie@transmute.industries
        Pages:      5
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-cose-typ-header-parameter-05.txt

        URL:        https://www.rfc-editor.org/info/rfc9596

        DOI:        10.17487/RFC9596

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.

This document is a product of the CBOR Object Signing and Encryption Working 
Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-edi...@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC

_______________________________________________
IETF-Announce mailing list -- ietf-announce@ietf.org
To unsubscribe send an email to ietf-announce-le...@ietf.org

Reply via email to