Re: [dmarc-ietf] Signaling MLMs

Neil Anuskiewicz <neil@marmot-tech.com> Mon, 17 April 2023 01:11 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 0869EC14CE47 for <dmarc@ietfa.amsl.com>; Sun, 16 Apr 2023 18:11:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.096
X-Spam-Level:
X-Spam-Status: No, score=-7.096 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_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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=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 PoZec8ObDKa1 for <dmarc@ietfa.amsl.com>; Sun, 16 Apr 2023 18:11:08 -0700 (PDT)
Received: from mail-pf1-x433.google.com (mail-pf1-x433.google.com [IPv6:2607:f8b0:4864:20::433]) (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 2829AC14CE42 for <dmarc@ietf.org>; Sun, 16 Apr 2023 18:11:08 -0700 (PDT)
Received: by mail-pf1-x433.google.com with SMTP id d2e1a72fcca58-63b5fca48bcso938072b3a.0 for <dmarc@ietf.org>; Sun, 16 Apr 2023 18:11:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=marmot-tech.com; s=google1; t=1681693867; x=1684285867; h=to:in-reply-to:cc:references:message-id:date:subject:mime-version :from:content-transfer-encoding:from:to:cc:subject:date:message-id :reply-to; bh=mgKSK5Xt9qmaARYfk3ovGl9HDjlMbzGFsWwwPXOq9uw=; b=Ts9iGuArZtfeskJAgb4YM8QQydHZyGLCdCQt3VzveHMlKuwwYHPYkOzPhbfkDFwWK6 xiL3ZJgTHESrsceaRgwhyX2c7UK7OxVabIY08e25lXg6PTkTkFtJxR2wDGLSPkuUMQFJ x+F/TGjPBMUhbyn9h6ZaWTFKgLXb2RhTKmD0LwxET4knuRAxbjg4aWCp2i+D33kWGJQN eyYwS22Wm6L9K0qD7II0JWUJNkZNW9SFEWOgk2M9crziWTqk0TJSWyZiCoo5pFI1FseJ T7jCygw2aEpYBdaXijwqC7FG432Cu5Tu1/e2jzqGbEWp73sCfmdwdp1JvgGsdR5z3vaZ 66Vw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1681693867; x=1684285867; h=to:in-reply-to:cc:references:message-id:date:subject:mime-version :from:content-transfer-encoding:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=mgKSK5Xt9qmaARYfk3ovGl9HDjlMbzGFsWwwPXOq9uw=; b=MJ7aMa9mgzituunSyGg4cNw0vXKJLW9qKvFlP9fxSLtzSETRfs1cDNc154W8gi0zMa tDE0e6HlqoOm0Rp3/qQVzMkXeAfnld410Z8ZQ9kCl2CwTDSNLr3TKLQ5zKQxn/kb6Iv/ TxIPFkC2FhJ92MOwmWpDLwxBlthii0gvwCNBSE+z3qwF4hqs6o/ISBOjfpUANjf7jzc/ MFSfw+hrAoP3W0Lyu+grB/7MJZIhtLsfH5s+91B3UasHLtFVKofzwsuZN76YMUoeWc9I w3wg1U5foNimk506k5jgKmzKQXKxvtvaCJGrniVVIr8grntqiVT3J0zTfp5tAG6hZVHU 2G4Q==
X-Gm-Message-State: AAQBX9cZFjABVD766kxIbGq9ACABSJ38rUQGeBxPpKal48of4wQHgIZv uDtrQ6frZPK65Wp3/1GeL6itoDeRG+cVlVlzRA9WTg==
X-Google-Smtp-Source: AKy350YVYizwj5f/uLiM7er8TXZmVEo61mineGzaBNq09Rt7pcOLsfsHiNuKzD0LyPfYrkwanqnqnA==
X-Received: by 2002:a05:6a00:23d2:b0:626:29ed:941f with SMTP id g18-20020a056a0023d200b0062629ed941fmr18938231pfc.5.1681693867219; Sun, 16 Apr 2023 18:11:07 -0700 (PDT)
Received: from smtpclient.apple ([2601:1c0:cb02:fad0:7c16:68af:d685:6313]) by smtp.gmail.com with ESMTPSA id g18-20020aa78192000000b0063b7f3250e9sm2773445pfi.7.2023.04.16.18.11.06 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 16 Apr 2023 18:11:06 -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)
Date: Sun, 16 Apr 2023 18:10:56 -0700
Message-Id: <29E0D61F-B338-460D-9F8E-67D5D4CC54CB@marmot-tech.com>
References: <FAA07113-9BEE-4C45-A017-5C88EEF23C6B@kitterman.com>
Cc: dmarc@ietf.org
In-Reply-To: <FAA07113-9BEE-4C45-A017-5C88EEF23C6B@kitterman.com>
To: Scott Kitterman <sklist@kitterman.com>
X-Mailer: iPad Mail (20D67)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/Joo7f_XVxqRMfaKBz1-lR0HX1y0>
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:11:12 -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