Opened 4 months ago

Last modified 3 months ago

#121 new enhancement

Single-Level Tree Walk

Reported by: dougfoster.emailstandards@… Owned by:
Priority: minor Milestone: Deliverable #3 (changes to DMARC base spec + DMARC Usage Guide
Component: dmarc-bis Version:
Severity: - Keywords:
Cc:

Description

DMARC Policies can only be configured within leaf nodes underneath a DNS domain, while email suffixes can be configured as either DNS domain names or host names within a DNS domain. When the email suffix is not a DNS domain, the domain owner cannot specify a DMARC policy. Therefore, the evaluator can only use the SP clause of the organizational domain policy. An optimal design should provide a granular option for any email suffix.

One solution to this problem would be to allow DMARC policies to be implemented as TXT records that match the name of the email suffix. This approach seems too disruptive to existing implementations.

Instead, I propose a one-level domain walk when a DMARC policy does not exist for the email suffix, and the email suffix is two or more segments below the organizational domain. This allows non-domain email suffixes to benefit from the SP clause of the parent subdomain’s DMARC policy, rather than being protected only by the organizational SP policy. The SP clause of subdomain DMARC policies are currently unused, so the proposal is upward compatible.

Risk Assessment:

If the Organizational SP policy matches the new parent subdomain SP policy, then the evaluation result will be the same whether or not the evaluator uses the one-level walk feature.

If the Organizational SP policy is weaker than the parent subdomain SP policy, then evaluators which do not implement the one-level walk will apply the same result as if the additional SP policy did not exist. Evaluators which do implement the one-level walk will benefit from the stricter policy.

If an Organizational SP policy is stronger than the parent subdomain SP policy, then evaluators which do not use the one-level domain walk will obtain a result which is stricter than the domain owner intends, while those that evaluate the one-level walk will obtain the weaker policy that the domain owner intends. In the absence of a one-level walk, the domain owner can only ensure a weak policy at the lower policy by applying a weak SP policy for all levels.

Change History (1)

comment:1 Changed 3 months ago by todd.herr@…

  • Milestone set to Deliverable #3 (changes to DMARC base spec + DMARC Usage Guide
Note: See TracTickets for help on using tickets.