Opened 2 years ago

Last modified 16 months ago

#71 infoneeded defect

Revise sending intervals (ri=) and size control logic

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


Size limitation, as specified in the mailto: uri, may require to send reports more often. Report consumers indicate the preferred rate by the ri= tag. However, most reporting agents run at fixed hours, e.g. by cron jobs. Hence, they have to accommodate the reporting interval "on a best-effort basis".

If reports tend to grow in size, the report producer can double the calls to the reporting agent during the day. That way, the size of the reports should about halve. This decision has to be made at the report producer side.

It should be clarified that ri=43200, say, means the shortest interval that a consumer can accept. That is, the best effort is done by increasing the proposed ri=. Or is it legitimate to make it shorter?

Note: size limits can produce chunks (see ticket:#53), or can result in plain data loss. See also ticket:#50.

Change History (3)

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

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

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

  • Status changed from accepted to assigned

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

  • Status changed from assigned to infoneeded

ri= tag is proposed to be deprecated in #50

report chunking is proposed to be eliminated in #53

If those two issues are accepted by the working group, then this issue should be closed as wontfix.

Note: See TracTickets for help on using tickets.