[Ietf-dkim] Re: PQC Threat Model statement

Wei Chuang <weihaw@google.com> Sun, 25 October 2026 01:11 UTC

Received: from mail-qt1-x830.google.com (mail-qt1-x830.google.com [IPv6:2607:f8b0:4864:20::830]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519 server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by mx.ietf.org (Postfix) with ESMTPS id BE82946 for <ietf-dkim@ietf.org>; Sun, 25 Oct 2026 01:11:23 +0000 (UTC)
Authentication-Results: mx.ietf.org; dkim=pass header.d=google.com header.s=20251104 header.b=ZIkFpccC; dmarc=pass (policy=reject) header.from=google.com; spf=pass (mx.ietf.org: domain of weihaw@google.com designates 2607:f8b0:4864:20::830 as permitted sender) smtp.mailfrom=weihaw@google.com; arc=pass ("google.com:s=arc-20260327:i=1")
Received: by mail-qt1-x830.google.com with SMTP id d75a77b69052e-536c13893adso31cf.0 for <ietf-dkim@ietf.org>; Sat, 24 Oct 2026 18:11:23 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; t=1792890677; cv=none; d=google.com; s=arc-20260327; b=dZJ3asGGBDG4ENm6up1XOyGFmCAZ+AhM2qf+6vWOyoi97jsQczNDr2Z1HrUrqHsPGI oVQMPKfDiHgKW7HbUt/yAxqEwd7wjOWFEu8w7ww7Rh8FHLOZbqdd2sQ9DnubVApF4AL2 EnhDgSU4k3o396gmYeIKEWzXUgIZlKlXfTe0nTWNY/OD2B9S5gqR8slnHb0Tfxs8rX4H jkrpqw5XTgr7fK4XOuBq5lhfS/UXR4yKXnU2PJKrpmAlZhFe6TwwkOE92n8sm2EryZit Qxw9YloqPVzweFKBjpHN8IRoa1fnIYSjqFqIlir9MUk2872s1DfTx8AZgwlZe/6MfaHr UXEg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20260327; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:dkim-signature:message-instance:dkim2-signature; bh=eJHMH9A557lvUhYXl6RgURjiRGhPL5f+WO3ErueYPmY=; fh=0N/EcF8qcDo4fvM5yHAzA1yQA7VJ7JgPBT17NmtvZag=; b=ifb6A/Kbu5zmdZmOLwrgYe3+vUfZWmnHGGlO+7qHum7cn2ozF8ClOKP8v1vCBOA9/H GodI6wXZX9vINwYcz99c4VdsOFXZN/+pwV4JiZW2NGY1C4S93MmGlVOaBTw5fp8HZy0P /ZGtuHUNxubY9h/EK682b8OoggkdQxHbIZJd9mXZk5DNPJDS4DSX4gDW6KG4nUFs5K4a uk5UQWPRn9RirE2HU9quR35pA1ikToua9bPz48/A+XS1Prw5xhYKPfBkiPwuktN5rvG2 L0uxJ9/u8igjJ/FQPAmVnznNGodtrs8rqHc6vfLTEymAJJMEBcfNE6GWVHAiMlHsGKRK MwxA==; darn=ietf.org
ARC-Authentication-Results: i=1; mx.google.com; arc=none
DKIM2-Signature: i=1; m=1; t=1792890677; d=google.com; mf=PHdlaWhhd0Bnb29nbGUuY29tPg==; rt=PGlldGYtZGtpbUBpZXRmLm9yZz4=; s=20251104:rsa-sha256:CleESytmPuOY2lhHChm1NT0lJC0yLWobW1C6DSRkxYSiN93bQwCcp5fjp/UtYYzPlqomey3NR/0zMeVJ3Iuz3DPw6W12/fVyIhNIqvWHuf28a1P0EUAIDu82MxfHHaTpCP3RldkdHa2DVEos0nloc2uCF3Wpvv3cNRpCLX5UBL7tlr40n6o6LSp876PRWJgPC/uKKmqXcxvpYqPGelmwmnRCIpMAHbC5hm9PHfCFfIio5wlUZVHCB/oaL7JXnAsBmfHtGwTJruuu+QwoBqEkS4XJR2yD3gG8i/SBz1KPfsaIDpVh5o/5DmaAJZfdYcvFX4K/DSv6MTFwRvSafKlJXQ==;
Message-Instance: m=1; h=sha256:0gzPgoI0WP10Kl8LlV+PWs2xjcZ6h69KcReTfaZ6xKI=:xUEXfRngIIPsPKfo7O7FrKQo57VYP1KkkmkpHxTLgtQ=;
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20251104; t=1792890677; x=1793495477; darn=ietf.org; h=content-type:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:from:to:cc:subject:date:message-id:reply-to :content-type; bh=eJHMH9A557lvUhYXl6RgURjiRGhPL5f+WO3ErueYPmY=; b=ZIkFpccCB5voRs0mvLrPQtAN0X3bTto7ZUtcJBLq1Ose4FAMGukty/zL2xrSUnLUJp A4i51xhX/3fwVZhPDKXrP5XhDQc4ZAi21mHGEKFf+kvkJsV5ZMBvvoy+oRC5nImTRkiI tJHAF8O7PfgKUiWwK9ruG84QJLzftJBDE8dATs+CzigCs4imayT9icBVIqrMVJnsSBPX Og+MYbHPaNz5SQ2ZWqsZWaH1ISVBcD24DppZ55U9g1B5r/1LO6TXX3CxShHZPsQY45EJ +wS0HG1t6NDTC4SyFUOAY/dm4k4zcICwQaCAFZVbKCXhgLe0MzztFFOKWaLeHRrRR7R9 7YZw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20260707; t=1792890677; x=1793495477; h=content-type:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:x-gm-gg:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to:content-type; bh=eJHMH9A557lvUhYXl6RgURjiRGhPL5f+WO3ErueYPmY=; b=VYpNRGiiDijvvNS1BgsTy0sESb6sB/pkj95QQ9s+vUbHI8pbY9gHdq5BJzXUPtNPvm +O0QuWyl+y1q8KUQeJHudUH5D2SeJ+KeboprPtNRpznXRxONX22RWU+nATeb/ciVb/BB YhvVmKcTF+4MbqWpqgdGBk//HTeHDBp5GZsLJY3FvrKgTNZs+jN72Mh/x2Cr3zwVfvav 2OOLL10YS7xRRutakGqxZQg0C86efwWQF/lBuId6EHmhCz+p1p48puHfvQfrLPnoS5xm U0qsXgz9jskyqFRH0ycwqIE8HsD9eK2xdJ/LG3WM3IhYO90BiLLiEW8bK9nRDhka0NSW 0vtA==
X-Gm-Message-State: AFq9FYLn6L/yMUoS4dN3OjHooffo1RdwJALV05JUkuR69ke82VNKEzfN 3+QsAZvfPYKQ1O+antejGsaliZrrT4UeJm87s29SfhPUws4vbD8+kyBvJpZl+dbBFi79vLH/xJV X9ekn843nqQcfSQkl58HaS0m+d9E8dqoVk9c3HqMa7dTkcoEky1SU44VD
X-Gm-Gg: AYBFou1RAzHMtVkCbDdJwEuMWeb4KpdQAHNqkKuH1lybN7yNTbxNbVaoZ8doZq7tv0K HjLh5r2oCnKSJEVZ9wsWRClU+kB4OeHHFrXAgI7OoZ67+yfxfEUA/RWqvFI5+iL5pc9nnmNrsrB QeSWujvIyJKRTns+yZJxDPiAZJpPMfRmjUs+gcZ4ts7FyUenaV8Ym7VgQZVewUNOwztpLp04uFS bYIXF+hTupyd90RZcrqIn2NizFtPZBQFKBJN18HkGlQWcATocAbdXafu2cdrs1oa7XXZIiMbe9t 3sOGwy5MKtU5rvxFAd5ofxbLS+eH3x0T7O0Oeih4mvniWbFjHMEmffUY4LE/psV8s+JBdWzDtHV xrHY3LO4K3Z0mp8X7RQl7dOQnMXDQjHCDaw+zP7vSa74kpImyMp9DyltrShMy7zBhLgdX0x0Mv+ xnUSmWsD7kLfMjfBEZ/vSc1Fxub2P+PIkuJgdu2LzyS6u6rQaM2bc7FBpjqf71CphUZb562Is=
X-Received: by 2002:a05:622a:ea01:20b0:538:ba0f:5ee0 with SMTP id d75a77b69052e-53bf46e3e23mr1701cf.2.1792890675722; Sat, 24 Oct 2026 18:11:15 -0700 (PDT)
MIME-Version: 1.0
References: <CAAFsWK3DawKLZ1zvxjSTDDzqy+40Rnqzzd2Sxa-t8Hv2Rk8mKw@mail.gmail.com> <CAL0qLwYN4dCtAZdm8ENpCvL7Rd6SPn3PGt+mDSc-EcE47rgrmw@mail.gmail.com> <CAAFsWK30uVwBg+bHFNJp610FU3PeuvXYDsY4evJCFFN97kta8g@mail.gmail.com> <20260728153833.438991176CEE2@ary.qy> <61149c8f-821f-4d3d-9af9-2e5fa4114331@1und1.de> <CAAFsWK18kDkrTd0775r4xfjCSBEMzmXnTdBbWRHopEm81gh0VA@mail.gmail.com> <CAAFsWK1mShO6UoouRXPwABJXbbtWiom7Tbh5SqMv5jBMuieESQ@mail.gmail.com> <1D3101F2-1DCC-4E76-B5BC-FE93AF82AEE7@stalw.art> <CAAFsWK2B9eUfc7hWCF-PppDakeh0QAkYvC6k18JjiX=hZR-NuA@mail.gmail.com> <EED72F8C-9BCF-436A-919D-01B395453795@stalw.art>
In-Reply-To: <EED72F8C-9BCF-436A-919D-01B395453795@stalw.art>
From: Wei Chuang <weihaw@google.com>
Date: Sat, 24 Oct 2026 18:11:03 -0700
X-Gm-Features: AclHuK_h938IPYzdX0S2VUY818MaUZdKzFL_bmlh8eYSAnWMY1AS8yGhXjvpnDs
Message-ID: <CAAFsWK3W9_d_yg6MwHTtJFB-mkp1v_kTgsOpbg+whKM7p4dq1g@mail.gmail.com>
To: Mauro De Gennaro <mauro@stalw.art>
Content-Type: multipart/alternative; boundary="000000000000d9c7c9065e9fe345"
X-Spamd-Bar: --------------------------
Message-ID-Hash: DVMVQDCEXZUAQUJG3PEOIIPSYUZAOE6K
X-Message-ID-Hash: DVMVQDCEXZUAQUJG3PEOIIPSYUZAOE6K
X-MailFrom: weihaw@google.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; header-match-ietf-dkim.ietf.org-0; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: ietf-dkim@ietf.org
X-Mailman-Version: 3.3.10
Precedence: list
Subject: [Ietf-dkim] Re: PQC Threat Model statement
List-Id: IETF DKIM List <ietf-dkim.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-dkim/EK6IXbPe_OAYkyQSDBoOJp5jZ1M>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-dkim>
List-Help: <mailto:ietf-dkim-request@ietf.org?subject=help>
List-Owner: <mailto:ietf-dkim-owner@ietf.org>
List-Post: <mailto:ietf-dkim@ietf.org>
List-Subscribe: <mailto:ietf-dkim-join@ietf.org>
List-Unsubscribe: <mailto:ietf-dkim-leave@ietf.org>

Thanks Mauro.  As I recall the main direction
<https://meetecho-player.ietf.org/playout/?session=IETF-DKIM-20261021-2000>
seems to be supporting multiple signatures for handling the composite
structure.  How that would be done wasn't resolved.  I suspect this will
all come back for another round of discussion at IETF-127.
-Wei

On Thu, Oct 22, 2026 at 10:46 AM Mauro De Gennaro <mauro=
40stalw.art@dmarc.ietf.org> wrote:

> Hi Wei,
>
> Yes, I'm okay with that. If the group decides to go with
> mldsa44-ed25519-sha512, documenting the processing in an Internet-Draft
> makes sense.
>
> Unfortunately I wasn't able to join the interim meeting, but I'll catch up
> with the emails on the list now.
>
>
> Best,
> Mauro
>
> On 21 Oct 2026, at 06:46, Wei Chuang <weihaw=40google.com@dmarc.ietf.org>
> wrote:
>
> Many thanks for implementing and describing the processing Mauro.  If
> after the interim, the WG wants to pursue mldsa44-ed25519-sha512, and
> you're okay with it, I propose this example gets documented as an
> Internet-Draft, so that there is common documentation to follow.  Plus it
> can be further security reviewed, and can exactly specify the key format.
> Thanks again.
> -Wei
>
> On Mon, Oct 19, 2026 at 7:41 AM Mauro De Gennaro <mauro=
> 40stalw.art@dmarc.ietf.org> wrote:
>
>>
>>
>> > One other point here, is that we should try at least one interop
>> experiment with the PQC algorithm, whether it's composite
>> mldsa44-ed25519-sha512 or mldsa44-sha512.   This choice should be discussed
>> at the interim Wednesday.
>> > -Wei
>>
>>
>> Some implementation experience that may help before Wednesday's interim:
>>
>> I have implemented mldsa44-ed25519-sha512 in mail-auth, the Rust library
>> behind Stalwart's DKIM2 support, as part of updating it to
>> draft-ietf-dkim-dkim2-spec-07. It is available for interop testing in the
>> mail-auth playground at https://mail-auth.stalw.art, where you can
>> generate keys, sign and verify messages with rsa-sha256, ed25519-sha256 and
>> mldsa44-ed25519-sha512. I am happy to share keys and test messages with
>> anyone who wants to try it against their own implementation.
>>
>> On the "implementing your own crypto" concern: I did not have to
>> implement any primitive myself. ML-DSA-44 and Ed25519 come from AWS-LC
>> (and, in a second backend, from the RustCrypto ml-dsa and ed25519-dalek
>> crates). The composite part from draft-ietf-lamps-pq-composite-sigs is only
>> the construction of M' (a fixed prefix, the label, the context length and
>> context, and the SHA-512 pre-hash) plus splitting and concatenating keys
>> and signatures. Both backends pass the test vectors in Appendix E of the
>> LAMPS draft. The one library feature it needs is pure ML-DSA with a
>> caller-supplied context string, since the LAMPS label is used as the ML-DSA
>> context. AWS-LC supports that in its C API, although the aws-lc-rs wrapper
>> does not expose it yet, so I call AWS-LC directly for that step. OpenSSL
>> has the same building blocks: it has no composite algorithm as such, but
>> OpenSSL 3.6 signs and verifies pure ML-DSA-44 with a caller-supplied
>> context string (for example "openssl pkeyutl -sign -rawin -p
>>  keyopt context-string:COMPSIG-MLDSA44-Ed25519-SHA512"), so the composite
>> can be built on it in the same way. Performance is not a concern either: on
>> my machine a composite signature takes about 46 microseconds to sign and 30
>> microseconds to verify with AWS-LC, against about 18 microseconds for an
>> Ed25519 verification.
>>
>> While implementing it I found some points the current texts leave open. I
>> think they need answers whichever PQ algorithm the group picks, because
>> most of them apply to a plain mldsa44-sha512 as well.
>>
>> 1. What is signed. Section 3.4 of -07 says the algorithm "computes a hash
>> over all the Message-Instance and DKIM2-Signature fields as described in
>> Section 12.8 using SHA-512 [FIPS-180-4] as the hash-alg. It signs the hash
>> with both the "post-quantum" MLDSA-44 algorithm [FIPS-204] and the
>> PureEdDSA variant Ed25519 (see [RFC8032])." That mirrors Section 3.3 and
>> does not cite LAMPS; only dns-01 says the algorithm "is specified in" the
>> LAMPS draft, and lists it as an informative reference. I can see three
>> readings that do not interoperate:
>>
>>    a. The LAMPS composite, where its message M is the Section 12.8
>> signing input, and the SHA-512 in Section 3.4 is the LAMPS pre-hash
>> computed outside the signer (LAMPS Section 10.5, External Pre-hashing). The
>> input is hashed once.
>>
>>    b. The LAMPS composite, where M is the SHA-512 digest of the Section
>> 12.8 input, by analogy with Section 3.3. M' then contains
>> SHA-512(SHA-512(input)).
>>
>>    c. No LAMPS combiner: plain ML-DSA-44 and Ed25519 each sign the digest
>> and the two values are concatenated.
>>
>>    I implemented (a), which matches Richard's pointer to the LAMPS draft
>> and avoids hashing twice. It is also the "pre-hashed input model" from
>> Wei's threat model statement, which LAMPS explicitly allows. For a plain
>> mldsa44-sha512 the equivalent question is whether pure ML-DSA signs the
>> SHA-512 digest (as Ed25519 does in Section 3.3) or whether HashML-DSA is
>> meant. Either way, a sentence stating exactly what bytes are passed to the
>> signature primitive would remove the ambiguity.
>>
>> 2. Context string. Neither draft specifies an application context, so for
>> the composite the LAMPS default (empty) applies, and that is what I use.
>> Plain ML-DSA also takes a context string. Should DKIM2 define one (for
>> example "DKIM2") for domain separation, or is empty deliberate?
>>
>> 3. Key encoding. I publish the raw composite public key in p=, that is
>> the 1312-byte ML-DSA-44 public key followed by the 32-byte Ed25519 public
>> key, not a SubjectPublicKeyInfo structure, which is how I read dns-01
>> together with LAMPS Sections 4.1 and 5. Given the RSA format errata in
>> dns-01 Appendix A, it would help to say explicitly whether SPKI is allowed
>> for the new key types.
>>
>> If the interim decides to go with plain ML-DSA-44 instead, adding it on
>> my side is a small change, and I will add it to the playground as well so
>> there is something to interop against.
>>
>>
>> Best,
>> Mauro
>>
>> _______________________________________________
>> Ietf-dkim mailing list -- ietf-dkim@ietf.org
>> To unsubscribe send an email to ietf-dkim-leave@ietf.org
>>
>
> _______________________________________________
> Ietf-dkim mailing list -- ietf-dkim@ietf.org
> To unsubscribe send an email to ietf-dkim-leave@ietf.org
>