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

Seth Blank <seth@valimail.com> Sun, 07 June 2020 20:37 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 1F4323A0927 for <dmarc@ietfa.amsl.com>; Sun, 7 Jun 2020 13:37:58 -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=[AC_BR_BONANZA=0.001, 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, 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 u46LcLHxM49t for <dmarc@ietfa.amsl.com>; Sun, 7 Jun 2020 13:37:56 -0700 (PDT)
Received: from mail-wr1-x434.google.com (mail-wr1-x434.google.com [IPv6:2a00:1450:4864:20::434]) (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 B7F7F3A0926 for <dmarc@ietf.org>; Sun, 7 Jun 2020 13:37:55 -0700 (PDT)
Received: by mail-wr1-x434.google.com with SMTP id r7so15267091wro.1 for <dmarc@ietf.org>; Sun, 07 Jun 2020 13:37:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=valimail.com; s=google2048; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=j5nFoObm12zUu5Wt1scAipQgsmwwJ1G59ePgfUd1SZs=; b=bPgvDvYcwK70mXLHCZOi7BBRE3t0k98rUiLHcJ0qDfKJdVezl8mX44EXPjax+DsiEY aj5DTXZh6WFVpvQeTXjIUafxro8Ve7avmQKJ+4RYBSsyrvGUiyFpmwQN2PhG8fBi4KmL GRnY7WlBDKrfNq4ebUgCMp0pK+I9jbU8sib73zNNYtekeYLqn55vN/5MqlyQmvPNrHUv hXoLyOvkzn65rJAaigXRZWuG71F4V4jCe4x3m7fpTxN0Q4aIrYuJhNL/ofQlhBNDho7I KuRt7DhGRvtacLK0VuZC6eL+bzCH0NKevPVqNyV4xI9sd+pR7z2ZnNUWIprBhaSgc+Po AUmA==
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; bh=j5nFoObm12zUu5Wt1scAipQgsmwwJ1G59ePgfUd1SZs=; b=Ih/fnUUaEvzN4vOLy8ptUG6nx51iXHlXj3pE3GnLU84yP1giP16eoaVw2J5SjVzqja 6fiX4UjiqdkDU0rQqhXVoiguc5PSwyJh0LltOYEtZZgc23s5g0x+LMqlJVYwUjK00/UG tcLLHcfvY03txnrCLNJIUNNdxVoApSio5zkmSQr1x170XJKFhwRAn6C+kVQ5E3SbJJT4 zBO1okhMLPCUbjt+NCzpFIa7GlxED/jmip37EW/aPWyWZauy5h4rIsnHDFgKZte1/5h6 oVUy/UDk7VHtTDWchfPidWadi29M9XHlk9oCzyEgNmNcDkciny1T15adX0S6Cliz1OpI GTug==
X-Gm-Message-State: AOAM531KffxCAuf6cfrDx0s8YsKXQ7DH3sB61zPDUJfDkhk1lDNJ0sdh xHCFIj7sn/fThkRBSaHsbnofrb4x97zJCPO7yYgkv2Gi
X-Google-Smtp-Source: ABdhPJxjCBdytDj8RbsjHVvYzyAfCrqalV1rp6b0PtQoB/eU5clEp+syWWU3BVkIlburNSSsacchr091alJJejaj0V8=
X-Received: by 2002:adf:f507:: with SMTP id q7mr19791382wro.353.1591562273829; Sun, 07 Jun 2020 13:37:53 -0700 (PDT)
MIME-Version: 1.0
References: <CAOZAAfP9AiYi2Gpyd2gfhbN5tUmTA5oH4_bOGq_HY4JnqYT+fQ@mail.gmail.com> <r9nefr$12k0$1@gal.iecc.com> <CADyWQ+HNGSQwxvCcsHykG9AN2rVeXCecmrpr4H+d1HDZUYUUUA@mail.gmail.com> <1784228.uJLO1Brz0r@localhost> <7c29c378-56cf-d601-6a18-215fe2b502d2@tana.it>
In-Reply-To: <7c29c378-56cf-d601-6a18-215fe2b502d2@tana.it>
From: Seth Blank <seth@valimail.com>
Date: Sun, 07 Jun 2020 13:37:42 -0700
Message-ID: <CAOZAAfOX3vptGrQSBkMwZc0AZKkaYSNtOpwOY4FsKiYZwwfjiQ@mail.gmail.com>
To: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000f8490405a7847792"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/DLQj-GC5ijXVZMzTQ7Yb5Advm-o>
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: Sun, 07 Jun 2020 20:37:58 -0000

As Chair, I'm closing ticket #49 and recording the consensus of the group
as in favor of removing the constraint.

On Fri, May 22, 2020 at 1:03 AM Alessandro Vesely <vesely@tana.it> wrote:

> On Thu 21/May/2020 23:11:54 +0200 Scott Kitterman wrote:
> > Agreed.  I don't think this is controversial.
> >
> > Also, I don't see a problem with making the p= tag optional (with an
> inferred
> > value of None if not present).  This is consistent with an existing
> SHOULD in
> > RFC 7489 and appears to be broadly supported in existing implementations.
> >
> > I'd propose we close this ticket with the following resolution:
> >
> > The requirement that the v=DMARC1 tag be first will be retained.
> >
> > The requirement that the p= tag be second and the requirement that the
> p= tag
> > is mandatory will be dropped.  If the p= tag is not present, the implied
> > policy value is None.
>
>
> Please, let's not forget to update the grammar, e.g. as proposed in
> https://mailarchive.ietf.org/arch/msg/dmarc/tRjV69kdM6XzkiIb3ceZ2T8OWK8
>
> Best
> Ale
> --
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> _______________________________________________
> dmarc mailing list
> dmarc@ietf.org
> https://www.ietf.org/mailman/listinfo/dmarc
>


-- 

*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.