Opened 5 years ago

Closed 5 years ago

#18 closed defect (fixed)

Error in current example ARC-enhanced DMARC report

Reported by: kboth+ietf@… Owned by: draft-ietf-dmarc-arc-protocol@…
Priority: minor Milestone: Deliverable #2 (DMARC improvements to better support indirect email flows)
Component: arc-protocol Version:
Severity: Active WG Document Keywords:


Re: -12, it doesn't appear to capture the feedback in the email Mark Eissler sent to the list on 2/27. There was also no on-list reply to his email that I saw, so I wanted to re-raise the issue. His email is included below.

Mark's analysis appears to be on-point, and I think the XML fragment he references (now in ARC draft-12 section 7.3) should be revised to:



<comment>arc=pass ams[2].d=d2.example ams[2].s=s1 as[2].d=d2.example
as[2].s=s2 as[1].d=d1.example as[1].s=s3</comment>



As he notes, this is consistent with the existing DMARC aggregate report schema and the source_ip is already captured in an XML element that is a sibling to <policy_evaluated> per Appendix C of RFC 7489, in the definition of the complex type RowType?.

If you believe this is a correct update, can we get it incorporated into the draft? If not, where's the mistake in the above?

Change History (1)

comment:1 Changed 5 years ago by kboth+ietf@…

  • Resolution set to fixed
  • Status changed from new to closed

fixed in -14; there was no objection earlier, just overlooked

Note: See TracTickets for help on using tickets.