Domain-based Message Authentication, Reporting, and Conformance (DMARC) Aggregate Reporting
draft-ietf-dmarc-aggregate-reporting-32

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: The IESG <iesg@ietf.org>, barryleiba@computer.org, dmarc-chairs@ietf.org, dmarc@ietf.org, draft-ietf-dmarc-aggregate-reporting@ietf.org, rfc-editor@rfc-editor.org, superuser@gmail.com
Subject: Protocol Action: 'Domain-based Message Authentication, Reporting, and Conformance (DMARC) Aggregate Reporting' to Proposed Standard (draft-ietf-dmarc-aggregate-reporting-32.txt)

The IESG has approved the following document:
- 'Domain-based Message Authentication, Reporting, and Conformance
   (DMARC) Aggregate Reporting'
  (draft-ietf-dmarc-aggregate-reporting-32.txt) as Proposed Standard

This document is the product of the Domain-based Message Authentication,
Reporting & Conformance Working Group.

The IESG contact persons are Murray Kucherawy and Orie Steele.

A URL of this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-dmarc-aggregate-reporting/

Ballot Text

Technical Summary

   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 to the Domain Owner's
   specified destination as supported by the receiver.

Working Group Summary

   Nothing of note.  There is ongoing discussion about this
   document but only in the proverbial sense of always having
   one more thing to discuss.  Consensus to proceed is solid.

Document Quality

   There are several existing implementations, mostly custom or
   proprietary but at least one open source.

   No further reviews other than the directorate ones already
   done are required or recommended.

Personnel

   The Document Shepherd for this document is Barry Leiba. The Responsible
   Area Director is Murray Kucherawy.

RFC Editor Note