<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>RFC on kalfaoglu.net</title><link>https://blog.kalfaoglu.net/tags/rfc/</link><description>Recent content in RFC on kalfaoglu.net</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 22 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.kalfaoglu.net/tags/rfc/index.xml" rel="self" type="application/rss+xml"/><item><title>DMARCbis Is Official: RFC 9989 Upgrades DMARC From Suggestion to Standard</title><link>https://blog.kalfaoglu.net/posts/2026-06-22-dmarcbis-rfc-9989-proposed-standard-en/</link><pubDate>Mon, 22 Jun 2026 00:00:00 +0000</pubDate><guid>https://blog.kalfaoglu.net/posts/2026-06-22-dmarcbis-rfc-9989-proposed-standard-en/</guid><description>&lt;p&gt;In May 2026, the IETF quietly did something that email administrators have been waiting on for years: they published &lt;a href="https://datatracker.ietf.org/doc/rfc9989/"&gt;RFC 9989&lt;/a&gt;, &lt;a href="https://www.rfc-editor.org/rfc/rfc9990.txt"&gt;RFC 9990&lt;/a&gt;, and &lt;a href="https://www.rfc-editor.org/rfc/rfc9991.txt"&gt;RFC 9991&lt;/a&gt; — collectively known as DMARCbis. These three documents replace RFC 7489, which has been the authoritative reference for DMARC since 2015.&lt;/p&gt;
&lt;p&gt;The headline change isn&amp;rsquo;t technical; it&amp;rsquo;s procedural. The original RFC 7489 was published as an &lt;strong&gt;Informational&lt;/strong&gt; document, meaning it described what the industry was already doing, not what it was required to do. DMARCbis arrives as a &lt;strong&gt;Proposed Standard&lt;/strong&gt; on the IETF Standards Track — the first formal step toward becoming an Internet Standard. In plain terms: DMARC just graduated from &amp;ldquo;strong industry recommendation&amp;rdquo; to &amp;ldquo;official protocol.&amp;rdquo;&lt;/p&gt;</description></item></channel></rss>