Re: [dmarc-ietf] what to document about the tree walk

John Levine <johnl@taugh.com> Wed, 13 July 2022 16:52 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 65680C14F741 for <dmarc@ietfa.amsl.com>; Wed, 13 Jul 2022 09:52:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.86
X-Spam-Level:
X-Spam-Status: No, score=-6.86 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, HEADER_FROM_DIFFERENT_DOMAINS=0.248, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=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 (2048-bit key) header.d=iecc.com header.b=aSQWyfiD; dkim=pass (2048-bit key) header.d=taugh.com header.b=dcffHThn
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 4jUOMLEN_-NR for <dmarc@ietfa.amsl.com>; Wed, 13 Jul 2022 09:52:34 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 75B71C14F6EC for <dmarc@ietf.org>; Wed, 13 Jul 2022 09:52:34 -0700 (PDT)
Received: (qmail 95350 invoked from network); 13 Jul 2022 16:52:32 -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:cleverness; s=17472.62cef850.k2207; bh=u5cxOAWrR1sXAaPt6nHilhDcaHLAoQKoMjdfZSkd9lo=; b=aSQWyfiDlEkK4OFL90Or4KHdL96UfggHtxuUeO6EYP3golSV01H+fMQ9Ia1GBBgQ3Uwl5+YvPYtbxo0V0qEKNZo+1wsRQWNz+3lIo1OqVgYEXgFQ8ffBwmzp2LRcG7vjm0wi1epVq2C09gmZPh/i/r10Uv6Nt1/wyAcEsYcIoCOmA2nUlOnTdT34RU4XIfS+h2YghMbpVgYLefX7EiJd8x39fkKhhdhvQceKwqqmPqjip4v+dfp2VCesXUkSmNfcECacFkGEB6uiDW+mVtj66uuO6gzZEjhrhFS1ut4mWg9E1Lb9ZMCvbk83GkoA/y830Mx7kqdmq5VX0Vw++OwFuQ==
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:cleverness; s=17472.62cef850.k2207; bh=u5cxOAWrR1sXAaPt6nHilhDcaHLAoQKoMjdfZSkd9lo=; b=dcffHThnjIqnEkeeaOI3ZAx/XqasA+n62hE0iuPFgEyF+hFrmlchJQmM7BuQs3mOYTxnJ8HnHPHAHAlWqJWJ2IaJhqUO8fjn0jFG2su6Tk60RjAvxv7HqTxRifUf12Ghsu8L/b/RoHCkPK1h/cLTku/6kAibkTG9Bu/+CjGuocQ+8NDNnSmepCQT2UaS2xAurL99orBCxER6samvrXir389JL5vUbTWWOtiuVC3iIcG18bXBFN+6dVmiiPFZcUMUDzu5ZApbXXN+Iheo3yZcHRMvGzP/eDPdVqKOgc92BJJUIZ2gFUKon5wQ01eTg/dY6bul6/tmjoYAaaZAJooAvw==
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 ESMTPS (TLS1.3 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 13 Jul 2022 16:52:32 -0000
Received: by ary.qy (Postfix, from userid 501) id D14484598A8A; Wed, 13 Jul 2022 12:52:30 -0400 (EDT)
Date: Wed, 13 Jul 2022 12:52:30 -0400
Message-Id: <20220713165231.D14484598A8A@ary.qy>
From: John Levine <johnl@taugh.com>
To: dmarc@ietf.org
Cc: superuser@gmail.com
In-Reply-To: <CAL0qLwZFO_KK3+RUdzMLyjW0uOnzi4mXcVww1Mqx8tmhe-x2hA@mail.gmail.com>
Organization: Taughannock Networks
X-Headerized: yes
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/t_47iZ3WGi_FCzWm_sXXZ6kF3VA>
Subject: Re: [dmarc-ietf] what to document about the tree walk
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: Wed, 13 Jul 2022 16:52:39 -0000

It appears that Murray S. Kucherawy  <superuser@gmail.com> said:
>There is indeed more of a burden on sending domains and registry operators
>to publish the needed markers in the DNS before this will all work the way
>we want it to. ...

Not really. If a mail sender has a DMARC record at its org domain, and
there are no DMARC records above the org domain, things will work
correctly, no psd tag needed. I expect that in practice this will
happen 100% of the time, rounding to the closest 0.01%.  That's why
it is not a problem that popular TLDs like .com, .org, and .net will
never publish a DMARC record, with or without psd=y.

There are at least 200 million registered domains but less than 10000
domains in the PSL. For PSDs, we are talking about one domain in
20,000, or about 0.005% of registered domains. 

Having surveyed all of the domains in the PSL to see which ones
publish DMARC records, I can report that the ones where the lack of a
psd tag might plausibly cause problems can be counted on your fingers.
Some of those already have np= tags which tells us they're aware of
what's going on. (See for example _dmarc.uk.com.)

The tree walk works fine. The psd tag is an arcane nit, mostly useful
to a handful of TLDs like .bank and .insurance that want to use the
aggregate reports to audit their registrants' mail configuration.

R's,
John