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

Douglas Foster <dougfoster.emailstandards@gmail.com> Thu, 14 July 2022 03:05 UTC

Return-Path: <dougfoster.emailstandards@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 7234AC157901 for <dmarc@ietfa.amsl.com>; Wed, 13 Jul 2022 20:05:16 -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 PlU8tJoSgnLH for <dmarc@ietfa.amsl.com>; Wed, 13 Jul 2022 20:05:16 -0700 (PDT)
Received: from mail-oa1-x32.google.com (mail-oa1-x32.google.com [IPv6:2001:4860:4864:20::32]) (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 09AE5C14CF0D for <dmarc@ietf.org>; Wed, 13 Jul 2022 20:05:16 -0700 (PDT)
Received: by mail-oa1-x32.google.com with SMTP id 586e51a60fabf-fe023ab520so934047fac.10 for <dmarc@ietf.org>; Wed, 13 Jul 2022 20:05:15 -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; bh=yC6BBU3IW2dur0BTuKn1TGaU2G+X2fxoK/w+m3XJ4c4=; b=ZOqBZBj9STEOWU5wo+Bokp+7xTD0eJwPDg2MpxS5O+F5fjHx/5YSnYi2ce1s2XJjX0 b9Z6hzgLZZIAM2SZbDmDEMRx3SKJxDzeJvqQGgpDVZ0ejjU6nmnmQOnRid7hH7culiqx LbhiE2kQUO7hV+eVfgetSjLSqI3eLVXoMUBa3Ro/Lu0tpuKi/owibn0nu0nQCjmgbUuL Ii7nFNsRvCjR5MkyshO4AXJFUd7+JrLoh+UkpFc/twzhwJJFOgz0Ukqy69viaiaP+si0 zmz2wogXenKIfUyaFQ4d9Rr2i9Lxg9EYvwccyqXsq5H7eyw4qSziq2grHJ9xduZlul6P 7f2Q==
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; bh=yC6BBU3IW2dur0BTuKn1TGaU2G+X2fxoK/w+m3XJ4c4=; b=c+lzZhhUicM3dLqUisd6Dbzs2qnRrzwCr4AKOLLl7sg+wfc9/9M02J4AU5SFOZq1r8 X5yWdtUek+mrErG87g6sVKjmgdzturI5c1OoCC697urBArvJamCGfBSGu3qqOw/Mn6pk 9LK1g9SyFBmjWPrfXRJNifAGo2AL7SXZM+i3t836j4NqYWuY3hDDgaQVig1hK/3Ohb40 o0eJbr/4ZRDBP8IEywj9Rd0Cmhe/lSHPHb8gzYrf3BKDsB+UbY4sC5VdjyGWU8FTuKb5 XnOTwEYeJxt7yp5/VhapE1AhQyQaaqZhzelvIYfYsjgiowWaSI+7JMXaSm0nvtfyw2z7 fGsg==
X-Gm-Message-State: AJIora+Ti/joxQjlxgn2bCzX10E19dl2t+cfWoRowF4NJl/Dh/JryLAv jZkbMYG6UaLQv7HMOd9d5v3TdijwTjJVGlqf3+aDjx0x
X-Google-Smtp-Source: AGRyM1swk0JV7e9diOddfdK1kp8vhhAsyWEGMmhULsVlN939j0QEOMmoQtgZO3C6ULnqh0yzL2eaZF1u8jn7jABLtV8=
X-Received: by 2002:a05:6870:ac14:b0:10c:1d60:d4d2 with SMTP id kw20-20020a056870ac1400b0010c1d60d4d2mr6344489oab.58.1657767915060; Wed, 13 Jul 2022 20:05:15 -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> <CAL0qLwbxoijfdfxpS5-LRPifxg+4e_ndBGQhne5s5of0zxBbMQ@mail.gmail.com>
In-Reply-To: <CAL0qLwbxoijfdfxpS5-LRPifxg+4e_ndBGQhne5s5of0zxBbMQ@mail.gmail.com>
From: Douglas Foster <dougfoster.emailstandards@gmail.com>
Date: Wed, 13 Jul 2022 23:05:02 -0400
Message-ID: <CAH48Zfzvox5xOXbdR2oGL4ixZE8xEWf0997CdzZ29R=vokJi_Q@mail.gmail.com>
To: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000b2846105e3bb2b69"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/O2K4cwoo7-2gFrxSmHCWrCgI5t0>
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: Thu, 14 Jul 2022 03:05:16 -0000

We can limit the transition period by specifying a date, after which any
untagged record is interpreted with strict alignment.



On Wed, Jul 13, 2022, 11:10 AM Murray S. Kucherawy <superuser@gmail.com>
wrote:

> 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
>