[prev in list] [next in list] [prev in thread] [next in thread]
List: ipsec
Subject: Re: [IPsec] Comment on draft-kampanakis-ml-kem-ikev2
From: "Kampanakis, Panos" <kpanos=40amazon.com () dmarc ! ietf ! org>
Date: 2024-01-31 4:11:44
Message-ID: e76e4c34353942e988eda569eca9c4da () amazon ! com
[Download RAW message or body]
Thx Leonie. Good idea. Will do. I will align the text a bit with the termin=
ology draft.
From: IPsec <ipsec-bounces@ietf.org> On Behalf Of Bruckert, Leonie
Sent: Tuesday, January 30, 2024 6:40 AM
To: ipsec@ietf.org
Subject: [EXTERNAL] [IPsec] Comment on draft-kampanakis-ml-kem-ikev2
CAUTION: This email originated from outside of the organization. Do not cli=
ck links or open attachments unless you can confirm the sender and know the=
content is safe.
Thanks for setting up this draft!
Have you considered to align terminology with draft-ietf-pquip-pqt-hybrid-t=
erminology? It defines a "PQ/T Hybrid Key Encapsulation Mechanism" as a "mu=
lti-algorithm KEM made up of two or more component KEM algorithms where at =
least one is a post-quantum algorithm and at least one is a traditional alg=
orithm". This definition may not perfectly match how a hybrid KEM is done i=
n IKEv2 as it is a sequential approach. However, I think it would be good t=
o have a reference to the terminology draft.
Leonie
[Attachment #3 (text/html)]
<html xmlns:v="urn:schemas-microsoft-com:vml" \
xmlns:o="urn:schemas-microsoft-com:office:office" \
xmlns:w="urn:schemas-microsoft-com:office:word" \
xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" \
xmlns="http://www.w3.org/TR/REC-html40"> <head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:Consolas;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
p.HTMLVorformatiert, li.HTMLVorformatiert, div.HTMLVorformatiert
{mso-style-name:"HTML Vorformatiert";
mso-style-link:"HTML Vorformatiert Zchn";
margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.HTMLVorformatiertZchn
{mso-style-name:"HTML Vorformatiert Zchn";
mso-style-priority:99;
mso-style-link:"HTML Vorformatiert";
font-family:Consolas;}
span.EmailStyle25
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:70.85pt 70.85pt 56.7pt 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal">Thx Leonie. Good idea. Will do. I will align the text a bit with \
the terminology draft. <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> IPsec <ipsec-bounces@ietf.org> <b>On Behalf \
Of </b> Bruckert, Leonie<br>
<b>Sent:</b> Tuesday, January 30, 2024 6:40 AM<br>
<b>To:</b> ipsec@ietf.org<br>
<b>Subject:</b> [EXTERNAL] [IPsec] Comment on \
draft-kampanakis-ml-kem-ikev2<o:p></o:p></p> </div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" \
style="border-collapse:collapse"> <tbody>
<tr style="height:15.25pt">
<td width="1123" valign="top" style="width:842.35pt;border:solid #ED7D31 \
1.5pt;padding:0in 5.4pt 0in 5.4pt;height:15.25pt"> <p><strong><span \
style="font-family:"Calibri",sans-serif;background:#FFFF99">CAUTION</span></strong><span \
style="background:#FFFF99">: This email originated from outside of the organization. \
Do not click links or open attachments unless you can confirm the sender and know \
the content is safe.</span><o:p></o:p></p> </td>
</tr>
</tbody>
</table>
<p class="MsoNormal"><span lang="DE"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal">Thanks for setting up this draft!<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Have you considered to align terminology with \
draft-ietf-pquip-pqt-hybrid-terminology? It defines a “PQ/T Hybrid Key \
Encapsulation Mechanism” as a “multi-algorithm KEM made up of two or more \
component KEM algorithms where at least one is a post-quantum algorithm and at least \
one is a traditional algorithm“. This definition may not perfectly match how a \
hybrid KEM is done in IKEv2 as it is a sequential approach. However, I think it would \
be good to have a reference to the terminology draft.<o:p></o:p></p> <p \
class="MsoNormal"><o:p> </o:p></p> <p class="MsoNormal">Leonie<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</body>
</html>
_______________________________________________
IPsec mailing list
IPsec@ietf.org
https://www.ietf.org/mailman/listinfo/ipsec
--===============3513949213672803863==--
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic