Deirdre pinged me privately to complain about the abstract:
“The Module-Lattice-based Key-Encapsulation Mechanism (ML-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 ML-KEM public key.
I agree that when combined with CMS and KEMRI, you get a one-pass store-and-forward construct – IE the encrypted CMS payload and all the crypto stuff go together in the same message. But ML-KEM by itself is not a store-and-forward; it’s a KEM.
I suggest instead just borrowing the abstract off draft-ietf-lamps-kyber-certificates:
“Module-Lattice-Based Key-Encapsulation Mechanism (ML-KEM) is a
quantum-resistant key-encapsulation mechanism (KEM). This document
specifies conventions for using ML-KEM within the Cryptographic Message Syntax (CMS).
Deirdre pinged me privately to complain about the abstract:
“The Module-Lattice-based Key-Encapsulation Mechanism (ML-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 ML-KEM public key.
I agree that when combined with CMS and KEMRI, you get a one-pass store-and-forward construct – IE the encrypted CMS payload and all the crypto stuff go together in the same message. But ML-KEM by itself is not a store-and-forward; it’s a KEM.
I suggest instead just borrowing the abstract off draft-ietf-lamps-kyber-certificates:
“Module-Lattice-Based Key-Encapsulation Mechanism (ML-KEM) is a quantum-resistant key-encapsulation mechanism (KEM). This document specifies conventions for using ML-KEM within the Cryptographic Message Syntax (CMS).