Opened 2 years ago
Last modified 17 months ago
#65 new enhancement
Make DMARC reporting extensible
Reported by: | seth@… | Owned by: | alex_brotman@… |
---|---|---|---|
Priority: | major | Milestone: | Deliverable #3 (changes to DMARC base spec + DMARC Usage Guide |
Component: | dmarc-aggregate-reporting | Version: | |
Severity: | - | Keywords: | improve reports |
Cc: |
Description
It should be possible in a DMARC report to define custom authentication attributes (beyond SPF and DKIM) for a report to convey.
This allows for DMARC itself to more extensible, data on new authentication to be gathered, and future needs for DMARC and other authentication mechanisms to be cleanly gathered without needing to build out new mechanisms for reporting.
Change History (4)
comment:1 Changed 2 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 20 months ago by alex_brotman@…
- Owner set to alex_brotman@…
- Status changed from assigned to new
comment:3 Changed 19 months ago by todd.herr@…
- Component changed from dmarc-bis to dmarc-aggregate-reporting
comment:4 Changed 17 months ago by alex_brotman@…
Note: See
TracTickets for help on using
tickets.
Added as of version -01
https://datatracker.ietf.org/doc/html/draft-ietf-dmarc-aggregate-reporting-01#section-3