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

"Kurt Andersen (b)" <kboth@drkurt.com> Fri, 19 April 2019 16:12 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 268061202E7 for <dmarc@ietfa.amsl.com>; Fri, 19 Apr 2019 09:12:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, URIBL_BLOCKED=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 az1ASx_WXRL7 for <dmarc@ietfa.amsl.com>; Fri, 19 Apr 2019 09:12:16 -0700 (PDT)
Received: from mail-io1-xd2f.google.com (mail-io1-xd2f.google.com [IPv6:2607:f8b0:4864:20::d2f]) (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 627B0120172 for <dmarc@ietf.org>; Fri, 19 Apr 2019 09:12:16 -0700 (PDT)
Received: by mail-io1-xd2f.google.com with SMTP id r18so3904098ioh.2 for <dmarc@ietf.org>; Fri, 19 Apr 2019 09:12:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=drkurt.com; s=20130612; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=vvfdb3BvTJcIuluogwXnvPAZQIvRKf2UBgcv85ER0Jk=; b=HibGR9WdgnACebcnGvtCpEZPILKzaqCys1cx/cy91BBONvVEssbKsFcD2P7kzTgYFk oX49xxNbwNjy/dRLLrcRwwGpb1LjzOEKiLNTunAp9/4+5NBkEmZAOm1z5FlerFQBL8+N X9DBmhiE/Wq6iAbJjgN7wk9Fi8w6vTxLVVcPY=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=vvfdb3BvTJcIuluogwXnvPAZQIvRKf2UBgcv85ER0Jk=; b=XuQZQtBoy2S4eePkBKFiz0DZTG2ClO/ZVBxr12S9Th8KeqaNwMI9TfdzdWDAI8ikwR ez4/1A/nJg9rQhl5TKgojg2LUizjyFk/HOLbNVkD1NmSkTAh5EqGayAXpDzlstmv8AuD TQiREEQgh4wruew86EBoTc34S1QN4VMa3t8vrYt3GO+oAYYpo50jQJXyahI2oAwapj42 Tjk+BWMXyAAb1CAux75LHzZc8aiJ9vG5ujnAWuhgwDXiREjW0CvPRfCuynEYGtHLsZ9i 7IKRaAjdRlW2slDhfj4QGuT1IJe5hy+lifQJz8xCK6vDDARknDjy02DKXwTV3pm/G+9Y gzuw==
X-Gm-Message-State: APjAAAWspZhx3cLNgnw1KfzXrpaZcov9QX5rj10++KA3+tq5DbU5oq/p 4GqCqplyjq2N6CV4QayfQv+uQcZ9cL9I812feOCHqg==
X-Google-Smtp-Source: APXvYqxRlWdrGv5XDhhE69vkvUf3zKgRvlsIilEXnM3XL+HxsKui8UOKDBZVhYPbd3d3ZlWTSnQL72Fo1p/KbVtOXCY=
X-Received: by 2002:a5e:8517:: with SMTP id i23mr3033886ioj.228.1555690335355; Fri, 19 Apr 2019 09:12:15 -0700 (PDT)
MIME-Version: 1.0
References: <CABuGu1qEbPGed+abDH8Ps06+4L=hQn+9QrbZc9EDsWmoQHWVsg@mail.gmail.com> <1897481.12dR8pik7S@kitterma-e6430>
In-Reply-To: <1897481.12dR8pik7S@kitterma-e6430>
From: "Kurt Andersen (b)" <kboth@drkurt.com>
Date: Fri, 19 Apr 2019 09:11:45 -0700
Message-ID: <CABuGu1o4nAZ1uwLq+pTTZQ6ew3Mp2Yj6BrNnZfGDTPna2xs5Cg@mail.gmail.com>
To: Scott Kitterman <sklist@kitterman.com>
Cc: "dmarc@ietf.org" <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000d1e0860586e46113"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/WyLp693aLIyM0NQJv1ChGiA9hto>
Subject: Re: [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: Fri, 19 Apr 2019 16:12:18 -0000

On Fri, Apr 19, 2019 at 8:44 AM Scott Kitterman <sklist@kitterman.com>
wrote:

>
> I took a look at the non-comment content of the public portion of the PSL
> to
> get an idea of the scope of this problem.  Here's the distribution of
> lengths
> of public suffixes:
>
> one: 3077
> two: 3821
> three: 1986
> four: 3
>
> None longer than that, unless I screwed up my script.
>

While it may have changed since the days of DBOUND, I recall that there was
at least one hierarchy which had a public --> private --> public -->
private double transition which could make for longer names.

--Kurt