We’re launching Lyria 3.5 in Google Flow Music, with advances across musicality, lyrics, vocals, and creative control
deepmind.google·6d ago
AI Engineering
Lobsters·Jun 22·5 min read
Reclassifying DMARC ARC as historic
TL;DR
Email authentication faced issues with DMARC (Domain-based Message Authentication, Reporting & Conformance) when messages passed through intermediaries. The Authenticated Received Chain (ARC) protocol was developed to address these issues but has now been deemed ineffective.
✦ Why It Matters
Engineers should focus on developing and adopting more effective email authentication methods like DKIM2.
Key Takeaways
- Avoid using ARC for email authentication.
- Explore DKIM2 as a successor to improve email security.
- Understand the limitations of current email authentication methods.
- Stay updated on changes in email authentication standards.
Full Summary
Email authentication is crucial for preventing spam and phishing, but DMARC often breaks when emails are forwarded through intermediaries, leading to delivery failures. To mitigate this, the Authenticated Received Chain (ARC) protocol was introduced to preserve authentication information across these intermediaries.
However, operational experience has shown that ARC does not effectively solve the underlying problems. The document proposes that ARC be reclassified as 'Historic,' indicating it should no longer be used or relied upon.
This decision is based on the lessons learned during the ARC experiment, which will inform the development of DKIM2, a successor to DomainKeys Identified Mail (DKIM). By transitioning away from ARC, the email community aims to streamline authentication processes and improve overall email security.
This change emphasizes the need for more effective solutions in email authentication.