Re: [dmarc-ietf] Thoughts on choosing N

Alessandro Vesely <vesely@tana.it> Mon, 15 April 2024 11:43 UTC

Return-Path: <vesely@tana.it>
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 F174EC14F69B for <dmarc@ietfa.amsl.com>; Mon, 15 Apr 2024 04:43:16 -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=pass (1152-bit key) header.d=tana.it
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 Mn6hXioPJUr9 for <dmarc@ietfa.amsl.com>; Mon, 15 Apr 2024 04:43:12 -0700 (PDT)
Received: from wmail.tana.it (wmail.tana.it [94.198.96.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DFA8EC14F5FE for <dmarc@ietf.org>; Mon, 15 Apr 2024 04:43:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1713181386; bh=KSABQRY/qceJq19cgdVzMg+Yen33OfeQLal9a29cXlg=; h=Date:Subject:To:References:From:In-Reply-To; b=BzacW3VdzcI5xjNs8rj2rylg3jOAzQNNMixjTECSHe1076AkVGauZl+VnaNy840Mn 2rH8WJslyHowxulI9dj0US8xhi0hqnYqHqtrQ1Ppkl+9IhY2LHlvyoj8AvkfjZZZ/7 8NcnlX+xB90sW4ujQc7i9I+Cec8srP8dBGxNfXDoT20w0vDKzljrTCw7p0qd2
Original-Subject: Re: [dmarc-ietf] Thoughts on choosing N
Author: Alessandro Vesely <vesely@tana.it>
Received: from [172.25.197.120] (pcale.tana [::ffff:172.25.197.120]) (AUTH: CRAM-MD5 uXDGrn@SYT0/k, TLS: TLS1.3, 128bits, ECDHE_RSA_AES_128_GCM_SHA256) by wmail.tana.it with ESMTPSA id 00000000005DC028.00000000661D12CA.00002D1C; Mon, 15 Apr 2024 13:43:06 +0200
Message-ID: <a2bd52d6-7bb3-4526-a0d8-075f4ab44f33@tana.it>
Date: Mon, 15 Apr 2024 13:43:08 +0200
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
To: dmarc@ietf.org
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>
Authentication-Results: tana.it; auth=pass (details omitted)
From: Alessandro Vesely <vesely@tana.it>
Content-Language: en-US, it-IT
In-Reply-To: <CAH48ZfzckPscoSPUVEqy1WS71iAnKyj7gQVDOW4Hi=FXo0PzYg@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/Ok6m3YFJpupIdcNa7XBa9D_QkYk>
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:43:17 -0000

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.


Best
Ale
--