IETF Logo Mail Archive

[TLS] Re: Composite ML-DSA

Viktor Dukhovni <ietf-dane@dukhovni.org> Thu, 16 April 2026 05:52 UTC

Return-Path: <ietf-dane@dukhovni.org>
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 66715DD5B1F1 for <tls@mail2.ietf.org>; Wed, 15 Apr 2026 22:52:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1776318739; bh=HzQvOLCugdWZMn/vzOdGqoM/RHkEJ4XqUriTz0oL3BI=; h=Date:From:To:Subject:Reply-To:References:In-Reply-To; b=VbIvmXoOpdA8aKu04P5hciVNZMphW+e4yjCNPqnKXM1mel12pKpi2CqIOF0DV8W49 waFuy7gAIwH2orynuddbyBxO/g7Z001uDo1tWn9opsqhgR6yBnfgseUu7XlYvMrJP5 1fyiLcQFJjW3gPSF8NTVdgOqa7dq3+YNOe5ePfxE=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -4.398
X-Spam-Level:
X-Spam-Status: No, score=-4.398 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_MED=-2.3, 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 (1024-bit key) header.d=dukhovni.org
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 MAZSHbnifgM2 for <tls@mail2.ietf.org>; Wed, 15 Apr 2026 22:52:19 -0700 (PDT)
Received: from chardros.imrryr.org (chardros.imrryr.org [144.6.86.210]) (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 DD757DD5B1EC for <tls@ietf.org>; Wed, 15 Apr 2026 22:52:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=dukhovni.org; i=@dukhovni.org; q=dns/txt; s=f8320d6e; t=1776318728; h=date : from : to : subject : message-id : reply-to : references : mime-version : content-type : in-reply-to : content-transfer-encoding : from; bh=HzQvOLCugdWZMn/vzOdGqoM/RHkEJ4XqUriTz0oL3BI=; b=qvwZcpjhnp4mVPtUMhrqwN+CLa/DalCc+7S1VmjIh1jIYz8DwRhjcWMFJnJDfGjT9gG2J 6h0FngNtE+h38c6ZTtP5PdP4Lmt/H27CGX34G92w+ei0YCjWaTr34w2ExgsUIj+jXjzUfg+ QcbW4vT3u7jP57F1O9pKEovyDlKdFuE=
Received: by chardros.imrryr.org (Postfix, from userid 1000) id E58B9937704; Thu, 16 Apr 2026 15:52:08 +1000 (AEST)
Date: Thu, 16 Apr 2026 15:52:08 +1000
From: Viktor Dukhovni <ietf-dane@dukhovni.org>
To: tls@ietf.org
Message-ID: <aeB5CF8hmcy5ltYg@chardros.imrryr.org>
References: <CACsn0c=GDta824UF7uJ3nw_4U_rT=XhYOGHRemMWa+2AdbsiAg@mail.gmail.com> <3a16c7c4-345e-48ce-af70-a3bf503c8caf@app.fastmail.com> <CACf5n7_0hdeHJXXucva9pb=+pjhcgveHRpjA8XAcXB3LsYUvaw@mail.gmail.com> <CAFpG3gcC+UfO7E=ADGhwr2En5PwipZiq_r6_RdqvmT-5nnh2jw@mail.gmail.com> <d69ba150-0257-4e64-9abb-9229d03a03a6@app.fastmail.com> <PA0P264MB69259DDB3DA252DC57E4B4EBB6222@PA0P264MB6925.FRAP264.PROD.OUTLOOK.COM> <MN2PR17MB40311654550B8396E7AC238BCD222@MN2PR17MB4031.namprd17.prod.outlook.com> <PA0P264MB6925B21D490AD376437A1AA3B6222@PA0P264MB6925.FRAP264.PROD.OUTLOOK.COM> <SYCPR01MB366173C5FE49E8734A709062EE232@SYCPR01MB3661.ausprd01.prod.outlook.com> <aeB2ndUVkUb5Prxn@ubby>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
In-Reply-To: <aeB2ndUVkUb5Prxn@ubby>
Mail-Followup-To: <tls@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-ID-Hash: D57EASUXXMZA7AYUZIVFISVD3FQOUB5I
X-Message-ID-Hash: D57EASUXXMZA7AYUZIVFISVD3FQOUB5I
X-MailFrom: ietf-dane@dukhovni.org
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
Reply-To: tls@ietf.org
Subject: [TLS] Re: Composite ML-DSA
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/-5hcBRSBI733bE3sFF3vYqHzvvI>
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 16, 2026 at 12:41:49AM -0500, Nico Williams wrote:

> The composite is atomic.

Yes, that's how it should be.  This does of course make it difficult to,
say, have PKCS#11 wrap-up two smart-card readers, one for each key, as a
single logical composite smart-card, but that's a rather exotic
hypothetical use-case.  The requirement would now be a single smart-card
(or more capable hardware device) with a composite key.

-- 
    Viktor.  đŸ‡ºđŸ‡¦ Đ¡Đ»Đ°Đ²Đ° Đ£ĐºÑ€Đ°Ñ—Đ½Ñ–!

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