Domain-based Message Authentication, Reporting & Conformance (dmarc) Internet Drafts

      
 Domain-based Message Authentication,Reporting,and Conformance (DMARC)
 
 draft-ietf-dmarc-dmarcbis-41.txt
 Date: 04/04/2025
 Authors: Todd Herr, John Levine
 Working Group: Domain-based Message Authentication, Reporting & Conformance (dmarc)
 This document describes the Domain-based Message Authentication, Reporting, and Conformance (DMARC) protocol. DMARC permits the owner of an email's Author Domain to enable validation of the domain's use, to indicate the Domain Owner's or Public Suffix Operator's message handling preference regarding failed validation, and to request reports about the use of the domain name. Mail receiving organizations can use this information when evaluating handling choices for incoming mail. This document obsoletes RFCs 7489 and 9091.
 Domain-based Message Authentication,Reporting,and Conformance (DMARC) Failure Reporting
 
 draft-ietf-dmarc-failure-reporting-25.txt
 Date: 18/04/2026
 Authors: Steven Jones, Alessandro Vesely
 Working Group: Domain-based Message Authentication, Reporting & Conformance (dmarc)
 Domain-based Message Authentication, Reporting, and Conformance (DMARC) is a mechanism by which a Domain Owner can request feedback about email messages using their domain in the From: address field. This document describes "failure reports", or "failed message reports", which provide details about individual messages that failed to authenticate according to the DMARC mechanism. This document updates RFC 6591 and obsoletes RFC 7489.
 Domain-based Message Authentication,Reporting,and Conformance (DMARC) Aggregate Reporting
 
 draft-ietf-dmarc-aggregate-reporting-32.txt
 Date: 17/03/2025
 Authors: Alex Brotman
 Working Group: Domain-based Message Authentication, Reporting & Conformance (dmarc)
 Domain-based Message Authentication, Reporting, and Conformance (DMARC) allows for Domain Owners to request aggregate reports from receivers. This report is an XML document, and contains extensible elements that allow for other types of data to be specified later. The aggregate reports can be submitted by the receiver to the Domain Owner's specified destination as declared in the associated DNS record.

data-group-menu-data-url="/group/groupmenu.json">

Domain-based Message Authentication, Reporting & Conformance (dmarc)

WG Name Domain-based Message Authentication, Reporting & Conformance
Acronym dmarc
Area Applications and Real-Time Area (art)
State Active
Charter charter-ietf-dmarc-04 Approved
Document dependencies
Additional resources DMARCbis issue tracker
Wiki
Zulip stream
github
Personnel Chair Barry Leiba
Area Director Andy Newton
Mailing list Address dmarc@ietf.org
To subscribe https://www.ietf.org/mailman/listinfo/dmarc
Archive https://mailarchive.ietf.org/arch/browse/dmarc/
Chat Room address https://zulip.ietf.org/#narrow/stream/dmarc

Charter for Working Group

DMARC was previously chartered to develop and publish a base document and two reporting documents.
This work has been completed.

In the intervening time, the working group also published the Authenticated Received Chain protocol
as experimental RFC 8617. Industry experience has shown that this proposal has enjoyed neither
noteworthy uptake nor sufficient impact.

Accordingly, DMARC is being chartered (again) to find consensus on a document that changes RFC 8617 to
historical status, including prose describing the history and current status of the work.

This iteration of the DMARC working group is chartered for the sole purpose of completing this task.
This working group will adopt no other documents or work items. This sole task is to be completed
no later than six months from working group rechartering. If this working group fails to meet this deadline,
the group will close at that time.

Milestones

Date Milestone Associated documents
Nov 2026 Request approval of a status-change document moving ARC to Historic