Re: [dmarc-ietf] WGLC editorial review of draft-ietf-dmarc-dmarcbis-30

Alessandro Vesely <vesely@tana.it> Mon, 01 April 2024 10:51 UTC

Return-Path: <vesely@tana.it>
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 92C66C14F68F for <dmarc@ietfa.amsl.com>; Mon, 1 Apr 2024 03:51:31 -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=pass (1152-bit key) header.d=tana.it
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 ohnhKFTPGPO1 for <dmarc@ietfa.amsl.com>; Mon, 1 Apr 2024 03:51:24 -0700 (PDT)
Received: from wmail.tana.it (wmail.tana.it [94.198.96.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1188CC14E515 for <dmarc@ietf.org>; Mon, 1 Apr 2024 03:51:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1711968677; bh=ri26WnrkUGaRyK6BsUxUFpgJW0w4f0LBi6SnOrpw54I=; h=Date:Subject:To:References:From:In-Reply-To; b=C6la++tOKE5rWuRA28Z3NP55w67rlGoQRVSXitPSmC4gV4Q0vFG3pVAewgbxE7/KN niqhJIMiegiqBcId4A/9FaqF7I8rjXyNs+XvRKmq1q635ex3115GMHxbhnCoer8Y5Q wd2ytbXs7CJfYLIKUhKyRzO7QjHLhiu/nlYCAILvSOYF6KA0yeFXcJ6gzPOif
Original-Subject: Re: [dmarc-ietf] WGLC editorial review of draft-ietf-dmarc-dmarcbis-30
Author: Alessandro Vesely <vesely@tana.it>
Received: from [172.25.197.120] (pcale.tana [::ffff:172.25.197.120]) (AUTH: CRAM-MD5 uXDGrn@SYT0/k, TLS: TLS1.3, 128bits, ECDHE_RSA_AES_128_GCM_SHA256) by wmail.tana.it with ESMTPSA id 00000000005DC25D.00000000660A91A4.0000442D; Mon, 01 Apr 2024 12:51:16 +0200
Message-ID: <f03f26c4-8844-4094-a7aa-85d7d089afae@tana.it>
Date: Mon, 01 Apr 2024 12:51:16 +0200
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
To: dmarc@ietf.org
References: <CAOZAAfPwJHKGyLjTkdGDqkMeK4RQX4Fj0rw-Upn0cLZ+cE74aA@mail.gmail.com> <2cdd13ec-9d7f-4732-91ea-9c8983d7a28c@tana.it> <CAH48ZfzaNR2A6zUWVeeoay+UHLHTzja9f5RGfAt5htXd21C0KQ@mail.gmail.com> <d4405d75-f22e-4cdc-92d9-71a3fc258c13@tana.it> <CAL0qLwYtc-jyosmhb1_CwK=SBL9azqfD5_Z2aL8h-kJiZedjxA@mail.gmail.com>
Authentication-Results: tana.it; auth=pass (details omitted)
From: Alessandro Vesely <vesely@tana.it>
Content-Language: en-US, it-IT
In-Reply-To: <CAL0qLwYtc-jyosmhb1_CwK=SBL9azqfD5_Z2aL8h-kJiZedjxA@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/4s26XdcjWGBHqW5Aqbc64-Le5T0>
Subject: Re: [dmarc-ietf] WGLC editorial review of draft-ietf-dmarc-dmarcbis-30
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, 01 Apr 2024 10:51:31 -0000

On Sun 31/Mar/2024 22:33:10 +0200 Murray S. Kucherawy wrote:
> On Sun, Mar 31, 2024 at 9:32 AM Alessandro Vesely <vesely@tana.it> wrote:
>> On Sun 31/Mar/2024 14:22:04 +0200 Douglas Foster wrote:
>>> On SPF, our document should say simply,
>>> " a DMARC-compliant evaluator MUST NOT reject a message, based on SPF result, 
>>> prior to receiving the Data section and checking for aligned and verifiable 
>>> signatures."
>>
>> Nonsense.  Rejecting at RCPT TO is much quicker than waiting for the whole 
>> message.  People who publish -all know what they do.
>
> Of course it is, but it prevents DKIM signatures from being tested, and 
> hence DMARC from being evaluated.  Maybe that's what you want, but maybe 
> it's not what everyone wants.


I agree there may be people who inadvertently set -all and would be better off 
changing it to ~all.  However, by claiming Best Practice, we'd be scaring those 
who want -all for good reasons.


>> I also reject based on RBLs and private IP lists; does that affect DMARC 
>> compliance?
> 
> I might argue that you can't possibly claim DMARC compliance if you're not 
> even getting far enough to execute its algorithm.


I'd say I comply /when/ I execute its algorithm.


Best
Ale
--