[Ietf-dkim] Re: PQC Threat Model statement

John Levine <johnl@ietf.email> Mon, 22 June 2026 02:10 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 1A082104DE674 for <ietf-dkim@mail2.ietf.org>; Sun, 21 Jun 2026 19:10:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1782094209; bh=GTeLqZHHwD5YL8pDMBbqSbw3Dmqii5WPs6iY/N/B7No=; h=Date:From:To:Cc:Subject:In-Reply-To:References; b=tjwyqcH6uIKqBS9uGNlqY5eJ8IdtJVMvYcbYPCyWQG8sLN5lBXVHU7+Oe9gFmfa+q GgzKujmmAvD6bcn6RzzUUUN5doxs3Ne17l0OAqt97XqcYT9BXMdWESxAf66iBCHLfx qSkacpcuMoMmmP3f0hxoSa6nT6jfXeXU6ui0X6s4=
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="ILMh9XuN"; dkim=pass (2048-bit key) header.d=ietf.email header.b="G8qaFT77"
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 o4bljta30wDj for <ietf-dkim@mail2.ietf.org>; Sun, 21 Jun 2026 19:10:08 -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 A61B1104DE66F for <ietf-dkim@ietf.org>; Sun, 21 Jun 2026 19:10:08 -0700 (PDT)
Received: (qmail 91606 invoked from network); 22 Jun 2026 02:10:08 -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=165d16a389980.k2606; t=1782094198; x=1782439798; bh=GTeLqZHHwD5YL8pDMBbqSbw3Dmqii5WPs6iY/N/B7No=; b=ILMh9XuNqBR/IILWPdaKdRMRvDHrYMy2bqw0jgIDXFz6/cr4XEEtuou/cbl1ejT1ERZttSqBI3F4SvcskNOpQEXFXYquocAe+qmdxrXT45M7ZHPrEG1KLsFAG1DtQp79NvvUjzZOEa1oDNJJlGxpPgw80SNMeCd67/HfRPKoSEcMM07vnM8dsTYp9WJrL9jFMKJEYeXzB8Y6KYkhE36PGJKjnislBCJvWrct7xpuqNRfz6EeARc7beGwwBLoci5S1zA1F5fTtOohWcBBAZtoa3NFGg7YFr1Va+XuND3d+7F+A6cLZJmbnVusZN+XZx0C6FXnMQSnAcwwKHuYSN7DsA==
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=165d16a389980.k2606; bh=GTeLqZHHwD5YL8pDMBbqSbw3Dmqii5WPs6iY/N/B7No=; b=G8qaFT77NO9uZLliuDgNi+gz0D3YiFKWXuMaasBe+3JGmqqwIfXapF8MhBlBeU2KCNLBJYcxYbW8iYFm561ihjQJj5zUErA5YiXY9wekg2xEUjoaChDeBLwGl7gNQB1o76Xaum99YSOqfM7d9aiiI39rVnTLGhAkG6eDakJTIzcp/Zd9Dx5dk3mf9oh0VQUUw6F1xz5q9Wd6GIdAIRg341iDXqisiLBXxlFa/QJalN4l8298a8Wzk2/Fscn5JLojJreBkXrEEvDh2P8SOqjeCGGRNFPAFKK/kbyEb3QkKVup61k20aaBNYgbm5tfmngX6FnN8F32t4BFhyWP+w4jBg==
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; 22 Jun 2026 02:10:07 -0000
Received: by ary.qy (Postfix, from userid 501) id A968F1114012C; Sun, 21 Jun 2026 22:10:07 -0400 (EDT)
Date: Sun, 21 Jun 2026 22:10:07 -0400
Message-Id: <20260622021007.A968F1114012C@ary.qy>
From: John Levine <johnl@ietf.email>
To: ietf-dkim@ietf.org
In-Reply-To: <c92d0ad4-ed81-4c8c-8630-2c83003c7def@alestrix.de>
Organization: Taughannock Networks
References: <CAAFsWK3DawKLZ1zvxjSTDDzqy+40Rnqzzd2Sxa-t8Hv2Rk8mKw@mail.gmail.com> <db66bfa4-e6ba-4909-bc28-c33516d0414e@cs.tcd.ie> <20260621014122.A2C6C11123A0C@ary.qy> <c92d0ad4-ed81-4c8c-8630-2c83003c7def@alestrix.de>
X-Headerized: yes
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Message-ID-Hash: OIY7NB2RPHW7XMYFLI3UCC22UX5U6AET
X-Message-ID-Hash: OIY7NB2RPHW7XMYFLI3UCC22UX5U6AET
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: dkim@alestrix.de
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/5SXs3iNfKu99yW-ghJeZyYLlnaY>
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 Alexander Stumpf  <dkim@alestrix.de> said:
>Hi,
>
>How about including the PQC public key as another info in the header and only store its SHA3 in a TXT record? SHA3 is, as of now, quantum-safe.

Yes, that's one of the things I suggested,.

>> IIM put both the key and the signature in the message, with a hash of the key in
>> the DNS record.  Would that still work for a PQ scheme?  I gather Cisco had a
>> patent on that but I belive it's expired or will expire shortly.

R's,
John