Re: [Last-Call] OT: change BCP 83 [Re: Last Call: BCP 83 PR-Action Against Dan Harkins]

Toerless Eckert <tte@cs.fau.de> Mon, 03 October 2022 22:06 UTC

Return-Path: <eckert@i4.informatik.uni-erlangen.de>
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 5B377C15258A for <last-call@ietfa.amsl.com>; Mon, 3 Oct 2022 15:06:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.96
X-Spam-Level:
X-Spam-Status: No, score=-3.96 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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 gs-A2kkQq10q for <last-call@ietfa.amsl.com>; Mon, 3 Oct 2022 15:06:29 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [131.188.34.40]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 10C11C1524DF for <last-call@ietf.org>; Mon, 3 Oct 2022 15:06:27 -0700 (PDT)
Received: from faui48e.informatik.uni-erlangen.de (faui48e.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:51]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTPS id 571065484B2; Tue, 4 Oct 2022 00:06:22 +0200 (CEST)
Received: by faui48e.informatik.uni-erlangen.de (Postfix, from userid 10463) id 45EF54EBC12; Tue, 4 Oct 2022 00:06:22 +0200 (CEST)
Date: Tue, 04 Oct 2022 00:06:22 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: last-call@ietf.org
Message-ID: <Yztc3qw/+lhxsZkW@faui48e.informatik.uni-erlangen.de>
References: <CFE25E25-D131-468E-9923-80350D6216F3@ietf.org> <3e0356f6-8288-2ab4-ef77-52bda4ad54cf@nostrum.com> <76f3ef5e-13d0-7b0d-2b94-8f3085e06344@lear.ch> <69cff9aa-9540-b369-06d6-5cee531852f0@nostrum.com> <ab216c77-47e6-cce0-1e40-2c455ecab601@lear.ch> <YzsyLdJZ1Erwb0Bb@faui48e.informatik.uni-erlangen.de> <3591bb36-5ca2-c493-40cd-8d9c799ed24e@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <3591bb36-5ca2-c493-40cd-8d9c799ed24e@gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/last-call/392hEUjvRwrMPJwBCwMvnbO1ltE>
Subject: Re: [Last-Call] OT: change BCP 83 [Re: 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: Mon, 03 Oct 2022 22:06:31 -0000

On Tue, Oct 04, 2022 at 09:00:26AM +1300, Brian E Carpenter wrote:
> > - There are references made to unreasonable behavior in private conversation, which we can not vet,
> That's true, and technically irrelevant anyway since the topic is inappropriate postings on specific lists.
> >    and drafts that have been completely removed, so we can not vet those either (now).
> 
> Consider yourself fortunate. Those of us who read them at the time were mainly glad to see them removed. But a point that I haven't seen made on list is that even if we construe those drafts as satire in the spirit of (e.g.) Jonathan Swift, such satire is mainly recognizable to people of English mother tongue and with a broad general education. They would appear simply offensive to IETF participants who know English mainly as a language for technical, engineering and scientific work. So whatever the intention of those drafts, they definitely had a negative impact on our community as a whole.

After a friendly person gave me access to the drafts and i first understood
how they relate to the PR at all, that input just reconfirms to me that the BCP 83 public
feedback step is not very useful unless you are privileged to a lot more in-the-know and
have some reason to spend a lot more time on it than most of us would or should. 

> If you think the BCP83 process has that defect, see the above Subject header.

A key defect is exactly that it encourages to utter opinions with too little detail
of the situation.  It may be useful to ask the community to provide additional evidence for or
against the case, but without having a real detailled rundown of the evidence and how the
people responsible for judging are evaluating it, i don't think we should let the public
chime in with judging opinions. This judging is just exactly incurring all the problems we did
try to avoid with the NomCom process. Of course, BCP 83 does not exactly detail 
"discussion by the community", but the practice we see here on the list is exactly that
of judgments.

> As far as I can tell, the IESG has followed the current process correctly.

Sure, but BCP 83 is too unspecific as to how detailled the rundown of the evidence and
decision making process has to be, and whether or not or how judgements by the community
should be taken into account, etc. pp. 

> > IMHO all that makes those process steps overall more hurtfull to the reputation of the IETF than helpfull,
> 
> I don't agree. I think it's better to have the debate on the record than behind closed doors.

Unless someone files a BCP 83 notion against us (community), we would be having a
public debate about the issue whatever BCP 83 says, and that is fine. The debate
does not have to be part of BCP 83, and uneducated input shouldn't be counted for
judgements in a BCP 83 case. 

Cheers
    Toerless

> Regards,
>    Brian

-- 
---
tte@cs.fau.de