Re: [Eligibility-discuss] RFC criterion [was ISE vs IETF Stream RFCs for Path 3]

John C Klensin <john-ietf@jck.com> Wed, 31 August 2022 18:40 UTC

Return-Path: <john-ietf@jck.com>
X-Original-To: eligibility-discuss@ietfa.amsl.com
Delivered-To: eligibility-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E1427C15AB6B for <eligibility-discuss@ietfa.amsl.com>; Wed, 31 Aug 2022 11:40:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.907
X-Spam-Level:
X-Spam-Status: No, score=-1.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 1f8Qsqp57mfW for <eligibility-discuss@ietfa.amsl.com>; Wed, 31 Aug 2022 11:40:46 -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 805EEC14EB1C for <eligibility-discuss@ietf.org>; Wed, 31 Aug 2022 11:40:46 -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 1oTSdo-0003qE-Qr; Wed, 31 Aug 2022 14:40:44 -0400
Date: Wed, 31 Aug 2022 14:40:39 -0400
From: John C Klensin <john-ietf@jck.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>
cc: eligibility-discuss@ietf.org
Message-ID: <21131E4C5D79995F32A369E4@PSB>
In-Reply-To: <22111.1661951409@localhost>
References: <CALaySJ+uvZME0bWQnB9tSvABxkjgsTG8xpfLT1g62bBL3QeG6w@mail.gmail.com> <2b7ada30-7919-fef4-6d8a-6bd85e1c5625@lear.ch> <edb6684b-a1cb-6e95-eac9-1f7e9fc9f0ad@gmail.com> <CABcZeBOJk-5ksk+mixU8Qm1gp1BDEd=0fgQ+hd9TcgACqa82ew@mail.gmail.com> <5012c5dc-e8c0-202c-0a28-6cf2f982b77d@lear.ch> <CABcZeBMe1wckz0edXyETTp2qAMKZ9QbZBGEoM8cMHahbUAk+1w@mail.gmail.com> <d25f4549-5976-6c1e-6356-e48ca8251f19@lear.ch> <31835.1661872935@localhost> <08d901d8bc90$eec4b150$cc4e13f0$@olddog.co.uk> <2347.1661883651@localhost> <08fc01d8bca0$cf92c000$6eb84000$@olddog.co.uk> <4613faf0-4c56-f3a2-de7b-035ec76f99c6@gmail.com> <19015280-a164-dd20-931d-8585b8526010@cs.tcd.ie> <20052.1661907094@localhost> <08F52ED9277D1F67E527014D@PSB> <22111.1661951409@localhost>
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/eligibility-discuss/VAO9y3O-UpXyENLTUKF1Qp5KUVM>
Subject: Re: [Eligibility-discuss] RFC criterion [was ISE vs IETF Stream RFCs for Path 3]
X-BeenThere: eligibility-discuss@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: IETF eligibility procedures <eligibility-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/eligibility-discuss>, <mailto:eligibility-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/eligibility-discuss/>
List-Post: <mailto:eligibility-discuss@ietf.org>
List-Help: <mailto:eligibility-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eligibility-discuss>, <mailto:eligibility-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Aug 2022 18:40:51 -0000


--On Wednesday, August 31, 2022 09:10 -0400 Michael Richardson
<mcr+ietf@sandelman.ca> wrote:

> 
> <NOHATS>
> 
> John C Klensin <john@jck.com> wrote:
>     > --On Tuesday, August 30, 2022 20:51 -0400 Michael
> Richardson     > <mcr+ietf@sandelman.ca> wrote:
> 
>     >> ...  I note that we don't have a lot of comments about
> Path 2!  ADs     >> could pad the list by appointing lots of
> secretaries.  Why aren't we     >> worried about that?
> 
>     > Because a few would not make much difference, most of
> them would (again     > and as you have pointed out) be picked
> up by other criteria, and, if a     > particular AD started
> appointing lots of secretaries who were not doing     > that
> job or participating in other ways, I assume the community
> would     > hold it against them, possibly to the point of
> starting recall     > proceedings but certainly at the "tell
> it to the Nomcom" level :-).
> 
> Do the the same considerations apply to WG chairs that add a
> lot contributors to documents?

I would think so.  Remembering that WG Chairs rarely change the
documents themselves and that, if one were to do so, the
author(s) would be notified at posting time, I'd expect any
author who was victimized in that way (i.e., not fully
complicit) to immediately complain to the WG and/or initiate a
formal appeal of the action.  Unless there were special
circumstances they were prepared to explain to the rest of the
IESG and/or the community, I would also expect the responsible
AD to either rapidly engage in some reeducation for the relevant
WG Chair or fire them.

So, again, I'm having trouble seeing a problem in this area that
is worth the energy that has gone into it already.

>...

best,
  john