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

Scott Kitterman <sklist@kitterman.com> Sat, 20 April 2019 02:35 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 344A012019A for <dmarc@ietfa.amsl.com>; Fri, 19 Apr 2019 19:35:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-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=0gmlKxT7; dkim=pass (2048-bit key) header.d=kitterman.com header.b=bLSXCM4N
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 N40pPiQQhXrJ for <dmarc@ietfa.amsl.com>; Fri, 19 Apr 2019 19:35:29 -0700 (PDT)
Received: from interserver.kitterman.com (interserver.kitterman.com [64.20.48.66]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B68AE12004F for <dmarc@ietf.org>; Fri, 19 Apr 2019 19:35:29 -0700 (PDT)
Received: from interserver.kitterman.com (interserver.kitterman.com [64.20.48.66]) by interserver.kitterman.com (Postfix) with ESMTPS id 963C4F80319 for <dmarc@ietf.org>; Fri, 19 Apr 2019 22:35:27 -0400 (EDT)
DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201903e; t=1555727727; h=from : to : subject : date : message-id : in-reply-to : references : mime-version : content-transfer-encoding : content-type : from; bh=yeQvsJx8+U+h/Y1RqCRHm/425PgGa8pi7uegWn16VEE=; b=0gmlKxT7FU9ZwfcHnqU0rXFeeB8Oh2dK+Q/vhyTZxOEPEJV2mdIrQ5pQ ARjUCJYPDw+WayGRea3kmtjFeQDwAg==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201903r; t=1555727727; h=from : to : subject : date : message-id : in-reply-to : references : mime-version : content-transfer-encoding : content-type : from; bh=yeQvsJx8+U+h/Y1RqCRHm/425PgGa8pi7uegWn16VEE=; b=bLSXCM4NWzgSiQJ5uUdhbBFsGFcLUjAnznrdiH+LkcO6XWEj+70UDphL s5TTsQiPvee83swQEiNGErr60uiJQG9xUXfx8fvVyFzmivdg7JqQhRYBSE VGYuYrIlEaCtMUuzGN4kwP+msBrozC1+xoQyPFRmdWO3OIsE8l2mDBaAeF oWUx1SRGUy+cnDxlBrBui1O9/nTPPCu0Arwl/7ecFQTRhTkduQjp3tGYCG 1ExRSkV0Y+9Uig24GB5QiF7VIw2MAlfP6edii0J4R0UA4JHHak0lgbRGJv i46SqHhixSNZWR1sW7VYQFC+NSPEOITCohvHTscet+roYwe7PcdE2w==
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 6173DF8027D for <dmarc@ietf.org>; Fri, 19 Apr 2019 22:35:27 -0400 (EDT)
From: Scott Kitterman <sklist@kitterman.com>
To: dmarc@ietf.org
Date: Fri, 19 Apr 2019 22:35:26 -0400
Message-ID: <2133744.rL2vL2M1mL@kitterma-e6430>
User-Agent: KMail/4.13.3 (Linux/3.13.0-168-generic; KDE/4.13.3; x86_64; ; )
In-Reply-To: <20190419212437.B66E72012B0300@ary.qy>
References: <20190419212437.B66E72012B0300@ary.qy>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/p5BXNyXrTwXjXuw0AohCAysK-Gc>
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: Sat, 20 Apr 2019 02:35:31 -0000

On Friday, April 19, 2019 05:24:37 PM John Levine 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
> 
> 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.

Thanks.  

My script was counting blank lines (sigh).  Now I get the same result you do.

That raises the three or more percentage over 27%.

Scott K