Opened 3 years ago

Last modified 20 months ago

#42 assigned enhancement

Expand DMARC reporting URI functionality

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: reports


Right now, reporting only functions via mailto: but other functionality had been previously discussed. Does the group wish to extend reporting mechanisms?


Change History (6)

comment:1 Changed 3 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 2 years ago by johnl@…

We can adapt the approach MTA-STS uses in RFC 8460.

If rua= has an https URI, the reporter uses HTTP POST to that URI with the report as an uncompressed or gzipped XML file as the POST body. The media type is the same as is used in mail reports, application/xml or application/gzip. Reports SHOULD be gzipped. If we keep the !size hack, they MUST be no larger than the size limit.

I suppose failure reports could be posted the same way with the same message type as if mailed, but they're not usually very big and I don't think there are many generated.

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

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

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

Long thread on mailing list is here -

Thread seemed to fizzle out with takeaways being:

  • Yeah, we can specify other URIs in the policy record, but
  • No one's implemented anything but mailto so far, and there hasn't been much call for it, so should we?

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

  • Status changed from started to accepted

comment:6 Changed 20 months ago by todd.herr@…

  • Status changed from accepted to assigned
Note: See TracTickets for help on using tickets.