Re: [dmarc-ietf] Are Evaluators motivated to switch to Tree Walk?

Scott Kitterman <sklist@kitterman.com> Sat, 18 June 2022 15:16 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 7BF64C14CF06 for <dmarc@ietfa.amsl.com>; Sat, 18 Jun 2022 08:16:51 -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, 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=4qBcHGFn; dkim=pass (2048-bit key) header.d=kitterman.com header.b=OiHAMBkt
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 aiHadkxxx_HY for <dmarc@ietfa.amsl.com>; Sat, 18 Jun 2022 08:16:47 -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)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 58C29C14CF01 for <dmarc@ietf.org>; Sat, 18 Jun 2022 08:16:47 -0700 (PDT)
Received: from interserver.kitterman.com (interserver.kitterman.com [IPv6:2604:a00:6:1039:225:90ff:feaa:b169]) by interserver.kitterman.com (Postfix) with ESMTPS id CEE82F802DB; Sat, 18 Jun 2022 11:16:43 -0400 (EDT)
DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201903e; t=1655565403; h=date : from : to : subject : in-reply-to : references : message-id : mime-version : content-type : content-transfer-encoding : from; bh=5rBewzes2oMwrSebLXHA2OtCfVT/HPuutUTR4LBwglk=; b=4qBcHGFnuYq4KgTEcOvtn4hfQoGI4b/nae8aOdhR4Yh+Y/AF9Q1nu4mxN1jKfQTpYfmyX c5aq4RDdBr4D3GkDg==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201903r; t=1655565403; h=date : from : to : subject : in-reply-to : references : message-id : mime-version : content-type : content-transfer-encoding : from; bh=5rBewzes2oMwrSebLXHA2OtCfVT/HPuutUTR4LBwglk=; b=OiHAMBktGed3tugM8Nky2e6/tw5XcvNEYYr3SxtSrRXiIoIhtcydEWQykvep6XW8jrCLz v4UysWd4/YIkeToKekMVkrzpm76BCI/SeUiUzSE65tsdD5xQUQpp1txW1jDbgeK+vOyJFX7 4L+O7Q7+K/780J/j8C2lvVfGDMjegCI+YLaVriHAVARCxTs40q7pbUGv3j7mSaDfbvySzb9 62lrndQ4ZVNl5jt/zBk1pBgVfCC6gSpgEY0HlHT4bmB5R671sM7Qw9NFGkQZ1nX2Gfg2K/I JwU4WA5K3rJ8KbUPKls8S+NWYqvPo0qa4hemzyCZqEMPlP44HdkEaGeTLVVQ==
Received: from [127.0.0.1] (mobile-166-170-35-176.mycingular.net [166.170.35.176]) by interserver.kitterman.com (Postfix) with ESMTPSA id 8B155F8020E; Sat, 18 Jun 2022 11:16:43 -0400 (EDT)
Date: Sat, 18 Jun 2022 15:16:43 +0000
From: Scott Kitterman <sklist@kitterman.com>
To: dmarc@ietf.org
In-Reply-To: <CAL0qLwa0fGJRGXaueKERwM_bfSBjwB4dG8=-iTTWQ6trPohuxQ@mail.gmail.com>
References: <CAH48ZfzxqiPQMdRA5SNZOJA2Sd9GsL5dsGdK4aYCHBY4sNmL_Q@mail.gmail.com> <6179411.nDTXd1jgoo@zini-1880> <CAL0qLwYLWdmK4n94O=ofk3Xa4pDVYRvLuG0HwEdo1SFFNZ=5Vw@mail.gmail.com> <A8F0CF1E-1EC1-40CE-A0DB-028164B75B43@kitterman.com> <CAL0qLwa0fGJRGXaueKERwM_bfSBjwB4dG8=-iTTWQ6trPohuxQ@mail.gmail.com>
Message-ID: <2C61746A-D171-4D32-8FC6-92188417DE1C@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/JdE3UAkqxgtFmMj6iOOrBMbmSnw>
Subject: Re: [dmarc-ietf] Are Evaluators motivated to switch to 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: Sat, 18 Jun 2022 15:16:51 -0000


On June 18, 2022 3:09:19 PM UTC, "Murray S. Kucherawy" <superuser@gmail.com> wrote:
>On Sat, Jun 18, 2022 at 7:49 AM Scott Kitterman <sklist@kitterman.com>
>wrote:
>
>> Given that the mechanism we've defined uses DMARC records to make the
>> determination, I don't think it would be useful to separate it into a
>> different document.  If we ever get an approach that's not DMARC specific,
>> then I think it would make sense to document it independently.
>>
>
>The tree walk might be the DBOUND solution, for all we know.  Having it in
>a separate, generic-as-possible, document might make the technique usable
>by other applications as well.
>
>I rather liked the idea of DMARCbis saying "You need some way to determine
>the Organizational Domain.  One way is with the PSL as described in X, or
>you could do a tree walk as described in Y."  It also means if we ever want
>to introduce some third mechanism, we don't need to do a DMARCbisbis (which
>I think is DMARCter).

I did too, but I think what we have now is too DMARC specific to potentially be a DBOUND solution.  

If something else does appear that turns out to be suitable for DMARC, I don't think we will need to re-roll the whole document.  It would be simple enough to have a short draft that updates DMARCbis which days that in addition to what's in DMARCbis, the organizational domain discovery mechanism identified in X can also be used.

That's part of why I think we needn't worry about it now.

Scott K