Re: [dmarc-ietf] Proposed text for p=reject and indirect mail flows

Scott Kitterman <sklist@kitterman.com> Mon, 10 April 2023 00:28 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 05265C15155F for <dmarc@ietfa.amsl.com>; Sun, 9 Apr 2023 17:28:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.398
X-Spam-Level:
X-Spam-Status: No, score=-4.398 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_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=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=neutral reason="invalid (unsupported algorithm ed25519-sha256)" header.d=kitterman.com header.b="24igclzT"; dkim=pass (2048-bit key) header.d=kitterman.com header.b="ej+zLNdR"
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 7p1Mp4Q_zuAS for <dmarc@ietfa.amsl.com>; Sun, 9 Apr 2023 17:28:07 -0700 (PDT)
Received: from interserver.kitterman.com (interserver.kitterman.com [64.20.48.66]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 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 F2C7AC14CEFD for <dmarc@ietf.org>; Sun, 9 Apr 2023 17:28:06 -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 9950BF801E7; Sun, 9 Apr 2023 20:27:56 -0400 (EDT)
DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201903e; t=1681086462; h=date : from : to : subject : in-reply-to : references : message-id : mime-version : content-type : content-transfer-encoding : from; bh=lfnHIJKg+RslinO2g7gmoBfEhJXbRXgual9IWzJAMHM=; b=24igclzTe77AEvW4Sruju1sA4T4cfsoTLlpmbnmSa9r32ELd8HmSP7W/wEvFu2J+0Czsp /u39Xcqf3fAMyNdCA==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201903r; t=1681086462; h=date : from : to : subject : in-reply-to : references : message-id : mime-version : content-type : content-transfer-encoding : from; bh=lfnHIJKg+RslinO2g7gmoBfEhJXbRXgual9IWzJAMHM=; b=ej+zLNdR1f4NRToovQAZigE84swjFZW1MMkETHedTMhs/mEbmNbUSq4WphYiZmB1Z+v1K Q+JQKXwOwfolvXGBY09EsBqOCXbFRHkLcnkuWXs6k529fGz+9R0XABSSe9tOIbnQZiMi6Lr tVP27aqsB8gkzXkrWszfOPEtgE8UjvhGLB1y9dLVUbyxlJs8A0FenW3LwJtIbNyOyJ12H+1 SM+o1hK5CQucat6An+GnIOYGbmhrQZmBJoZy944eRuYv6ounjsbk2m/yNjTcQyLSX+4YUSh NyR5zvT0vlKCjXp7V59d0kT9BuLg1/jZ2VtWsJih7wvfA+o1l40bxXHUjJ+A==
Received: from [127.0.0.1] (mobile-166-170-34-136.mycingular.net [166.170.34.136]) by interserver.kitterman.com (Postfix) with ESMTPSA id D05E1F801CC; Sun, 9 Apr 2023 20:27:41 -0400 (EDT)
Date: Mon, 10 Apr 2023 00:27:34 +0000
From: Scott Kitterman <sklist@kitterman.com>
To: dmarc@ietf.org
In-Reply-To: <CALaySJJQ-Mh+=EsmA7QatrcCbCSSTGHt6fRGWequ+KCH3adYUg@mail.gmail.com>
References: <20230409005207.DCA8BBD1CC17@ary.qy> <4a0dba74-3e25-b9cb-dd64-20bf04ae76ba@tekmarc.com> <7b599a98-922a-44db-af91-2f8aa0f74181@app.fastmail.com> <CALaySJJQ-Mh+=EsmA7QatrcCbCSSTGHt6fRGWequ+KCH3adYUg@mail.gmail.com>
Message-ID: <6456DDBA-6C9A-47F2-BC88-17154270D49D@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/yaNersE40EtsM2KojlMa_3El3Ys>
Subject: Re: [dmarc-ietf] Proposed text for p=reject and indirect mail flows
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, 10 Apr 2023 00:28:11 -0000


On April 9, 2023 6:33:54 PM UTC, Barry Leiba <barryleiba@computer.org> wrote:
>> As Todd previously stated, my preference is for language that
>> acknowledges the primacy of the domain owner over interoperability
>
>The problem is that IETF standards are about interoperability, not about
>anyone’s primacy.
>
>There is an alternative, though: we can acknowledge that because of how
>those deploying DMARC view their needs over interoperability, DMARC is not
>appropriate as an IETF standard, and we abandon the effort to make it
>Proposed Standard.
>
>I see that as the only way forward if we cannot address the damage that
>improperly deployed DMARC policies do to mailing lists.
>
I think this is a reasonable conclusion.

I think we either need to take a strong stand on interoperability or come up with another plan.

If we decide to punt on interoperability, we might document the interoperability mess in an appendix, make it experimental, and then wait for then wait for the market to decide.

I'd prefer we don't do that, but avoiding a result like that is going to take some compromise.

I suspect there's a path forward built around domains which [conditions] MUST NOT p=reject because interoperability, but no one is likely to be entirely happy with the results (and that's fine, IETF rough consensus is about "I can live with it", not "I like it").

Scott K