On Thu 03/Jul/2025 13:48:12 +0200 Douglas Foster wrote:
I believe the reporting strategy needs to be defined in more detail than provided in section 2, because we need to ensure that report volumes are manageable for both sender and receiver, and to ensure that receivers can make sense of multiple reports from multiple sources. Leaving this issue to the imagination of each implementer will cause interoperability problems.
I don't think we can get into much more detail than stating the principles and mentioning a couple of ways to keep volumes low. The most basic implementation might be to limit reports to N per hour, say, trying to randomize which reports are sent and which are dropped.
Analyzing why authentication fails can require a huge amount of computing resources, the allocation of which cannot be justified by the desire to generate smarter reports. Admins develop the system as they see fit, and generating quality reports can only be a byproduct, methinks.
Best Ale -- _______________________________________________ dmarc mailing list -- dmarc@ietf.org To unsubscribe send an email to dmarc-le...@ietf.org
