Re: [Eligibility-discuss] Fwd: The "eligibility" list, and a virtual meeting

John C Klensin <john-ietf@jck.com> Wed, 18 September 2019 19:08 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 D68641200E6 for <eligibility-discuss@ietfa.amsl.com>; Wed, 18 Sep 2019 12:08:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 zUzPXH2iyd1J for <eligibility-discuss@ietfa.amsl.com>; Wed, 18 Sep 2019 12:08:39 -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 BD496120128 for <eligibility-discuss@ietf.org>; Wed, 18 Sep 2019 12:08:39 -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 1iAfJc-00059i-PH; Wed, 18 Sep 2019 15:08:36 -0400
Date: Wed, 18 Sep 2019 15:08:30 -0400
From: John C Klensin <john-ietf@jck.com>
To: Eric Rescorla <ekr@rtfm.com>
cc: Barry Leiba <barryleiba@computer.org>, eligibility-discuss@ietf.org
Message-ID: <3DCA5969B3017F3DC1D50FB2@PSB>
In-Reply-To: <CABcZeBNmT2ONMacUiVsjUuR=cHz=fAog3ojNuhrD7P0eqQbOSQ@mail.gmail.com>
References: <CALaySJ+BEoDd5aas9VfAmfcF+H_54w4ETNafVwFAObhY_A2v-Q@mail.gmail.com> <C90E6D6D-D058-40A5-AA3B-2D2002077016@episteme.net> <CALaySJJggQqYhVHSdKCx4BvpiR31oodx9C9NkzfMoFGbUv+gmg@mail.gmail.com> <939D2A7C64A58595AD2B9CBD@PSB> <CABcZeBNxVgJE=jv7+Zf6RjkG3r-+00zuMQ=2mtESrP4skkPgzQ@mail.gmail.com> <4A244E1EFA8D1821D2D49ABD@PSB> <CABcZeBNmT2ONMacUiVsjUuR=cHz=fAog3ojNuhrD7P0eqQbOSQ@mail.gmail.com>
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/Z9Ge8DMAJOyQv6K_5x1C8rnhI70>
Subject: Re: [Eligibility-discuss] Fwd: The "eligibility" list, and a virtual meeting
X-BeenThere: eligibility-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <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, 18 Sep 2019 19:08:43 -0000


--On Wednesday, September 18, 2019 10:50 -0700 Eric Rescorla
<ekr@rtfm.com> wrote:

> On Wed, Sep 18, 2019 at 10:24 AM John C Klensin
> <john-ietf@jck.com> wrote: . Recalls are the
> 
>> community's only socially-acceptable way of removing someone
>> who has exhibited a consistent pattern of unacceptably bad
>> behavior, whether it is demonstrated through particular
>> decisions or not.
> 
> This seems like a rather odd claim, given that we have any
> number of worked examples of people being successfully removed
> by the ordinary nomcom process.

I should have said "removing someone before the next nomcom
cycle".  Sorry.  I'm busy and have been told to use fewer words,
so I thought that would be clear.  Of course, given how slow and
painful the recall process is, one could argue that one doesn't
need it at all but should simply wait for the next nomcom.  I
believe that is any argument you'd made in suggesting that the
IAB and/or IESG should be able to remove their own members for
non-performance.  Or if may be an argument that the recall
process needs far more radical modification than Barry's list of
issues would suggest.  

Of course, whether there is any sort of out-of-line behavior
(with the possible exception of disappearing completely) severe
enough to justify removal rather than just waiting for the next
relevant nomcom to do its work.  I believe the answer is "yes".
That is certainly debatable but, if that is what we are really
discussing, let's be explicit about it.

best,
   john