[Ietf-dkim] Re: Proposal key validity field vor DKIM2
Mauro De Gennaro <mauro@stalw.art> Tue, 15 September 2026 21:26 UTC
Received: from mail.stalw.art (mail.stalw.art [135.181.195.209]) (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 EBC9744 for <ietf-dkim@ietf.org>; Tue, 15 Sep 2026 21:26:27 +0000 (UTC)
Authentication-Results: mx.ietf.org; dkim=pass header.d=stalw.art header.s=v1-ed25519-20260717 header.b=mekuVALt; dkim=pass header.d=stalw.art header.s=v1-rsa-20260717 header.b=shoC6wJg; dmarc=pass (policy=reject) header.from=stalw.art; spf=pass (mx.ietf.org: domain of mauro@stalw.art designates 135.181.195.209 as permitted sender) smtp.mailfrom=mauro@stalw.art
DKIM-Signature: v=1; a=ed25519-sha256; s=v1-ed25519-20260717; d=stalw.art; c=relaxed/relaxed; r=y; h=Message-Id:To:Date:Subject:From; t=1789507580; bh=AvDG71GqH7943gMsqCxcaqw W474/hVXwJL/FcxpV0Yo=; b=mekuVALt3ovEhqhWq63oTe0J6wArt1IrR4rJne2UTZV0xZOixl Ha5omrIH5PuZpQIeduNwfoJOcrtif1BieDCw==;
DKIM-Signature: v=1; a=rsa-sha256; s=v1-rsa-20260717; d=stalw.art; c=relaxed/relaxed; r=y; h=Message-Id:To:Date:Subject:From; t=1789507580; bh=AvDG71GqH7943gMsqCxcaqw W474/hVXwJL/FcxpV0Yo=; b=shoC6wJgjBrUGul7ZWZscPlpQ8W4AJq60QM9cTqhVUua7x4HX+ n33Vx/TXT+Juep8dFYzlVipD2uGg7VKQ1VJ72zblF+wi2yA0ACMysdMwvO7Iq9S9Pe75AaiBzIS ZZd/U4f8AIIxTsko0WluxvbYCsjpuE6GFcH49weCGgFiuUfFX39HV/hegYp4J58nIllI3oeatp5 /j47UuQXIN4q14bQW5+icVREMcSUKet9w2kKAs0hE1yKf6R+R6aGj+uFQ6wMJyCWhEY9IWn2cC6 SY0yeFgNFfy9LcI1ErnjCTi2JCC7y2EB68eiGmZdcy2B5dXkCdAV5HrNkfU/TsnrCwA==;
Message-Instance: m=1; h=sha256:HNup8B+/3AKkxEXgia4uRGtJKA1+f79JKrfwfknK z8Q=:qqrML+XK6e1Sj8XX7MZNIVxs7Ccaboq/caiRaXx/GZ8=;
DKIM2-Signature: i=1; m=1; t=1789507580; d=stalw.art; mf=PG1hdXJvQHN0YWx3 LmFydD4=; rt=PGlldGYtZGtpbUBpZXRmLm9yZz4=; s=v2-ed25519-20260704: ed25519-sha256:Th17UFt95Y6LLCY23FH9qKJYPkVv2Ank6JA40qtmEVxvpaTwsEDb/IhsEE8h GtYrMBdNiuzqZ1r/3YkmOICzDw==;
From: Mauro De Gennaro <mauro@stalw.art>
Content-Type: multipart/alternative; boundary="Apple-Mail=_19F1B582-74EA-489E-A65E-83E4513E7E7C"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3864.700.51.1.1\))
Date: Tue, 15 Sep 2026 23:26:09 +0200
References: <269c0f07-69de-4956-bb40-3e4d7981921b@timogerke.de> <E2A39DDA-313D-4D52-9DC3-6D7722BA6103@stalw.art> <adb2c4a4-f902-454c-8d75-78eddc1f95bf@timogerke.de> <GBpim5Av0XpqFAbj@highwayman.com> <0c198844-8bb8-45da-8491-4bc8263ab943@timogerke.de> <FF095F68-4166-4803-B9A8-B8FCE43ACD77@episteme.net> <90178ff2-17e3-4713-96da-19c5724a4916@timogerke.de> <B34A4B8A-30DC-4F5F-A1B9-7A1EC90171C0@episteme.net> <04841fb8-1c80-44f8-a5ee-3ff264596dad@timogerke.de>
To: ietf-dkim@ietf.org
In-Reply-To: <04841fb8-1c80-44f8-a5ee-3ff264596dad@timogerke.de>
Message-Id: <7657CB85-F76D-4E8E-8B40-71976F647792@stalw.art>
X-Mailer: Apple Mail (2.3864.700.51.1.1)
X-Spamd-Bar: /
Message-ID-Hash: BYO5O4IWFPHT3I2Y37M4CNY7ZRELIGAU
X-Message-ID-Hash: BYO5O4IWFPHT3I2Y37M4CNY7ZRELIGAU
X-MailFrom: mauro@stalw.art
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
X-Mailman-Version: 3.3.10
Precedence: list
Subject: [Ietf-dkim] Re: Proposal key validity field vor DKIM2
List-Id: IETF DKIM List <ietf-dkim.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-dkim/ADmJblRAEHmRDZGOT0hm9cDCBZ0>
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>
Hi Timo, > A flattened JSON array forces strict sequential determinism. > It ensures that duplicate context tags cannot overwrite each > other or create ambiguous parsing paths. > > Regarding predictable parsing time: Sterile lab setups do not > simulate a CRITIS gateway under a DDoS attack. Deeply nested JSON > opens the door to algorithmic complexity exploits. An array > guarantees linear O(n) parsing time at wire speed. > > My idea of a flat array reduces the attack surface to the > smallest possible level. It provides security by design, rather > than security by policy. On flattening as a DoS mitigation: changing the schema does not change what arrives on the wire. An attacker sending a hostile value is not emitting schema-conformant JSON. They will send 10,000 levels of nesting whether the spec describes nested objects or a flat array. A verifier therefore has to bound depth and input length at the parser under either design, and since the mitigation is identical either way, flattening buys no additional resistance. Regarding linear time, a conforming JSON parser makes a single pass and consumes each token exactly once, regardless of shape. Nesting depth determines how much parser stack is live at a given moment, not how many times any byte is examined. Nested JSON is already O(n) in input length, so the guarantee you want from the array is one the current design has. JSON also cannot express the expansion attacks that motivate this worry in other formats, because it has no entity or anchor references; output size is bounded by input size. Also, about algorithmic complexity attacks specifically, in JSON these are normally hash flooding, many colliding keys within a single object degrading insertion. That depends on key count per object, not on depth, so flattening does not mitigate it. Best, Mauro
- [Ietf-dkim] Proposal key validity field vor DKIM2 Timo Gerke
- [Ietf-dkim] Re: Proposal key validity field vor D… Bron Gondwana
- [Ietf-dkim] Re: Proposal key validity field vor D… Timo Gerke
- [Ietf-dkim] Re: JSON vs tag-value encoding and th… Vittorio
- [Ietf-dkim] Re: JSON vs tag-value encoding and th… G.W. Haywood
- [Ietf-dkim] Re: JSON vs tag-value encoding and th… Richard Clayton
- [Ietf-dkim] Re: JSON vs tag-value encoding and th… Vittorio
- [Ietf-dkim] Re: JSON vs tag-value encoding and th… Hannah Stern
- [Ietf-dkim] Re: JSON vs tag-value encoding and th… Hannah Stern
- [Ietf-dkim] Re: Proposal key validity field vor D… Taavi Eomäe
- [Ietf-dkim] Re: Proposal key validity field vor D… Timo Gerke
- [Ietf-dkim] Re: Proposal key validity field vor D… Allen Robinson
- [Ietf-dkim] Re: Proposal key validity field vor D… John Levine
- [Ietf-dkim] Re: Proposal key validity field vor D… Timo Gerke
- [Ietf-dkim] Re: Proposal key validity field vor D… Bron Gondwana
- [Ietf-dkim] Re: Proposal key validity field vor D… John Levine
- [Ietf-dkim] Re: Proposal key validity field vor D… Steve Atkins
- [Ietf-dkim] Re: base64+JSON on the critical path … Vittorio
- [Ietf-dkim] Re: base64+JSON on the critical path … Bron Gondwana
- [Ietf-dkim] Re: base64+JSON on the critical path Vittorio
- [Ietf-dkim] Re: base64+JSON on the critical path Bron Gondwana
- [Ietf-dkim] R: Re: base64+JSON on the critical pa… MCN-IETF
- [Ietf-dkim] Re: R: Re: base64+JSON on the critica… Bron Gondwana
- [Ietf-dkim] Re: base64+JSON on the critical path Hannah Stern
- [Ietf-dkim] Re: base64+JSON on the critical path Vittorio
- [Ietf-dkim] Re: base64+JSON on the critical path Hannah Stern
- [Ietf-dkim] Re: base64+JSON on the critical path Vittorio
- [Ietf-dkim] Re: base64+JSON on the critical path Hannah Stern
- [Ietf-dkim] R: Re: base64+JSON on the critical pa… MCN-IETF
- [Ietf-dkim] Re: R: Re: base64+JSON on the critica… John Levine
- [Ietf-dkim] Re: R: Re: base64+JSON on the critica… Richard Clayton
- [Ietf-dkim] Re: base64+JSON on the critical path Vittorio
- [Ietf-dkim] Re: base64+JSON on the critical path Pete Resnick
- [Ietf-dkim] Re: base64+JSON on the critical path Vittorio
- [Ietf-dkim] Re: base64+JSON on the critical path Richard Clayton
- [Ietf-dkim] Re: base64+JSON on the critical path Bron Gondwana
- [Ietf-dkim] Re: base64+JSON on the critical path Vittorio
- [Ietf-dkim] Re: Moderation (was Re: base64+JSON o… Hannah Stern
- [Ietf-dkim] Re: base64+JSON on the critical path Bron Gondwana
- [Ietf-dkim] Re: base64+JSON on the critical path Bron Gondwana
- [Ietf-dkim] Re: Proposal key validity field vor D… Richard Clayton
- [Ietf-dkim] Re: Proposal key validity field vor D… Richard Clayton
- [Ietf-dkim] Re: Proposal key validity field vor D… John Levine
- [Ietf-dkim] Re: Proposal key validity field vor D… Taavi Eomäe
- [Ietf-dkim] Re: Proposal key validity field vor D… Timo Gerke
- [Ietf-dkim] Re: Proposal key validity field vor D… Richard Clayton
- [Ietf-dkim] Re: Proposal key validity field vor D… Timo Gerke
- [Ietf-dkim] Re: Proposal key validity field vor D… Bron Gondwana
- [Ietf-dkim] Procedural notice on avoidance of the… Timo Gerke
- [Ietf-dkim] Re: Procedural notice on avoidance of… Pete Resnick
- [Ietf-dkim] Re: Proposal key validity field vor D… Timo Gerke
- [Ietf-dkim] Re: Proposal key validity field vor D… Richard Clayton
- [Ietf-dkim] Re: Proposal key validity field vor D… Bron Gondwana
- [Ietf-dkim] Re: Proposal key validity field vor D… Timo Gerke
- [Ietf-dkim] Re: Proposal key validity field vor D… Bron Gondwana
- [Ietf-dkim] Re: Proposal key validity field vor D… Richard Clayton
- [Ietf-dkim] Re: Proposal key validity field vor D… Hannah Stern
- [Ietf-dkim] Re: Proposal key validity field vor D… Hannah Stern
- [Ietf-dkim] Re: Proposal key validity field vor D… Timo Gerke
- [Ietf-dkim] Re: Proposal key validity field vor D… Pete Resnick
- [Ietf-dkim] Re: Proposal key validity field vor D… Timo Gerke
- [Ietf-dkim] Re: Proposal key validity field vor D… Pete Resnick
- [Ietf-dkim] Re: Proposal key validity field vor D… Timo Gerke
- [Ietf-dkim] Re: Proposal key validity field vor D… Mauro De Gennaro
- [Ietf-dkim] Re: Proposal key validity field vor D… Timo Gerke
- [Ietf-dkim] Re: Proposal key validity field vor D… Barry Leiba
- [Ietf-dkim] Re: Proposal key validity field vor D… Timo Gerke
- [Ietf-dkim] Re: Proposal key validity field vor D… Richard Clayton
- [Ietf-dkim] Re: Proposal key validity field vor D… Timo Gerke
- [Ietf-dkim] Re: Proposal key validity field vor D… Richard Clayton
- [Ietf-dkim] Re: Proposal key validity field vor D… Timo Gerke
- [Ietf-dkim] Re: Proposal key validity field vor D… Pete Resnick
- [Ietf-dkim] Re: Proposal key validity field vor D… Timo Gerke
- [Ietf-dkim] Re: Proposal key validity field vor D… Pete Resnick
- [Ietf-dkim] Re: Proposal key validity field vor D… Timo Gerke
- [Ietf-dkim] Re: Proposal key validity field vor D… Pete Resnick
- [Ietf-dkim] Re: Proposal key validity field vor D… Timo Gerke
- [Ietf-dkim] Re: Proposal key validity field vor D… Murray S. Kucherawy
- [Ietf-dkim] Re: Proposal key validity field vor D… Timo Gerke
- [Ietf-dkim] Re: Proposal key validity field vor D… Pete Resnick
- [Ietf-dkim] Re: Proposal key validity field vor D… Timo Gerke
- [Ietf-dkim] Re: Proposal key validity field vor D… Murray S. Kucherawy
- [Ietf-dkim] Re: Proposal key validity field vor D… Timo Gerke
- [Ietf-dkim] Re: Proposal key validity field vor D… Murray S. Kucherawy
- [Ietf-dkim] Re: Proposal key validity field vor D… Timo Gerke
- [Ietf-dkim] Re: Proposal key validity field vor D… Pete Resnick
- [Ietf-dkim] Re: Proposal key validity field vor D… Timo Gerke
- [Ietf-dkim] Re: Proposal key validity field vor D… Timo Gerke
- [Ietf-dkim] Re: Proposal key validity field vor D… Murray S. Kucherawy
- [Ietf-dkim] Re: Proposal key validity field vor D… Mauro De Gennaro
- [Ietf-dkim] Re: Proposal key validity field vor D… Timo Gerke
- [Ietf-dkim] Re: Proposal key validity field vor D… Mauro De Gennaro
- [Ietf-dkim] Re: Proposal key validity field vor D… Timo Gerke
- [Ietf-dkim] Re: Proposal key validity field vor D… Mauro De Gennaro
- [Ietf-dkim] Re: Proposal key validity field vor D… Timo Gerke
- [Ietf-dkim] Re: Proposal key validity field vor D… Mauro De Gennaro
- [Ietf-dkim] Re: Proposal key validity field vor D… Timo Gerke
- [Ietf-dkim] Re: Proposal key validity field vor D… Mauro De Gennaro
- [Ietf-dkim] Re: Proposal key validity field vor D… Timo Gerke
- [Ietf-dkim] Re: Proposal key validity field vor D… Mauro De Gennaro
- [Ietf-dkim] Re: Proposal key validity field vor D… Timo Gerke
- [Ietf-dkim] Re: Proposal key validity field vor D… Taavi Eomäe
- [Ietf-dkim] Re: Proposal key validity field vor D… Timo Gerke
- [Ietf-dkim] Re: Proposal key validity field vor D… Taavi Eomäe
- [Ietf-dkim] Re: Proposal key validity field vor D… Timo Gerke
- [Ietf-dkim] Re: Proposal key validity field vor D… Pete Resnick
- [Ietf-dkim] Re: Proposal key validity field vor D… Vittorio
- [Ietf-dkim] Re: Proposal key validity field vor D… Bron Gondwana
- [Ietf-dkim] Re: Proposal key validity field vor D… Timo Gerke
- [Ietf-dkim] Re: Proposal key validity field vor D… Hannah Stern
- [Ietf-dkim] Re: Proposal key validity field vor D… Timo Gerke
- [Ietf-dkim] Re: Proposal key validity field vor D… Hannah Stern
- [Ietf-dkim] Re: Proposal key validity field vor D… Timo Gerke
- [Ietf-dkim] Re: Proposal key validity field vor D… Richard Clayton
- [Ietf-dkim] Re: Proposal key validity field vor D… Hannah Stern
- [Ietf-dkim] Re: Proposal key validity field vor D… Hannah Stern
- [Ietf-dkim] Re: Proposal key validity field vor D… Timo Gerke
- [Ietf-dkim] Re: Proposal key validity field vor D… Mauro De Gennaro
- [Ietf-dkim] Re: Proposal key validity field vor D… Timo Gerke
- [Ietf-dkim] Re: Proposal key validity field vor D… Mauro De Gennaro
- [Ietf-dkim] Re: Proposal key validity field vor D… Timo Gerke
- [Ietf-dkim] Re: Proposal key validity field vor D… Mauro De Gennaro
- [Ietf-dkim] Re: Proposal key validity field vor D… Timo Gerke
- [Ietf-dkim] JSON elements -- was: Proposal key va… Richard Clayton