Re: [dmarc-ietf] DMARCbis WGLC - Issue 135 - What To Say About Too-Permissive/Third-Party SPF and Where To Say It?

Scott Kitterman <sklist@kitterman.com> Mon, 18 March 2024 20:39 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 A912FC1D5C65 for <dmarc@ietfa.amsl.com>; Mon, 18 Mar 2024 13:39:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.108
X-Spam-Level:
X-Spam-Status: No, score=-7.108 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_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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="Ejxarw7Z"; dkim=pass (2048-bit key) header.d=kitterman.com header.b="mR3Yyhcq"
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 SIjZwi9LIMYn for <dmarc@ietfa.amsl.com>; Mon, 18 Mar 2024 13:39:24 -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 F1F36C1D5C77 for <dmarc@ietf.org>; Mon, 18 Mar 2024 13:39:23 -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 0A3EEF8029B; Mon, 18 Mar 2024 16:39:12 -0400 (EDT)
DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201903e; t=1710794337; h=date : from : to : subject : in-reply-to : references : message-id : mime-version : content-type : content-transfer-encoding : from; bh=VRe8W5YRpxBGX79lIDOmiAcQIBhy2EOEtn7+mP2cf+E=; b=Ejxarw7Z4BPNe5PdwANkk2lHTkvX1eHQX/WZ664J2TJ1lFPnfGH6MwBLPvWgGeicchd9m NRTc1UlWkYYZ8xPDg==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201903r; t=1710794337; h=date : from : to : subject : in-reply-to : references : message-id : mime-version : content-type : content-transfer-encoding : from; bh=VRe8W5YRpxBGX79lIDOmiAcQIBhy2EOEtn7+mP2cf+E=; b=mR3Yyhcq+sqD4v5Thyt5sfQzy7VLG44D0ziR6CrSRwmr0MXOrGfFLohP7c4ymK0iQULOM QdTZVZWI3/rATGwIGLogo+kKaJd/NpNDBXk0BrqkKXYCR2kJVeZi2YGHWERlKTKsKnd07jv y+aOQJjFb2yLns3u4gNpjl/pPH9DlXaYCnnZ5JXV9FYlmNKIqSQobM8X/6+zsCiuqxxKrk+ Ia5B69dWQYBd9GtScDwV2XZ57yPIt4MtQJiwMlri75Tpf+dErJ82wts0Dx+GaHjJzNMSw+1 GiZq9tjsuMeMFpCup63GHF0u3t6QvkDnKDsQVGkqVXw7a1qC5wGOU5dMTu6g==
Received: from [127.0.0.1] (mobile-166-171-58-151.mycingular.net [166.171.58.151]) by interserver.kitterman.com (Postfix) with ESMTPSA id AAE55F80211; Mon, 18 Mar 2024 16:38:56 -0400 (EDT)
Date: Mon, 18 Mar 2024 20:38:50 +0000
From: Scott Kitterman <sklist@kitterman.com>
To: dmarc@ietf.org
In-Reply-To: <bb401fec-b3e8-dc56-929c-9aeda594d012@taugh.com>
References: <2068150.yCtiIVWOOC@zini-1880> <20240318013630.455118593233@ary.qy> <CAJ4XoYcoJFqYoAt_jq6jfsSjqtjaifiUzaqY-zkg7R3o5Bio0A@mail.gmail.com> <810a3322-4ba3-ac67-5c7b-0118028aeb34@taugh.com> <CAJ4XoYfCgo6DrD0HLMrL3+xT=K0TebQJdKjsUh3e+d-1ND3uUQ@mail.gmail.com> <40acfc56-8d00-4be1-b3fb-c5f2670b0b88@tana.it> <bb401fec-b3e8-dc56-929c-9aeda594d012@taugh.com>
Message-ID: <F3FF7287-A94C-4C44-A4EC-8DDA72B7717D@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/dkfeQ3rp0NYHAcxm5Iz_sCeIjWc>
Subject: Re: [dmarc-ietf] DMARCbis WGLC - Issue 135 - What To Say About Too-Permissive/Third-Party SPF and Where To Say It?
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, 18 Mar 2024 20:39:29 -0000


On March 18, 2024 6:53:29 PM UTC, John R Levine <johnl@taugh.com> wrote:
>On Mon, 18 Mar 2024, Alessandro Vesely wrote:
>> The text should be terser and clearer, possibly with an example.
>
>I would be happy to remove the whole thing, since it's only distantly related to defining or implementing DMARC.

I disagree.  I think this is a foreseeable risk, so we need to document it.

I think the current text strikes the right balance between being silent and being a how-to.

Scott K