Re: [dmarc-ietf] Thoughts on choosing N

Scott Kitterman <sklist@kitterman.com> Mon, 15 April 2024 11:58 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 58933C14F619 for <dmarc@ietfa.amsl.com>; Mon, 15 Apr 2024 04:58:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.398
X-Spam-Level:
X-Spam-Status: No, score=-4.398 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=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="yje1dzJz"; dkim=pass (2048-bit key) header.d=kitterman.com header.b="lolc1yGR"
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9PlHdLCn54DM for <dmarc@ietfa.amsl.com>; Mon, 15 Apr 2024 04:58:04 -0700 (PDT)
Received: from interserver.kitterman.com (interserver.kitterman.com [64.20.48.66]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3EC62C14F69B for <dmarc@ietf.org>; Mon, 15 Apr 2024 04:58:03 -0700 (PDT)
Received: from interserver.kitterman.com (interserver.kitterman.com [IPv6:2604:a00:6:1039:225:90ff:feaa:b169]) by interserver.kitterman.com (Postfix) with ESMTPS id D994BF80238; Mon, 15 Apr 2024 07:57:53 -0400 (EDT)
DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201903e; t=1713182258; h=date : from : to : subject : in-reply-to : references : message-id : mime-version : content-type : content-transfer-encoding : from; bh=M/80gIIb8/SUmJZ540AjaHlf7/deN/ewGNyfYarDgl4=; b=yje1dzJzK957L/lBcOzgfKk7Fc4MrTvph5Dq1qpDjEgcEc9BvIfIjKteI7ahfFboH/vqk r3tsvHcF9ClDKHnAg==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201903r; t=1713182258; h=date : from : to : subject : in-reply-to : references : message-id : mime-version : content-type : content-transfer-encoding : from; bh=M/80gIIb8/SUmJZ540AjaHlf7/deN/ewGNyfYarDgl4=; b=lolc1yGRIKeINXhrRkGzDU8ZLr2EUYGdAyq8YgAJewU/sG07JYRQaDwZIN7vUYgf28cmT HTnHyqwIXeWOhereSEnDW6IY97bYw/PgZsmtMsu7O5VkTNq8Iawv1Dtiqxa80d4zRIQTBCS wExzoARuuSI+4M5jZo21UGcQZUOrVyNpsvViQzFXfbyjT77JAiCjb2WChLW+8wOwSs6j4QD SOV7r+HgLoD3Z66g13X5JAMXL5de97AXtMA2TQf/u4DRZgoMm8heQCIBLHwsFlIxNluk8xU IJLaMKLAUrLxYe+OmO/iuDdwVF/QSRgclMq671HMj3ibG94p4aCam4uYLAFA==
Received: from [127.0.0.1] (static-72-81-252-22.bltmmd.fios.verizon.net [72.81.252.22]) by interserver.kitterman.com (Postfix) with ESMTPSA id 5804CF80035; Mon, 15 Apr 2024 07:57:38 -0400 (EDT)
Date: Mon, 15 Apr 2024 11:57:33 +0000
From: Scott Kitterman <sklist@kitterman.com>
To: dmarc@ietf.org
In-Reply-To: <a2bd52d6-7bb3-4526-a0d8-075f4ab44f33@tana.it>
References: <CAOZAAfPwJHKGyLjTkdGDqkMeK4RQX4Fj0rw-Upn0cLZ+cE74aA@mail.gmail.com> <2764165.rv8vZNihtd@zini-1880> <53f29df5-031a-8711-aed6-25c310f539a2@iecc.com> <8C54A48A-5665-41A1-B64F-93A39CF0B12C@kitterman.com> <CAL0qLwZ2TuV_EW6D9HZYwErmwL_n7q4ZKTEpHBZbyxnkKJ8m6w@mail.gmail.com> <CAH48ZfzckPscoSPUVEqy1WS71iAnKyj7gQVDOW4Hi=FXo0PzYg@mail.gmail.com> <a2bd52d6-7bb3-4526-a0d8-075f4ab44f33@tana.it>
Message-ID: <92E339E5-0A4C-4929-A751-375B892C2C53@kitterman.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/YyXnJ7dV5a3Bzs_8-Wd-pKZqRyI>
Subject: Re: [dmarc-ietf] Thoughts on choosing N
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.39
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: Mon, 15 Apr 2024 11:58:08 -0000


On April 15, 2024 11:43:08 AM UTC, Alessandro Vesely <vesely@tana.it> wrote:
>On Mon 15/Apr/2024 13:16:50 +0200 Douglas Foster wrote:
>> Our original choice of N was based on the PSL.    The PSL could not detect organizational boundaries could not boundaries below level 5, because it had no entries longer than 5 labels, and we determined that the 5-label entries were not used for mail.    Therefore, any increase in N is new capability.   That new capability is probably desirable, but need not be limitless.  Using an N of 8 introduces a lot of new capability.
>
>
>8 is not needed and not justified.  A mail site using 8 labels would have troubles with the RFC 7489 version, which uses the PSL.  They'd have to ask for PSL upgrades, right?
>
>Now, we can relax our ambition to be PSL-free and state N=max number of labels of public suffixes used by mail.  Or we could put N in an IANA registry that can be updated by expert review.  Such methods allow to have N low enough, yet upgradable and equal for all (compliant) implementations.
>
>Otherwise we can drop the requirement that N be equal for all implementations, and just make it configurable.  After all, it is an anti-abuse measure, akin to SPF lookup limit.  We can also keep it fixed at 5 and be sure that implementations will differ anyway.
>
Whatever we decide, I think it needs to be specified.  If N is whatever, you will end up with difficult to troubleshoot interoperability issues when various sites pick different values.

I don't think we need to worry about revising it later.  In general, DNS is getting wider (new TLDs), not deeper.

Scott K