Opened 2 years ago

Closed 12 months ago

#64 closed enhancement (fixed)

Clarify whose data is actually being returned in a DMARC aggregate report

Reported by: seth@… Owned by: alex_brotman@…
Priority: major Milestone: Deliverable #3 (changes to DMARC base spec + DMARC Usage Guide
Component: dmarc-aggregate-reporting Version:
Severity: - Keywords: clarify reports
Cc:

Description

One of the reasons some major DMARC validators don't send DMARC reports is that there is confusion over whose data is included in the report.

While this is not normally something the IETF opines on, some clarity in privacy considerations around what the data in each type of report represents, would go a long way in making it easier for reports to be provided.

Change History (7)

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 18 months ago by alex_brotman@…

  • Owner set to alex_brotman@…

comment:3 Changed 18 months ago by johnl@…

  • Summary changed from Clarify whose data is actually being returned in a DMARC report to Clarify whose data is actually being returned in a DMARC aggregage report

comment:4 Changed 18 months ago by johnl@…

  • Summary changed from Clarify whose data is actually being returned in a DMARC aggregage report to Clarify whose data is actually being returned in a DMARC aggregate report

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

  • Component changed from dmarc-bis to dmarc-aggregate-reporting

comment:7 Changed 12 months ago by alex_brotman@…

  • Resolution set to fixed
  • Status changed from assigned to closed
Note: See TracTickets for help on using tickets.