IETF Logo Mail Archive

[TLS] Re: WG Last Call: draft-ietf-tls-mlkem-05 (Ends 2025-11-26)

Benjamin Kaduk <bkaduk@akamai.com> Thu, 27 November 2025 22:35 UTC

Return-Path: <bkaduk@akamai.com>
X-Original-To: tls@mail2.ietf.org
Delivered-To: tls@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 7C00991D7E9A; Thu, 27 Nov 2025 14:35:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: 0.54
X-Spam-Level:
X-Spam-Status: No, score=0.54 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_SBL_CSS=3.335, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=no autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=akamai.com
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U-4P9ca80R5Z; Thu, 27 Nov 2025 14:35:16 -0800 (PST)
Received: from mx0b-00190b01.pphosted.com (mx0b-00190b01.pphosted.com [67.231.157.127]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 603F691D7E83; Thu, 27 Nov 2025 14:35:15 -0800 (PST)
Received: from pps.filterd (m0409410.ppops.net [127.0.0.1]) by m0409410.ppops.net-00190b01. (8.18.1.11/8.18.1.11) with ESMTP id 5ARMEh3C2808720; Thu, 27 Nov 2025 22:35:09 GMT
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h= content-type:date:from:in-reply-to:message-id:mime-version :references:subject:to; s=jan2016.eng; bh=ZIexrI83bJ5LC4XW8MBxDm oxN+J2ZgDR1xODzooBCxs=; b=K8HMA7cj3mbHrjsNgiwXbr5zBRfp3MW03ChA+a E7yMFaSQyjZ6JJFGcbm1lv10vWqgm6D8kq64WxTSgII9x69DSe0kCARVqhb+Th9T j+OKTUBCNIrCr7rWbeGBSOw8IsHGdNsDpQOp7HoNbu9Y/XhqJAdpm/sEwYvyza3Z fji/g2cwIdQNL8s85NtDchhTV8ZMLjyjQfLhyyTmHOd75vq/A5d0OSDogy49qzlk tKCVvpRP3bCtnT0X8rpDIIfar5AlfE07RRfv4M3hAuNU+wCABzHXfyYtNy315tOC gZIZgIq9Aov1ZbQOUzWl6Bh5zpvbUVF816U+RYbbE/Ej556Q==
Received: from prod-mail-ppoint1 (prod-mail-ppoint1.akamai.com [184.51.33.18]) by m0409410.ppops.net-00190b01. (PPS) with ESMTPS id 4anh7f0jcp-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 27 Nov 2025 22:35:09 +0000 (GMT)
Received: from pps.filterd (prod-mail-ppoint1.akamai.com [127.0.0.1]) by prod-mail-ppoint1.akamai.com (8.18.1.2/8.18.1.2) with ESMTP id 5ARGiU3B013794; Thu, 27 Nov 2025 17:35:08 -0500
Received: from email.msg.corp.akamai.com ([172.27.91.40]) by prod-mail-ppoint1.akamai.com (PPS) with ESMTPS id 4ak9d20b5r-2 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 27 Nov 2025 17:35:08 -0500
Received: from usma1ex-dag4mb3.msg.corp.akamai.com (172.27.91.22) by usma1ex-dag5mb1.msg.corp.akamai.com (172.27.91.40) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.2562.29; Thu, 27 Nov 2025 14:35:08 -0800
Received: from usma1ex-dag5mb1.msg.corp.akamai.com (172.27.91.40) by usma1ex-dag4mb3.msg.corp.akamai.com (172.27.91.22) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.2562.27; Thu, 27 Nov 2025 17:35:07 -0500
Received: from akamai.com (172.27.118.139) by usma1ex-dag5mb1.msg.corp.akamai.com (172.27.91.40) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.2562.29 via Frontend Transport; Thu, 27 Nov 2025 14:35:07 -0800
Date: Thu, 27 Nov 2025 14:35:05 -0800
From: Benjamin Kaduk <bkaduk@akamai.com>
To: draft-ietf-tls-mlkem@ietf.org, tls-chairs@ietf.org, tls@ietf.org
Message-ID: <aSjSGfo2EG2+i2ov@akamai.com>
References: <aSdquOwZR8xKeVLt@akamai.com> <20251127110348.410183.qmail@cr.yp.to>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <20251127110348.410183.qmail@cr.yp.to>
X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.293,Aquarius:18.0.1121,Hydra:6.1.9,FMLib:17.12.100.49 definitions=2025-11-25_02,2025-11-27_02,2025-10-01_01
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 adultscore=0 mlxscore=0 suspectscore=0 malwarescore=0 spamscore=0 mlxlogscore=751 phishscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2510240000 definitions=main-2511270169
X-Proofpoint-GUID: 45hY1fErQ8GlF8tp3iCOYgWc2SMh7Nk6
X-Proofpoint-ORIG-GUID: 45hY1fErQ8GlF8tp3iCOYgWc2SMh7Nk6
X-Proofpoint-Spam-Details-Enc: AW1haW4tMjUxMTI3MDE3MCBTYWx0ZWRfXxr/MYiC7V7xg nfOP0/K0iV+snXa28QCCUzfPqp8PR79NJTlu6yNqPDZJ4qGcJhPpqvmPX3lXBxlTNhfDON3igBL xogDThC2csuY6GJec+71Aqhka90yPOpvgc5DSNff4XGXMNBFZ0BrEnDcWGJDti9hyqBxkEuYsWa bSmVuaeNojTRUvhcJ8bUPA4YzCdqZrtzmNjNrSU5hF5vWsb25IUTiMm1Gn+zz098SWiYaDRxjK2 nmhjL1onsF7iRWRG6B/mJjLYqmACwuO+wLT94uyzKEhtjGYYefzP5F8g+D2c1uSmeWehGTonxWC O77PUlPljx7eJ7yGiOqQjUHqg24zjDXriPHOsahbG1B8mqJiOk7ccHjyII5Pciosp/L2F8LNNF1 F5LH8T430KVF+TW3U/CECwlYDPhydw==
X-Authority-Analysis: v=2.4 cv=De8aa/tW c=1 sm=1 tr=0 ts=6928d21d cx=c_pps a=StLZT/nZ0R8Xs+spdojYmg==:117 a=StLZT/nZ0R8Xs+spdojYmg==:17 a=kj9zAlcOel0A:10 a=6UeiqGixMTsA:10 a=VkNPw1HP01LnGYTKEx00:22 a=8tPVeKGMo2tu1raoI8IA:9 a=CjuIK1q_8ugA:10 a=ZXulRonScM0A:10
X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.293,Aquarius:18.0.1121,Hydra:6.1.9,FMLib:17.12.100.49 definitions=2025-11-25_02,2025-11-27_02,2025-10-01_01
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 priorityscore=1501 suspectscore=0 impostorscore=0 bulkscore=0 phishscore=0 clxscore=1015 spamscore=0 adultscore=0 malwarescore=0 lowpriorityscore=0 classifier=typeunknown authscore=0 authtc= authcc= route=outbound adjust=0 reason=mlx scancount=1 engine=8.22.0-2510240001 definitions=main-2511270170
Message-ID-Hash: LTWLCIH3XXPVMUG3XY3ODB76GGTNLQ7R
X-Message-ID-Hash: LTWLCIH3XXPVMUG3XY3ODB76GGTNLQ7R
X-MailFrom: bkaduk@akamai.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-tls.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [TLS] Re: WG Last Call: draft-ietf-tls-mlkem-05 (Ends 2025-11-26)
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/INgh1tIvU6uoc4Bp36-iuBBIOH4>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tls>
List-Help: <mailto:tls-request@ietf.org?subject=help>
List-Owner: <mailto:tls-owner@ietf.org>
List-Post: <mailto:tls@ietf.org>
List-Subscribe: <mailto:tls-join@ietf.org>
List-Unsubscribe: <mailto:tls-leave@ietf.org>

(again not quoting the original due to the presence of a no-derived-works disclaimer)

Yes, I was indeed asking for the key-exchange timings, since those are a fairly well-defined and somewhat transferable metric.  However, once you have the value of the metric, you need to determine whether the difference in the metric is acceptable or not acceptable, and for that assessment the use-case and surrounding context are indespensible.  The numbers here suggest that only in a limited set of use-cases will the additional cost of hybrid have a chance of outweighing the risk to the security properties of the system.  Which presumably does not surprise either of us, but in particular the numbers here are *not* conclusive for all possible use cases and deployment contexts.

I don't think we can reasonably publish the document without including some discussion of when the suitable use-cases and deployment contexts might occur, though.

-Ben

v2.37.1 | Report a Bug | By Email | System Status