<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-dmarc-interoperability" target="https://datatracker.ietf.org/doc/html/draft-ietf-dmarc-interoperability-18">
   <front>
      <title>Interoperability Issues between Domain-based Message Authentication, Reporting, and Conformance (DMARC) and Indirect Email Flows</title>
      <author initials="F." surname="Martin" fullname="Franck Martin">
         <organization>LinkedIn</organization>
      </author>
      <author initials="E." surname="Lear" fullname="Eliot Lear">
         <organization>Cisco Systems GmbH</organization>
      </author>
      <author initials="T." surname="Draegen" fullname="Tim Draegen">
         </author>
      <author initials="E." surname="Zwicky" fullname="Elizabeth Zwicky">
         <organization>Yahoo</organization>
      </author>
      <author initials="K." surname="Andersen" fullname="Kurt Andersen">
         <organization>LinkedIn</organization>
      </author>
      <date month="July" day="18" year="2016" />
      <abstract>
	 <t>Domain-based Message Authentication, Reporting, and Conformance (DMARC) introduces a mechanism for expressing domain-level policies and preferences for email message validation, disposition, and reporting.  However, the DMARC mechanism enables potentially disruptive interoperability issues when messages do not flow directly from the author&#x27;s administrative domain to the final Recipients.  Collectively, these email flows are referred to as &quot;indirect email flows&quot;.  This document describes these interoperability issues and presents possible methods for addressing them.
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-dmarc-interoperability-18" />
   
</reference>
