Timeline
20/04/21:
- 15:00 Ticket #83 (New sp=policy quallifiers: "Exists" and "MailEnabled") closed by
- wontfix: Closing in favor of np clause for DMARC in PSDs
15/04/21:
- 19:24 Ticket #109 (Sanity Check DMARCbis Document) created by
- Proposed text has been submitted for a quite a number of tickets (all …
- 13:37 Ticket #91 (Revise Authentication-Results Result Registry Update) closed by
- out-of-scope: Out of scope, as it calls for modification of Authentication-Results …
- 13:28 Ticket #77 (Add options to throttle aggregate reporting volumes) closed by
- wontfix: Aggregate report traffic is not highly sensitive to the success of …
- 13:13 Ticket #67 (Better feedback loop to sending service upon DMARC failure) closed by
- wontfix: {#rejecting-messages} already contains the following text: […] …
- 13:08 Ticket #78 (dmarc-record ABNF extensibility) closed by
- wontfix: I don't think it's necessary to document hypothetical extended tags. …
14/04/21:
- 18:54 Ticket #74 (Multi-address From: fields) closed by
- fixed: Addressed in proposed text for issue #107. Closing this ticket.
- 17:58 Ticket #36 (update IANA Considerations for _dmarc registry addition) closed by
- fixed: Closing ticket as work seems to be done.
13/04/21:
- 15:10 Ticket #5 (Definition of "pct" parameter) closed by
- wontfix: Ticket #47 (remove pct= tag) overrides this one, so closing this one.
12/04/21:
- 22:23 Ticket #96 (Tweaks to Abstract and Introduction) closed by
- fixed: Will do the RFC5322.From reference change when there's a new version …
- 21:38 Ticket #96 (Tweaks to Abstract and Introduction) closed by
- fixed: Pushed to github and merged to main branch
- 19:39 Ticket #66 (Define what it means to have implemented DMARC) closed by
- fixed: pushed to github and merged to main branch
- 19:01 Ticket #50 (Remove ri= tag) closed by
- fixed: Pushed to github and merged to main branch
29/03/21:
27/03/21:
- 22:09 Ticket #101 (DMARC reporting requires explilct knowledge of all valid sending IP ...) closed by
- wontfix: This ticket misunderstands how DMARC reporting works.
- 22:07 Ticket #98 (failure reports should be authenticated) closed by
- worksforme: Sec 7.2.1.1 already says reports must be aligned.
- 22:01 Ticket #95 (Need to allow multiple ARC Sets per domain) closed by
- out-of-scope: ARC is out of scope
23/03/21:
- 21:41 Ticket #90 (DMARC should require a normative Authentication-Results Requirements ...) closed by
- out-of-scope: we're still not revising the A-R RFCs
- 21:38 Ticket #89 (Should Authentication-Results be standards track?) closed by
- out-of-scope: we are not revising the A-R RFCs
- 21:37 Ticket #88 (Authentication-Results is an orphan) closed by
- out-of-scope: misunderstands how DMARC works
- 21:36 Ticket #87 (DMARC scaling issue) closed by
- out-of-scope: misunderstands how DMARC is used
- 20:56 Ticket #72 (Remove absolute requirement for p= tag in DMARC record) closed by
- fixed: Changes pushed to github and merged to main branch.
- 17:45 Ticket #75 (Using wording alternatives to 'disposition', 'dispose', and the like) closed by
- fixed
Note: See TracTimeline
for information about the timeline view.