[lamps] Re: Call for adoption: draft-chen-lamps-cms-frodokem-01 (Ends 2026-10-28)

[Daniel Van Geest <[e-mail]>]

I support adoption and will be available for hackathon interop testing of this draft.

Daniel

> -----Original Message-----
> From: Russ Housley via Datatracker <[e-mail]>
> Sent: Wednesday, October 14, 2026 7:06 PM
> To: [e-mail]; [e-mail]; draft-chen-lamps-cms-
> [e-mail]
> Subject: [lamps] Call for adoption: draft-chen-lamps-cms-frodokem-01 (Ends
> 2026-10-28)
> 
> This message starts a lamps WG Call for Adoption of:
> draft-chen-lamps-cms-frodokem-01
> 
> This Working Group Call for Adoption ends on 2026-10-28
> 
> Abstract:
>    FrodoKEM is a quantum-resistant key encapsulation mechanism (KEM)
>    based on the standard Learning With Errors (LWE) problem，standardized
>    by ISO.  FrodoKEM offers multiple parameter sets, with the
>    recommended sets for general use including (e)FrodoKEM-976-AES and
>    (e)FrodoKEM-976-SHAKE for security level 3, and (e)FrodoKEM-1344-AES
>    and (e)FrodoKEM-1344-SHAKE for security level 5.  This document
>    specifies the conventions for using FrodoKEM in the Cryptographic
>    Message Syntax (CMS), using the KEMRecipientInfo structure defined in
>    "Use of Key Encapsulation Mechanism (KEM) Algorithms in the
>    Cryptographic Message Syntax (CMS)" [RFC9629].
> 
> Please reply to this message and indicate whether or not you support
> adoption of this Internet-Draft by the lamps WG. Comments to explain your
> preference are greatly appreciated. Please reply to all recipients of this
> message and include this message in your response.
> 
> Authors, and WG participants in general, are reminded of the Intellectual
> Property Rights (IPR) disclosure obligations described in BCP 79 [2].
> Appropriate IPR disclosures required for full conformance with the provisions
> of BCP 78 [1] and BCP 79 [2] must be filed, if you are aware of any.
> Sanctions available for application to violators of IETF IPR Policy can be found
> at [3].
> 
> Note that the CFRG has just adopted [4]. This document, if adopted would
> not be sent to the IESG until the CFRG publishes [4] as an RFC.
> 
> Thank you.
> 
> [1] https://datatracker.ietf.org/doc/bcp78/
> [2] https://datatracker.ietf.org/doc/bcp79/
> [3] https://datatracker.ietf.org/doc/rfc6701/
> [4] https://datatracker.ietf.org/doc/draft-longa-cfrg-frodokem-security-
> considerations/
> 
> The IETF datatracker status page for this Internet-Draft is:
> https://datatracker.ietf.org/doc/draft-chen-lamps-cms-frodokem/
> 
> There is also an HTML version available at:
> https://www.ietf.org/archive/id/draft-chen-lamps-cms-frodokem-01.html
> 
> A diff from the previous version is available at:
> https://author-tools.ietf.org/iddiff?url2=draft-chen-lamps-cms-frodokem-01
> _______________________________________________
> Spasm mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]