%% You should probably cite draft-ietf-ipsecme-ikev2-mlkem instead of this I-D.
@techreport{kampanakis-ml-kem-ikev2-00,
    number =    {draft-kampanakis-ml-kem-ikev2-00},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-kampanakis-ml-kem-ikev2/00/},
    author =    {Panos Kampanakis and Gerardo Ravago},
    title =     {{Post-quantum Hybrid Key Exchange with ML-KEM in the Internet Key Exchange Protocol Version 2 (IKEv2)}},
    pagetotal = 11,
    year =      ,
    month =     ,
    day =       ,
    abstract =  {{[}EDNOTE: The intention of this draft is to get IANA KE codepoints for ML-KEM. It could be a standards track draft given that ML-KEM will see a lot of adoption, an AD sponsored draft, or even a individual stable draft which gets codepoints from Expert Review. The approach is to be decided by the IPSECME WG. {]} NIST recently standardized ML-KEM, a new key encapsulation mechanism, which can be used for quantum-resistant key establishment. This draft specifies how to use ML-KEM as an additionall key exchange mechanism in IKEv2 along with traditional (Elliptic Curve) Diffie- Hellman. This hybrid approach allows for negotiating IKE and Child SA keys which are safe against cryptanalytically-relevant quantum computers and theoretical weaknesses in ML-KEM as it is relatively new.},
}