ML-KEM Security Considerations
draft-sfluhrer-cfrg-ml-kem-security-considerations-03
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Active".
Expired & archived
|
|
|---|---|---|---|
| Authors | Scott Fluhrer , Quynh Dang , John Preuß Mattsson , Kevin Milner , Daniel Shiu | ||
| Last updated | 2025-11-16 (Latest revision 2025-05-15) | ||
| RFC stream | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
NIST standardized ML-KEM as FIPS 203 in August 2024. This document discusses how to use ML-KEM and how to use it within protocols - that is, what problem it solves, and what you need to do to use it securely.
Authors
Scott Fluhrer
Quynh Dang
John Preuß Mattsson
Kevin Milner
Daniel Shiu
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)