Re: [Last-Call] Change of position: Last Call: BCP 83 PR-Action Against Dan Harkins

John C Klensin <john-ietf@jck.com> Fri, 28 October 2022 19:43 UTC

Return-Path: <john-ietf@jck.com>
X-Original-To: last-call@ietfa.amsl.com
Delivered-To: last-call@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5984EC14F731; Fri, 28 Oct 2022 12:43:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.907
X-Spam-Level:
X-Spam-Status: No, score=-6.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8pRU_eFLtut6; Fri, 28 Oct 2022 12:42:58 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6E67FC14F72B; Fri, 28 Oct 2022 12:42:56 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1ooVFk-000Mbx-Kq; Fri, 28 Oct 2022 15:42:52 -0400
Date: Fri, 28 Oct 2022 15:42:46 -0400
From: John C Klensin <john-ietf@jck.com>
To: Pete Resnick <resnick@episteme.net>
cc: Ted Lemon <mellon@fugue.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>, IETF Chair <chair@ietf.org>, last-call@ietf.org
Message-ID: <5F20823EFE2B9F312D337134@PSB>
In-Reply-To: <A5F3BB1B-EE56-477F-B2AB-F239FD5175FC@episteme.net>
References: <CFE25E25-D131-468E-9923-80350D6216F3@ietf.org> <d5f91bf1-4407-8ec5-50ab-a8bdb7327c0f@gmail.com> <ef5c4886-5438-0537-611f-19b7ac54daa4@gmail.com> <CAPt1N1kOCKi=1kdLucU+dxDSdqCGW38U0Du8nDbc2chLdVJVCQ@mail.gmail.com> <E35A397E4DCDAD5D0BA33D9A@PSB> <476691AB-6B2E-421B-8112-BD90EAE13EA2@episteme.net> <40901823039A72E927E6387C@PSB> <EFE5E8FB-9791-4E81-8502-9B3A65B64216@episteme.net> <5EE93148C706EEA966757077@PSB> <A5F3BB1B-EE56-477F-B2AB-F239FD5175FC@episteme.net>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/last-call/kGwtJEo0jM35BDUyvjA_bpJIQA4>
Subject: Re: [Last-Call] Change of position: Last Call: BCP 83 PR-Action Against Dan Harkins
X-BeenThere: last-call@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: IETF Last Calls <last-call.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/last-call>, <mailto:last-call-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/last-call/>
List-Post: <mailto:last-call@ietf.org>
List-Help: <mailto:last-call-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/last-call>, <mailto:last-call-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Oct 2022 19:43:00 -0000

In the hope of winding this thread down, both generally and in
line with Bron's comment/ suggestion, one small comment at the
end rather than quibbling about details.  If this needs a
response, and I hope it does not, please direct it to the
ietf@ietf.org list.

--On Friday, October 28, 2022 10:21 -0500 Pete Resnick
<resnick@episteme.net> wrote:

> On 27 Oct 2022, at 22:24, John C Klensin wrote:
> 
>> I do have two concerns from what I remember of
>> BCP 83 and some of the recent discussion.   One is that BCP 83
>> does, IIR rather clearly, say that a PR-action cannot be
>> reviewed in less than a year.  So, if the "time of someone's
>> liking", were significantly shorter than that, I'm not sure
>> the above is possible.
> 
> It's a SHOULD, not a MUST:
> 
>     Once taken, this action remains in force until explicitly
> nullified
>     and SHOULD remain in force for at least one year.
> 
>> The other is that, if we are trying to
>> avoid being punitive, giving Dan the "award" of being one of
>> the very few PR-actions we have used does sound a bit like
>> punishment.
> 
> Giving chairs and list moderators the ability to control
> unrestricted posting by someone with a track record is a way
> to reduce disruptions. If non-disruptive postings were
> blocked, that would seem like punishment.
> 
>> In the light of some of the disagreements we've seen over the
>> last month, I would also be a bit concerned about adding to
>> the burdens on the moderators to try to make decisions in
>> this case consistent with community consensus (rough or
>> otherwise).  The arrangement I think you are proposing might
>> also set Dan up for a fall if the moderators decided to
>> reject something he submitted for posting and he thought,
>> after consideration, that the posting was appropriate and the
>> decision inappropriate.
> 
> I would hope that someone subject to a PR-Action would do
> their best to keep their posts well within the lines, and if
> something approached but did not cross the line but was
> nonetheless held, I would hope that moderators (or the IESG)
> would quickly review and correct the decision.
> 
> Again, this does put some trust in moderators and the IESG to
> do the right thing, something I know others in this discussion
> do not trust them to do. But if we have lost that trust, we
> really have a different sort of problem than this one
> PR-Action.
> 
>> The
>> model I proposed would carry much the same risk, but would
>> encourage immediate IESG review and, if needed, decisive
>> action.
>> 
>> But, again, your suggestion and mine don't seem very different
>> in practice, especially if there are no further inappropriate
>> postings.
> 
> But your proposal would default to messages going through to
> everybody on the list and potentially causing disruption. If
> the behavior has in fact changed, there is very little
> difference between the outcomes. If the behavior has not
> changed, there is a big difference.

Borrowing from one of your comments above, I don't believe that
confidence and trust in the IESG and the various moderators is
as high as I would like it to be nor that the discussions of the
last month has improved that situation.  At last some
non-trivial number of us definitely have something of a trust
problem.  So, after hundreds of messages went through to the
list in the last month, IMO disrupting the ability of many of us
to get work done, I see the possibility of a few (very few)
problematic messages getting through, followed by  complete and
effective ban if needed, as a comparatively low price to pay for
considerably improved transparency.   That is clearly a tradeoff
and, of course. YMMD.

    john