Re: [dmarc-ietf] "psd=" tag early assignment

Scott Kitterman <sklist@kitterman.com> Mon, 27 June 2022 13:46 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 7B45DC15AACA for <dmarc@ietfa.amsl.com>; Mon, 27 Jun 2022 06:46:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Level:
X-Spam-Status: No, score=-2.106 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_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, 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=neutral reason="invalid (unsupported algorithm ed25519-sha256)" header.d=kitterman.com header.b=ZCSZRXsu; dkim=pass (2048-bit key) header.d=kitterman.com header.b=O8wX5C+T
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 QRFYuD6jpOPk for <dmarc@ietfa.amsl.com>; Mon, 27 Jun 2022 06:46:20 -0700 (PDT)
Received: from interserver.kitterman.com (interserver.kitterman.com [IPv6:2604:a00:6:1039:225:90ff:feaa:b169]) (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 A5436C157B36 for <dmarc@ietf.org>; Mon, 27 Jun 2022 06:46:20 -0700 (PDT)
Received: from interserver.kitterman.com (interserver.kitterman.com [64.20.48.66]) by interserver.kitterman.com (Postfix) with ESMTPS id 8A917F80263; Mon, 27 Jun 2022 09:46:16 -0400 (EDT)
DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201903e; t=1656337576; h=date : from : to : subject : in-reply-to : references : message-id : mime-version : content-type : content-transfer-encoding : from; bh=JVOJLH6XLieBftsZqS7mcCGXiCkAc8b1SQEqGy5GDaI=; b=ZCSZRXsuy3iD49WPMH3Ow3H4xVY+B2zjME0JVGpzwl9IusbLk4A8hFISMa4jsyukVlJbk sphZvVz8LhmjcLNBA==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201903r; t=1656337576; h=date : from : to : subject : in-reply-to : references : message-id : mime-version : content-type : content-transfer-encoding : from; bh=JVOJLH6XLieBftsZqS7mcCGXiCkAc8b1SQEqGy5GDaI=; b=O8wX5C+TKMSyMiw+7HMhovbJNXJ+KFP+oTiV4xfTS4OWTugxYTFs+4ITzRT6ihESYLz/o O8OBoqqgkuc6skwmCtYXL6vxjzj3rNqu8w9E1B1Tng7FJgPr2IzB2QsFakMo+sfcl4UNZX2 Ym6BDaPfXq0Qu/H8SWIBlkjLg5B/YpPDqjaLU0mkoG5YmkOZPNmEj6f2oK8ZQGvo/QZwD6r Ol6Yy6IhHGAE/ulELuqzBxVwMks3VQAL+aGgz/vbc3tTUZu5KOQzy9YRhqhnD7E7E+xf2Px N0kB8Amh7NxTdS6u/jvqfgexwdrCcssXOBs8C7bsvDuLrsA5C3Y5kgArXr/Q==
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 463D2F801E4; Mon, 27 Jun 2022 09:46:16 -0400 (EDT)
Date: Mon, 27 Jun 2022 13:46:19 +0000
From: Scott Kitterman <sklist@kitterman.com>
To: dmarc@ietf.org
In-Reply-To: <CALaySJJcd1e+iT0CwbQ738fMaX2-UQ+q7NvduK4a7J+H5Q0dVg@mail.gmail.com>
References: <2106279.dWI8RDzgUi@zini-1880> <CALaySJLFY6s6+4xFs9iu-YSbrihnThgDEkb1+g2NUAt-QS_mTw@mail.gmail.com> <95b1d241-0e3c-edf3-4768-cf08b7d73283@tana.it> <CALaySJJcd1e+iT0CwbQ738fMaX2-UQ+q7NvduK4a7J+H5Q0dVg@mail.gmail.com>
Message-ID: <05AB0F55-F8EF-40F7-97BE-23C9B96747D2@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/XWevVNP9D5CVxsv_zmB5PG5bA3o>
Subject: Re: [dmarc-ietf] "psd=" tag early assignment
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, 27 Jun 2022 13:46:24 -0000

If we use a different term, we'll need to define it.  Fundamentally, I think changing the name only adds a level of indirection (and thus complexity).

Current:

PSD (which is defined in the document) yes or no or use tree walk.

Proposed:

Role (needs a definition) PSD (defined), Org (defined as not a PSD), and Subdomain (which isn't defined and is technically wrong - all three might be subdomains).

Whether you directly use psd as the tag or not, the question is still is it a PSD or not.  The suggested change doesn't do anything towards getting away from PSD as a concept or a defined term.

I think that by hiding it in the definitions, it will be more confusing, not less.

Scott K

On June 27, 2022 1:27:37 PM UTC, Barry Leiba <barryleiba@computer.org> wrote:
>I have to say, as a participant, that I have more than a little
>sympathy for this suggestion or some derivative of it.  Using "psd" as
>the tag name is rooted in history that will be lost as we move away
>from using a public suffix list.
>
>Barry
>
>On Mon, Jun 27, 2022 at 6:20 AM Alessandro Vesely <vesely@tana.it> wrote:
>>
>> On Sun 26/Jun/2022 18:05:44 +0200 Barry Leiba wrote:
>> >
>> > Please comment in this thread about whether you agree with making the
>> > registration now, or whether you do not agree and why.
>>
>>
>> I'd like to make a last appeal to use more intuitive symbols to be used instead
>> of the current ones:
>>
>> instead of | use      | to mean
>> -----------+----------+-----------------------------------------------------
>> psd=u      | role=sub | the default subdomain role (never needed)
>> psd=n      | role=org | the org domain (only needed with non compliant PSDs)
>> psd=y      | role=psd | a PSD (needed if PSD published DMARC record.)
>>
>>
>> The reason to use cryptic symbols seems to be to discourage their usage, which
>> I can hardly understand.  I'd be OK with the current symbols if the WG can
>> explain somewhat better, possibly as part of the spec itself, the rationale of
>> using counter-intuitive yes/ no/ undefined to express that three-valued value.
>>
>>
>> Best
>> Ale
>> --
>>
>>
>>
>>
>>
>> _______________________________________________
>> dmarc mailing list
>> dmarc@ietf.org
>> https://www.ietf.org/mailman/listinfo/dmarc
>
>_______________________________________________
>dmarc mailing list
>dmarc@ietf.org
>https://www.ietf.org/mailman/listinfo/dmarc