Re: [dmarc-ietf] picking nits with the ABNF

Alessandro Vesely <vesely@tana.it> Sun, 10 March 2024 09:05 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 F023BC14F690 for <dmarc@ietfa.amsl.com>; Sun, 10 Mar 2024 01:05:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Level:
X-Spam-Status: No, score=-2.106 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_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=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=tana.it header.b="8Shg+aOy"; dkim=pass (1152-bit key) header.d=tana.it header.b="C3vSDItC"
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 41ACPxAeTMVI for <dmarc@ietfa.amsl.com>; Sun, 10 Mar 2024 01:05:08 -0800 (PST)
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 A1597C14F680 for <dmarc@ietf.org>; Sun, 10 Mar 2024 01:05:06 -0800 (PST)
DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=tana.it; s=epsilon; t=1710061503; bh=uG3Ugjv1hGVqxnAo5YtKsRYETiIRvQAGfs6STMWks7c=; h=Author:Date:Subject:To:References:From:In-Reply-To; b=8Shg+aOy780PWILymePPGK/0vIiR/AWEOk56McXRj7kE6tVYTjaaiMdai7KfvkQ8x QrsgTnR4Va8YJLuhPhnDQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1710061503; bh=uG3Ugjv1hGVqxnAo5YtKsRYETiIRvQAGfs6STMWks7c=; h=Date:Subject:To:References:From:In-Reply-To; b=C3vSDItCBLuZbLc3EzI8TrFt5rM1RDW+gJHfKIK8kBEE/8JIp7x8zp8sYXW4SE39K ohmRryPR5MmpzywWP9TO5W9wntZ2fpMhz6dCRWBRejXIqVYgfz0cjoHBpi+Qvn4LqO vPvqg9SHM6fxQrtpyat8Ft7ge4Itn8yHmzGMkIGKA9g8mh6XQiJfuhwr0mVTd
Original-Subject: Re: [dmarc-ietf] picking nits with the ABNF
Author: Alessandro Vesely <vesely@tana.it>
Received: from [192.168.1.100] (93-44-30-117.ip95.fastwebnet.it [93.44.30.117]) (AUTH: CRAM-MD5 uXDGrn@SYT0/k, TLS: TLS1.3, 128bits, ECDHE_RSA_AES_128_GCM_SHA256) by wmail.tana.it with ESMTPSA id 00000000005DC03D.0000000065ED77BF.00000910; Sun, 10 Mar 2024 10:05:03 +0100
Message-ID: <5de7a9ae-b080-4c4c-be61-7fd037707cae@tana.it>
Date: Sun, 10 Mar 2024 10:04:57 +0100
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Content-Language: en-US, it
To: IETF DMARC WG <dmarc@ietf.org>
References: <CADyWQ+HbLfZbTOQLbvGBVNGENb2p3iTja9-ML-wuWuLmieUO-w@mail.gmail.com> <1752625415.1824107.1710041591566.JavaMail.zimbra@univ-grenoble-alpes.fr> <CADyWQ+HyQNEzNTXcWVwazbodTvjOfMVDUdQNMr2T9YXVsRvbRg@mail.gmail.com>
Authentication-Results: tana.it; auth=pass (details omitted)
From: Alessandro Vesely <vesely@tana.it>
In-Reply-To: <CADyWQ+HyQNEzNTXcWVwazbodTvjOfMVDUdQNMr2T9YXVsRvbRg@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/KP8ZoXZFSZYK0oscOyjFVO8YQFs>
Subject: Re: [dmarc-ietf] picking nits with the ABNF
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: Sun, 10 Mar 2024 09:05:16 -0000

On 10/03/2024 05:34, Tim Wicinski wrote:
> On Sat, Mar 9, 2024 at 10:33 PM OLIVIER HUREAU <olivier.hureau@univ-grenoble-alpes.fr> wrote:
> [...]
>>
>> I would also add comment about the dmarc-fo ABNF :
>>
>> dmarc-fo  = "0" / "1" / "d" / "s" / "d:s" / "s:d"
>>
>> The FO paragraph (
>> https://www.ietf.org/archive/id/draft-ietf-dmarc-dmarcbis-30.html#name-general-record-format)
>> explicitly states that there exist 3 kinds of failure reports :
>> - DMARC failure report.
>> - DKIM failure report.
>> - SPF failure report.
>
> You got me going back to 7489 and the mail archives.  First it appears we 
> did have some discussion about this part of the ABNF 
> https://mailarchive.ietf.org/arch/msg/dmarc/2TT-2WiNVwCXozBz0JYRI1F1qME/
>
>> However, with the current ABNF, we could only ask for "DMARC failure 
>> report" or ("DKIM failure report" and/or "SPF failure report")
>>
>> Shouldn't we have an ANBF rule with all the possible permutations or a more 
>> generic one such as :
>>
>> dmarc-fo = dmarc-fo-value *(":" dmarc-fo-value)
>> dmarc-fo-value = "0" / "1" / "d" / "s"
>
> The wording for FO has changed to say "0", "1" OR a colon-separated list. 
> Looking at the 7489 ABNF I 
> am wondering if someone could say "fo=0:1:d:s"


Has anybody tried to request DKIM and/or SPF failure reports via the 
DMARC record?

Those failure reports can be requested in the apposite DNS records.  I 
wonder what sense does it make to allow them to be requested via DMARC.

Allowing fo="0:1" is an obvious nonsense.  For "d" and "s", the current 
OR syntax would be consistent if the meaning of the symbols, instead of 
the current ones, e.g. (my emphasis):

     d:  Generate a *DKIM* failure report if the message had a signature
        that failed evaluation, regardless of its alignment.  DKIM-
        specific reporting is described in [RFC6651].

were:

     d:  Generate a *DMARC* failure report if the message had a signature
        that failed evaluation, regardless of its alignment.  DKIM-
        specific reporting is described in [RFC6651].

That would restrict fo= to just express /when/ to generate a DMARC 
failure report to ruf=, where ruf= is the address for /DMARC/ failure 
reports.  The address for DKIM failure reports is specified in the ra= 
tag found at _report._domainkey.example.com.


Best
Ale
--