Re: [dmarc-ietf] I-D Action: draft-ietf-dmarc-dmarcbis-03.txt

Barry Leiba <barryleiba@computer.org> Fri, 20 August 2021 13:34 UTC

Return-Path: <barryleiba@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 8F93A3A2AFF for <dmarc@ietfa.amsl.com>; Fri, 20 Aug 2021 06:34:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.649
X-Spam-Level:
X-Spam-Status: No, score=-1.649 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
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 gwOAaX5RFd_2 for <dmarc@ietfa.amsl.com>; Fri, 20 Aug 2021 06:34:33 -0700 (PDT)
Received: from mail-lj1-f176.google.com (mail-lj1-f176.google.com [209.85.208.176]) (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 AE3D33A2AD3 for <dmarc@ietf.org>; Fri, 20 Aug 2021 06:34:32 -0700 (PDT)
Received: by mail-lj1-f176.google.com with SMTP id q21so17352154ljj.6 for <dmarc@ietf.org>; Fri, 20 Aug 2021 06:34:32 -0700 (PDT)
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:content-transfer-encoding; bh=5UzmgpGqY4vueSi7/OSnkNg9RJYH+dS9iwEsMtDftzs=; b=p04HpPkmiFeyNUhOtOzBBijtCj5eFnNKANYIZKAwf+myc6aEvp1bwGMt28Xkz27MGW e1oMF1BBaYOlly4Yvib8+s0LstO5pHYXb5l+PbE+mK+UjbxiQdddO6JdAE80VAXLOl0r xgGNdiGwICT6GX7EUEZMend4aJI/gIMFEEVzjYe8t+PN0OkzQnw5Ze+Rco9dkSzIsC76 gyg7dWcu5Excr1TPg0PWE5744/fGhZSdKeCk/zrhIoHBMAZNzZpXJx51WCA2zTO7/1UL L9b0dQDL8/FyF88HztqH/ZpkNiiR8VE6/fN7BbDpuWbd1MGz5GnpAawvssLPnFMqCOc0 cy8w==
X-Gm-Message-State: AOAM530o9MntRi8bhP8CaB5recnMdaBE81AFeuOmAHDjT5bqESUBZGaq /72nVQGrvKwdmg5BS2Tas3sT7FN4NLPXCeVDJEE=
X-Google-Smtp-Source: ABdhPJzk0KNQolZmSETitYXEe1+cbCfIz0wDw2gzJBgB0zvx0/C+YS0Jub4Q5vJvzeAbAGxIyHCdlHRTVCGHsYnEEow=
X-Received: by 2002:a05:651c:904:: with SMTP id e4mr9591099ljq.467.1629466470502; Fri, 20 Aug 2021 06:34:30 -0700 (PDT)
MIME-Version: 1.0
References: <162931752865.27585.10197515584988072678@ietfa.amsl.com> <CAHej_8mcwKcjwxV09_6ENrOnh5t+seDv_kTZiO0mgyRS2BVgTA@mail.gmail.com> <3e4b2087-a866-6f66-3964-71a3c67eab8b@tana.it> <CAHej_8kVW8daPQhghouneRS37WhaCHo4Os6Ggd43FbOpo=ri6A@mail.gmail.com> <CAL0qLwZjou+Qtr1JHjCmV+jAk1FqicB+zG4KTiRHZOLRHLV5Ng@mail.gmail.com> <CAHej_8mzm_w9S282FxHg3saMtU1i_O_69VWz9veDHNrbkA2U3w@mail.gmail.com> <ae135d56-c5ed-7b5d-dbb6-5dfbd44da5ba@tana.it> <CAH48ZfxjTyYeKegPDN2M=2qYzA5dSX6WPOgqzjF9=a0oNng=ZQ@mail.gmail.com>
In-Reply-To: <CAH48ZfxjTyYeKegPDN2M=2qYzA5dSX6WPOgqzjF9=a0oNng=ZQ@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
Date: Fri, 20 Aug 2021 09:34:19 -0400
Message-ID: <CALaySJLEEfMJHLSfguxDfRjp4etPnAWFd9Kb2gnp4-R-VnNw=Q@mail.gmail.com>
To: Douglas Foster <dougfoster.emailstandards@gmail.com>
Cc: IETF DMARC WG <dmarc@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/tImLhQ3kNpAQ1hmUTEgazJ1Q6FA>
Subject: Re: [dmarc-ietf] I-D Action: draft-ietf-dmarc-dmarcbis-03.txt
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, 20 Aug 2021 13:34:49 -0000

There is a difference between silencing dissenters and saying that the
dissent has been discussed and the rough consensus disagrees with the
dissenters.  Everyone needs to understand when they've lost an
argument -- not because people are against them, but simply because
reasonable people disagree, and we need to make a rough-consensus
decision -- and move on.

In this case, my reading of the discussion is that (1) there are good
arguments and plenty of evidence that PCT isn't working consistently
and interoperably, that PCT is mostly not necessary in a Proposed
Standard (as opposed to Experimental or Informational) version of
DMARC, and that the main use case that has been raised for retaining
it is a binary, on/off situation.  I believe the working group has
*rough* consensus on that, recognizing that agreement on it is not
unanimous.

There is a *proposal* for handling the binary situation differently.
I believe the working group as a whole has expressed interest in that
proposed solution, though we do not yet have rough consensus on the
details and text of that.

Barry, as chair

On Fri, Aug 20, 2021 at 6:19 AM Douglas Foster
<dougfoster.emailstandards@gmail.com> wrote:
>
> On the subject of PCT, we did not reach agreement, we reached silence.   Silence comes across as a move by the majority to silence dissenters.   The chairs are empowered to decide whether this is an appropriate tactic by the majority, and whether a majority or supermajority is a sufficient approximation of consensus.
>
> I believe that PCT is a weak solution to a real problem, and that eliminating PCT makes the problem much worse.    This situation will operate against the interests of all legitimate participants.    PCT needs to be improved, not discarded.   There is a lot to talk about here.
>
> Doug Foster
>
>
>
>
> On Fri, Aug 20, 2021 at 4:42 AM Alessandro Vesely <vesely@tana.it> wrote:
>>
>> On Thu 19/Aug/2021 21:37:06 +0200 Todd Herr wrote:
>> > On Thu, Aug 19, 2021 at 3:22 PM Murray S. Kucherawy wrote:
>> >
>> >> I agree the parsers won't break from this change, but an operator
>> >> currently advertising "pct=33" will suddenly stop getting what it thought
>> >> it was asking for.  One could argue that this constitutes "breakage".
>> >>
>> > It has been argued by some that an operator currently advertising "pct=33"
>> > (or anything other than 0 or 100) was never getting what it thought it was
>> > asking for in the first place, hence the discussion about removing the pct
>> > tag.
>>
>>
>> Argued by some is not the same as rough consensus.
>>
>>
>> Best
>> Ale
>> --
>>
>>
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> dmarc mailing list
>> dmarc@ietf.org
>> https://www.ietf.org/mailman/listinfo/dmarc
>
> _______________________________________________
> dmarc mailing list
> dmarc@ietf.org
> https://www.ietf.org/mailman/listinfo/dmarc