RFC 9935 on Internet X.509 Public Key Infrastructure - Algorithm Identifiers for the Module-Lattice-Based Key-Encapsulation Mechanism (ML-KEM)
rfc-editor@rfc-editor.org Fri, 06 March 2026 23:31 UTC
Return-Path: <wwwrun@rfcpa.rfc-editor.org>
X-Original-To: ietf-announce@ietf.org
Delivered-To: ietf-announce@mail2.ietf.org
Received: from rfcpa.rfc-editor.org (unknown [167.172.21.234]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id B9C98C5EA331; Fri, 6 Mar 2026 15:31:54 -0800 (PST)
Received: by rfcpa.rfc-editor.org (Postfix, from userid 461) id A80C02BCA76; Fri, 6 Mar 2026 15:31:54 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 9935 on Internet X.509 Public Key Infrastructure - Algorithm Identifiers for the Module-Lattice-Based Key-Encapsulation Mechanism (ML-KEM)
From: rfc-editor@rfc-editor.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20260306233154.A80C02BCA76@rfcpa.rfc-editor.org>
Date: Fri, 06 Mar 2026 15:31:54 -0800
Message-ID-Hash: Q73A7DUHQOXD6IMUWTTISTH6SQWI6R5N
X-Message-ID-Hash: Q73A7DUHQOXD6IMUWTTISTH6SQWI6R5N
X-MailFrom: wwwrun@rfcpa.rfc-editor.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ietf-announce.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, spasm@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/Au2XEeP8P_VnIftlPRG2ZLBaaBA>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Owner: <mailto:ietf-announce-owner@ietf.org>
List-Post: <mailto:ietf-announce@ietf.org>
List-Subscribe: <mailto:ietf-announce-join@ietf.org>
List-Unsubscribe: <mailto:ietf-announce-leave@ietf.org>
A new Request for Comments is now available in online RFC libraries.
RFC 9935
Title: Internet X.509 Public Key Infrastructure -
Algorithm Identifiers for the Module-Lattice-Based
Key-Encapsulation Mechanism (ML-KEM)
Author: S. Turner,
P. Kampanakis,
J. Massimo,
B. E. Westerbaan
Status: Standards Track
Stream: IETF
Date: March 2026
Mailbox: sean@sn3rd.com,
kpanos@amazon.com,
jakemas@amazon.com,
bas@westerbaan.name
Pages: 71
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-lamps-kyber-certificates-11.txt
URL: https://www.rfc-editor.org/info/rfc9935
DOI: 10.17487/RFC9935
The Module-Lattice-Based Key-Encapsulation Mechanism (ML-KEM) is a
quantum-resistant Key Encapsulation Mechanism. This document
specifies the conventions for using the ML-KEM in X.509 Public Key
Infrastructure. The conventions for the subject public keys and
private keys are also specified.
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