[TLS] Re: New Liaison Statement, "Liaison communication to IETF regarding draft-ietf-tls-mlkem"

Nico Williams <nico@cryptonector.com> Thu, 09 April 2026 05:01 UTC

Return-Path: <nico@cryptonector.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 3836DD88166E for <tls@mail2.ietf.org>; Wed, 8 Apr 2026 22:01:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1775710919; bh=RWTfgyIQd6cb4+LuQ0KYEwmqrZN3FKkQmmawQjLMlNE=; h=Date:From:To:Subject:References:In-Reply-To; b=kqCvF7EN6+c+y7MJFBVx/zYfxkzeczggAZPW33OQE2XfbiYF+A7jSBf6U+suU8LJz IWFU9CRwXUICY0uqT2e4giEh4Qs7iDAqQ17dLw/+ZnDcVKnPXMcRrPI7Ml8TeP38Ne fPweFfJiJTQ/4Mr+88kV/ifWmFR0uYXQc9ge6Z5o=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=cryptonector.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 lhUj60LKOMBv for <tls@mail2.ietf.org>; Wed, 8 Apr 2026 22:01:58 -0700 (PDT)
Received: from dormouse.pear.relay.mailchannels.net (dormouse.pear.relay.mailchannels.net [23.83.216.50]) (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 B0F8CD881669 for <tls@ietf.org>; Wed, 8 Apr 2026 22:01:58 -0700 (PDT)
X-Sender-Id: dreamhost|x-authsender|nico@cryptonector.com
Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id 17AF040130B; Thu, 09 Apr 2026 05:01:51 +0000 (UTC)
Received: from pdx1-sub0-mail-a227.dreamhost.com (100-102-32-37.trex-nlb.outbound.svc.cluster.local [100.102.32.37]) (Authenticated sender: dreamhost) by relay.mailchannels.net (Postfix) with ESMTPA id B8993401C9F; Thu, 09 Apr 2026 05:01:50 +0000 (UTC)
ARC-Seal: i=1; a=rsa-sha256; d=mailchannels.net; s=arc-2022; cv=none; t=1775710910; b=kq0/loYcYWxHf9aKHOhlASFjifDSt6G8xMdqxj1vjLMD7HkCbQczn28McqitQgV6TCRe4i 0VSu7PSVXqtbn4ySHQZhBmEQZ1aOGKNB4FCsz2KAjkPYkT38n00zlgvHgaNy5wLkmvk9PV bc6UBwS0AY1hSFOXysepruTYfO1T2L8nwbZjicmin46RrzXuL7bJvbYFq8wqLW7OLv7f6X 1f5dPTKcPB3QkpbTbfsbbGYjyV1bua19gbjvFhUN8zy2miHlIKH9PXLXyG+Bn55StKcEz3 Ikouob7nmvMX+0hDhPmoVdSIuYkKlnrJuVu0kKVzoy8f4+UXeoIR8MoOXkiapw==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=mailchannels.net; s=arc-2022; t=1775710910; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:dkim-signature; bh=EdjiVq2v76y8VnTDLRNrFr43QKxYv1T+nLsptCz8SLY=; b=12AUlIns6w1lphmXQysBU4jE1hHzqsrMUE1UX+0Ixrl91rHRh2BkFBr5AOef7rrxXgDsJ4 YtGTDKKDIXJ4sW0y0YQKp0ZExhHG9BG7ugzAv6Pp7IMBQMJC9Mc8oCmNXYtE3JNcMK/WyN 7/d4oRtC1tPM23R+UXtC1MzXH5duDSYc12LBQQCTlB3ZljgGk86bcK6traPYyr0K7tIk1U wxvn8hvdDU0Ip0dG4VwBzpe3T00G3enV52jBfL6qStsezzJMCd4cLzhHMsl0W8tiyyz5/b nsDNCDxyZeeQ4P1pv+cPNl0IHKyTs7/uy5Gi71tDm6f/r4s3oVRitpMTmf4qdw==
ARC-Authentication-Results: i=1; rspamd-6c65dd77f-ffgk6; auth=pass smtp.auth=dreamhost smtp.mailfrom=nico@cryptonector.com
X-Sender-Id: dreamhost|x-authsender|nico@cryptonector.com
X-MC-Relay: Good
X-MailChannels-SenderId: dreamhost|x-authsender|nico@cryptonector.com
X-MailChannels-Auth-Id: dreamhost
X-Interest-Hook: 1fd47d26400fac3f_1775710910952_3443616048
X-MC-Loop-Signature: 1775710910952:3903750390
X-MC-Ingress-Time: 1775710910951
Received: from pdx1-sub0-mail-a227.dreamhost.com (pop.dreamhost.com [64.90.62.162]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384) by 100.102.32.37 (trex/7.1.5); Thu, 09 Apr 2026 05:01:50 +0000
Received: from ubby (unknown [75.81.95.64]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by pdx1-sub0-mail-a227.dreamhost.com (Postfix) with ESMTPSA id 4frnpk2BRzz2l; Wed, 8 Apr 2026 22:01:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cryptonector.com; s=dreamhost; t=1775710910; bh=EdjiVq2v76y8VnTDLRNrFr43QKxYv1T+nLsptCz8SLY=; h=Date:From:To:Subject:Content-Type:Content-Transfer-Encoding; b=tI9vag9CZtL2YalkJKKseKh42K2PXNIsUn9VSdCGgDd5rILs9s6G8uZ0wj4jA2Ezh U583mAhFV4pCT/Ho7Y5PPDikHkNUz6pfbYPDc+bwiWYIjI3fcz0UvPSuRwUuhiBwC9 zva6ozL4q1txeO7b4berPgjs4cqshW4Rg9hWipaqNPyFWUxXap769l37UekBmpdH6h iOLtiemVM2xp5C9dilvglRkioOLHgDwzcc06Vyr968UBB5nQqoexXg8LSy/LZBEc6q yQfJSd4f1Bx7+GvHi7TzNjheZllCkyGjMG92ZmdaGPlSV9UTnDj3EG/etBJpMZ/Too YPFe1/dGhm7Uw==
Date: Thu, 09 Apr 2026 00:01:48 -0500
From: Nico Williams <nico@cryptonector.com>
To: tls@ietf.org
Message-ID: <adcyvLVb+JAHBeuP@ubby>
References: <CABcZeBM-eoqh+kJ7H6SiwC9p4tKAt+YiQhzetJZJmPNpXc+5OA@mail.gmail.com> <CAF8qwaALDXR6d=jLD46wXmKHDjyj=OdJ1X3a1AgxF+ByQceeMg@mail.gmail.com> <CABcZeBO0ysBjtbiPuSboP4fAATuVHQxq1TA5TbQ+_Oy-NrET0g@mail.gmail.com> <7A4F9775-8929-469D-B454-B027A0BAFA69@vigilsec.com> <CABcZeBPk3fdfPw=S_f5v2E9Y1LUfQL8f6sKvTYG0R6qRHm6rgg@mail.gmail.com> <b1527204-149e-6979-a344-8d530613e979@nohats.ca> <24a09e13-ad76-4af2-9e2c-27f1c2282b02@cs.tcd.ie> <adXVIdmIOG8SonlM@chardros.imrryr.org> <CH2PR17MB4022FAA970DA4E497AA75AC6CD5BA@CH2PR17MB4022.namprd17.prod.outlook.com> <adcutmQqdmhtJvaH@chardros.imrryr.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <adcutmQqdmhtJvaH@chardros.imrryr.org>
Message-ID-Hash: FJNWL3SHTI24PNA3FEWAJ6QIT6OBL7GQ
X-Message-ID-Hash: FJNWL3SHTI24PNA3FEWAJ6QIT6OBL7GQ
X-MailFrom: nico@cryptonector.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: New Liaison Statement, "Liaison communication to IETF regarding draft-ietf-tls-mlkem"
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/YihXEP3UVRIX8hIq3LiO2PBfJsc>
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>

On Thu, Apr 09, 2026 at 02:44:38PM +1000, Viktor Dukhovni wrote:
> I don't see it as sufficient for a "rough" consensus that both:

What?  "don't"?

>     - The technical specification is sound, **AND**
>     - The security considerations adequately cover the questions
>       that implemtnations and users need to consider.
> 
> -- 
>     Viktor.  🇺🇦 Слава Україні!
> 
> _______________________________________________
> TLS mailing list -- tls@ietf.org
> To unsubscribe send an email to tls-leave@ietf.org