[dmarc-ietf] Re: Proposed Recharter to Conclude the ARC Experiment

"John R. Levine" <johnl@iecc.com> Tue, 03 February 2026 19:54 UTC

Return-Path: <johnl@iecc.com>
X-Original-To: dmarc@mail2.ietf.org
Delivered-To: dmarc@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 25B79B168BE9 for <dmarc@mail2.ietf.org>; Tue, 3 Feb 2026 11:54:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -4.401
X-Spam-Level:
X-Spam-Status: No, score=-4.401 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, 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
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 jZ5Xwb3G_dHy for <dmarc@mail2.ietf.org>; Tue, 3 Feb 2026 11:54:11 -0800 (PST)
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 1DB45B168BD5 for <dmarc@ietf.org>; Tue, 3 Feb 2026 11:54:11 -0800 (PST)
Received: (qmail 86350 invoked from network); 3 Feb 2026 19:54:04 -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; s=1514c6982525c.k2602; t=1770148434; x=1770494034; bh=wom5qgEC3yjBDKbJYdX0sXWWy+ECdsFfY8va6U4ucOU=; b=dme6TNFxgH3eM6VkQQwL6J14jfVulrSlzoLBdtCdPZOmax16wHTMPaSsM/AVhHo2KuaKCPlKRmkKj5HSv3cNTR/YD5DUPYoocET7tFAkEyoTWtIeSNMk5cdk79d0zEiWnSPCFcVXR6w1dG/gRvVMa1Z3OsBvimMwTq0pJuwuJY85wNPTef+gE2ZRIjVzWP0m4Jz2P8HJNfiwda9K4WNxvOXnSMsDQCi9WzCEgdNsML4HywEpxRgGlPp5kQ8zj58LB4y+0KTMSt/Rl37R5Nz78ZCfiaVxTDrpFcGTKTGp6PpPbvYrH12etLVEKjjw0z8ks0W1C6Il15y3WzjJJ4FuxQ==
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; 03 Feb 2026 19:54:03 -0000
Received: by ary.qy (Postfix, from userid 501) id 6AB08F4B63C7; Tue, 3 Feb 2026 14:54:03 -0500 (EST)
Received: from localhost (localhost [127.0.0.1]) by ary.qy (Postfix) with ESMTP id 35BD0F4B63A9; Tue, 3 Feb 2026 14:54:03 -0500 (EST)
Date: Tue, 03 Feb 2026 14:54:03 -0500
Message-ID: <2da87b12-749d-1210-70cd-a1c2e8fa5a65@iecc.com>
From: "John R. Levine" <johnl@iecc.com>
To: Jeroen Massar <jeroen@massar.ch>
In-Reply-To: <9E413BEA-D93E-495A-940B-A21B27E357FA@massar.ch>
References: <IA1PR12MB6531B11FBE068CEAF0F23DDCB39FA@IA1PR12MB6531.namprd12.prod.outlook.com> <CALaySJJYe47R-778ZPt2fHgcKcxYUOzZrH+KuwLum14tqF2TZw@mail.gmail.com> <CAH48ZfyAjHsOkqcr0JjE42qpyAq+68VLXn2sGyGEU8xHNe7YBA@mail.gmail.com> <CAD2i3WNCbf-kwYuaXtM3S4z9nZ6YJzESgsz75v8hkyQg8ccZpA@mail.gmail.com> <SJ2PR11MB82979B8C6F62136F806B94B4F79AA@SJ2PR11MB8297.namprd11.prod.outlook.com> <5cbf90df-ccff-2935-a9f9-c646d29ca7a4@iecc.com> <9E413BEA-D93E-495A-940B-A21B27E357FA@massar.ch>
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"; charset="us-ascii"
Message-ID-Hash: HGO3LS4ME34C4GLC4FYDZLFORSJ2HQK3
X-Message-ID-Hash: HGO3LS4ME34C4GLC4FYDZLFORSJ2HQK3
X-MailFrom: johnl@iecc.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-dmarc.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: "Brotman, Alex" <Alex_Brotman@comcast.com>, Seth Blank <seth@sethblank.com>, IETF DMARC WG <dmarc@ietf.org>, Trent Adams <tadams=40proofpoint.com@dmarc.ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [dmarc-ietf] Re: Proposed Recharter to Conclude the ARC Experiment
List-Id: "Domain-based Message Authentication, Reporting, and Compliance (DMARC)" <dmarc.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/LjS6axczRMwY65I248qXhQiIGu4>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc>
List-Help: <mailto:dmarc-request@ietf.org?subject=help>
List-Owner: <mailto:dmarc-owner@ietf.org>
List-Post: <mailto:dmarc@ietf.org>
List-Subscribe: <mailto:dmarc-join@ietf.org>
List-Unsubscribe: <mailto:dmarc-leave@ietf.org>

On Tue, 3 Feb 2026, Jeroen Massar wrote:
> For obsoleting ARC. It would be good to have Google + Microsoft and 
> others on board, have a time-line for when they turn it off.

I gather that Google no longer pays attention to ARC headers, and 
Microsoft is phasing them out.

It doesn't hurt to add them, so there's no reason to remove the existing 
code, but as I said, I don't want people to waste time adding new ARC 
code.

> As a side-note in the above codebase, when a message is received with a 
> DKIM header, we replace the original "From: jeroen@massar.ch 
> <mailto:jeroen@massar.ch>" with "From: jeroen=massar.ch@via.<domain>", 
> then DKIM sign it ...

Yes, IETF lists including this one do a similar hack based on one I did 
for my sympa lists a quite a while ago.  One of the goals of DKIM2 is to 
let mailing lists stop using that ugly hack and just describe the changes 
they wanted to make so recipients can look back and see the original DMARC 
alignment, i.e., what we hoped ARC would do but in fact it doesn't.

R's,
John