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

"John Levine" <johnl@taugh.com> Fri, 19 April 2019 21:24 UTC

Return-Path: <johnl@iecc.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 89BFD120156 for <dmarc@ietfa.amsl.com>; Fri, 19 Apr 2019 14:24:42 -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, HEADER_FROM_DIFFERENT_DOMAINS=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=A4AT7tAe; dkim=pass (1536-bit key) header.d=taugh.com header.b=KhFits+7
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 Mjqgs0Ii3ItB for <dmarc@ietfa.amsl.com>; Fri, 19 Apr 2019 14:24:40 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 862C7120131 for <dmarc@ietf.org>; Fri, 19 Apr 2019 14:24:40 -0700 (PDT)
Received: (qmail 47753 invoked from network); 19 Apr 2019 21:24:38 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=ba7c.5cba3c96.k1904; bh=kt77yDCsRSNwHDmZYo1P7+SoVZ8299aUOkYglCo6i6I=; b=A4AT7tAebs76gdatZmnjHtYmNnGDrqVsVlUfO364pWX7BJVEMYTXTJ24Jsr6/+W9vUwPN8DOA09D6ube4iMHp+mf2zxX5Lwax23rYDO5TvnmUBmrgAho7xAgPn71MGPAgaPv0/xyVnOJyuYZ7kzJ6iXPfYzv96jmmzgBbLj/agOANzIXqUQFZRaIMyhtddePAA+3zFx/x0p+Gx/8J9CXWpSO3j07a9phSL+gAC/khLqpFTm6wFxrwI5sbG+Ubh8n
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=ba7c.5cba3c96.k1904; bh=kt77yDCsRSNwHDmZYo1P7+SoVZ8299aUOkYglCo6i6I=; b=KhFits+7w6CmbIh/4oHZ5yqemhDkauiV1mHRaLduzkhAdnuESyzs49ez/flsYSkzwRxDDoxvtHSHr2WsAsZOqTot9HkaBjmF+3Xhj37beKbeFGRiEbzVHQfBtR08mvoJCp+Pw2N4OnDuoSmYrKSWBIg4BFXmKlNg9VeYrqTSZtYRcOBIeSmRT6vNKx/9vgkNRzVPgleqg66Z+ZLXFQSeIY4sflmLwmi/5JzKV5T2ekqHGFQw46h/ll5BOYs9/enz
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTP via TCP6; 19 Apr 2019 21:24:37 -0000
Received: by ary.qy (Postfix, from userid 501) id B66E72012B0300; Fri, 19 Apr 2019 17:24:37 -0400 (EDT)
Date: 19 Apr 2019 17:24:37 -0400
Message-Id: <20190419212437.B66E72012B0300@ary.qy>
From: "John Levine" <johnl@taugh.com>
To: dmarc@ietf.org
Cc: sklist@kitterman.com
In-Reply-To: <1897481.12dR8pik7S@kitterma-e6430>
Organization: Taughannock Networks
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/n4mqBS0Ee2sE2jrI7B-uC1b2r3E>
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 21:24:43 -0000

>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

I only see 1527 with no dot.  Since there's only 1532 TLDs it's hard to
see where another 1500 could come from.

The other numbers look right.

R's,
John