IETF Logo Mail Archive

[Ietf-dkim] Re: Concerns about the recipe/rollback mechanism and deployment architecture in draft-clayton-dkim2-spec

John Levine <johnl@ietf.email> Wed, 25 March 2026 20:50 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 CCD85D16EEA8 for <ietf-dkim@mail2.ietf.org>; Wed, 25 Mar 2026 13:50:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -4.399
X-Spam-Level:
X-Spam-Status: No, score=-4.399 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, FROM_FMBLA_NEWDOM14=0.001, 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="WNHkwlhR"; dkim=pass (2048-bit key) header.d=ietf.email header.b="kQeXWo6v"
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 qoOMlb6lWpe2 for <ietf-dkim@mail2.ietf.org>; Wed, 25 Mar 2026 13:50:58 -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 3E9C9D16EEA3 for <ietf-dkim@ietf.org>; Wed, 25 Mar 2026 13:50:58 -0700 (PDT)
Received: (qmail 15485 invoked from network); 25 Mar 2026 20:50:57 -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=3c7969c44ab1.k2603; t=1774471847; x=1774817447; bh=8gFnxmydLGDyB5z3zJTZ7oNBv9YYELb0wm6bq7C2y5Q=; b=WNHkwlhRWq97C3zfKOJrM07rLPupE+X1BjNV6bWVFw7pqtvM3sh0rmRNG7wNvOQCGfPoVq2sFP6WjzAQW9RHZOFxTrvOxa6JjR8RNwqSESZNS2i84EsZV+FK/93xUv3/UhrS/8Qrav/o/+v+emHAQPiurRcy8RkqeoGKm+Qvb2OFT1e5FbzZzn6HhVvzEu76Ar3XwHycHqdEtAKYXIXgyT4ryQnZD2GSID5/WiSKOR3m8xQk6nKMCXqqHSN0evYBuFx86RrsLls4sj67tjKGBH1C5woNqUU8emmQCFSkMYO6BhzMyocOYMuqD+KzirFN4QVDIQjsArFV0N0mZmlSPg==
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=3c7969c44ab1.k2603; bh=8gFnxmydLGDyB5z3zJTZ7oNBv9YYELb0wm6bq7C2y5Q=; b=kQeXWo6vS3HGRoAd7OpMIcOic5kQvq2ZXX5TC4+/7JtZ34wliPsOXg11TDe7qt7wUr6BH+LP7xHYZ4MVoCvGsB2t/i49Bzg63ITDZyxzyIiLxYbTyLXF8aWs4OeS9taBgisZNixkLUScuz//uf8b98JjeteWimDPzzr73uHk3Xjh1u96jTT2j6wDTU1z9HENR2fXwf2H7r6/JrKvioh1vQB+irZQS6+7HPSsIhYmDAAhDGWDmZQqPXQgayclrURo+ThLZNJZz1AGLRCp4wuzsjUpS34HMOjgHkVnmHwORu4gNnYVZvPHh/OoqbTvoHUvHBPi3pM6j/2yozauzb1qhA==
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; 25 Mar 2026 20:50:57 -0000
Received: by ary.qy (Postfix, from userid 501) id 1FD84FE9C57C; Wed, 25 Mar 2026 16:50:56 -0400 (EDT)
Date: Wed, 25 Mar 2026 16:50:56 -0400
Message-Id: <20260325205057.1FD84FE9C57C@ary.qy>
From: John Levine <johnl@ietf.email>
To: ietf-dkim@ietf.org
In-Reply-To: <879cd4a9-b0df-407c-8ae3-cb829c860735@inveigle.net>
Organization: Taughannock Networks
References: <e68f89452178831fca6f4137e19d4c35@itb.it> <da87fc77-cd45-41fe-be3b-8bf2477959d3@app.fastmail.com> <f2d1390155092b4b89811f5d1f98abb5@itb.it> <6f02a636-7ab4-4e7f-aa73-a4407963ac77@app.fastmail.com> <3c2db52d617020f5196b364ce60a033d@itb.it> <10178f6a-ab54-4e38-b097-8286e70bdb88@inveigle.net> <0A972C82-6808-4BFD-9A85-DB68B0155C7A@episteme.net> <9d9388135235d47df170798200655c6e@itb.it> <CAL0qLwZ8Xpe0i+EsJdPOcGYFr2TkJ7aWOV0CBQV0aq2+WAu-Gw@mail.gmail.com> <19beac01-33dc-41e0-bafd-36ceadb781eb@inveigle.net> <c67e862-94c7-aaac-766c-3559d0f4f2af@jubileegroup.co.uk> <879cd4a9-b0df-407c-8ae3-cb829c860735@inveigle.net>
X-Headerized: yes
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Message-ID-Hash: RG4ZVBQ2EXOXDVXBFTXM7BNUJIQFLOPM
X-Message-ID-Hash: RG4ZVBQ2EXOXDVXBFTXM7BNUJIQFLOPM
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: cs@inveigle.net
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Ietf-dkim] Re: Concerns about the recipe/rollback mechanism and deployment architecture in draft-clayton-dkim2-spec
List-Id: IETF DKIM List <ietf-dkim.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-dkim/FtZOHpc09wTfgHKbfHdNDiXEEuw>
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 Inveigle.net  <cs@inveigle.net> said:
>Vittorio asked about implementing his proposal using milters only. In 
>both that case and with Gondwana et al., fully implementing the 
>requirements of DKIM2 within a milter would require the ability for a 
>milter to create and inject new instances of an e-mail, ...

When do you think it would have to do that?

R's,
John

v2.46.0 | Report a Bug | By Email | System Status