![(please configure the [header_logo] section in trac.ini)](https://www.ietf.org/images/ietflogotrans.gif)
Timeline
03/05/20:
- 23:54 Ticket #70 (DMARC report software version string) created by
- Add an optional software version string to DMARC reports This way, …
- 23:52 Ticket #69 (Add JSON reporting format) created by
- It is desirable to send DMARC reports in JSON in addition to XML
- 23:51 Ticket #68 (Do away with the PSL and Org Domain entirely; just walk the tree) created by
- When DMARC was first developed, there was concern about DNS load and …
- 23:46 Ticket #67 (Better feedback loop to sending service upon DMARC failure) created by
- Small services rarely ever know when mail sent is being blocked by …
- 23:43 Ticket #66 (Define what it means to have implemented DMARC) created by
- In particular: - What does it mean to implement DMARC as a domain …
- 23:40 Ticket #65 (Make DMARC reporting extensible) created by
- It should be possible in a DMARC report to define custom …
- 23:37 Ticket #64 (Clarify whose data is actually being returned in a DMARC aggregate report) created by
- One of the reasons some major DMARC validators don't send DMARC …
- 23:35 Ticket #63 (Make p=none with no reporting URI invalid) created by
- p=none without reporting is the same as having no record, but many …
- 23:32 Ticket #62 (Make aggregate reporting a normative MUST) created by
- Reporting is the third leg of DMARC. Without reports, domain owners …
- 23:28 Ticket #61 (Define and add a simplified (redacted) failure report) created by
- It has been asked for a new report type (perhaps a subset of failure …
- 23:24 Ticket #60 (Define and add NXDOMAIN aggregate reporting) created by
- Public Suffix Domains might want a special type of reporting limited …
- 23:22 Ticket #59 (Add third lookup for organizational home) created by
- In the event there is something like DBOUND that defines a grouping of …
- 23:20 Ticket #58 (Add third lookup for public suffix domains) created by
- Many public suffix domains want to enforce DMARC or apply policy …
- 23:18 Ticket #57 (Make DKIM selectors required in DMARC reports) created by
- Selectors are currently optional in the reporting schema, but …
- 23:15 Ticket #56 (Codify ARC reporting in DMARC XML) created by
- ARC data doesn't have a clean place to live in a DMARC report. Right …
- 23:10 Ticket #55 (Clarify legal and privacy implications of failure reports) created by
- Make it clear in privacy considerations that failure reports can …
- 22:50 Ticket #54 (Remove or expand limits on number of recipients per report) created by
- https://tools.ietf.org/html/rfc7489#section-6.2 says "Receivers MAY …
- 22:43 Ticket #53 (Remove reporting message size chunking) created by
- A dmarc-uri allows for message chunking (see …
- 22:40 Ticket #52 (Remove strict alignment (and adkim and aspf tags)) created by
- Strict alignment is rarely deployed, doesn't provide additional …
- 22:36 Ticket #51 (Fix disposition reporting in aggregate reports) created by
- In a DMARC report, a record with a disposition of "none" is confusing …
- 22:34 Ticket #50 (Remove ri= tag) created by
- Almost no one uses it, and it is generally ignored by mail systems. …
- 22:32 Ticket #49 (p= placement requirement should be removed) created by
- Normatively, p= must be the second tag (after v=) or the record is …
- 22:31 Ticket #48 (Remove sp= tag) created by
- sp= appears to be more trouble than it's worth. Once a domain puts …
- 22:26 Ticket #47 (Remove pct= tag) created by
- How pct= is written, how it is implemented, how it is understood, and …
- 22:23 Ticket #46 (Separate org domain definition from core DMARC) created by
- i.e. remove any direct reliance on the PSL from within the DMARC …
- 22:22 Ticket #45 (Address missing report elements from deprecated drafts) created by
- See: …
- 22:21 Ticket #44 (Address aggregate reporting XML schema inconsistencies) created by
- From …
- 22:18 Ticket #43 (Subdomain reporting clarity) created by
- The spec appears to be unclear on how subdomains are to be reported - …
- 22:17 Ticket #42 (Expand DMARC reporting URI functionality) created by
- Right now, reporting only functions via mailto: but other …
- 22:13 Ticket #41 (Potentially separate reporting and policy into different documents) created by
- Potentially move reporting into its own I-D to make normative …
- 22:12 Ticket #40 (Clarify data integrity needs within DMARC reports) created by
- The spec needs clarification to be specific about what constitutes …
- 22:08 Ticket #39 (Remove p=quarantine) created by
- Is p=quarantine needed? …
- 22:04 Ticket #38 (DKIM correctness) created by
- The spec is ambiguous about which DKIM key needs to be reported; the …
- 21:58 Ticket #37 (Address ABNF for sub-domain inherited from DKIM) created by
- From Elizabeth Zwicky: The question I was looking at was domains …
Note: See TracTimeline
for information about the timeline view.
