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 Chairs.
Domain-based Message Authentication, Reporting & Conformance (dmarc) ----------------------------------------------------------------------- Current status: Proposed WG Chairs: Seth Blank <[email protected]> Barry Leiba <[email protected]> Assigned Area Director: Andy Newton <[email protected]> Applications and Real-Time Area Directors: Orie Steele <[email protected]> Andy Newton <[email protected]> Mailing list: Address: [email protected] 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 Charter [DRAFT] The DMARC working group was chartered in 2014 to produce a Standards Track revision to DMARC (RFC 7489), originally published via the Independent Submissions stream. The revision to the original document, along with one of two reporting documents, was approved by the IESG in 2025, and the working group closed shortly thereafter. This closure left behind a second reporting document which, incomplete, reverted to being an individual submission. There is little evidence of uptake of this work in industry. However, it was overlooked that the base document produced by the working group includes normative references to this document, an artifact of the original DMARC RFC. This issue needs to be resolved before the revised base document can proceed to publication. There now appears to be consensus to recharter in order to “un-abandon” the dangling document and complete the work. This instance of the DMARC working group is chartered for the sole purpose of completing the “failure reporting” document and sending it to the IESG for publication as a Standards Track item, or removing failure reporting from DMARC in its entirety. This will complete the document cluster and allow the base document to proceed. The working group will adopt no other documents or work items. However, the working group may reclaim the base document from the RFC Editor only if it finds that edits are required to complete this charter item, and then may alter it only to the extent necessary to meet this goal. The responsible Area Director will have discretion regarding whether a full Last Call and IESG loop is needed to review those limited modifications. The working group will submit the failure reporting document to the IESG no later than six months from formation of the working group. If it fails to meet this deadline or reaches consensus to cease work on the document, it will abandon that objective and instead begin the work of removing all references from the base document to the failure reporting document, and the latter will be permanently abandoned. Milestones: Nov 2025 - Request IESG to publish DMARC Failure Reporting I-D as Standards Track _______________________________________________ dmarc mailing list -- [email protected] To unsubscribe send an email to [email protected]
