[Pqc] PQC integration in IPsec/IKEv2 - implementation experien ce and interop
Matt Ige <[email protected]> Fri, 15 May 2026 19:06:12 +0000
| Newsgroups | gmane.ietf.pqc,gmane.ietf.ipsec |
|---|---|
| Message-ID | <IA3PR00MB21814CB13608DD1BC9BB1671F2042@IA3PR00MB2181.namprd00.prod.outlook.com> |
--===============0197703998837399978==
Content-Language: en-US
Content-Type: multipart/alternative;
boundary="_000_IA3PR00MB21814CB13608DD1BC9BB1671F2042IA3PR00MB2181namp_"
--_000_IA3PR00MB21814CB13608DD1BC9BB1671F2042IA3PR00MB2181namp_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
Hi,
I=92m reaching out to understand how others are approaching the integration=
of post-quantum cryptography (PQC) into their IPsec/IKEv2 implementations.
We are currently looking at the CNSA 2.0 IPsec profile draft as a reference=
: https://datatracker.ietf.org/doc/draft-guthrie-cnsa2-ipsec-profile
I have a couple of specific questions:
1. Beyond what is outlined in this draft, are there additional requirements=
, design considerations, or extensions that implementations are incorporati=
ng in practice?
2. Are there organizations actively implementing PQC for IPsec that would b=
e interested in interoperability testing or collaboration?
We are actively working on our implementation and are particularly interest=
ed in ensuring alignment with emerging standards and ecosystem compatibilit=
y. I appreciate any insights or pointers.
Thanks,
Matt
--_000_IA3PR00MB21814CB13608DD1BC9BB1671F2042IA3PR00MB2181namp_
Content-Type: text/html; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
<style type=3D"text/css" style=3D"display:none;"> P {margin-top:0;margin-bo=
ttom:0;} </style>
</head>
<body dir=3D"ltr">
<div style=3D"font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, =
Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">
Hi,</div>
<div class=3D"elementToProof" style=3D"font-family: Aptos, Aptos_EmbeddedFo=
nt, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; c=
olor: rgb(0, 0, 0);">
I=92m reaching out to understand how others are approaching the integration=
of post-quantum cryptography (PQC) into their IPsec/IKEv2 implementations.=
</div>
<div class=3D"elementToProof" style=3D"font-family: Aptos, Aptos_EmbeddedFo=
nt, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; c=
olor: rgb(0, 0, 0);">
<br>
</div>
<div class=3D"elementToProof" style=3D"font-family: Aptos, Aptos_EmbeddedFo=
nt, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; c=
olor: rgb(0, 0, 0);">
We are currently looking at the CNSA 2.0 IPsec profile draft as a reference=
: https://datatracker.ietf.org/doc/draft-guthrie-cnsa2-ipsec-profile</div>
<div class=3D"elementToProof" style=3D"font-family: Aptos, Aptos_EmbeddedFo=
nt, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; c=
olor: rgb(0, 0, 0);">
<br>
</div>
<div class=3D"elementToProof" style=3D"font-family: Aptos, Aptos_EmbeddedFo=
nt, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; c=
olor: rgb(0, 0, 0);">
I have a couple of specific questions:</div>
<div class=3D"elementToProof" style=3D"font-family: Aptos, Aptos_EmbeddedFo=
nt, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; c=
olor: rgb(0, 0, 0);">
1. Beyond what is outlined in this draft, are there additional require=
ments, design considerations, or extensions that implementations are incorp=
orating in practice?</div>
<div class=3D"elementToProof" style=3D"font-family: Aptos, Aptos_EmbeddedFo=
nt, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; c=
olor: rgb(0, 0, 0);">
2. Are there organizations actively implementing PQC for IPsec that would b=
e interested in interoperability testing or collaboration?</div>
<div style=3D"font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, =
Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class=3D"elementToProof" style=3D"font-family: Aptos, Aptos_EmbeddedFo=
nt, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; c=
olor: rgb(0, 0, 0);">
We are actively working on our implementation and are particularly interest=
ed in ensuring alignment with emerging standards and ecosystem compatibilit=
y. I appreciate any insights or pointers.</div>
<div class=3D"elementToProof" style=3D"font-family: Aptos, Aptos_EmbeddedFo=
nt, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; c=
olor: rgb(0, 0, 0);">
<br>
</div>
<div id=3D"Signature" class=3D"elementToProof">
<p class=3D"elementToProof" style=3D"margin: 0in; font-family: Calibri, san=
s-serif; font-size: 11pt;">
Thanks,</p>
<p class=3D"elementToProof" style=3D"margin: 0in; font-family: Calibri, san=
s-serif; font-size: 11pt;">
Matt</p>
</div>
</body>
</html>
--_000_IA3PR00MB21814CB13608DD1BC9BB1671F2042IA3PR00MB2181namp_--
--===============0197703998837399978==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline
LS0gClBxYyBtYWlsaW5nIGxpc3QgLS0gcHFjQGlldGYub3JnClRvIHVuc3Vic2NyaWJlIHNlbmQg
YW4gZW1haWwgdG8gcHFjLWxlYXZlQGlldGYub3JnCg==
--===============0197703998837399978==--