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

Pete Resnick <resnick@episteme.net> Fri, 28 October 2022 15:21 UTC

Return-Path: <resnick@episteme.net>
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 02756C14F749; Fri, 28 Oct 2022 08:21:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.107
X-Spam-Level:
X-Spam-Status: No, score=-2.107 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, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=episteme.net
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 7_QDJqEpKvNy; Fri, 28 Oct 2022 08:21:28 -0700 (PDT)
Received: from helm.helm.episteme.net (helm.helm.episteme.net [209.51.32.195]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 87568C14CE30; Fri, 28 Oct 2022 08:21:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=episteme.net; s=mail; t=1666970487; bh=Ai/gS6bWO2wfz2v8rDaBYqCo6/OPHJ24WTtpFNcMgwI=; h=From:To:Cc:Subject:Date:In-Reply-To:References; b=Dc7kdE3u7rFHy98hE9tSsG/ycitTjNN1fwHF2rE+4QpWL/FbU4FG68M7s1BJBQALs QWg8iRPZmhzo9qXBc+jJLzf3LF+thvl9UfUbAPdTeDUuqSqErHU5EgsZXkI+fp2qbT NJuUVzz1razIa0r1oYaFALbKhZq8ZYL1tyOqwEJw=
From: Pete Resnick <resnick@episteme.net>
To: John C Klensin <john-ietf@jck.com>
Cc: Ted Lemon <mellon@fugue.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>, last-call@ietf.org, IETF Chair <chair@ietf.org>
Date: Fri, 28 Oct 2022 10:21:25 -0500
X-Mailer: MailMate (1.14r5923)
Message-ID: <A5F3BB1B-EE56-477F-B2AB-F239FD5175FC@episteme.net>
In-Reply-To: <5EE93148C706EEA966757077@PSB>
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>
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/last-call/C8GhkuVmwmJnCZi__GIMnoX0y1I>
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 15:21:33 -0000

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.

pr
-- 
Pete Resnick https://www.episteme.net/
All connections to the world are tenuous at best