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

"Murray S. Kucherawy" <superuser@gmail.com> Fri, 15 May 2020 22:08 UTC

Return-Path: <superuser@gmail.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 0F0593A09EC for <dmarc@ietfa.amsl.com>; Fri, 15 May 2020 15:08:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 zJSpvoYtjT3K for <dmarc@ietfa.amsl.com>; Fri, 15 May 2020 15:08:28 -0700 (PDT)
Received: from mail-vs1-xe33.google.com (mail-vs1-xe33.google.com [IPv6:2607:f8b0:4864:20::e33]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 737683A09EB for <dmarc@ietf.org>; Fri, 15 May 2020 15:08:28 -0700 (PDT)
Received: by mail-vs1-xe33.google.com with SMTP id o26so2163931vsr.10 for <dmarc@ietf.org>; Fri, 15 May 2020 15:08:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=YGCPJai21q610w62ZxqFyVo4AMrip5IVviwIVpAOyDc=; b=ISC3c8bcTwRWVh+gw4/7E4t+ZkL5nC1HXJAMUQn7PA2Rc7nh1QkC8Pwb8lJGOn+Joj 4T8HFB2avWPFn+p1w3VN7j6d14qtcdL0gVRA+YgI5IsXJwQeowMxVne/VReDjEkaRDVE edIzLMN5nrzUYdRQTPd5qlnH+L3xMM+Jg959xrvD0ic//y4hZiscI+k9oSjwNRWvxspT m1L0PuFOwRC5kczDvmsZJNvcsSd3AkcXTIwSL/LyCK66pgYgK8mpEQtmxoC3ca1OP8Ul 1Y9uqpu2DZKNZsKXWRjwE+uTpWTFwv8ClQrk+uXb7SXHz3a2pQBjMgECfnrabMIJTxi2 p7gQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=YGCPJai21q610w62ZxqFyVo4AMrip5IVviwIVpAOyDc=; b=L9VVVBqJGjPhJq6rF6DRzlgFDR798qf6KIpsnVOhULEcUxVUb3qwoog6a6SFm3qq4U JpULr7zy2pZRpgWT6ktxYnIg0qX7NDdW8mGD9NjIHEGJEJrhEgbfQbwvXGqbZm5iUo01 wA/NywzSjylnsq9738SjkxlFstN/xw4vvZt09DhER99cxQZ8p6uM42giqZ0nPOPOi6ZC CFRWAYPvLDkBJpqjpbZYuHM6SR/I0a/8kKm1zXjGZbBco/lOBxFfZUwiBaCRPM1I42ZQ 7PyiIGcVe2dF5KB0liDX1CGAmsqjKUiOv7gT6YPHMv28uhCAbLdXkmwQLVt4NYntBytZ wLmQ==
X-Gm-Message-State: AOAM530WTDOVWzy41vjKu4sI9w12gdr8snsqlBdMiAKAIWC/UTllwYKM DxJimOMNeCtz++ZuCwse3bbhp9Ytn08GpPrRPZ1ht9lE
X-Google-Smtp-Source: ABdhPJyJYjZ5rDwK2R1DcyuBnLo/siQS48ZpdY/iXF2rl7PmvDSsv3eGgbVATAYX8tfZOnXv14Sg0iInlGnIDHnp1Qk=
X-Received: by 2002:a67:f7c9:: with SMTP id a9mr4366792vsp.7.1589580507269; Fri, 15 May 2020 15:08:27 -0700 (PDT)
MIME-Version: 1.0
References: <CAOZAAfP9AiYi2Gpyd2gfhbN5tUmTA5oH4_bOGq_HY4JnqYT+fQ@mail.gmail.com>
In-Reply-To: <CAOZAAfP9AiYi2Gpyd2gfhbN5tUmTA5oH4_bOGq_HY4JnqYT+fQ@mail.gmail.com>
From: "Murray S. Kucherawy" <superuser@gmail.com>
Date: Fri, 15 May 2020 15:08:15 -0700
Message-ID: <CAL0qLwa-iuyB_iNQU+g6e3NH1+q0W413RaCZcHp==s9CQA7s1g@mail.gmail.com>
To: Seth Blank <seth=40valimail.com@dmarc.ietf.org>
Cc: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000007a502505a5b70dfc"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/ZDppkPvVmJPT5FRHNmbIqBumcZY>
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 22:08:30 -0000

On Fri, May 15, 2020 at 11:27 AM Seth Blank <seth=
40valimail.com@dmarc.ietf.org> 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?
>

It's been a while since the original discussion, but I can't remember why
the requirement is there in the first place.  The only benefit I can think
of is that having "v=" first lets you decide very quickly if you care to
continue, but the savings is really pretty small.

-MSK, devoid of hat