IMHO, the interoperability sections 8.5 and 8.6 as currently in the dmarcbis I-D are necessary and useful. They may require minor changes, spelt out below. By contrast, Section 7.6 is useless and should be removed.

Section 8.6, *Interoperability Considerations*

The second part of the section suggests that receivers apply /more analysis/ before rejecting a message based on DMARC results. Such analysis is not specified, so those paragraphs might be misunderstood as a generic invite to not honor DMARC. I suggest to specify more exactly what receivers are invited to do.

OLD
   |  It is therefore critical that receiving domains MUST NOT reject
   |  incoming messages solely on the basis of a p=reject policy by the
   |  sending domain.  Receiving domains must use the DMARC policy as
   |  part of their disposition decision, along with other knowledge and
   |  analysis.


NEW
   |  It is therefore REQUIRED that receiving domains exempt from DMARC
   |  disposition messages forwarded by trusted third parties, either
   |  aliases or mailing lists, provided that forwarders are authenticated
   |  by a secure method.  Receiving domains must seek methods to
   |  acknowledge forwarders' quality and grant trust where deserved.


Section 8.5, *Interoperability Issues*

This section seems to me to lack some kind of conclusion. What do we mean by /interoperability/, actually? Here's an attempt:

OLD
    Mail that is sent by authorized, independent third parties might not be
    sent with Identifier Alignment, also preventing a "pass" result.

NEW
    Mail that is sent by authorized, independent third parties might not be
    sent with Identifier Alignment, also preventing a "pass" result.  In
    case of strict policies, this can prevent proper functioning of alias
    or mailing list forwarding (Section 3.9 of [RFC5321]).  The "improper"
    functioning that often results is an interoperability issue.


Best
Ale
--
I'm writing on the same, seldom used laptop that yesterday failed.
I had got it in Atalanta in 2012, when the previous device unexpectedly crashed.

_______________________________________________
dmarc mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dmarc

Reply via email to