On Tue 12/May/2026 21:40:26 +0200 John Levine wrote:
It appears that Murray S. Kucherawy  <[email protected]> said:
Maybe for a Standards Track specification. But ARC is Experimental, and I submit that the experiment has run its course.

Several suggestions indicate we might salvage things from ARC, but I'm not sensing the broader community's willingness to invest.

DKIM2 includes a lot we've learned from ARC while trying to fix the holes that made ARC fail. I don't see either energy or benefit from trying to do both DKIM2 and a hypothetical ARC++.


While I agree that DKIM2 includes many features beyond ARC, I have two observations about the mindset expressed both in Trent's draft and in the above comment.

First, ARC's Experimental status not withstanding, the I-D explicitly suggests that DKIM2 should supersede ARC:

    This document reports the experiment’s results and explains why, with the
    emergence of the proposed successor to DKIM, currently known as DKIM2, the
    community should retire ARC and incorporate the useful pieces directly into
    the successor to DKIM.

I find the timing of that conclusion somewhat difficult to evaluate. DKIM2 still appears to be at an early stage, seems to require substantial architectural changes in MTAs, and AFAIK there is not yet significant implementation or deployment experience.

Hence, if the WG proceeds with Trent's I-D, ARC could potentially be moved to Historic status well before DKIM2 becomes deployable in practice. In that case, it is not entirely clear to me what “incorporate the useful pieces” would concretely mean, or where those useful pieces are expected to live in the meantime.

Second, and more importantly, I think understanding /why/ ARC failed is considerably more important than merely changing its status.

My own current interpretation is that ARC failed because it lacks an authorization counterpart. In other words, it can preserve authentication context, but it does not provide a corresponding mechanism for granting authorization.

Since DKIM2 also appears to rely primarily on domain reputation, I am not yet seeing how it would address the mailing-list problem differently. I would be particularly interested in comments on that point, since it seems central to the overall discussion.

AFAICS, there are currently no concrete ARC++ proposals anyway.


Best
Ale
--




_______________________________________________
dmarc mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to