Closed ietf-svn-bot closed 1 year 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 changed status from assigned
to new
_@alexbrotman@comcast.com _set owner to alex_brotman@comcast.com
_
@todd.herr@valimail.com changed component from dmarc-bis
to dmarc-aggregate-reporting
@todd.herr@valimail.com changed status from new
to assigned
@todd.herr@valimail.com _changed owner from alex_brotman@comcast.com
to todd.herr@valimail.com
_
@todd.herr@valimail.com _changed owner from todd.herr@valimail.com
to alex_brotman@comcast.com
_
_@alexbrotman@comcast.com commented
As there's a newly defined section for DMARC Report Extensions, it feels like that is where ARC reporting belongs. It can/should be defined outside of this document. If we include it here, that would open the door to other DMARC-related mechanisms being included in this document, and creates a stream of revisions.
See comment about extensions. This is where ARC data should go.
keyword_clarify_reports
owner:alex_brotman@comcast.com
type_enhancement
| by seth@sethblank.comARC data doesn't have a clean place to live in a DMARC report. Right now, results from ARC are shimmed into a local_policy comment, but this is a text blob. ARC reporting needs a structured schema for data to come back through, and probably a new section of the DMARC report to live within.
Issue migrated from trac:56 at 2022-01-24 16:17:18 +0000