Folks,
The current draft has this text concerning Organizational Domain:
3.2.7.
<https://www.ietf.org/archive/id/draft-ietf-dmarc-dmarcbis-04.html#section-3.2.7>Organizational
Domain
<https://www.ietf.org/archive/id/draft-ietf-dmarc-dmarcbis-04.html#name-organizational-domain>
The Organizational Domain is typically a domain that was registered
with a domain name registrar. More formally, it is any Public Suffix
Domain plus one label. The Organizational Domain for the domain in the
RFC5322.From domain is determined by applying the algorithm found in
Section 4.6
<https://www.ietf.org/archive/id/draft-ietf-dmarc-dmarcbis-04.html#determining-the-organizational-domain>.
I believe the text is not adequately helpful, in terms of DMARC's
history, and especially not helpful in the move towards supporting (at
least) two very different methods of finding it. I understand the
desire to declare The One True mechanism, but I will claim it is too
late for that. Also, I think the term continues to be useful...
Here is some alternative phrasing:
For DMARC, an Organizational Domain can contain a DMARC record, to
be used as the default DMARC record for subordinate domains that do
not have a DMARC record of their own, and for subordinate domains
that do not exist.
This is text about the what, rather than the how. It defines
DMARC-relevant semantics, without saying anything about the mechanics of
finding it.
In that light, I'll renew my strong suggestion, from back in the days of
PSD development, that this core DMARC document NOT contain details or
sections devoted to PSD, in the style now shown in the current sections
3.2.8 - 3.2.10
Rather, I suggest adding an additional sentence to the alternative
phrasing, above:
The method of finding an Organizational Domain is outside the scope
of this specification. Examples of such methods include the Public
Suffice Domain (PSD) [RFC9091] and Public Suffix List
[http://publicsuffix.org].
I think this gives an adequate nod to established and new practice,
without emphasizing either or the excluding the possibility of other
methods.
d/
--
Dave Crocker
dcroc...@gmail.com
408.329.0791
Volunteer, Silicon Valley Chapter
Information & Planning Coordinator
American Red Cross
dave.crock...@redcross.org
_______________________________________________
dmarc mailing list
dmarc@ietf.org
https://www.ietf.org/mailman/listinfo/dmarc