Hi,

Yes, I am suggesting publishing the report for its revised content. I think a document that explains what we learned and clarifies the problem is valuable, and we should take the opportunity to publish it.

Changing the status of RFC 8617 is, in my view, a separate question. It seems less important than documenting the outcome of the experiment and, depending on the intended status change, might require rechartering. I neither advocate nor oppose that here; my point is simply that the report itself has value regardless of whether the RFC status changes.


Best
Ale


On Mon 20/Jul/2026 20:29:37 +0200 Barry Leiba wrote:
To be clear: Are you suggesting publishing the report for its
(revised) content, and NOT changing the status of the ARC RFC ?

Barry

On Sun, Jul 19, 2026 at 12:34 PM Alessandro Vesely <[email protected]> wrote:

On Sat 18/Jul/2026 00:14:48 +0200 [email protected] wrote:
> 1) Shut the group down and leave ARC status as-is. Let the supporters of ARC
> continue their experiment and come back at a later point with an updated
> document and data.
> 2) Shut the group down and leave ARC status as-is until DKIM2 has time in the
> wild and it is shown that it's functionality does in fact replace ARC. That
> would be a more appropriate time to consider marking ARC historic.


3) Edit the I-D reporting the state of the experiment and documenting the
reasons why ARC couldn't solve the mailing list problem.


Best
Ale
--






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

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

Reply via email to