From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: dmarc@ietf.org
Reply-To: iesg@ietf.org
Subject: WG Review: Domain-based Message Authentication, Reporting & Conformance (dmarc)
The Domain-based Message Authentication, Reporting & Conformance (dmarc) WG
in the Applications and Real-Time Area of the IETF is undergoing
rechartering. The IESG has not made any determination yet. The following
draft charter was submitted, and is provided for informational purposes only.
Please send your comments to the IESG mailing list (iesg@ietf.org) by
2026-04-16.
Domain-based Message Authentication, Reporting & Conformance (dmarc)
-----------------------------------------------------------------------
Current status: Active WG
Chairs:
Barry Leiba <barryleiba@computer.org>
Assigned Area Director:
Andy Newton <andy@hxr.us>
Applications and Real-Time Area Directors:
Andy Newton <andy@hxr.us>
Charles Eckel <eckelcu@cisco.com>
Mailing list:
Address: dmarc@ietf.org
To subscribe: https://www.ietf.org/mailman/listinfo/dmarc
Archive: https://mailarchive.ietf.org/arch/browse/dmarc/
Group page: https://datatracker.ietf.org/group/dmarc/
Charter: https://datatracker.ietf.org/doc/charter-ietf-dmarc/
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, though it continues to develop momentum that is believed to be
unsupportable by evidence.
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:
Nov 2026 - Request approval of a status-change document moving ARC to
Historic
WG action announcement
WG Action Announcement
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: The IESG <iesg@ietf.org>,
dmarc-chairs@ietf.org,
dmarc@ietf.org
Subject: WG Action: Rechartered Domain-based Message Authentication, Reporting & Conformance (dmarc)
The Domain-based Message Authentication, Reporting & Conformance (dmarc) WG
in the Applications and Real-Time Area of the IETF has been rechartered. For
additional information, please contact the Area Directors or the WG Chair.
Domain-based Message Authentication, Reporting & Conformance (dmarc)
-----------------------------------------------------------------------
Current status: Active WG
Chairs:
Barry Leiba <barryleiba@computer.org>
Assigned Area Director:
Andy Newton <andy@hxr.us>
Applications and Real-Time Area Directors:
Andy Newton <andy@hxr.us>
Charles Eckel <eckelcu@cisco.com>
Mailing list:
Address: dmarc@ietf.org
To subscribe: https://www.ietf.org/mailman/listinfo/dmarc
Archive: https://mailarchive.ietf.org/arch/browse/dmarc/
Group page: https://datatracker.ietf.org/group/dmarc/
Charter: https://datatracker.ietf.org/doc/charter-ietf-dmarc/
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:
Nov 2026 - Request approval of a status-change document moving ARC to
Historic
Ballot announcement
Ballot Announcement
Technical Summary
Relevant content can frequently be found in the abstract
and/or introduction of the document. If not, this may be
an indication that there are deficiencies in the abstract
or introduction.
Working Group Summary
Was there anything in the WG process that is worth noting?
For example, was there controversy about particular points
or were there decisions where the consensus was
particularly rough?
Document Quality
Are there existing implementations of the protocol? Have a
significant number of vendors indicated their plan to
implement the specification? Are there any reviewers that
merit special mention as having done a thorough review,
e.g., one that resulted in important changes or a
conclusion that the document had no substantive issues? If
there was a MIB Doctor, Media Type, or other Expert Review,
what was its course (briefly)? In the case of a Media Type
Review, on what date was the request posted?
Personnel
Who is the Document Shepherd for this document? Who is the
Responsible Area Director? If the document requires IANA
experts(s), insert 'The IANA Expert(s) for the registries
in this document are <TO BE ADDED BY THE AD>.'
RFC Editor Note
(Insert RFC Editor Note here or remove section)
IRTF Note
(Insert IRTF Note here or remove section)
IESG Note
(Insert IESG Note here or remove section)
IANA Note
(Insert IANA Note here or remove section)