Re: [dmarc-ietf] nit in section 7.2

Alessandro Vesely <vesely@tana.it> Wed, 27 January 2021 10:41 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 9E4C43A0D50 for <dmarc@ietfa.amsl.com>; Wed, 27 Jan 2021 02:41:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.121
X-Spam-Level:
X-Spam-Status: No, score=-2.121 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, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SZJ_IOIto8pK for <dmarc@ietfa.amsl.com>; Wed, 27 Jan 2021 02:41:51 -0800 (PST)
Received: from wmail.tana.it (wmail.tana.it [62.94.243.226]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 134343A0D44 for <dmarc@ietf.org>; Wed, 27 Jan 2021 02:41:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1611744107; bh=Rpf5kzED1802NdOrDnK+05zBBclyVNy0ASDMIRpT2j4=; l=894; h=To:References:From:Date:In-Reply-To; b=AoqOcWje3wLyZXLvb5nzjSfNvKrkpVNgYVhaz6x7wTLITElhHoMKk8b/DeL5aMba9 Ply7MkFrpLPK+bcb6kDpQWcBoSbx0Sd2YQBN23q6QsbI6ttYEVi0eVwMonElGAwuYD DsV0viH2YHv5w7n9BUoH1alJjacju9gk30hSIhYfQC2inQtYpAr03n4IXx0W5
Authentication-Results: tana.it; auth=pass (details omitted)
Original-From: Alessandro Vesely <vesely@tana.it>
Received: from [172.25.197.111] (pcale.tana [172.25.197.111]) (AUTH: CRAM-MD5 uXDGrn@SYT0/k, TLS: TLS1.3, 128bits, ECDHE_RSA_AES_128_GCM_SHA256) by wmail.tana.it with ESMTPSA id 00000000005DC053.000000006011436B.0000239E; Wed, 27 Jan 2021 11:41:47 +0100
To: dmarc@ietf.org
References: <71342cc2-9f87-89e4-42f1-1d617ee71f80@mtcc.com>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <6e4e3091-743d-570c-2cf9-459fea115d01@tana.it>
Date: Wed, 27 Jan 2021 11:41:46 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <71342cc2-9f87-89e4-42f1-1d617ee71f80@mtcc.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/XgeFVCLw-D_U4Yo-zMS7aaUCEfo>
Subject: Re: [dmarc-ietf] nit in section 7.2
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 27 Jan 2021 10:41:53 -0000

On Tue 26/Jan/2021 19:58:36 +0100 Michael Thomas wrote:
> "The report SHOULD include the following data:"
> 
> Normative SHOULD here since very strange because what follows is informational, 
> and why would it be SHOULD in the first place?
> 
> It seems to me it ought to be:
> 
> "The report includes the following data:"


That list looks like a leftover from an earlier phase of analysis.

Alex added up-to-date descriptive text, which is going to complement or replace that list.  Let's refine that for version -02:
https://github.com/ietf-wg-dmarc/draft-ietf-dmarc-aggregate-reporting/blob/main/draft-ietf-dmarc-aggregate-reporting.md#user-content-aggregate-reports


> If there are normative requirements, it seems like it would be better to put it 
> into the XML section itself.


The semantic of each field, however, is more readable in plain text.


Best
Ale
--