[lamps] Re: WG Last Call: draft-ietf-lamps-pq-composite-sigs-08 (Ends 2025-10-06)

Mike Ounsworth <ounsworth+ietf@gmail.com> Tue, 21 October 2025 02:29 UTC

Return-Path: <ounsworth@gmail.com>
X-Original-To: spasm@mail2.ietf.org
Delivered-To: spasm@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 0EB45792F97C for <spasm@mail2.ietf.org>; Mon, 20 Oct 2025 19:29:17 -0700 (PDT)
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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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=gmail.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 9GqbjIJATaJQ for <spasm@mail2.ietf.org>; Mon, 20 Oct 2025 19:29:16 -0700 (PDT)
Received: from mail-il1-x132.google.com (mail-il1-x132.google.com [IPv6:2607:f8b0:4864:20::132]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id C68F9792F8D1 for <spasm@ietf.org>; Mon, 20 Oct 2025 19:28:50 -0700 (PDT)
Received: by mail-il1-x132.google.com with SMTP id e9e14a558f8ab-424da17e309so54279185ab.2 for <spasm@ietf.org>; Mon, 20 Oct 2025 19:28:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1761013730; x=1761618530; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=09/H1uo4GNZXGTX55wEbI1HHQvrAb85ntSIrGhpqDfU=; b=RzNOLGokGtMaVZjsfdUQQX1i8QVmBMQAHCDhFRW5xyD82u5+2rOCIqzxWG+YN0bD2I +GR1dU4j9J6xbd72evXq+ViQndI/Tdu+nCoiQNNHSJYx6x2evkpge1K+sYSahLrVMQzy gCWQ8+mpc5beqMRrkRyrmvWqn2jgsZeMQfgVeHk5a5Q8h5jr1l6u6qUJp2mmqm7/1C8r NVMgx4TuC27qTVCVIducF3qfJLgdTSbikP0bbxRW7FBHz8JHvfTfT3sdtvhXHlJUA8Wy XLgelFLS2HKhyygXskWrHfoWeeCvt53UMeC8eXonjpcBZi+eKSWSemGuKp2R0gXa+Mbz u2XQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1761013730; x=1761618530; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=09/H1uo4GNZXGTX55wEbI1HHQvrAb85ntSIrGhpqDfU=; b=KwFLDnLozHyimBPLoIOKcw9uuBCo7Usy5vXfA+jopCs5HCB269l886cSbMXKUPnp/S LW1oT8ZkqxCe7TL8lsy2dJLz5gpD73Tynl8VOkW7fz9F7n3XdAcFa3ial2Z49vaWvLPC ovTTNJo/MFVtsoKfpEytZpHj3DtfgcsIzVCk2x53TyYEqR+JKrZ5RC3hzbDC+QPY4q6g ysHbMSivvzPzy/PBLY4GjXxxvdcbcKeZoTHswCVskn9eE9CqzynZkx/LmSiRCg5zx9xz relZ8XOTZ4w62SwgDYNbsiV66ml+DP6l2SO5iF521ffMQOZVZNHQlibCp1Fi1vJP83Ld x5rQ==
X-Forwarded-Encrypted: i=1; AJvYcCX5R7DBMcJEWmMaL/bgU1cZb4zChCGuQiuoE+PtavOzOH617h1vCafsro9a05W/C4GEarBcLw==@ietf.org
X-Gm-Message-State: AOJu0YywhbWbux16ZrJEuBaqUc2LVWB7XW35o2P4qrv2aixnJCV46Xw5 DmdP5XXaOrEgRyTT43AFe+5NhHyPm7ND/EHybXwBKNUFxwnS45seKzf7u8Xovl1Vk+hgsAUApKX 2nGUdk43MMRQJ652WxI4ZOanNe24eSDjN99KI
X-Gm-Gg: ASbGnct5GsmYS1fiaiRNxUj3aFGKNdBb2yboVavBrryWwkRn3kqGKaG3t7ROaeIVCcK p/D4s54Tq7zSK9IFKRy6brgOF+1YMJzCVnAMtc4fl8zFfWQHxDgEUbRXFn9Fu1HiIz0kYUjRY28 I503UnI04JN1vzONueWQG3ahrp8E6ry+O6miubMadQMZQUc3VtwXBYQFyPTcXUPouvEjPxnT1Hq QPa1/bQVgzGStFZ61iJW1HNj8gn/4zqRwJaxzKTnZs9yWJaPXgzSUZ6AjTfMoI8dFBhgfna
X-Google-Smtp-Source: AGHT+IHY/Awn3YT3z/MF1cukOEFsSMHhMQg9pfXL78fxi76ELuBHGItaVGYk5uPR2pa1YvqgOuuxZmtM8Nbr4WkAY14=
X-Received: by 2002:a05:6e02:2301:b0:430:c046:5428 with SMTP id e9e14a558f8ab-430c5268df3mr40804275ab.17.1761013729899; Mon, 20 Oct 2025 19:28:49 -0700 (PDT)
MIME-Version: 1.0
References: <175855620751.648048.16646357165291761730@dt-datatracker-6c6cdf7f94-h6rnn> <A2A9D21F-EF4D-4F1F-81A2-7552A883BE4B@vigilsec.com> <C1ABC7C4-F718-4B12-8C1A-E1AA0135FC1B@vigilsec.com> <701BF3EE-57FC-4B17-80C2-30AA138836CB@vigilsec.com> <55bfe95f-9086-42d6-bbfd-005fbe783331@bouncycastle.org> <6708600F-60D6-4021-A53C-8C03478302B6@vigilsec.com> <2FADE50D-2A66-470C-B47A-EB823C1C5902@vigilsec.com>
In-Reply-To: <2FADE50D-2A66-470C-B47A-EB823C1C5902@vigilsec.com>
From: Mike Ounsworth <ounsworth+ietf@gmail.com>
Date: Mon, 20 Oct 2025 21:28:38 -0500
X-Gm-Features: AS18NWDjG_7xwIezjwVE0fjRpcfMaKmS413JjI2VPHwkX1_Id2Y4Z8jOQmD2k00
Message-ID: <CAKZgXHqgGJeXVJcYfvkKe1gSpDWyjsg6=2Pqq+NXHOpfhP-Rkg@mail.gmail.com>
To: Russ Housley <housley@vigilsec.com>
Content-Type: multipart/alternative; boundary="000000000000d0b9980641a1f5cb"
Message-ID-Hash: 6NFJTWXWACRFFNI63M37ODGM7CD65QOW
X-Message-ID-Hash: 6NFJTWXWACRFFNI63M37ODGM7CD65QOW
X-MailFrom: ounsworth@gmail.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-spasm.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: David Hook <dgh@bouncycastle.org>, spasm@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [lamps] Re: WG Last Call: draft-ietf-lamps-pq-composite-sigs-08 (Ends 2025-10-06)
List-Id: This is the mail list for the LAMPS Working Group <spasm.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/SUdBnkn7mQ_oyL-Ha-2dw1pvytQ>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Owner: <mailto:spasm-owner@ietf.org>
List-Post: <mailto:spasm@ietf.org>
List-Subscribe: <mailto:spasm-join@ietf.org>
List-Unsubscribe: <mailto:spasm-leave@ietf.org>

I updated the OIDs in the draft. This is fiddly copy&paste work, so I would
like at least one other pair of eyes to double-check that I didn't make a
typo before I push to datatracker.

Pull Request:
https://github.com/lamps-wg/draft-composite-sigs/pull/308/files

Rendered HTML page:
https://lamps-wg.github.io/draft-composite-sigs/draft-ietf-lamps-pq-composite-sigs.html


On Mon, 20 Oct 2025 at 17:26, Russ Housley <housley@vigilsec.com> wrote:

> Here is the corrected list:
>
> 37 id-MLDSA44-RSA2048-PSS-SHA256 [draft-ietf-lamps-pq-composite-sigs-12]
> 38 id-MLDSA44-RSA2048-PKCS15-SHA256
> [draft-ietf-lamps-pq-composite-sigs-12]
> 39 id-MLDSA44-Ed25519-SHA512 [draft-ietf-lamps-pq-composite-sigs-12]
> 40 id-MLDSA44-ECDSA-P256-SHA256 [draft-ietf-lamps-pq-composite-sigs-12]
> 41 id-MLDSA65-RSA3072-PSS-SHA512 [draft-ietf-lamps-pq-composite-sigs-12]
> 42 id-MLDSA65-RSA3072-PKCS15-SHA512
> [draft-ietf-lamps-pq-composite-sigs-12]
> 43 id-MLDSA65-RSA4096-PSS-SHA512 [draft-ietf-lamps-pq-composite-sigs-12]
> 44 id-MLDSA65-RSA4096-PKCS15-SHA512
> [draft-ietf-lamps-pq-composite-sigs-12]
> 45 id-MLDSA65-ECDSA-P256-SHA512 [draft-ietf-lamps-pq-composite-sigs-12]
> 46 id-MLDSA65-ECDSA-P384-SHA512 [draft-ietf-lamps-pq-composite-sigs-12]
> 47 id-MLDSA65-ECDSA-brainpoolP256r1-SHA512
> [draft-ietf-lamps-pq-composite-sigs-12]
> 48 id-MLDSA65-Ed25519-SHA512 [draft-ietf-lamps-pq-composite-sigs-12]
> 49 id-MLDSA87-ECDSA-P384-SHA512 [draft-ietf-lamps-pq-composite-sigs-12]
> 50 id-MLDSA87-ECDSA-brainpoolP384r1-SHA512
> [draft-ietf-lamps-pq-composite-sigs-12]
> 51 id-MLDSA87-Ed448-SHAKE256 [draft-ietf-lamps-pq-composite-sigs-12]
> 52 id-MLDSA87-RSA3072-PSS-SHA512 [draft-ietf-lamps-pq-composite-sigs-12]
> 53 id-MLDSA87-RSA4096-PSS-SHA512 [draft-ietf-lamps-pq-composite-sigs-12]
> 54 id-MLDSA87-ECDSA-P521-SHA512 [draft-ietf-lamps-pq-composite-sigs-12]
>
> (No numbers skipped)
>
> Russ
>
>
> On Oct 20, 2025, at 3:47 PM, Russ Housley <housley@vigilsec.com> wrote:
>
> I hav arranged for early assignments in this registry:
> https://www.iana.org/assignments/smi-numbers/
>
> 37 id-MLDSA44-RSA2048-PSS-SHA256 [draft-ietf-lamps-pq-composite-sigs-12]
> 38 id-MLDSA44-RSA2048-PKCS15-SHA256
> [draft-ietf-lamps-pq-composite-sigs-12]
> 39 id-MLDSA44-Ed25519-SHA512 [draft-ietf-lamps-pq-composite-sigs-12]
> 40 id-MLDSA44-ECDSA-P256-SHA256 [draft-ietf-lamps-pq-composite-sigs-12]
> 41 id-MLDSA65-RSA3072-PSS-SHA512 [draft-ietf-lamps-pq-composite-sigs-12]
> 42 id-MLDSA65-RSA3072-PKCS15-SHA512
> [draft-ietf-lamps-pq-composite-sigs-12]
> 43 id-MLDSA65-RSA4096-PSS-SHA512 [draft-ietf-lamps-pq-composite-sigs-12]
> 44 id-MLDSA65-RSA4096-PKCS15-SHA512
> [draft-ietf-lamps-pq-composite-sigs-12]
> 45 id-MLDSA65-ECDSA-P256-SHA512 [draft-ietf-lamps-pq-composite-sigs-12]
> 46 id-MLDSA65-ECDSA-P384-SHA512 [draft-ietf-lamps-pq-composite-sigs-12]
> 47 id-MLDSA65-ECDSA-brainpoolP256r1-SHA512
> [draft-ietf-lamps-pq-composite-sigs-12]
> 48 id-MLDSA65-Ed25519-SHA512 [draft-ietf-lamps-pq-composite-sigs-12]
> 49 id-MLDSA87-ECDSA-P384-SHA512 [draft-ietf-lamps-pq-composite-sigs-12]
> 50 id-MLDSA87-ECDSA-brainpoolP384r1-SHA512
> [draft-ietf-lamps-pq-composite-sigs-12]
> 51 id-MLDSA87-Ed448-SHAKE256 [draft-ietf-lamps-pq-composite-sigs-12]
> 52 id-MLDSA87-RSA3072-PSS-SHA512 [draft-ietf-lamps-pq-composite-sigs-12]
> 52 id-MLDSA87-RSA4096-PSS-SHA512 [draft-ietf-lamps-pq-composite-sigs-12]
> 54 id-MLDSA87-ECDSA-P521-SHA512 [draft-ietf-lamps-pq-composite-sigs-12]
>
> Note that I somehow skipped 53 in my request to IANA.
>
> Russ
>
> On Oct 19, 2025, at 3:05 AM, David Hook <dgh@bouncycastle.org> wrote:
>
>
> I'd just like to congratulate the authors of composite sigs on lasting the
> distance. This one has been quite a long haul!
>
> Speaking as someone who has found themselves with a number of users who
> are extremely keen to start deploying solutions based on this, I note the
> draft is still using the test OIDs, is anyone able to tell me when we'll
> see the IANA OIDs get allocated?
>
> Thanks,
>
> David
>
> On 18/10/25 06:26, Russ Housley wrote:
>
> It looks to me like we have reached consensus.  I will start the write-up
> to request publication.  Authors, each of you will need to reply to confirm
> that parts of the write-up are correct.
>
> For the LAMPS WG chairs,
> Russ
>
>
> On Oct 14, 2025, at 2:46 PM, Russ Housley <housley@vigilsec.com> wrote:
>
> No one raised any new issues.  With the posting of -12, the authors
> believe that the two open issues have been resolved.
>
> If you do not agree that the two open issues have been resolved, please
> speak now.
>
> Russ
>
> On Oct 8, 2025, at 4:41 PM, Russ Housley <housley@vigilsec.com> wrote:
>
> I have read the many messaged on this WG Last Call.  I believe that all of
> the issues that have been raise have reached rough consensus, except two.
>
> First, the discussion of EUF-CMA vs SUF-CMA has not yet reached closure.
>
> Second, there are disagreements about the proposed wording for the
> RECOMMENDED private key format.
>
> In the Datatracker, I have set the state to:
> State: In WG Last Call
> Tag: Revised I-D Needed - Issue raised by WGLC
>
> The intent is to allow time for the unresolved topics to continue being
> discussed.
>
> I know that we do not have 100% agreement on every detail.  However, If
> you see other items that need further discussion, please speak now.
>
> For the LAMPS WG chairs,
> Russ
>
>
> On Sep 22, 2025, at 11:50 AM, Russ Housley via Datatracker <
> noreply@ietf.org> wrote:
>
>
> Subject: WG Last Call: draft-ietf-lamps-pq-composite-sigs-08 (Ends
> 2025-10-06)
>
> This message starts a 2-week WG Last Call for this document.
>
> Abstract:
> This document defines combinations of ML-DSA [FIPS.204] in hybrid
> with traditional algorithms RSASSA-PKCS1-v1.5, RSASSA-PSS, ECDSA,
> Ed25519, and Ed448.  These combinations are tailored to meet security
> best practices and regulatory guidelines.  Composite ML-DSA is
> applicable in any application that uses X.509 or PKIX data structures
> that accept ML-DSA, but where the operator wants extra protection
> against breaks or catastrophic bugs in ML-DSA.
>
> File can be retrieved from:
> https://datatracker.ietf.org/doc/draft-ietf-lamps-pq-composite-sigs/
>
> Please review and indicate your support or objection to proceed with the
> publication of this document by replying to this email keeping
> spasm@ietf.org
> in copy. Objections should be motivated and suggestions to resolve them are
> highly appreciated.
>
> Authors, and WG participants in general, are reminded again of the
> Intellectual Property Rights (IPR) disclosure obligations described in BCP
> 79
> [1]. Appropriate IPR disclosures required for full conformance with the
> provisions of BCP 78 [1] and BCP 79 [2] must be filed, if you are aware of
> any. Sanctions available for application to violators of IETF IPR Policy
> can
> be found at [3].
>
> Thank you.
>
> [1] https://datatracker.ietf.org/doc/bcp78/
> [2] https://datatracker.ietf.org/doc/bcp79/
> [3] https://datatracker.ietf.org/doc/rfc6701/
>
>
>
> _______________________________________________
> Spasm mailing list -- spasm@ietf.org
> To unsubscribe send an email to spasm-leave@ietf.org
>
>
>
> _______________________________________________
> Spasm mailing list -- spasm@ietf.org
> To unsubscribe send an email to spasm-leave@ietf.org
>
>
>
> _______________________________________________
> Spasm mailing list -- spasm@ietf.org
> To unsubscribe send an email to spasm-leave@ietf.org
>