%% You should probably cite rfc9936 instead of this I-D.
@techreport{ietf-lamps-cms-kyber-04,
    number =    {draft-ietf-lamps-cms-kyber-04},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-ietf-lamps-cms-kyber/04/},
    author =    {PRAT Julien and Mike Ounsworth and Daniel Van Geest},
    title =     {{Use of ML-KEM in the Cryptographic Message Syntax (CMS)}},
    pagetotal = 17,
    year =      ,
    month =     ,
    day =       ,
    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. Three parameters sets for the ML-KEM algorithm are specified by NIST in {[}FIPS203-ipd{]} {[}EDNOTE: Change to {[}FIPS203{]} when it is published{]}. 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 KEMRecipientInfo as specified in {[}I-D.ietf-lamps-cms-kemri{]}.},
}