I still agree with Trent. Seems to me those who lean “historic” have made objections clear, and shared their rationale. Maybe it’s just not a hill to die on, or perhaps they feel their prior notes are sufficient?
P1: While others have found value in ARC, I found the opposite due to some of the points that the proposed document mentions in 3.1. Should we examine each of those bullets for accuracy? Have we sufficiently addressed that section? P2: I’d rather see those who have the ability to do so work toward DKIM2, either (IETF) design or deployment. If P1 suggests there is no/limited value in ARC (as RFC8617 is written), why wait for DKIM2 to note it as “historic”? -- Alex Brotman Sr. Engineer, Anti-Abuse & Messaging Policy Comcast From: Murray S. Kucherawy <[email protected]> Sent: Monday, July 20, 2026 4:08 AM To: Barry Leiba <[email protected]> Cc: DMARC Working Group <[email protected]> Subject: [dmarc-ietf] Re: Evaluating consensus on the idea of making ARC "Historic" On Sat, Jul 18, 2026 at 9:34 PM Barry Leiba <[email protected]<mailto:[email protected]>> wrote: The next step is for those who still want to proceed with making ARC Historic *now*... to respond to these objections and either accept the suggestion to wait, or to address reasons we should not. I think it's curious that consensus appears to have swung towards "do nothing" when, during chartering (and thus the reason we're still here), consensus was clearly "Trent's right, we should do this". I can't tell why it changed in the interim. -MSK
_______________________________________________ dmarc mailing list -- [email protected] To unsubscribe send an email to [email protected]
