RFC 9936 on Use of ML-KEM in the Cryptographic Message Syntax (CMS)

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

        RFC 9936

        Title:      Use of ML-KEM in the 
                    Cryptographic Message Syntax (CMS) 
        Author:     P. Julien,
                    M. Ounsworth,
                    D. Van Geest
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2026
        Mailbox:    julien.prat@cryptonext-security.com,
                    mike.ounsworth@entrust.com,
                    daniel.vangeest@cryptonext-security.com
        Pages:      18
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-lamps-cms-kyber-13.txt

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

        DOI:        10.17487/RFC9936

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).

This document is a product of the Limited Additional Mechanisms for PKIX and SMIME Working Group of the IETF.

This is now a Proposed 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