Opened 2 years ago
Closed 12 months ago
#57 closed enhancement (fixed)
Make DKIM selectors required in DMARC reports
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: | nits reports |
Cc: |
Description
Selectors are currently optional in the reporting schema, but especially with ARC they are necessary for disambiguation of DKIM keys. Further, the point of a DMARC report -- prior to having authentication in place across the domain -- is to understand what is sending on behalf of the domain, the selector is required for this.
Change History (5)
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 19 months ago by alex_brotman@…
- Owner set to alex_brotman@…
comment:3 Changed 18 months ago by todd.herr@…
- Component changed from dmarc-bis to dmarc-aggregate-reporting
comment:4 Changed 17 months ago by alex_brotman@…
comment:5 Changed 12 months ago by alex_brotman@…
- Resolution set to fixed
- Status changed from assigned to closed
Note: See
TracTickets for help on using
tickets.
https://github.com/ietf-wg-dmarc/draft-ietf-dmarc-aggregate-reporting/commit/39c6fb8de584183ade66ca925307849fd8efdc4a