RFC 9690: Use of the RSA-KEM Algorithm in the Cryptographic Message Syntax (CMS)
In plain English — editorial summary, not part of the RFC
The RSA Key Encapsulation Mechanism (RSA-KEM) algorithm is a one-pass (store-and-forward) cryptographic mechanism for an originator to securely send keying material to a recipient using the recipient's RSA public key. The RSA-KEM algorithm is specified in Clause 11.5 of ISO/IEC: 18033-2:2006. This document specifies the conventions for using the RSA-KEM algorithm as a standalone KEM algorithm and the conventions for using the RSA-KEM algorithm with the Cryptographic Message Syntax (CMS) using KEMRecipientInfo as specified in RFC 9629. This document obsoletes RFC 5990.
Document record
- Document ID
- RFC9690
- Published
- February 2025
- Authors
- R. Housley; S. Turner
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 30
- Also known as
- —
- Obsoletes:
- RFC 5990
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9936Use of ML-KEM in the Cryptographic Message Syntax (CMS)Current
March 2026
- RFC 9629Using Key Encapsulation Mechanism (KEM) Algorithms in the Cryptographic Message Syntax (CMS)Current
August 2024
- RFC 9688Use of the SHA3 One-Way Hash Functions in the Cryptographic Message Syntax (CMS)Current
November 2024
- RFC 9684A YANG Data Model for Challenge-Response-Based Remote Attestation (CHARRA) Procedures Using Trusted Platform Modules (TPMs)Current
December 2024
- RFC 9683Remote Integrity Verification of Network Devices Containing Trusted Platform ModulesCurrent
December 2024
- RFC 9700Best Current Practice for OAuth 2.0 SecurityCurrent
January 2025
- RFC 9701JSON Web Token (JWT) Response for OAuth Token IntrospectionCurrent
January 2025
- RFC 9679CBOR Object Signing and Encryption (COSE) Key ThumbprintCurrent
December 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?