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

Seth Blank <seth@valimail.com> Fri, 15 May 2020 18:26 UTC

Return-Path: <seth@valimail.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 305683A0064 for <dmarc@ietfa.amsl.com>; Fri, 15 May 2020 11:26:45 -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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=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=valimail.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 P5Ba4MLPCGbh for <dmarc@ietfa.amsl.com>; Fri, 15 May 2020 11:26:43 -0700 (PDT)
Received: from mail-wr1-x429.google.com (mail-wr1-x429.google.com [IPv6:2a00:1450:4864:20::429]) (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 3F7293A03F6 for <dmarc@ietf.org>; Fri, 15 May 2020 11:26:43 -0700 (PDT)
Received: by mail-wr1-x429.google.com with SMTP id k13so2525881wrx.3 for <dmarc@ietf.org>; Fri, 15 May 2020 11:26:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=valimail.com; s=google2048; h=mime-version:from:date:message-id:subject:to; bh=jjyvPrppP/u4g5G3Rb1u4V9HpEdSOzR9y4pvYdiMwuM=; b=KsZgMfeBbp+SOcEd9v8rqBfLgDi4qga9PqyKonLjMA9fMFpFRJoSpDwpSzHpXzzYLd Hky/j8wYD37Jl3zi+ChptirIrXAZei4omwcZekDUzkVYZBraq8wRv+bTgJOBCZY20bYQ 2YyeDjrRQl9i2P9l/Nblof2oRSc/lF058rpeQ/omnIL20eRf3sRCqfH/wgKYmKBCBg60 OEfh1ybuqwauTNZqjd6ckCP+nQ85hxt3kotyL/YHEGk7Z3g2ehz5kddgAOwBe9REXbsb iMQXYDOTjSYWpdkI5mSKfs4IqykTuRV8PLIlobddckW9LmH01HauuCJK+DHSa0wWOezZ OV+A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=jjyvPrppP/u4g5G3Rb1u4V9HpEdSOzR9y4pvYdiMwuM=; b=SOspjicGag1Q5GKmFOAUgnDT0SMU8MuC6JLPaWIdvFYmjgaIEiOI7DVvdHmu6IfWBn /XBGh/RBW6cK930zzskEs9oV2Nz4diua+AzkAnTrt83eoYwNBUlmt/Yz5ciVV154E+kd 9vC2eAc+ZTJt5/37aNhZyZsPaKYPSCH6hBPEcSeQBSyR0z1Je2IfXFfc2QbBZoZJlUL6 xl6PeMk3MmWjHHuxXyRzF5dn2HESph0LTrnwoJn6uXq03b06DLrx2Z2zKI07kE0Vijv4 GEh9JAcfJIofnk4J4FtisPZajWXuUfjrn881lvMIN7YtGnm3r40OD+iUjDIoYy/gBShf wH7w==
X-Gm-Message-State: AOAM532G5c7D5e1v6HpRNFc012obe4i/+DUqDrYMFUE657fpwNJt+3aw TZ+7UzbhCe3qxN1GKlGxTG8slP6RHKFrRbtslXAtFaUFNEU=
X-Google-Smtp-Source: ABdhPJy6JVls3ek3WOtkYe47NXmkiPstCTb8mWpry1UlxpLs+Ohq11Ns3JHe8laxvgvPcgaFM5t9rUGi18jghiU/xU0=
X-Received: by 2002:a5d:46cf:: with SMTP id g15mr6044088wrs.276.1589567201340; Fri, 15 May 2020 11:26:41 -0700 (PDT)
MIME-Version: 1.0
From: Seth Blank <seth@valimail.com>
Date: Fri, 15 May 2020 11:26:30 -0700
Message-ID: <CAOZAAfP9AiYi2Gpyd2gfhbN5tUmTA5oH4_bOGq_HY4JnqYT+fQ@mail.gmail.com>
To: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000062077d05a5b3f42d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/DhGgMjqJld2eBjQtqpsGdyaBEj8>
Subject: [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 18:26:52 -0000

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?

-- 

*Seth Blank* | VP, Standards and New Technologies
*e:* seth@valimail.com
*p:* 415.273.8818



This email and all data transmitted with it contains confidential and/or
proprietary information intended solely for the use of individual(s)
authorized to receive it. If you are not an intended and authorized
recipient you are hereby notified of any use, disclosure, copying or
distribution of the information included in this transmission is prohibited
and may be unlawful. Please immediately notify the sender by replying to
this email and then delete it from your system.