Re: [dmarc-ietf] Signaling MLMs

Neil Anuskiewicz <neil@marmot-tech.com> Mon, 17 April 2023 01:12 UTC

Return-Path: <neil@marmot-tech.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 8DA85C14CE47 for <dmarc@ietfa.amsl.com>; Sun, 16 Apr 2023 18:12:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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=pass (2048-bit key) header.d=marmot-tech.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 KzpC3ORtfyBw for <dmarc@ietfa.amsl.com>; Sun, 16 Apr 2023 18:12:11 -0700 (PDT)
Received: from mail-pl1-x635.google.com (mail-pl1-x635.google.com [IPv6:2607:f8b0:4864:20::635]) (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 0B57BC14CE42 for <dmarc@ietf.org>; Sun, 16 Apr 2023 18:12:11 -0700 (PDT)
Received: by mail-pl1-x635.google.com with SMTP id p17so12826687pla.3 for <dmarc@ietf.org>; Sun, 16 Apr 2023 18:12:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=marmot-tech.com; s=google1; t=1681693930; x=1684285930; h=to:cc:date:message-id:subject:mime-version:from :content-transfer-encoding:from:to:cc:subject:date:message-id :reply-to; bh=/F5Dt1RQ7IXrWRioeY5ZJxKAkc3OVYagGYFNSZA54B4=; b=QTkvZrXtDDydCaZs4BGgSf9XoX5ph3+7cOHH/Q3MiwBDzTLhk/Bc8sSFZ0S+DHbzBy oFW8cAT4TMOzWog8lhoQ7HucITn9JJT1es221gTuBuCmvrgH1ym1gOIPQ3kRE3cPCYyG e5xRw8eadbPGbchDeAefBhnk7jLwNOQ64PqXJe+0eD7hJ3WvunBlYaSYcKhNynx9hIkQ S2kDeGXC8RLn7/vacCAJ7c2+htlNKLSkdqW5lh5FxTlU2j9U98c6qld57pZRS4Rhjj/y yGG8ADiwSr6Q7FnT2mNwVdezzkhjcLeXSi0/YpPQtbB82ZgA9r9vfTS5sODeqhKPMhU6 Eubw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1681693930; x=1684285930; h=to:cc:date:message-id:subject:mime-version:from :content-transfer-encoding:x-gm-message-state:from:to:cc:subject :date:message-id:reply-to; bh=/F5Dt1RQ7IXrWRioeY5ZJxKAkc3OVYagGYFNSZA54B4=; b=mCCqC+d3cp+TG/k9vkgm1v7FmkegyT35a3pazFTdpdza0I4LmCjevBC3wAxA+GWfqP FU0Oy9w03rTmEDqKlMXp0bSeYIfHZAA9V79iieI5WrvlSAu5TpwVtJqiBTzQItzw+1aJ p0atPWYVNQCrAJKbByfWTOK9Zc0h4u0MXnlIxSCTTy3ZGOJR7IfnclaHvXoXHf0NNjIe E+TYhplIzlu9PuvVHUKWA3XOfPnXpQIJGyzHv9JI7Bp2TTE6xCTsdrgjpVG3XUE2oZfW N97PcBn1OVO0MuwwbR7MNgkA5ss9qV+prl6hki1VsXlpfQq4SAkAONkEY6Q6wRp3h/08 NavQ==
X-Gm-Message-State: AAQBX9exBgpTQVk23/Q5Fd4XcVNSg+bLbd1K8ff3HzZGoB0iXclpwT2n kTRaBip4gTsZmnA6EANscAdAAfUUzwQ8LOmX/KGilQ==
X-Google-Smtp-Source: AKy350Z+o2Ig7q7Px8zul+CoVGNC5Klvq2m3AHIJrxQjGJKNX8dzWUb71iNL3Auphwx+40xQPgxj+g==
X-Received: by 2002:a17:90a:ab14:b0:237:62f7:3106 with SMTP id m20-20020a17090aab1400b0023762f73106mr13000620pjq.17.1681693930189; Sun, 16 Apr 2023 18:12:10 -0700 (PDT)
Received: from smtpclient.apple ([2601:1c0:cb02:fad0:7c16:68af:d685:6313]) by smtp.gmail.com with ESMTPSA id b16-20020a17090a101000b00246ba2b48f3sm3589137pja.3.2023.04.16.18.12.09 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 16 Apr 2023 18:12:09 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: Neil Anuskiewicz <neil@marmot-tech.com>
Mime-Version: 1.0 (1.0)
Message-Id: <2DF45F0D-1CA3-4A2C-991B-83504382838D@marmot-tech.com>
Date: Sun, 16 Apr 2023 18:11:59 -0700
Cc: dmarc@ietf.org
To: Scott Kitterman <sklist@kitterman.com>
X-Mailer: iPad Mail (20D67)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/h5vR1txwYu_XeiufYbkdKfO0zlQ>
Subject: Re: [dmarc-ietf] Signaling MLMs
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, 17 Apr 2023 01:12:15 -0000




> On Apr 15, 2023, at 7:29 AM, Scott Kitterman <sklist@kitterman.com> wrote:
> 
> 
>> On April 15, 2023 12:26:16 PM UTC, Laura Atkins <laura@wordtothewise.com> wrote:
>> On Apr 15, 2023, at 4:25 AM, Scott Kitterman <sklist@kitterman.com> wrote:
> ...
>>> Or [person] gets a Gmail account for his IETF work and doesn't bother tilting at
>>> windmills.
>> 
>> That solution only works until gmail publishes p=reject. At one point they said they were going to do that. 
>> 
>> It seems to me that there is zero harm in actively documenting the problems with DMARC and making interoperability recommendations about who should and should not be publishing restrictive policies.
> 
> I agree on documenting the issues with DMARC and making recommendations to improve interoperability.  There are issues and they're significant, but we shouldn't catastrophize them either.
> 
> To your other point, if that happens then people will move to another provider if it affects them negatively.  If free email providers that don't have p=reject get hard to find, then that probably creates a demand signal and some entrepreneur will fill the void.

Does anyone know if there are promising paths that these market signals could impel?

I don’t like dealing with mailing list issues either and I have to do so regularly. If there were some avenues of r&d that looked promising then that would mean the market signals would likely make it worth the hassle of implementing a solution. 

I agree there’s a problem. There was that one that gave me headaches and stress as recently as a couple weeks ago. It’s not that I don’t think there’s a problem but I do think there’s some catastrophising. I think this is a solvable problem.

If we write a solid appendix that explains the problems and the options for addressing it as I think was proposed, that would provide the information needed, while making it clear the IETF isn’t the internet regulatory agency. 

I think if someone came up with a viable solution their ML software would do well. Problems are the markets way of facilitating the solving of difficult problems. I’m not a market purist but the market is very good at certain things. Market signals are the bat signal for entrepreneurs to leverage gaps in the market. It could be one of the established players that gets there first or it could be an upstart. I think the odds favor one of the better established players.

Neil