[dmarc-ietf] DMARCbis WGLC Issue - Section 11.5

Scott Kitterman <sklist@kitterman.com> Sat, 16 March 2024 21:35 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 B1406C14F61D for <dmarc@ietfa.amsl.com>; Sat, 16 Mar 2024 14:35:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.408
X-Spam-Level:
X-Spam-Status: No, score=-4.408 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, 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="EBklzsm1"; dkim=pass (2048-bit key) header.d=kitterman.com header.b="LT5azZxt"
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 oBzb3qAs-AMi for <dmarc@ietfa.amsl.com>; Sat, 16 Mar 2024 14:35:12 -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) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 81FA1C14F619 for <dmarc@ietf.org>; Sat, 16 Mar 2024 14:35:12 -0700 (PDT)
Received: from interserver.kitterman.com (interserver.kitterman.com [64.20.48.66]) by interserver.kitterman.com (Postfix) with ESMTPS id 4C0F4F8022F for <dmarc@ietf.org>; Sat, 16 Mar 2024 17:34:52 -0400 (EDT)
DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201903e; t=1710624876; h=from : to : subject : date : message-id : mime-version : content-transfer-encoding : content-type : from; bh=H7XZuYOQfPZGJK04Fym93Xj3OjKJ4MdXIMkz0CDKM8E=; b=EBklzsm1BQiUoYpGAnK9xPONAfKMLTnup39/RJx02k4xEy/LR+YXzoxq2kFNl3f/WoLL+ R6N+BGniSJ8yAZRBA==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201903r; t=1710624876; h=from : to : subject : date : message-id : mime-version : content-transfer-encoding : content-type : from; bh=H7XZuYOQfPZGJK04Fym93Xj3OjKJ4MdXIMkz0CDKM8E=; b=LT5azZxt7Yb5D2jlk2cuH8PDEHB7FS1H5jZsxIjlthmLUYRMAMPlkQoIPIg7AcYGbS8hd Jvozna/gTON5gei+3YUYwmbmtrKANWmFAlIyujtyEaxhfYCBXHOC5mlNdrwHnS4famIglFw UbNnAPY6I1vbfhLtPMVz26nEic4KZmIWWq3qM7mELZiYgjVJGJinNN5jm87GXUXUgXsWsxd hoJsnGXaaaf9XPgkysF1zosy/ywtazAjsrGaKaJBBbfk5zB1iVGSe1mUJOXw18mQMfs5IhW U+9TE+8pD8Kpoqs/pH1QTbc5dVqQVXFZMcYknInN26cHKSiq1OCsKfOlxzvQ==
Received: from zini-1880.localnet (static-72-81-252-22.bltmmd.fios.verizon.net [72.81.252.22]) by interserver.kitterman.com (Postfix) with ESMTP id 9AE7AF80156 for <dmarc@ietf.org>; Sat, 16 Mar 2024 17:34:36 -0400 (EDT)
From: Scott Kitterman <sklist@kitterman.com>
To: dmarc@ietf.org
Date: Sat, 16 Mar 2024 17:34:31 -0400
Message-ID: <36398463.d7gn8dBsVb@zini-1880>
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/Wae8Cq7XFCxjX8Dj1fBQetTzs_k>
Subject: [dmarc-ietf] DMARCbis WGLC Issue - Section 11.5
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: Sat, 16 Mar 2024 21:35:16 -0000

Not sure if this is "significant" or not.

I don't particularly like the title, but that's been that way for quite some 
time, so for WGLC, meh.

The particular concern I have is with the text that was added right before 
WGLC about multi-valued RFC5322.From fields.  It includes the statement:

> Such an approach might prove useful for a small number of Author
> Domains, but it is likely that applying such logic to messages with a larger
>  number of domains (as defined by each Mail Receiver) will expose the
> Mail Receiver to a form of denial of service attack, and so applying a
> negative disposition decision to the message may be the best course of
> action.

In particular, the word "likely" seems a bit much.  Additionally, I think 
beyond the Domain Owner DMARC policy published in a DMARC record, I think 
discussions about message disposition are outside the scope of this document.  
How about this instead:

> Such an approach might prove useful for a small number of Author
> Domains, but it is possible that applying such logic to messages with a
> large number of domains (as defined by each Mail Receiver) will expose the
> Mail Receiver to a form of denial of service attack.  Limiting the number of
> Author Domains processed will avoid this risk.  If not all Author Domains
> are processed, then the DMARC evaluation is incomplete.

I don't think we need to tell people what to do with such messages.  I think 
this is enough.

Scott K