[dmarc-ietf] Re: Evaluating consensus on the idea of making ARC "Historic"

Dan Mahoney <danm@prime.gushi.org> Thu, 09 July 2026 16:57 UTC

Return-Path: <danm@prime.gushi.org>
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 B80BA114131A4 for <dmarc@mail2.ietf.org>; Thu, 9 Jul 2026 09:57:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1783616231; bh=2Rp9VN1aDQ8NEqcHaspJumzwir4l/eiaFe6aQMLc/BQ=; h=From:Subject:Date:References:To:In-Reply-To; b=tA9S0NgugFWOOikr0R51Nbz8oCjGFaarMZcg3S/y970PJhCNsWzGKdf9CGQM5JTSi yl56gH5Rsb138I1xeyLZayfDrb0lc3lzJw3VEpzZEUkMWchNhsbdG3rQUGY/XUgOR2 G1tkTknWZz+lcxqTfWyM7fkFrmhde2yD+4Fp21FY=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_EF=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=gushi.org
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 hfz-flWhM4uv for <dmarc@mail2.ietf.org>; Thu, 9 Jul 2026 09:57:11 -0700 (PDT)
Received: from prime.gushi.org (prime.gushi.org [IPv6:2620:137:6000:10::142]) (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 1D25A11413199 for <dmarc@ietf.org>; Thu, 9 Jul 2026 09:57:10 -0700 (PDT)
Received: from smtpclient.apple ([IPv6:2001:500:6b:200:8000:0:0:28b]) (authenticated bits=0) by prime.gushi.org (8.18.2/8.18.2) with ESMTPSA id 669Gv2Qp001592 (version=TLSv1.2 cipher=ECDHE-ECDSA-AES256-GCM-SHA384 bits=256 verify=NOT) for <dmarc@ietf.org>; Thu, 9 Jul 2026 16:57:03 GMT (envelope-from danm@prime.gushi.org)
DKIM-Filter: OpenDKIM Filter v2.10.3 prime.gushi.org 669Gv2Qp001592
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gushi.org; s=prime2014; t=1783616223; bh=O/VPSKFyQmw/2NCMWwr8ksgobLP8z44Fg5fDmIzKyMc=; h=From:Subject:Date:References:To:In-Reply-To; z=From:=20Dan=20Mahoney=20<danm@prime.gushi.org>|Subject:=20Re:=20[ dmarc-ietf]=20Evaluating=20consensus=20on=20the=20idea=20of=20maki ng=20ARC=0D=0A=20"Historic"|Date:=20Thu,=209=20Jul=202026=2010:56: 51=20-0600|References:=20<CALaySJJx_Q7ANbhooNSHY7XawW51Lt42hM771O6 Kr-pKLrt5=3Dg@mail.gmail.com>=0D=0A=20<CAD2i3WMhQhKZUGjG_y0DGDXJdg M9qPMpHUAmvH5pjicQG+5EkQ@mail.gmail.com>=0D=0A=20<202607061956.485 79@sweets.iij.ad.jp>|To:=20dmarc@ietf.org|In-Reply-To:=20<20260706 1956.48579@sweets.iij.ad.jp>; b=RY6K5bIFXgLLJKN9q0GGyVoViqiCLf3OXjH/pctQkLypDq1dKy9UVX20XxS2M7Zuv ZRRcPsXXFT4UPBMSBhm0BKU0onxSi13iHCLds+i71DrjVKNcN5EM3qLm63jqIKrs/6 UBRNyIma78go1JtR9ZCMYcwOayRLUMWwu66dTqAojAFKaxwcNyOM9q6Nf79u5UntIA 26i432tRRyKLPA3SZLHs5W4SLrCs4+o/wyBtqkcH/3EpifguzxcrIL4MRpNILx7bxc cd4cQwlOICCyvTrnuBGdnyM0Pr1avByEk+uG/ut4qGD3zLpMLkaNC+h3vuQ4VxBVqS sflF0Qt61PJzg==
X-Authentication-Warning: prime.gushi.org: Host [IPv6:2001:500:6b:200:8000:0:0:28b] claimed to be smtpclient.apple
From: Dan Mahoney <danm@prime.gushi.org>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3864.600.51.1.1\))
Date: Thu, 09 Jul 2026 10:56:51 -0600
References: <CALaySJJx_Q7ANbhooNSHY7XawW51Lt42hM771O6Kr-pKLrt5=g@mail.gmail.com> <CAD2i3WMhQhKZUGjG_y0DGDXJdgM9qPMpHUAmvH5pjicQG+5EkQ@mail.gmail.com> <202607061956.48579@sweets.iij.ad.jp>
To: dmarc@ietf.org
In-Reply-To: <202607061956.48579@sweets.iij.ad.jp>
Message-Id: <1CA4099E-9F35-4AB1-846C-17DB06DE2E2E@prime.gushi.org>
X-Mailer: Apple Mail (2.3864.600.51.1.1)
Message-ID-Hash: SBMVGIW2D3XRGDHX2PRDMC5CIB36ISPM
X-Message-ID-Hash: SBMVGIW2D3XRGDHX2PRDMC5CIB36ISPM
X-MailFrom: danm@prime.gushi.org
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
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [dmarc-ietf] Re: Evaluating consensus on the idea of making ARC "Historic"
List-Id: "Domain-based Message Authentication, Reporting, and Compliance (DMARC)" <dmarc.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/U2wyuw34LjA4HOWWv_MdD5AaRTg>
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 Jul 6, 2026, at 6:56 AM, Isamu Koga <koga=40iij.ad.jp@dmarc.ietf.org> wrote:
> 
>> I think we should NOT make ARC historic, yet.
>> 
>> 1. ARC is actively deployed and utilized
>> 2. No interoperable replacement is yet published
> 
> I totally agree with Seth.
> 
> It is too early to make ARC Historic at this point.  ARC may eventually be
> deprecated, but no interoperable replacement exists today.  If a customer
> were to ask what interoperable alternative is currently available, I would
> not have a good answer.

I get it, technology marches on, but...

I am so tired of the "next great thing that's going to fix email that admins of both sending servers and receivers alike need to figure out how to staple in to their infrastructure even if it ignores some edge-case-thats-not-an-edge-case-at-all."

network-operators-actually-paying-attention-to-abuse@
RBL's
SPF with TXT records
SPF with SPF RRTYPES
No wait, SPF with TXT records (but not _spf.domain, let's continue to overload the apex).
MS Sender-ID with its wierd licensing requirements that no admin can agree to without contacting Legal.
Lets-put-a-haiku-in-your-headers and use that to assert copyright
Hashcash
The CAN-SPAM act
Domainkeys
DKIM
DKIM-Reputation
ADSP
SenderScore
SPEWS (and about 3 dozen other RBLs that will randomly return bad codes)
DMARC
DMARCbis
ARC
MTA-STS
BIMI

and...even if you do the right things according to the above, you can still get delivery issues to $big_mailbox, which will have its own vague rules and requirements.

After which, someone can STILL put "Paypal Official Support" <evilspammer@throwaway.domain> in their legitimate From header, fully signed, and pretty much every MUA out there won't flag it (or even display it) because that's "too confusing for the users", so either way mail admins are forced to put forwarding-breaking WARNING: EXTERNAL ORGANIZAION mime bodies in their mail.

If you want operator burnout, this is the way.

I'm sure the proponents of DKIM2 are going to be real proud of their new sliced-bread machine when it comes out and totally solves everything, no this time for real, but the time to deprecate ARC is *after* it's out, IMHO.  Maybe make it easier for admins to have a flag day to do both things?

-Dan