RFC 9936: Use of ML-KEM in the Cryptographic Message Syntax (CMS)
In plain English — editorial summary, not part of the RFC
Module-Lattice-Based Key-Encapsulation Mechanism (ML-KEM) is a quantum-resistant Key Encapsulation Mechanism (KEM). Three parameter sets for the ML-KEM algorithm are specified by the US National Institute of Standards and Technology (NIST) in FIPS 203. In order of increasing security strength (and decreasing performance), these parameter sets are ML-KEM-512, ML-KEM-768, and ML-KEM-1024. This document specifies the conventions for using ML-KEM with the Cryptographic Message Syntax (CMS) using the KEMRecipientInfo structure defined in "Using Key Encapsulation Mechanism (KEM) Algorithms in the Cryptographic Message Syntax (CMS)" (RFC 9629).
Document record
- Document ID
- RFC9936
- Published
- March 2026
- Authors
- J. Prat; M. Ounsworth; D. Van Geest
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 18
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9935Internet X.509 Public Key Infrastructure - Algorithm Identifiers for the Module-Lattice-Based Key-Encapsulation Mechanism (ML-KEM)Current
March 2026
- RFC 9690Use of the RSA-KEM Algorithm in the Cryptographic Message Syntax (CMS)Current
February 2025
- RFC 10024Post-Quantum Traditional (PQ/T) Hybrid Key Agreement Mechanisms for TLS 1.3Current
August 2026
- RFC 9629Using Key Encapsulation Mechanism (KEM) Algorithms in the Cryptographic Message Syntax (CMS)Current
August 2024
- RFC 9939PKCS #8: Private-Key Information Content TypesCurrent
February 2026
- RFC 9941Secure Shell (SSH) Key Exchange Method Using Hybrid Streamlined NTRU Prime sntrup761 and X25519 with SHA-512: sntrup761x25519-sha512Current
April 2026
- RFC 9930Tunnel Extensible Authentication Protocol (TEAP) Version 1Current
February 2026
- RFC 9942CBOR Object Signing and Encryption (COSE) ReceiptsCurrent
June 2026
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?