[Ietf-dkim] Re: PQC Threat Model statement

John Levine <johnl@ietf.email> Mon, 22 June 2026 21:44 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 121F010561426 for <ietf-dkim@mail2.ietf.org>; Mon, 22 Jun 2026 14:44:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1782164655; bh=vEMgQih66Pu0kLF40LOKC0NWVbdM+rsBP1h1Bkq6C0c=; h=Date:From:To:Cc:Subject:In-Reply-To:References; b=iA05LqPPTmG5+l3eM7N+4CwlVWkcWH+QknQPpiU/My/4yYRNcyOisUeZmQ6uufsuF pGY5YtVA2HF0icxzqDCt6B0yKkplurxnPEjT5IVoMM1EaLk3DGbWI2I0f18EEtMX1X uHd+GfhMOkfo/GpuqFWg6lv74QEIPAH0I7V9GQqQ=
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="agheKX4C"; dkim=pass (2048-bit key) header.d=ietf.email header.b="PCnRybMh"
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 8I5Eo2OnLIsz for <ietf-dkim@mail2.ietf.org>; Mon, 22 Jun 2026 14:44:14 -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 39FB310561421 for <ietf-dkim@ietf.org>; Mon, 22 Jun 2026 14:44:14 -0700 (PDT)
Received: (qmail 57112 invoked from network); 22 Jun 2026 21:44:13 -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=df156a39acad.k2606; t=1782164643; x=1782510243; bh=vEMgQih66Pu0kLF40LOKC0NWVbdM+rsBP1h1Bkq6C0c=; b=agheKX4C6cR8wZwlN6Od2Jo3Aox1Gs5ByV2I1sNBgzbUUmpLAO6x1+K1G/3YwmxM1ixd6X8jwx2kYQzSQlMix5rO0fq474KH73u8iOTr8v7ncfte7ipWBDiF9UxfrhEshpiqXYcMl/gybdJBRCYtz28i0dyby/OGKsJq2IYnH8fCJZzbJQmqBfQvIm3S8dTSrhzAmSWaVZaJoxPTJYmQSfedvL+dWFJL1sTqkfTgpu6LZh8Iaefmf+hyaOILPjOdXeLHpkgg61eZY3/Bf1dEbDQhGyREZC5FNXZw4WiCqjuXZ9+ltMMJxFVxwsKV02drL4zm7Dx2fHIzD4gt7o8moA==
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=df156a39acad.k2606; bh=vEMgQih66Pu0kLF40LOKC0NWVbdM+rsBP1h1Bkq6C0c=; b=PCnRybMhfnxqVE6BllHRcRFclgtUpsxNuEoCK10+YaXYTyI3Sev53QRZETqoZ8DugpDr1O50TDiLtmqhvgXO1+gTFgwpWbQOitjrzuBv8rBLwq45UE/Wx87E7VeVT5K4TsZ1DxBs+RytmBfg4QQHGrwmK1DxCEl2MxKNPE7X874EzInsqu6yJ5rbI/7I0fUwnZJrLls1ydv9bG09m7azpF++3UehBcfJN+i/b1YA98BRBMWeyC2XjQEBVXo0FOEIyDyZR3Q+K0jN7Oyo4SHpPF7xQTk7S7xqfWH2yNOZL6Ldy0SccaKFXKHlTcYlw61BnbD2TsSHDraWfCRMM9xDyw==
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 21:44:13 -0000
Received: by ary.qy (Postfix, from userid 501) id 1CD4311158F88; Mon, 22 Jun 2026 17:44:12 -0400 (EDT)
Date: Mon, 22 Jun 2026 17:44:12 -0400
Message-Id: <20260622214413.1CD4311158F88@ary.qy>
From: John Levine <johnl@ietf.email>
To: ietf-dkim@ietf.org
In-Reply-To: <ZNVllKBN37NqFAZp@highwayman.com>
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> <ZNVllKBN37NqFAZp@highwayman.com>
X-Headerized: yes
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Message-ID-Hash: PL4YT24YR2UBZSSHIJQ44YPXIVKBI3UT
X-Message-ID-Hash: PL4YT24YR2UBZSSHIJQ44YPXIVKBI3UT
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: richard@highwayman.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/0Vfv6C7UXLRWgezERLjjGgQ4IVA>
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 Richard Clayton  <richard@highwayman.com> said:
>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>In message <c92d0ad4-ed81-4c8c-8630-2c83003c7def@alestrix.de>, Alexander
>Stumpf <dkim=40alestrix.de@dmarc.ietf.org> writes
>
>>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.
>
>that makes PQ handling very different from other algorithms, not
>impossible but rather messy for the code to handle

Depends what the interface to the crypto is. If it's "here's the body
or header hash, return a blob of base64" it wouldn't be that messy.

But we need to decide whether how much of a problem we think it is if
the keys are too big to fit in one packet. If you're using 2K RSA
keys, the packets are already pretty close to 512, so my inclination
is to say that the keys are whatever size they are, so be it.

If people are using DoT or DoH they'll be wrapped in TCP anyway, and
nobody seems to think that's a problem.

R's,
John