[dmarc-ietf] What happens for org and PSD lookups when you are already above the PSL boundary?

Kurt Andersen <kurta@drkurt.com> Thu, 18 April 2019 19:46 UTC

Return-Path: <kurta@drkurt.com>
X-Original-To: dmarc@ietfa.amsl.com
Delivered-To: dmarc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC1651203E2 for <dmarc@ietfa.amsl.com>; Thu, 18 Apr 2019 12:46:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=drkurt.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YLSnJnMMr_Ca for <dmarc@ietfa.amsl.com>; Thu, 18 Apr 2019 12:46:12 -0700 (PDT)
Received: from mail-it1-x12e.google.com (mail-it1-x12e.google.com [IPv6:2607:f8b0:4864:20::12e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 931301203E7 for <dmarc@ietf.org>; Thu, 18 Apr 2019 12:46:12 -0700 (PDT)
Received: by mail-it1-x12e.google.com with SMTP id y134so5134287itc.5 for <dmarc@ietf.org>; Thu, 18 Apr 2019 12:46:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=drkurt.com; s=20130612; h=mime-version:from:date:message-id:subject:to; bh=MRVEGX3MhvWRBBcSeygbFJhW0wDj6DolgDmKKimbrIQ=; b=ZmQ95hmm/Ukvi6tjwhgOKMWFUhQCjRT2t06XeO0udvncuiep2NzFgeJPrU9nD3vHLm 1LdYz3NswYtmwtwOqWemolR7itjAzk2Qw+hJp8olLNZExtD/RW+QlyoXsmxQedwbaMdD PHezgzsdYVkZyvCsxeG1t4iEC5LvzflpqzlmQ=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=MRVEGX3MhvWRBBcSeygbFJhW0wDj6DolgDmKKimbrIQ=; b=WRAOn69kw5JhFpi+4kB4X7UCjUrFSeBL0U+xciF8i6QHHSg/vu2jyJQZ7TbHwGt9QI 7Lyz9WjZJpht193XSL5S+eosN62s3/21d3QlTNHZCCB7JE0TEQDRYC3qwevRgOTU6f2W a59u1spUrXpNhn84R96NN+8Tc/paX7iVMI8N/akmNTpmoYuyk6bUTrTq6kJPcE3faxTt 54sJMYyeni9u18UDj4Q2ljLyioXtXzxXZ+9EcILZ6CJkjlAxbeUD+QxQOSnN82W5nklb RTWF6p/n28UJAsc35RATujuUOcKBr6qfRlpDO8YIWNyO7fP5AS3kdUMzGJpCGkr0gvoI vQUA==
X-Gm-Message-State: APjAAAXA+JFjuLJC2nKjw7+ysoMVI5cfK9t5dXJ+ROi95lCMluwlbaDl kurkdLuPZZkYLqfRoVvim9a3JU2lQfckQNsY9QjmkAUV3cORLg==
X-Google-Smtp-Source: APXvYqxDI62ygxcsiIWVzjBO+T6LVcSXCywDN41rrvyL/GjFDI+GJtvPn+zLILT2A5hDwI6a2Xux/PfbcAy5gtfXq/Y=
X-Received: by 2002:a24:e004:: with SMTP id c4mr5351339ith.78.1555616771153; Thu, 18 Apr 2019 12:46:11 -0700 (PDT)
MIME-Version: 1.0
From: Kurt Andersen <kurta@drkurt.com>
Date: Thu, 18 Apr 2019 12:45:42 -0700
Message-ID: <CABuGu1qEbPGed+abDH8Ps06+4L=hQn+9QrbZc9EDsWmoQHWVsg@mail.gmail.com>
To: "dmarc@ietf.org" <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000000d36180586d3417a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/aFJkMOtx6diSrzjIRT51JeoYO5k>
Subject: [dmarc-ietf] What happens for org and PSD lookups when you are already above the PSL boundary?
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dmarc>, <mailto:dmarc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Apr 2019 19:46:15 -0000

If we have a boundary that is 6 names deep in the DNS hierarchy (so the org
domain would be 7 names long), then what is a DMARC validator supposed to
do with an email that claims to come from the domain that is only 5 names
long? What happens to the second lookup (org-level)?

Example:

priv-org.psd-a.b.c.d.e.example: If an email comes from
sub1.priv-org.psd-a.b.c.d.e.examplepriv-org.psd-a.b.c.d.e.example, then
lookup 1 is for _dmarc.sub1..., lookup 2 is _dmarc.priv-org... and the
proposed lookup 3 (for PSD protection) would be _dmarc.psd-a...

If the email comes from b.c.d.e.example, then lookup 1 is _dmarc.b... but
what would lookups 2 and 3 be? skipped?

--Kurt