Timeline


and

18/04/18:

13:56 Ticket #16 (Addl document for ARC additions to DMARC reporting (section 9.3)) closed by kboth+ietf@…
wontfix: Based on discussion during the IETF101 WG meeting, we will retain this …
13:54 Ticket #15 (Move section 8.2 (Assessing Chain Validity Violations) to "protocol ...) closed by kboth+ietf@…
fixed: Part of this was moved to the usage document; the other part was just …
13:39 Ticket #12 (Determine fate of section 6 last paragraph) closed by kboth+ietf@…
fixed: Cut the first sentence but kept the second with an INFORMATIONAL tag.
13:38 Ticket #10 (Should the statement about interpreting broken chains (4.1.1, last ...) closed by kboth+ietf@…
fixed: Moved the paragraph to the end of the verifier actions section …
13:17 Ticket #18 (Error in current example ARC-enhanced DMARC report) closed by kboth+ietf@…
fixed: fixed in -14; there was no objection earlier, just overlooked
13:14 Ticket #19 (Determine whether "A-R" is an acceptable abbreviation for ...) closed by kboth+ietf@…
fixed: Updated the document per option 3 (replace the abbreviation …

06/04/18:

16:46 Ticket #22 (Perverse incentives to use p!=none & pct=0) created by kboth+ietf@…
Pursuant to an email thread on the mailop list, we may want to …

02/04/18:

18:58 Ticket #8 (ARC definition statements are too DMARC-heavy) closed by kboth+ietf@…
fixed

21/03/18:

14:40 Ticket #21 (Resolve which document defines the ptypes & properties for AAR) created by kboth+ietf@…
Ongoing debate exists about whether to defined the necessary fields in …
14:37 Ticket #20 (Should 5322.from domain (Hdr From) be recorded in AAR?) created by kboth+ietf@…
Following the discussion @ IETF101 regarding "virtual DMARC", should …

19/03/18:

10:35 Ticket #19 (Determine whether "A-R" is an acceptable abbreviation for ...) created by kboth+ietf@…
In section 3.2 (draft version -12), the abbreviation is defined and …
Note: See TracTimeline for information about the timeline view.