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

Tim Wicinski <tjw.ietf@gmail.com> Thu, 21 May 2020 20:55 UTC

Return-Path: <tjw.ietf@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 2D5743A0ABC for <dmarc@ietfa.amsl.com>; Thu, 21 May 2020 13:55:09 -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 GvkhiQH-rJVV for <dmarc@ietfa.amsl.com>; Thu, 21 May 2020 13:55:07 -0700 (PDT)
Received: from mail-ot1-x332.google.com (mail-ot1-x332.google.com [IPv6:2607:f8b0:4864:20::332]) (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 4B78C3A0A8D for <dmarc@ietf.org>; Thu, 21 May 2020 13:55:07 -0700 (PDT)
Received: by mail-ot1-x332.google.com with SMTP id 63so6621503oto.8 for <dmarc@ietf.org>; Thu, 21 May 2020 13:55:07 -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=aTOZ0Yr/6DdNaKAbbHHtTUaAUHb6H9lgUvV2clQJe4Y=; b=fDHCViVJaHumWI1HH+5aS/ELvgbsW64dyDSDs6c1RMLUwcxgOHzHoxwnOxYKpWQFK2 rCC4boVl4DD1RbrQ7sCmlSyySdAxzbBg4Ue3aktYFcod2K4G79nZr62BdpUg8a70op7j R0jHoKU1Hy5/Yf2E3ieeD2wdByGYIr0JeKwol2vKMjVOyqCxePihvb/rUQrLQ8yO0aXl vrbn9/iubVex1PZNqtDkcJQ05roeBUIpYOQToRjmH72WWYfCbViU9dPak6VkddHvfEB+ bpnJEcI7/f7QyMqe3Hg0lsLlA3yegMKyjvFOOFUIeFKYddAgiHXsrHMy057MWKmZKLxr dMww==
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=aTOZ0Yr/6DdNaKAbbHHtTUaAUHb6H9lgUvV2clQJe4Y=; b=galzXJabao5xQfDUdEaFYfXHKmQvI88zE7HUsTaSwp3hj4lmYTD/n651BYZpWARup8 ckgM0s8zIW3rouZTiHgfGgXlaluZWrDTbkdbWXNwb6rlRv3f8IdHwHyndVaBWhNiAolZ uJR5GyIqkoHLLIUpjzb67wUAWjmkCAzrHY+/JPSFalmZUSJ8SPcP9mnj5BD+R7mPHZzC HwG93wu6AVa2HnPXCj+dSFOukMZoqACt0vYlRrkE/TbDV9qKKtKmGusRAoCVbtR8XTpB OpDkknVKE3TdZqod8MsXWkWRJ1q8IO9A65TMBsldoBeZVE2eR1ynH51fDIaTlvxfTdvF 22Dw==
X-Gm-Message-State: AOAM530dbbguWhZfwyoIZIymsrDz0WC3vLOxlU7u/hx25e5IMlOR1T8y pz9F3XlnaybAznq3+XoYl8dC+RQypVs1PlibMXI=
X-Google-Smtp-Source: ABdhPJzqfinV52pvP26XsbsVdrdjvOmr/wlWbNd+FcEmYTnHZ6oOZiqB2ebycKrwQVAAJgrw9nZQGy4IY4JN4NPiVac=
X-Received: by 2002:a05:6830:3109:: with SMTP id b9mr5461898ots.41.1590094506610; Thu, 21 May 2020 13:55:06 -0700 (PDT)
MIME-Version: 1.0
References: <CAOZAAfP9AiYi2Gpyd2gfhbN5tUmTA5oH4_bOGq_HY4JnqYT+fQ@mail.gmail.com> <CAL0qLwa-iuyB_iNQU+g6e3NH1+q0W413RaCZcHp==s9CQA7s1g@mail.gmail.com> <r9nefr$12k0$1@gal.iecc.com>
In-Reply-To: <r9nefr$12k0$1@gal.iecc.com>
From: Tim Wicinski <tjw.ietf@gmail.com>
Date: Thu, 21 May 2020 16:54:55 -0400
Message-ID: <CADyWQ+HNGSQwxvCcsHykG9AN2rVeXCecmrpr4H+d1HDZUYUUUA@mail.gmail.com>
To: John Levine <johnl@taugh.com>
Cc: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000039d37a05a62eba62"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/Ffy0YRtyrJWgEbBIlqS6RVlfNec>
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: Thu, 21 May 2020 20:55:09 -0000

(With no hats)

I agree with John the v=DMARC1; is magic and MUST be first.  Everything
else can show up wherever.

tim


On Fri, May 15, 2020 at 9:09 PM John Levine <johnl@taugh.com> wrote:

> In article <CAL0qLwa-iuyB_iNQU+g6e3NH1+q0W413RaCZcHp==
> s9CQA7s1g@mail.gmail.com>,
> Murray S. Kucherawy  <superuser@gmail.com> wrote:
> >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.
>
> The v=DMARC1; is a magic number that tells you whether it's worth decoding
> the
> rest of the record.  People put a lot of junk at tops of their zones, some
> of which is in k=v format and I would prefer not to try to decode records
> full
> of junk to see of a v= tag is in there somewhere.
>
> Other than that I agree there is no reason to specify the order of
> tags.
>
> --
> Regards,
> John Levine, johnl@taugh.com, Primary Perpetrator of "The Internet for
> Dummies",
> Please consider the environment before reading this e-mail. https://jl.ly
>
> _______________________________________________
> dmarc mailing list
> dmarc@ietf.org
> https://www.ietf.org/mailman/listinfo/dmarc
>