On Fri, Nov 6, 2020 at 7:27 AM Douglas E. Foster <fosterd=
40bayviewphysicians....@dmarc.ietf.org> wrote:

> I am just catching on to the implications of this discussion, and I must
> disagree
>
> It makes no sense to allow "p=" missing.   Why would we suggest that all
> existing implementations alter their code to tolerate additional
> unnecessary complexity, rather than requiring domain administrators to key
> a few more characters so that code changes will not be necessary?
>
> There is no functional difference between "p=" missing and "p=none".  Both
> configurations state: "I don't know what to tell you, you are on your own."
>

I disagree with the assertion that p=none means "I don't know what to tell
you".

"p=none" is the starting point for all DMARC implementations in any
non-trivial environment. "p=none" allows the domain owner, through the
consumption of DMARC reports, to effectively audit their own understanding
of their mailstreams and authentication practices, and address any
shortcomings before eventually moving along, theoretically, to
"p=quarantine" or "p=reject".


> I also don't understand this comment from Allesandro :
>
> "Operators who don't need policy, for example external report receivers
> who just
> want to publish verification records, would find the relevant info in the
> base
> spec."
>
> There is only one policy record, published by the domain owner.  The DNS
> record either suggests enforcement (p=quarantine, p=reject) or it does not
> (p=none, p=missing, no DMARC record).
>
>
I can't speak for him, but I believe he's referring to the records that a
report consumer outside the authority of the domain at issue might publish,
as documented currently in https://tools.ietf.org/html/rfc7489#section-7.1.
In those cases where, for example, foo.com publishes a DMARC policy record
with a rua= value of say "repo...@bar.org", there must exist a TXT record
of "v=DMARC1" at foo.com._report._dmarc.bar.org in order to confirm that
bar.org is consenting to receive these reports.

-- 

*Todd Herr* | Sr. Technical Program Manager
*e:* todd.h...@valimail.com
*p:* 703.220.4153


This email and all data transmitted with it contains confidential and/or
proprietary information intended solely for the use of individual(s)
authorized to receive it. If you are not an intended and authorized
recipient you are hereby notified of any use, disclosure, copying or
distribution of the information included in this transmission is prohibited
and may be unlawful. Please immediately notify the sender by replying to
this email and then delete it from your system.
_______________________________________________
dmarc mailing list
dmarc@ietf.org
https://www.ietf.org/mailman/listinfo/dmarc

Reply via email to