IETF Logo Mail Archive

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

Scott Kitterman <sklist@kitterman.com> Fri, 19 April 2019 16:15 UTC

Return-Path: <sklist@kitterman.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 3287712035B for <dmarc@ietfa.amsl.com>; Fri, 19 Apr 2019 09:15:50 -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, SPF_HELO_FAIL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=neutral reason="invalid (unsupported algorithm ed25519-sha256)" header.d=kitterman.com header.b=kZdAmFP3; dkim=pass (2048-bit key) header.d=kitterman.com header.b=h0u3Gqu0
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 AI-QSejCntxc for <dmarc@ietfa.amsl.com>; Fri, 19 Apr 2019 09:15:48 -0700 (PDT)
Received: from interserver.kitterman.com (interserver.kitterman.com [IPv6:2604:a00:6:1039:225:90ff:feaa:b169]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 97AE0120331 for <dmarc@ietf.org>; Fri, 19 Apr 2019 09:15:48 -0700 (PDT)
Received: from interserver.kitterman.com (interserver.kitterman.com [64.20.48.66]) by interserver.kitterman.com (Postfix) with ESMTPS id BD4F8F8073D for <dmarc@ietf.org>; Fri, 19 Apr 2019 12:15:47 -0400 (EDT)
DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201903e; t=1555690547; h=from : to : subject : date : message-id : in-reply-to : references : mime-version : content-transfer-encoding : content-type : from; bh=kHnGPnWbNn0/4E/giPx0gL1Mu8nV9NXgaJsn7kkbJqo=; b=kZdAmFP3xtaA4xJ+VJ+aeJZ+Cn3WXtb1blx5qxcJCXdb6AZ97HrbD8Yl 1ErNSw3udO8Z0NE90PQS1aStIyFlAw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201903r; t=1555690547; h=from : to : subject : date : message-id : in-reply-to : references : mime-version : content-transfer-encoding : content-type : from; bh=kHnGPnWbNn0/4E/giPx0gL1Mu8nV9NXgaJsn7kkbJqo=; b=h0u3Gqu0ybrgjYn2Ox92GH5/eUIMfKk1V6QY7T8ejb9V/Mp6r7OH+9Xv lc5ytyRTIW2GWXSgfEnoaPOs6QolmBjVIHjmSv1+H2KBZgp1KCriJfr0Bt 8DbnGiaKIVFGDwD4MFR/Cbbpk85yT/6t+GmluVKIqh0wOc/nJBUSdtxPxJ G1vPsmvw2/lJddYoij3ia17rFOd7eqziSLDLnMHhzsRmhl0+6ze+r+p6c3 q6N2pUAe3LLVw7QReic3zYf/pKTtEjg5kwQdV+WZBxNmSN+4xEH/ytFnco 594YoVOCUCOXd6fOiDEHKDxSuocWACrWooJS2nEOCulmZa1ucZ/biQ==
Received: from kitterma-e6430.localnet (static-72-81-252-22.bltmmd.fios.verizon.net [72.81.252.22]) by interserver.kitterman.com (Postfix) with ESMTPSA id 91024F801E7 for <dmarc@ietf.org>; Fri, 19 Apr 2019 12:15:47 -0400 (EDT)
From: Scott Kitterman <sklist@kitterman.com>
To: dmarc@ietf.org
Date: Fri, 19 Apr 2019 12:15:42 -0400
Message-ID: <7073931.FQBSMkfpyc@kitterma-e6430>
User-Agent: KMail/4.13.3 (Linux/3.13.0-168-generic; KDE/4.13.3; x86_64; ; )
In-Reply-To: <CABuGu1o4nAZ1uwLq+pTTZQ6ew3Mp2Yj6BrNnZfGDTPna2xs5Cg@mail.gmail.com>
References: <CABuGu1qEbPGed+abDH8Ps06+4L=hQn+9QrbZc9EDsWmoQHWVsg@mail.gmail.com> <1897481.12dR8pik7S@kitterma-e6430> <CABuGu1o4nAZ1uwLq+pTTZQ6ew3Mp2Yj6BrNnZfGDTPna2xs5Cg@mail.gmail.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/OI2LHcYdmfLhjhDKdQxBYjNjOgY>
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:15:56 -0000

On Friday, April 19, 2019 09:11:45 AM Kurt Andersen wrote:
> 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.

OK.  I don't think that changes the analysis as long as all the public 
components are listed.

Scott K

v2.23.0 | Report a Bug | By Email