<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ietf on Daily DMARC News</title><link>https://news.excello.email/tags/ietf/</link><description>Recent content in Ietf on Daily DMARC News</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Sun, 31 May 2026 08:00:00 +0000</lastBuildDate><atom:link href="https://news.excello.email/tags/ietf/index.xml" rel="self" type="application/rss+xml"/><item><title>The End of ARC: What the IETF's Move to Retire RFC 8617 Means for Your Forwarded Mail</title><link>https://news.excello.email/posts/2026-05-31-arc-deprecation-dkim2-email-forwarding-dmarc/</link><pubDate>Sun, 31 May 2026 08:00:00 +0000</pubDate><guid>https://news.excello.email/posts/2026-05-31-arc-deprecation-dkim2-email-forwarding-dmarc/</guid><description>&lt;p&gt;On April 22, 2026, the IETF DMARC working group published &lt;a href="https://datatracker.ietf.org/doc/draft-ietf-dmarc-arc-to-historic/"&gt;draft-ietf-dmarc-arc-to-historic-00&lt;/a&gt;, calling for RFC 8617 to be reclassified as a Historic standard. The working group had been rechartered less than a week earlier, on April 16, 2026, with a specific mandate to produce a status-change document for ARC by November 2026.&lt;/p&gt;
&lt;p&gt;The experiment that was ARC is, in the IETF&amp;rsquo;s formal language, over.&lt;/p&gt;
&lt;p&gt;That matters to anyone running a DMARC policy at &lt;code&gt;p=quarantine&lt;/code&gt; or &lt;code&gt;p=reject&lt;/code&gt;. ARC was the mechanism that was supposed to keep legitimate forwarded mail from breaking when it hit your enforcement policy. Understanding what is being retired, why it did not work, and what is coming next tells you exactly what you need to do today.&lt;/p&gt;</description></item></channel></rss>