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

Barry Leiba <barryleiba@computer.org> Sat, 09 July 2022 13:17 UTC

Return-Path: <barryleiba@gmail.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 343DBC15790C for <dmarc@ietfa.amsl.com>; Sat, 9 Jul 2022 06:17:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.428
X-Spam-Level:
X-Spam-Status: No, score=-1.428 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=no autolearn_force=no
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 JttK4yPqQIRF for <dmarc@ietfa.amsl.com>; Sat, 9 Jul 2022 06:17:49 -0700 (PDT)
Received: from mail-ej1-f54.google.com (mail-ej1-f54.google.com [209.85.218.54]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 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 3BA3FC14F738 for <dmarc@ietf.org>; Sat, 9 Jul 2022 06:17:49 -0700 (PDT)
Received: by mail-ej1-f54.google.com with SMTP id j22so1902538ejs.2 for <dmarc@ietf.org>; Sat, 09 Jul 2022 06:17:49 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=IGJUB7qH0OCZyTEbLlxdoLuM0HwWjhJbk361tgMnwy4=; b=aPr+os4bJY6Xt2H00APWHvScb5JLqH0nm3+9hb8zVWlo/0XpatgzIULLWn14Ogc7zq g1H3N5896XlJv5QRlbkKrDk4+Agxq8P0OSs5s55wT+Ewn5Y9PQgpGtuRkM+Zqazwp8in k+zy7d7g3WK+fddnzEfKg8wborsRcl0jCxXMKm6wXfjfukzigDGJzVO3yjx5TZ/f+uoJ GY8LOKtDAqcelcUC9HeeCo5IwHaKRBJNfEkSVlEDLjDvjIMU0C0e4FLMtXVQnes8KybM X+ljttI/kI+6AnwaJBa5URzboVWFjnaYq3qxCDcScIw3CVfTbHMvlNe1pOsNdOt2BTkR T9/w==
X-Gm-Message-State: AJIora9RCiB/kD3uroUAAgT8j4P5/dHa6FrN18MznHZjrS5LS2oJtwop nTz4QzjlYJ9ooMfryLGKVFQpJ2c6ujoyImY1HO6WshQhL508FQ==
X-Google-Smtp-Source: AGRyM1sd6DibdG/C2U27kW+5xy6OJWnT4bJRuaocd9wy7vFTZZYNSdrz04PwCThsEISuYZXQ5dRvekJYEsXNc2z0f8g=
X-Received: by 2002:a17:906:7309:b0:722:f9e9:3904 with SMTP id di9-20020a170906730900b00722f9e93904mr8846514ejc.198.1657372667535; Sat, 09 Jul 2022 06:17:47 -0700 (PDT)
MIME-Version: 1.0
References: <b87b71c5-c4bc-b963-06eb-dd94cca1340d@tana.it> <20220707203257.0602A45178AF@ary.qy> <CAH48Zfwvbkeq8CzXeb959Ehv-Gc9KxBc-Q5Op25oU1GGNF=NQg@mail.gmail.com> <CAL0qLwYNVZSBYnBWx7ASHGO00_FrUB1NW=vrNHji+K3F0NrOPw@mail.gmail.com> <CALaySJKNvatCE25T0ZAJ8eZqxNHxgW2q1N9qDoWfZqmaC+rjcg@mail.gmail.com> <CAH48ZfzGjKgocq15gUa-wR=rwSBCTKAA33t1oNAYjts5i6i9DQ@mail.gmail.com>
In-Reply-To: <CAH48ZfzGjKgocq15gUa-wR=rwSBCTKAA33t1oNAYjts5i6i9DQ@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
Date: Sat, 09 Jul 2022 09:17:35 -0400
Message-ID: <CALaySJKTPo6_GzCu76_tX1ntGaZ_f=tFYrbn2U+y+kLQPEH0nA@mail.gmail.com>
To: Douglas Foster <dougfoster.emailstandards@gmail.com>
Cc: "Murray S. Kucherawy" <superuser@gmail.com>, IETF DMARC WG <dmarc@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/QNULDrCZYCw6HqfYzHImdvN2Qqc>
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: Sat, 09 Jul 2022 13:17:50 -0000

First, let me be clear here: There will be no further discussion of
this "don't be nasty" issue on the list; if you have more to say to me
about it, please do it off list.

Nothing that Murray or I said is "endorsing the current document" (nor
is it not).  It's addressing your behaviour, your way of interaction.

"it is his intent to hide any information about private registries"
and "which he does not wish exposed" are both out of line, and we'll
not have any more of that.  Do you not see the difference between what
you said, which is attacking John, and what I suggested as a possible
alternative, which is making the same point without the attack?
(That's a rhetorical question.  Please just think about it; don't
answer it on list.)

Let's move back to the substantive discussion.
As a constructive suggestion in that regard: If you want something
specific in the document, why don't you post specific text for the
working group to consider, and say where in the document you'd like to
see it put?

Barry, as chair

On Sat, Jul 9, 2022 at 8:31 AM Douglas Foster
<dougfoster.emailstandards@gmail.com> wrote:
>
> I see no personal attack.   John was clear, and has been clear, that he has no intention of documenting any limitations or risks associated with the tree walk, because in his judgement, they are not important.   My concern is about a document that creates a new vulnerability, then fails to document it.  The private registries DO create complexities for the tree walk, complexities that have been trivialized instead of being mitigated.
>
> But if you wish to endorse the current document.  Let's do so honestly:
>
> "The tree walk is vulnerable to false PASS if certain combinations of present and missing data occur.   Even though this has happened in the past, it is the firm opinion of some work group members that this will not ever occur in the future.   Therefore the details of a non-problem are of no interest to DMARC participants."
>
> My issue is with the document.
>
> Doug
>
>
> On Fri, Jul 8, 2022 at 2:50 PM Barry Leiba <barryleiba@computer.org> wrote:
>>
>> >> So John has confirmed that it is his intent to hide any information about private registries, because the
>> >> private registries create complexity for his algorithm which he does not wish exposed.
>> >
>> > I submit that equating "this is not worth explaining as it's a corner case" to "we should hide this detail
>> > because I don't want anyone to know about it" is logically absurd as well as baldly antagonistic.
>>
>> Agreed, and thanks, Murray.
>>
>> Doug, I've called out others for similar things, and you get it here:
>> Please do not attribute bad intent to other participants, and please
>> do not put things in terms of accusations or in ways that seem only to
>> pour tar.
>>
>> A response such as, "John, I strongly disagree: I think it's really
>> important to talk about at least some uncommon cases in order to make
>> the situation clear.  Discussing private registries in one of those
>> important cases, as they create complexities for the algorithm that
>> need to be shown," gives your technical opinion without being
>> insulting or inflammatory.
>>
>> Barry