RFC 8230: Using RSA Algorithms with CBOR Object Signing and Encryption (COSE) Messages
In plain English — editorial summary, not part of the RFC
The CBOR Object Signing and Encryption (COSE) specification defines cryptographic message encodings using Concise Binary Object Representation (CBOR). This specification defines algorithm encodings and representations enabling RSA algorithms to be used for COSE messages. Encodings are specified for the use of RSA Probabilistic Signature Scheme (RSASSA-PSS) signatures, RSA Encryption Scheme - Optimal Asymmetric Encryption Padding (RSAES-OAEP) encryption, and RSA keys.
Document record
- Document ID
- RFC8230
- Published
- September 2017
- Authors
- M. Jones
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- —
- Pages
- 12
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8812CBOR Object Signing and Encryption (COSE) and JSON Object Signing and Encryption (JOSE) Registrations for Web Authentication (WebAuthn) AlgorithmsCurrent
August 2020
- RFC 9787Guidance on End-to-End Email SecurityCurrent
August 2025
- RFC 9980Post-Quantum Cryptography in OpenPGPCurrent
June 2026
- RFC 5091Identity-Based Cryptography Standard (IBCS) #1: Supersingular Curve Implementations of the BF and BB1 CryptosystemsUpdated
December 2007
- RFC 4491Using the GOST R 34.10-94, GOST R 34.10-2001, and GOST R 34.11-94 Algorithms with the Internet X.509 Public Key Infrastructure Certificate and CRL ProfileCurrent
May 2006
- RFC 8391XMSS: eXtended Merkle Signature SchemeCurrent
May 2018
- RFC 8998ShangMi (SM) Cipher Suites for TLS 1.3Current
March 2021
- RFC 2986PKCS #10: Certification Request Syntax Specification Version 1.7Updated
November 2000
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?