[Ietf-dkim] Re: PQC Threat Model statement

John Levine <johnl@ietf.email> Fri, 19 June 2026 18:41 UTC

Return-Path: <johnl@iecc.com>
X-Original-To: ietf-dkim@mail2.ietf.org
Delivered-To: ietf-dkim@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 6C1F410421656 for <ietf-dkim@mail2.ietf.org>; Fri, 19 Jun 2026 11:41:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1781894505; bh=xEJnjU5b9vfEYZtnlp+61iXwLHqsHF+X9mbyH8yqBoc=; h=Date:From:To:Cc:Subject:In-Reply-To:References; b=No98oxD+7m/8J7mPQHvT/Q0z+IQwpfl2/2Z9y4wjRXH2jiy1Y3VAYaCfOei/5vy4a rwWVBY4zzyQ4FDQnlVocpXbILRgqhyTvyvY/5NHg2RSkFpXlMCQI0dHrKFUgFflaKK eiiarhZOKbg2GJFTgx9zHL7y5y5uBL5KTGkX5AL0=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -4.4
X-Spam-Level:
X-Spam-Status: No, score=-4.4 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, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b="I9H7hbyX"; dkim=pass (2048-bit key) header.d=ietf.email header.b="HRiRX+WY"
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 f8UySsnhdzzj for <ietf-dkim@mail2.ietf.org>; Fri, 19 Jun 2026 11:41:44 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 2322310421537 for <ietf-dkim@ietf.org>; Fri, 19 Jun 2026 11:41:08 -0700 (PDT)
Received: (qmail 8210 invoked from network); 19 Jun 2026 18:41:07 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:content-transfer-encoding:cleverness; s=200b6a358d43.k2606; t=1781894457; x=1782240057; bh=xEJnjU5b9vfEYZtnlp+61iXwLHqsHF+X9mbyH8yqBoc=; b=I9H7hbyXZk2/hgKhoHEV/2fhv1POZ4tRxTCkGMX6QAMJJSzJpVXh5p2EPYUWwv576MsnOnQMsBMVomqwAqYYVNFf0IwVWfMzn9H3nKKGCkABq+L/aFN3Yaq1R/0XPjZvqeEoKTv7wO5tHtHTyu2aTpec2q/aZmUyJE2mNIiPHdT6gGC4XEFfCUdRl7g87OZyAhqei9DMHLTd8F3CPLVNPbpTBlXofrMKd7Z+EGbwhh2chFzlblBYBd+3nTqTvmt1tL+u1gEpIRQhyOn3TBSRtX/h1bF58B0SyMhopPuExK0QxRn8OIEKNmEZ161/QozwAoeiAf5lQAtGgJ1b80AoKQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=ietf.email; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:content-transfer-encoding:cleverness; s=200b6a358d43.k2606; bh=xEJnjU5b9vfEYZtnlp+61iXwLHqsHF+X9mbyH8yqBoc=; b=HRiRX+WYgKPlMz0TIAq+4QjcJwgv5viEvlOWaVGSL7+y4sTF1l5V5cNdiF2OjHMVXLFzq5DaLzcTygI/oPvQQNDJKEyA++GzTOW13jA0vf1y6djY3ZTgRiu6dOCdw4BS5TaNnuYDvs7ut0r2zLhflL/ztd65mslVVJqTQtuACUYh6a4a/zN01cMF/LrEtoemM5nezqWNfXIchddGmvxF4+f/W68DdDixGCtPaScta8yu6NlPhVptHVbOLITpWmaQ4XaPEO6CPuEMHCOs/qWpCqJbFXwe5OFC9V8tUHKtpn0ESSPWaDCT208W59xtMdFpKmeojneo3i2BWWuhSajpMg==
Received: from ary.qy ([IPv6:2001:470:1f07:1126:0:78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126:0:78:696d:6170]) with ESMTPS (TLS1.3 ECDHE-RSA CHACHA20-POLY1305 AEAD) via TCP6; 19 Jun 2026 18:41:07 -0000
Received: by ary.qy (Postfix, from userid 501) id B5A0111104DAF; Fri, 19 Jun 2026 14:41:06 -0400 (EDT)
Date: Fri, 19 Jun 2026 14:41:06 -0400
Message-Id: <20260619184106.B5A0111104DAF@ary.qy>
From: John Levine <johnl@ietf.email>
To: ietf-dkim@ietf.org
In-Reply-To: <CAAFsWK3DawKLZ1zvxjSTDDzqy+40Rnqzzd2Sxa-t8Hv2Rk8mKw@mail.gmail.com>
Organization: Taughannock Networks
References: <CAAFsWK3DawKLZ1zvxjSTDDzqy+40Rnqzzd2Sxa-t8Hv2Rk8mKw@mail.gmail.com>
X-Headerized: yes
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Message-ID-Hash: W7RWUR35M3FWFWWPEUDJ5KIDR5MQVS77
X-Message-ID-Hash: W7RWUR35M3FWFWWPEUDJ5KIDR5MQVS77
X-MailFrom: johnl@iecc.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ietf-dkim.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: weihaw@google.com
X-Mailman-Version: 3.3.9rc6
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/J_1XG2vmIWsI47AGg7f0Rjm_tnY>
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>

It appears that Wei Chuang  <weihaw@google.com> said:
>We've written the following DKIM threat model as a starting point:
>
>The DKIM Working Group requests guidance from the CFRG in identifying the
>most appropriate Post-Quantum Cryptography (PQC) digital signature
>algorithm for DomainKeys Identified Mail. Our primary threat model focuses
>on an adversary utilizing quantum analytic key compromise to forge
>signatures, thereby enabling widespread domain spoofing. To maintain the
>reliability of global email delivery, any proposed algorithm must navigate
>DKIM's strict operational constraints: public keys are distributed via DNS
>TXT records (imposing severe sensitivity to UDP payload limits and TCP
>fallback latency), and signatures are transmitted within standard email
>headers. Furthermore, DKIM’s existing architecture evaluates the message
>hash independently of the signature generation to facilitate the processing
>of streamed email bodies. We seek CFRG’s expertise in selecting an
>algorithm that optimizes for these stringent size constraints while
>providing secure, practical recommendations for accommodating our
>pre-hashed input model.

DKIM is intended for protection of messages in transit, which
typically takes under a minute and rarely more than a few days. Hence
"harvest now decrypt later" is unlikely to be a threat.

DKIM keys should be short in order to fit in UDP DNS packets, which
means ideally they are only a few hundred octets. If they are larger,
that means requests will fall back to TCP which is not ideal but not
terrible. DNS has a 64K limit for the combined size of everything in a
DNS message which puts a pratical limit of about 20K on the size of a
key record.

DKIM signatures are stored in e-mail message header fields which have
no formal length limit, and in practice are often several thousand
octets. Both the keys and the signatures are ASCII, with binary values
represented in base64 which is 4/3 the size of the binary.

R's,
John