Closed ietf-svn-bot closed 3 years ago
@seth@sethblank.com changed status from new
to assigned
@seth@sethblank.com removed owner (was draft-ietf-dmarc-rfc7601bis@ietf.org
)
@seth@sethblank.com changed component from rfc7601bis
to dmarc-bis
_@alexbrotman@comcast.com _set owner to alex_brotman@comcast.com
_
@johnl@taugh.com changed title 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
@johnl@taugh.com changed title 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
@todd.herr@valimail.com changed component from dmarc-bis
to dmarc-aggregate-reporting
_@alexbrotman@comcast.com commented
https://datatracker.ietf.org/doc/html/draft-ietf-dmarc-aggregate-reporting-01#section-5.3
_@alexbrotman@comcast.com changed status from assigned
to closed
_@alexbrotman@comcast.com set resolution to fixed
keyword_clarify_reports
owner:alex_brotman@comcast.com
resolution_fixed
type_enhancement
| by seth@sethblank.comOne 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.
Issue migrated from trac:64 at 2022-01-24 16:17:47 +0000