Re: [dmarc-ietf] DMARC2 & SPF Dependency Removal

"Murray S. Kucherawy" <superuser@gmail.com> Thu, 08 June 2023 14:21 UTC

Return-Path: <superuser@gmail.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 70458C14CEFF for <dmarc@ietfa.amsl.com>; Thu, 8 Jun 2023 07:21:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.097
X-Spam-Level:
X-Spam-Status: No, score=-7.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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 q0KZTDBPsdtz for <dmarc@ietfa.amsl.com>; Thu, 8 Jun 2023 07:21:01 -0700 (PDT)
Received: from mail-ed1-x52a.google.com (mail-ed1-x52a.google.com [IPv6:2a00:1450:4864:20::52a]) (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 07F24C14CF09 for <dmarc@ietf.org>; Thu, 8 Jun 2023 07:21:00 -0700 (PDT)
Received: by mail-ed1-x52a.google.com with SMTP id 4fb4d7f45d1cf-50c079eb705so159241a12.1 for <dmarc@ietf.org>; Thu, 08 Jun 2023 07:21:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1686234059; x=1688826059; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=g9CZVExLNcjs9XVaIHNjsa0RIBBQgeI/Z1vkzbKP9zA=; b=C/z10X6vNkE2NCQlJJaEdQaErQdDzp8eREdObA9omps2qZQIZ+7uTy1uTwl8IU/3He el9JKFUZLPTQIm+38PPMMTYr1fMm88Zls7Cxtti/t6feqj3fkHIZdhJR/VK6BUOiXYSy fP3azfueOeFtBHpM9H7sKqg0lDzzd1k96QYaPrCB2pZFbJNewrY4MBwTrhv5Zldm8zm7 z+m+fZT8ASI+TYCfEXh7bJPXjXKO7tHfiF/cvAC+lvz1MLrqDHD+fIHbcTc1zGN4xz6g BH4ILmSx5twuKTKZUJdpSSH5uw/IOL/tQBdBzU9MRPzHcqz+FVUttZzH7zMDDhBdVuKz tKGw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1686234059; x=1688826059; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=g9CZVExLNcjs9XVaIHNjsa0RIBBQgeI/Z1vkzbKP9zA=; b=bD6t2AmHXUzYiBYrLJIGXysqD9rJ9gKJzW2c9ToA74xsxDjIiF21bdwhGgAMjayONq gCO4eo4HNJzhBEnXg5NSdXgYjGbqvB+l7zO1sUTValRkUcuWSEy5mhETtaZDw2XxAysS br6ZmaFIZa+GD+wP+us1kvEgU9y2P4GPt80fLPyTK6p92ydtsk8/r989yz11IUKcPrCz eChwaedwO6xS2VIIRlRthK/yHHsM1fdhyDjvFPyX9gcsBLon5zi21nK8XoULGxOp1xE6 jgB/kDt0djVZvTVCAIPb33mfUU6zsqKZfeZoNJhLXQ7Dg1NkrQHCrD6kPBMr6EoTKRQ+ 08FQ==
X-Gm-Message-State: AC+VfDyja5Nj0j7VyyLCihzSmSJIx6jVbLS/F8+BPOCdrFVd+uE3zQXY VkEdziigT9dJiEZpZNgpit7wDRcm2aT5wsziuhk=
X-Google-Smtp-Source: ACHHUZ4C9tKvjBZwXmpZPiAI+WAlC04Z/xJKrDCEkZbGgS7S2lvYHTISHHKDMnOiHbKp+LFw4LZhBt1G2NNfH3tORUw=
X-Received: by 2002:a05:6402:40ce:b0:514:a656:5411 with SMTP id z14-20020a05640240ce00b00514a6565411mr8743624edb.4.1686234058535; Thu, 08 Jun 2023 07:20:58 -0700 (PDT)
MIME-Version: 1.0
References: <30BB83B2-B454-41B8-992B-8E2569802D9C@1und1.de>
In-Reply-To: <30BB83B2-B454-41B8-992B-8E2569802D9C@1und1.de>
From: "Murray S. Kucherawy" <superuser@gmail.com>
Date: Thu, 08 Jun 2023 07:20:44 -0700
Message-ID: <CAL0qLwbx6Y=kmB5pQZx8gNqD=rLBYz1vLOX6ngL=wUHHUm0Hjw@mail.gmail.com>
To: Tobias Herkula <tobias.herkula=401und1.de@dmarc.ietf.org>
Cc: "dmarc@ietf.org" <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000001136ff05fd9ef68b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/Stcb8moqOrVh-852XLqPgMUSFR4>
Subject: Re: [dmarc-ietf] DMARC2 & SPF Dependency Removal
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: Thu, 08 Jun 2023 14:21:01 -0000

On Thu, Jun 8, 2023 at 6:00 AM Tobias Herkula <tobias.herkula=
401und1.de@dmarc.ietf.org> wrote:

> My team recently concluded an extensive study on the current use and
> performance of DMARC. We analyzed a staggering 3.2 billion emails, and the
> insights drawn are quite enlightening. Of these, 2.2 billion emails
> (approximately 69%) passed the DMARC check successfully. It's quite an
> achievement, reflective of our collective hard work in fostering a safer,
> more secure email environment.
>
>
>
> However, upon further analysis, it's evident that a mere 1.6% (or
> thirty-six million) of these DMARC-passed emails relied exclusively on the
> Sender Policy Framework (SPF) for validation. This is a remarkably low
> volume compared to the overall DMARC-passed traffic, raising questions
> about SPF's relevancy and the load it imposes on the DNS systems.
>
>
>
> Given the current use case scenarios and the desire to optimize our
> resources, I propose that we explore the possibility of removing the SPF
> dependency from DMARC. This step could result in a significant reduction in
> DNS load, increased efficiency, and an accurate alignment with our
> predominant use cases.
>
> [...]
>

Does anyone have consonant (or dissonant) data?

-MSK, participating