ObsoletedPROPOSED STANDARDIETF stream

RFC 8152: CBOR Object Signing and Encryption (COSE)

This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 9052, RFC 9053.

Current document in this lineage: RFC 9052CBOR Object Signing and Encryption (COSE): Structures and Process; RFC 9053CBOR Object Signing and Encryption (COSE): Initial Algorithms

In plain English — editorial summary, not part of the RFC

Concise Binary Object Representation (CBOR) is a data format designed for small code size and small message size. There is a need for the ability to have basic security services defined 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.

Document record

Document ID
RFC8152
Published
July 2017
Authors
J. Schaad
Status
PROPOSED STANDARD
Stream
IETF
Area
sec
Pages
121
Also known as
Obsoleted by:
RFC 9052, RFC 9053

Topics

Standards lineage

This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.

  1. RFC 8152 (2017)
  2. RFC 9052 (2022)
  3. RFC 9053 (2022)

Read the full history of CBOR Object Signing and Encryption (COSE): Initial Algorithms

Referenced by

2 later RFCs formally update or obsolete part of this document.

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

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?

canonical URL: /rfc/8152-cbor-object-signing-and-encryption-cose