[rfc-dist] STD 96, RFC 9052 on CBOR Object Signing and Encryption (COSE): Structures and Process

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

        STD 96        
        RFC 9052

        Title:      CBOR Object Signing and Encryption (COSE):
                    Structures and Process 
        Author:     J. Schaad
        Status:     Standards Track
        Stream:     IETF
        Date:       August 2022
        Pages:      66
        Obsoletes:  RFC 8152
        See Also:   STD 96

        I-D Tag:    draft-ietf-cose-rfc8152bis-struct-15.txt

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

        DOI:        10.17487/RFC9052

Concise Binary Object Representation (CBOR) is a data format designed
for small code size and small message size.  There is a need to be
able to define basic security services for this data format.  This
document defines the CBOR Object Signing and Encryption (COSE)
protocol.  This specification describes how to create and process
signatures, message authentication codes, and encryption using CBOR
for serialization.  This specification additionally describes how to
represent cryptographic keys using CBOR.  

This document, along with RFC 9053, obsoletes RFC 8152.

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

This is now an Internet 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-editor@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