Re: [dmarc-ietf] DMARC bis: ticket 49: remove normative requirement on policy tag placement

Scott Kitterman <sklist@kitterman.com> Fri, 15 May 2020 20:09 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 5DB163A08E3 for <dmarc@ietfa.amsl.com>; Fri, 15 May 2020 13:09:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 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, SPF_PASS=-0.001, URIBL_BLOCKED=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=dY06CZnr; dkim=pass (2048-bit key) header.d=kitterman.com header.b=NxVxdiD4
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 6s2z1aGBoA-n for <dmarc@ietfa.amsl.com>; Fri, 15 May 2020 13:09:07 -0700 (PDT)
Received: from interserver.kitterman.com (interserver.kitterman.com [64.20.48.66]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B1DA73A0932 for <dmarc@ietf.org>; Fri, 15 May 2020 13:09:07 -0700 (PDT)
Received: from interserver.kitterman.com (interserver.kitterman.com [64.20.48.66]) by interserver.kitterman.com (Postfix) with ESMTPS id CD0D3F80331 for <dmarc@ietf.org>; Fri, 15 May 2020 16:09:06 -0400 (EDT)
DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201903e; t=1589573346; h=from : to : subject : date : message-id : in-reply-to : references : mime-version : content-transfer-encoding : content-type : from; bh=/MH1wuFHvuLzZsHOekJJUA7ghakPrfsQaqFfZau4dNg=; b=dY06CZnrnKCHZJrIsUfUsV/PFQOY7dYeid63CmN05vYpvzGpc7CmP+O6jEpJjZoglhUZG YpFNCkwKUa/t3tVCw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201903r; t=1589573346; h=from : to : subject : date : message-id : in-reply-to : references : mime-version : content-transfer-encoding : content-type : from; bh=/MH1wuFHvuLzZsHOekJJUA7ghakPrfsQaqFfZau4dNg=; b=NxVxdiD4I1wZb9TtdUFIPwXX8RS5lWf6hMXrUT05aj/eG47WpOwOwPW23/4/kqkC/atO2 ukNQvGD6RqlM52pnf6SoZepohLXVJqgQSO+IsdIPFXJswNl5y+1/udKIJXUG0gVQe58Nwlk 7eLeNGadYm17V78LguSJt3BhZzx2gX2VSKRhO3F9bdBEx8tX6zRK18NcY3ZKJTdV7JmKOd0 LfGwQGdJrz7bsJvN3RX++6xs/0rI+zHzqhyA3r/ZGEwoLUmwalLsirT4apsfqzpDls+nm49 2a7YmZQIhI+/XziZYZg7HfKp2qf/69AT/SoMRLMEzCUAvks8mayVl2SDoIMw==
Received: from sk-desktop.localnet (static-72-81-252-22.bltmmd.fios.verizon.net [72.81.252.22]) by interserver.kitterman.com (Postfix) with ESMTP id 9236FF80120 for <dmarc@ietf.org>; Fri, 15 May 2020 16:09:06 -0400 (EDT)
From: Scott Kitterman <sklist@kitterman.com>
To: dmarc@ietf.org
Date: Fri, 15 May 2020 16:09:06 -0400
Message-ID: <5977449.Cccs3KlKfv@sk-desktop>
In-Reply-To: <CAOZAAfP9AiYi2Gpyd2gfhbN5tUmTA5oH4_bOGq_HY4JnqYT+fQ@mail.gmail.com>
References: <CAOZAAfP9AiYi2Gpyd2gfhbN5tUmTA5oH4_bOGq_HY4JnqYT+fQ@mail.gmail.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/6-OBimBVYjYLTaPv6leZa9CNr9w>
Subject: Re: [dmarc-ietf] DMARC bis: ticket 49: remove normative requirement on policy tag placement
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: Fri, 15 May 2020 20:09:17 -0000

On Friday, May 15, 2020 2:26:30 PM EDT Seth Blank wrote:
> https://trac.ietf.org/trac/dmarc/ticket/49
> 
> The penultimate paragraph of https://tools.ietf.org/html/rfc7489#section-6.3
> states:
> 
> the "v" and "p" tags MUST be present and MUST
>    appear in that order.
> 
> While the v= tag pretty universally appears first, the p= tag does not in
> many records, and no implementation appears to care.
> 
> The v= tag must appear first, or the policy discovery mechanism as defined
> in https://tools.ietf.org/html/rfc7489#section-6.6.3 would break.
> 
> But there doesn't appear to be any real reason to keep the normative
> requirement that the p= tag MUST be second in the record after the v= tag,
> nor does this requirement seem to have any impact on interoperability or
> general record parsing in theory or in practice.
> 
> Should we remove this normative requirement?

Section 6.6.3, step 6, sub-step 1 already says:

>        1.  if a "rua" tag is present and contains at least one
>            syntactically valid reporting URI, the Mail Receiver SHOULD
>            act as if a record containing a valid "v" tag and "p=none"
>            was retrieved, and continue processing;

I don't see a problem with changing the MUST for p= to SHOULD and adding a 
MUST p= or rua=.  That's consistent with what we already tell receivers they 
SHOULD do.

Scott K