> Labeling ARC "historic" before DKIM2 proves itself as a replacement would > serve no good purpose.
It might prevent people from deploying a mechanism that most have decided serves no true purpose in its current form. Take a look at Section A.1 in RFC8617, and ask if we believe that ARC (the experiment) has satisfied those goals. I'm not suggesting there could not be a DKIM2 or ARC++ that revises what exists today and makes it better, but this document, RFC8617, is not what the email ecosystem needs to create a reliable chain-of-custody. Marking it as historic won't necessarily stop implementations or deployments, though hopefully gives them serious pause. We had been running ARC inbound for ages, and determined that due to the various/differing ways that it was being used at other sites, it just wasn't useful enough to rely on. As such, as a site-to-site chain-of-custody, I see no value in what currently exists. -- Alex Brotman Sr. Engineer, Anti-Abuse & Messaging Policy Comcast _______________________________________________ dmarc mailing list -- [email protected] To unsubscribe send an email to [email protected]
