Thanks for the Group Adoption Call, chairs. 

During the holiday season just past, we updated the draft to v03 and sent an 
email to summarize the progress. We are thinking it may be helpful for experts 
here by providing the links for the most related emails and info.  

1)  Email on Dec 24: 
https://mailarchive.ietf.org/arch/msg/ipsec/4_9Vj33EWByFTKWkZpKZoyUoldg/ 
- We updated our draft to v03 and sent a message in the IPSECME mailing list to 
highlight the main change made in v03. Namely, we have switched 4 variants of 
eFrodoKEM (ephemeral mode) to those of FrodoKEM (standard mode), together with 
our alignment with the authors of FrodoKEM draft in CFRG. 

2) Nov. 6: Presentation of v02 at IETF 124 meeting. 
https://datatracker.ietf.org/meeting/124/materials/slides-124-ipsecme-frodokem-for-the-ikev2-00
 
  - This version has addressed all comments received since July of 2025, 
including code points, why variants of both AES and SHAKE and description of 
payloads. 

3) Previous discussions (Nov 2024- March 2025) have been summarized on my 
presentation slides at IETF 122, 
https://datatracker.ietf.org/meeting/122/materials/slides-122-ipsecme-post-quantum-hybrid-key-exchange-in-the-ikev2-with-frodokem-00
 
 - Basically, over 20 discussions, most supportive, based on the recommendation 
to FrodoKEM from EU authorities. 
- These original discussions are also available at 
https://mailarchive.ietf.org/arch/search/?q=Frodo&f_list=ipsec  

Thank you! 

Guilin, Leonie, and Valery.

-----Original Message-----
From: Tero Kivinen via Datatracker <[email protected]> 
Sent: Tuesday, 13 January 2026 2:10 am
To: [email protected]; [email protected]; 
[email protected]
Subject: Call for adoption: draft-wang-ipsecme-hybrid-kem-ikev2-frodo-03 (Ends 
2026-02-09)

This message starts a ipsecme WG Call for Adoption of:
draft-wang-ipsecme-hybrid-kem-ikev2-frodo-03

This Working Group Call for Adoption ends on 2026-02-09

Abstract:
   Multiple key exchanges in the Internet Key Exchange Protocol Version
   2 (IKEv2) [RFC9370] specifies a framework, which supports multiple
   key encapsulation mechanisms (KEMs) in IKEv2 by allowing up to 7
   layers of additional KEMs to derive the final shared secret keys for
   IPsec protocols.  The primary goal is to mitigate the “harvest now
   and decrypt later” threat posed by Cryptographically Relevant Quantum
   Computers(CRQCs).  For this purpose, one or more post-quantum KEMs
   are usually performed in addition to the traditional (EC)DH key
   exchange.  This draft specifies how the post-quantum KEM algorithm
   FrodoKEM is instantiated for IKEv2 as an additional key exchange
   mechanism.

   [EDNOTE: IANA KE code points for FrodoKEM may need to be assigned, as
   the code points for ML-KEM has been considered in [W-D.K25]. ]

Please reply to this message and indicate whether or not you support adoption 
of this Internet-Draft by the ipsecme 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].

Thank you.
[1] https://datatracker.ietf.org/doc/bcp78/
[2] https://datatracker.ietf.org/doc/bcp79/
[3] https://datatracker.ietf.org/doc/rfc6701/

The IETF datatracker status page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-wang-ipsecme-hybrid-kem-ikev2-frodo/

There is also an HTML version available at:
https://www.ietf.org/archive/id/draft-wang-ipsecme-hybrid-kem-ikev2-frodo-03.html

A diff from the previous version is available at:
https://author-tools.ietf.org/iddiff?url2=draft-wang-ipsecme-hybrid-kem-ikev2-frodo-03
_______________________________________________
IPsec mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to