DMARC 1017 min read · Updated Jul 2026

What "Standards Track" means, and why it matters for DMARC

Not every RFC is a standard. The IETF publishes documents at different maturity levels, and the label on the front page (Standards Track, Informational, Experimental) tells you how much weight the document carries. For a decade, DMARC’s odd status was one of email authentication’s best-kept secrets.

RFC does not mean standard

Every document the IETF publishes is an RFC, but RFCs come in categories. The category is printed in the document header, and it defines the document’s authority:

Standards TrackProposed Standard → Internet Standard

The real thing. A Standards Track RFC has achieved rough consensus in an IETF working group, survived cross-area review, and been approved by the IESG. It starts as a Proposed Standard and, once widely deployed and proven interoperable, can be elevated to full Internet Standard (RFC 6410 reduced the ladder to these two rungs).

Informationalpublished for the record, not a standard

Documents something useful for the community (a design, a convention, an industry practice) without IETF consensus behind it as a standard. Implementers may follow it, but nothing obliges them to, and no working group is accountable for its quality.

Experimentaltry it, measure it, report back

A specification the IETF wants deployed in a controlled way to learn from. The first SPF specification, RFC 4408 (2006), was published as Experimental. SPF only joined the Standards Track when RFC 7208 replaced it in 2014.

Where SPF, DKIM and DMARC stand

The three pillars of email authentication reached maturity at very different speeds:

ProtocolCurrent RFCStatus
SPFRFC 7208 (2014)Proposed Standard
DKIMRFC 6376 (2011)Internet Standard (STD 76)
DMARCRFC 7489 (2015) → DMARCbisInformational → Standards Track

DMARC’s decade as a non-standard

Here’s the surprise: the DMARC the whole industry deployed (the RFC 7489 that Gmail, Yahoo and Microsoft built requirements around) was never a standard. It was published in 2015 as an Informational RFC on the Independent Submission stream, essentially documenting a private industry specification developed outside the IETF. It worked, and it was adopted at enormous scale, but no IETF working group had consensus-reviewed it, and known rough edges (the Public Suffix List dependency, reporting gaps, ambiguous edge cases) were frozen into the text.

That’s what the DMARC working group’s DMARCbis effort fixed. The revision splits the protocol into a core specification and separate aggregate/failure reporting documents, replaces the Public Suffix List with the DNS Tree Walk for organizational-domain discovery, retires pct in favour of np and t=, and, crucially, publishes the result on the Standards Track with full IETF consensus behind it.

Why it matters

Standards Track status changes who has to care

An Informational RFC is something vendors may follow. A Standards Track RFC is something they can be held to. Procurement checklists, government baselines (like BOD 18-01 or M3AAWG guidance), and mailbox-provider sender requirements all reference standards. With DMARC on the Standards Track, "we comply with the standard" finally has a precise, testable meaning, and future interoperability disputes are settled by working-group consensus, not by whichever big provider implements it loudest.

What it means for your deployment

Practically, the promotion matters in three ways:

  • Stability you can build on. Standards Track text is maintained by an accountable working group. Errata get processed. Ambiguities get resolved in one place instead of in each vendor’s interpretation.
  • A migration to plan for. DMARCbis changes real mechanics: Tree Walk instead of the PSL, pct deprecated, updated report schemas. Receivers and tooling will converge on the new behaviour over time, so records written against 7489 assumptions deserve a review.
  • Stronger footing with stakeholders. When security or compliance teams ask why DMARC enforcement is worth the migration effort, "it’s an IETF standard, and DKIM is a full Internet Standard" is a materially stronger answer than "it’s a common industry practice."

ClearDMARC tracks both schema generations. Reports conforming to RFC 7489 and to the DMARCbis reporting documents are parsed side by side, so the transition is invisible in your dashboards.

References
  • RFC 2026: The Internet Standards Process, Revision 3 (document categories and the standards track).
  • RFC 6410: Reducing the Standards Track to Two Maturity Levels (Proposed Standard, Internet Standard).
  • RFC 4408 (Experimental, 2006) and RFC 7208 (Proposed Standard, 2014): SPF.
  • RFC 6376 / STD 76: DKIM Signatures (Internet Standard).
  • RFC 7489: DMARC (Informational, Independent Submission, 2015).
  • DMARCbis: IETF DMARC WG core specification and aggregate reporting (RFC 9990, May 2026), Standards Track.
Was this guide helpful?