Opened 2 years ago

Last modified 16 months ago

#62 infoneeded enhancement

Make aggregate reporting a normative MUST

Reported by: seth@… Owned by: todd.herr@…
Priority: major Milestone: Deliverable #3 (changes to DMARC base spec + DMARC Usage Guide
Component: dmarc-bis Version:
Severity: - Keywords: improve reports


Reporting is the third leg of DMARC. Without reports, domain owners cannot understand their sending landscape and make sure all their legitimate mail gets properly authenticated. This means that systems which validate DMARC, but do not send reports, get in the way of the healthy functioning of the ecosystem and actually prevent widespread authentication from getting deployed, which is broadly valuable to all senders and receivers of mail.

DMARC doesn't work without reporting. Validators MUST send reports.

However, as the IETF, not sending reports doesn't interfere with interoperability, we may need to find another mechanism to require reporting without it being a normative MUST in the primary document.

Change History (5)

comment:1 Changed 2 years ago by seth@…

  • Component changed from rfc7601bis to dmarc-bis
  • Owner draft-ietf-dmarc-rfc7601bis@… deleted
  • Status changed from new to assigned

comment:2 Changed 16 months ago by todd.herr@…

  • Owner set to todd.herr@…
  • Status changed from assigned to accepted

comment:3 Changed 16 months ago by todd.herr@…

  • Status changed from accepted to assigned

comment:4 Changed 16 months ago by todd.herr@…

  • Status changed from assigned to infoneeded

Proposed text to do just that in Mail Receiver Actions, section titled "Send Aggregate Reports"

comment:5 Changed 16 months ago by todd.herr@…

Pushed to github and merged with main branch.

Note: See TracTickets for help on using tickets.