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

"Murray S. Kucherawy" <superuser@gmail.com> Wed, 13 July 2022 15:10 UTC

Return-Path: <superuser@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 0742EC16ECCC for <dmarc@ietfa.amsl.com>; Wed, 13 Jul 2022 08:10:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.107
X-Spam-Level:
X-Spam-Status: No, score=-2.107 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 uDCORL0MxPD1 for <dmarc@ietfa.amsl.com>; Wed, 13 Jul 2022 08:10:51 -0700 (PDT)
Received: from mail-lj1-x235.google.com (mail-lj1-x235.google.com [IPv6:2a00:1450:4864:20::235]) (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 97675C15A73A for <dmarc@ietf.org>; Wed, 13 Jul 2022 08:10:51 -0700 (PDT)
Received: by mail-lj1-x235.google.com with SMTP id a10so11996203ljj.5 for <dmarc@ietf.org>; Wed, 13 Jul 2022 08:10:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=pP8MlM53GdG+u09TrmubTFBoyaB0cyTe3xnkdPCMBtA=; b=di/fN9AaJMZLqcJQ0VpRRzXxh7SeROPIaLbpA5VY2zXK493AwWfuz8/ctU4R2mbzrx UPqeufyMtT60U7GQlABbr9OiQETJOCihhNSXReR1n1dMkRq92n8bmwgbv497awEXD8QV fiNiIAifDMxcVFpUnWxoDW7dRm/gEBdiXeHxGKuJ6mkKx4eH5Upk4PDnbIwkfBrFnyxm ZS+BzeotLmuvYg1oKNKzNZQv83Zo7+mlLjatRwnd4+CyEc9TnQmybim50Rz6wdOelvjY Y07LqKIDXDEHa3byIkoc5jw3LLM3Z+uXovMA3WsJMt+E0naaLsmqsjt2vGiUT+ur7U2s N/QQ==
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; bh=pP8MlM53GdG+u09TrmubTFBoyaB0cyTe3xnkdPCMBtA=; b=n8Qqprv72x8cu/Nf/fopNuMGsQbZEfenVi9gv0iTu49OOKRn0bDi1gdKzQLk9yrmpT vbO26Uk8fkY4yy+jsiMUmULF1BwqwCPxLN3BcVK3g8A0Ud6ghikayNmVIOeQs3/rlgK3 YYZrHol4UwtcW3hJXhoIeUT/Qn1xMZX0PdYaQlSeH4+PFBnCNnZwU0xJQiy25O/qsorG f5VZeSOKsKCsbJlRZhZvgjWYNa09JVWypE+bK77qrox4MYn/peyrS6LIcJN+VFKCbxcF mW2nDlT2VRU9SBqyyVQKu0iA+NbzFUtX7AHYMc50136Bar6bmWuw3gZFdGy+qvyO7xkI 7WGg==
X-Gm-Message-State: AJIora9ALmNkUWNAhqisEcHqzyto6qr5KdbTjjH5bJySA8KydD5qJnSg bKRLaTHuzmXlXLmjo/toeU4EnrM8GNtLahBcrDRDrs7RbAM=
X-Google-Smtp-Source: AGRyM1uTD1Pey2mgwiBlbrfWArXMpDYGu1mSviMQ8jNlMRtfr+MLhHgMlAmxx7uJGvojzVzVHEBCHLlxg7X+tdFDgCE=
X-Received: by 2002:a05:651c:a04:b0:25d:6c36:15b0 with SMTP id k4-20020a05651c0a0400b0025d6c3615b0mr1992128ljq.518.1657725049662; Wed, 13 Jul 2022 08:10:49 -0700 (PDT)
MIME-Version: 1.0
References: <20220710010547.DB3B04532F40@ary.qy> <d8716435-8a52-dac4-ede2-6c27fced7f0f@tana.it> <84DDA91C-26E2-4803-8C6C-0369ED67298F@kitterman.com> <c4a7fd03-eae8-497f-3133-73523a9c1ca2@tana.it> <5197ba5f-9de4-d838-1579-eae67683e2d4@taugh.com> <650cadee-db8f-a54a-4d14-082c2d0bed02@tana.it> <0f3a343b-e7ea-7509-ceab-e5670aac8616@taugh.com> <CAH48ZfxHgxZwu3zLh99pc1JS4s==9bxU-0nS78O=7UAnZ=DtUQ@mail.gmail.com> <CAHej_8nkpGo30b9-ZkRc_wokymJ2ry_hsMgzaB2m4EH-WWG_zw@mail.gmail.com> <CAH48ZfzoVocPRKeVTqf6AE6Z48AWKFObm7X5oDa1ic1sQ5V1zg@mail.gmail.com> <CAL0qLwZFO_KK3+RUdzMLyjW0uOnzi4mXcVww1Mqx8tmhe-x2hA@mail.gmail.com> <CAH48ZfwTaf75HiJS2_VJKez8s3FqMh-K_6eD2eqaJatXWwcKww@mail.gmail.com>
In-Reply-To: <CAH48ZfwTaf75HiJS2_VJKez8s3FqMh-K_6eD2eqaJatXWwcKww@mail.gmail.com>
From: "Murray S. Kucherawy" <superuser@gmail.com>
Date: Wed, 13 Jul 2022 08:10:38 -0700
Message-ID: <CAL0qLwbxoijfdfxpS5-LRPifxg+4e_ndBGQhne5s5of0zxBbMQ@mail.gmail.com>
To: Douglas Foster <dougfoster.emailstandards@gmail.com>
Cc: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000b872e205e3b1307e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/w2gcSGSrHvCFAQmcCf-nGMXKvho>
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 15:10:52 -0000

Once again, participating only:

On Wed, Jul 13, 2022 at 3:43 AM Douglas Foster <
dougfoster.emailstandards@gmail.com> wrote:

> [...]
>

> 2) I believe that the document needs a vigorous explanation of why the PSL
> needs to be replaced.   I made a stab at the effort in the text that I sent
> Sunday night.   Murray's text here is more comprehensive.   But we need
> something.  We are asking evaluators to undertake a change which requires
> effort and any change creates multiple risks.
>

I don't know about "vigorous", but I think some tutorial would be useful
given the wide variability of experience in the ultimate audience.  An
appendix would suffice.


> 3) The critical question is whether we can treat the PSL as replaced
> without obtaining the markers first.   On this issue, John and I have a
> different assessment of the risk.   I can accept a solution which lays out
> the assumptions and risks to the evaluator, and lets them decide what to
> do.  This is what sections 4.7. and 4.8 in my text from Sunday night
> attempted to do.
>

My suggestion would be that if we are going to offer a choice, there should
be some eventual path toward convergence rather than an open-ended period
of people doing either.  Otherwise, the PSL will be a part of DMARC for far
longer than we'd like.

-MSK