All,

I've been implementing the S4.10 DNS Tree Walk in OpenDMARC (replacing
the old PSL-based lookup for the Organizational Domain) and hit a few
spots where the text doesn't quite pin down what to do. Figured it was
worth asking rather than guessing and shipping it.

1. Walk exhaustion without psd= (S4.10.1)

If the walk runs out of labels without ever finding a record with
psd=n or psd=y, but it passed one or more valid DMARC Policy Records
(no psd= tag) along the way, does that count as "the set produced by
the DNS Tree Walk contains no DMARC Policy Record" (S4.10.1), or do
those earlier records still count for something? Right now we're
treating exhaustion-without-psd= the same as no-record-found at all,
which seemed like the safe reading, but it's not stated either way as
far as I can tell.

2. "might" in S4.10.2

S4.10.2 says alignment-evaluation tree walks "might" start at the
Author Domain, the SPF-Authenticated Identifier, or a DKIM-Authenticated
Identifier. Since "might" isn't 2119 language, is it actually optional
whether an implementation runs separate walks per identifier, or is
reusing the org domain from policy discovery for all of them not
really compliant? S5.3.4 points back at 4.10.2 normatively, so I want
to make sure we're not quietly skipping something that's meant to be
required.

3. "one label below" plus the 8-label shortcut (S4.10 step 4, S4.10.2 step 2)

S4.10.2 step 2 says when psd=y shows up somewhere other than the
walk's starting domain, the Organizational Domain is the domain one
label below it in the DNS hierarchy. But if the walk got there via the
8-label shortcut, it may never have actually queried that intermediate
label. We're reconstructing "one label below" from the original
starting domain rather than from whatever the walk's previous step
happened to be, since the previous step may not be that label at all
in shortcut cases. Does that match what you intended?

I recognize that "8" was chosen because you only observed up to 7 in the wild, 
so wanted to be conservative, but I also want to cover the edge case.

4. What happens to the non-psd= records collected along the way (S4.10.2)

The step 3 selection ("found at the name with the fewest number of
labels") only makes sense if the walk is accumulating every valid
record it sees, not just whatever it has when it stops. We're
accumulating all of them and running the psd=n / psd=y / fewest-labels
selection after the walk finishes. Wanted to confirm that's the model
rather than, say, only the stopping record being eligible.

Thanks for any clarification.

Dan Mahoney

_______________________________________________
dmarc mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to