If we're going with the suggested path below, I'd say to have the DKIM WG 
resolve the ARC status using Trent's proposed/separate document.  However, I 
believe their charter may need amending in order to accomplish that?

However, there's a suggestion that we may need to adjust some of the DMARC 
documents to accommodate DKIM2.  I'm guessing it would be your preference to 
manage that via the DKIM WG as well (as opposed to here)?  This might be a 
discussion point for tomorrow afternoon's session?

-- 
Alex Brotman
Sr. Engineer, Anti-Abuse & Messaging Policy
Comcast
 

> -----Original Message-----
> From: Barry Leiba <[email protected]>
> Sent: Saturday, November 14, 2026 2:19 PM
> To: DMARC Working Group <[email protected]>
> Subject: [dmarc-ietf] draft-ietf-dmarc-arc-to-historic
> 
> Hi, DMARCers,
> I've been remiss about wrapping this up, and I apologize for letting it sit 
> for so
> long.
> 
> My sense of the discussion is that while we mostly agree that ARC has not 
> been a
> success, the objections to making it historic at this time, and that we 
> should wait
> for DKIM2 to come out first, seem to sit on the operative side of the 
> consensus.
> That is, they point out a significant downside to doing this now, with no 
> harm in
> waiting and doing it later.
> 
> This, then, is a call for objections to this decision:
> - We mark the subject document as "dead".
> - We wait for DKIM2 to get finished, and...
> - ...either DKIM2 itself makes ARC historic or...
> - ...we resurrect this document in the DKIM2 WG later.
> - We close the DMARC working group.
> 
> Comments open for the next three weeks, to close on 30 November, an easy date
> to remember.
> 
> Barry
> _______________________________________________
> 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