On 1/29/2021 6:59 AM, Tim Wicinski wrote:
This starts a *one week* Working Group Last Call.


Sorry, but even the Abstract appears to be littered with problematic language.

I always try to provide alternate language, when I can, but in spite of having offered suggestions for this document in the past, I can't for this set.


Abstract

    DMARC (Domain-based Message Authentication, Reporting, and
    Conformance) is a scalable mechanism by which a mail-originating
    organization can express domain-level policies and preferences for
    message validation, disposition, and reporting, that a mail-receiving
    organization can use to improve mail handling.  The design of DMARC
    presumes that domain names represent either nodes in the tree below
    which registrations occur, or nodes where registrations have
DMARC does not have 'registrations'.

Also the occur/occured contrast has no obvious meaning to me. Really, I have no idea what's intended by it.


    occurred; it does not permit a domain name to have both of these
"both" of what?  registration?


    properties simultaneously.  Since its deployment in 2015, use of
    DMARC has shown a clear need for the ability to express policy for
    these domains as well.
Which domains?


    Domains at which registrations can occur are referred to as Public
    Suffix Domains (PSDs).  This document describes an extension to DMARC
    to enable DMARC functionality for PSDs.
This is the definition of public suffix provided by the PSL folk:

"A public suffix is a set of DNS names or wildcards concatenated with dots. It represents the part of a domain name which is *not* under the control of the individual registrant."


    This document also seeks to address implementations that consider a
    domain on a public Suffix list to be ineligible for DMARC
    enforcement.
seeks?

implementations don't 'consider' anything.

is 'ineligibility' really the essential issue?

d/


--

Dave Crocker
[email protected]
408.329.0791

Volunteer, Silicon Valley Chapter
American Red Cross
[email protected]

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

Reply via email to