Thanks, Brandon for filing the bug. I'll offer the following for consideration...
We, internet service operators, must categorically stop referring to domains levels (first, second, third, etc.) and instead evaluate based on the public suffix of any given domain. The Public Suffix List [0] allows us to do just that. The US. zone is not strictly a two-level domain, although many two and three level domains exist. In fact, a vast majority of the "independently authoritative" zones are at the second level but many others exist at the third and fourth levels. RFC1480 provides some historical context about where 3 & 4 level names exist. Essentially, the two characters postal abbreviation for a state marks the boundary. The third level domains, under the "second level" state code, can be registered independently. For example, lib.mi.us. is deligated to Merit Network and royal-oak.mi.us. is deligated to MultiParadigm. Both organizations offer fourth level registrations of their respective zones. tln.lib.mi.us. is registered and used by The Library Network independent of all other fourth level lib.mi.us. domains. At the same time, ci.royal-oak.mi.us. is registered and used independently by The City of Royal Oak, MI. If DMARC specifies that we should "ignore TLDs"; it should most certainly be interpreted as "ignore public suffixes" as the definition of "top-level" is contextual. - - Mitchell [0] https://publicsuffix.org/ ----- Original Message ----- From: "Brandon Long via dmarc-discuss" <dmarc-discuss@dmarc.org> To: st...@wordtothewise.com Cc: "DMARC Discussion List" <dmarc-discuss@dmarc.org> Sent: Friday, October 27, 2017 6:45:58 PM Subject: Re: [dmarc-discuss] Google not sending aggregate reports for my .US TLD yeah, seems reasonable, I'll file a bug. Brandon On Fri, Oct 27, 2017 at 3:44 PM Steve Atkins via dmarc-discuss < [ mailto:dmarc-discuss@dmarc.org | dmarc-discuss@dmarc.org ] > wrote: > On Oct 27, 2017, at 3:15 PM, Tyler South via dmarc-discuss < [ > mailto:dmarc-discuss@dmarc.org | dmarc-discuss@dmarc.org ] > wrote: > > The domain in question is [ http://cssi.us/ | cssi.us ] > > Thanks for any assistance you can provide. > Looks reasonable to me. v=DMARC1;rua=mailto: [ mailto:983a6a4164b9...@rep.dmarcanalyzer.com | 983a6a4164b9...@rep.dmarcanalyzer.com ] ,mailto: [ mailto:dmarc...@cssi.us | dmarc...@cssi.us ] ;ruf=mailto: [ mailto:983a6a4164b9...@for.dmarcanalyzer.com | 983a6a4164b9...@for.dmarcanalyzer.com ] ,mailto: [ mailto:dmarc...@cssi.us | dmarc...@cssi.us ] ; p=reject; fo=1; sp=none [ http://tools.wordtothewise.com/dmarc/check/cssi.us | http://tools.wordtothewise.com/dmarc/check/cssi.us ] Maybe someone at Google can take a look? Cheers, Steve > On Fri, Oct 27, 2017 at 5:08 PM, Tyler South < [ mailto:tsou...@gmail.com | > tsou...@gmail.com ] > wrote: > Hey everyone, > > > We’ve been trying to track down what could possibly be causing this issue. > Google nevers send an aggregate report for our .US domain. > > > > We get aggregate reports from AOL, Yahoo, and Outlook on occasion but have > yet to get a single report from Google. > > > We use this very same .US domain to receive DMARC reports, both aggregate and > forensic, for about ten other domains that we manage. Google sends us > aggregate reports about those domains every day. > > > So we do get aggregate reports from Google for other domains in which we are > setup as the rua.We just don't get them for our own domain. > > > The DMARC record for our domain is, "v=DMARC1;rua=mailto: [ > mailto:aggrepo...@xxxxx.us | aggrepo...@xxxxx.us ] ;ruf=mailto: [ > mailto:forrepo...@xxxxx.us | forrepo...@xxxxx.us ] ; p=reject; fo=1; sp=none" > > > We have modified it several times in failed attempts to resolve this issue. > We tried changing the RUA to other domains and services such as DMARCAnalyzer > and we have pretty much tried everything as far as changing tags in the DMARC > record goes. > > > Here is a copy of a DMARC record for a domain that google DOES send reports > for to us, "v=DMARC1;rua=mailto: [ mailto:aggrepo...@xxxxx.us | > aggrepo...@xxxxx.us ] ;ruf=mailto: [ mailto:forrepo...@xxxxx.us | > forrepo...@xxxxx.us ] ; p=reject; fo=1;" > > > We can’t figure out any pattern to this madness. > > > I mentioned our domain being a .US TLD repeatedly because I’m almost > convinced there is a bug that has something to do with reports not being > generated for a .US TLD. > > > Can anyone else with a .US TLD confirm you get reports from Google? > > > > If anyone has any ideas we’d really appreciate your time. This has been > driving us mad. > > > Thanks. _______________________________________________ dmarc-discuss mailing list dmarc-discuss@dmarc.org http://www.dmarc.org/mailman/listinfo/dmarc-discuss NOTE: Participating in this list means you agree to the DMARC Note Well terms (http://www.dmarc.org/note_well.html)
