Re: Challenge: was Re: Updated Nomcom 2020-2021: Result of random selection process

Toerless Eckert <tte@cs.fau.de> Sat, 11 July 2020 03:28 UTC

Return-Path: <eckert@i4.informatik.uni-erlangen.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 29D923A0D27 for <ietf@ietfa.amsl.com>; Fri, 10 Jul 2020 20:28:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.65
X-Spam-Level:
X-Spam-Status: No, score=-1.65 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 dPFN72vhIOst for <ietf@ietfa.amsl.com>; Fri, 10 Jul 2020 20:28:38 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [131.188.34.40]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 459D83A0D29 for <ietf@ietf.org>; Fri, 10 Jul 2020 20:28:37 -0700 (PDT)
Received: from faui48f.informatik.uni-erlangen.de (faui48f.informatik.uni-erlangen.de [131.188.34.52]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id EDBC3548011; Sat, 11 Jul 2020 05:28:32 +0200 (CEST)
Received: by faui48f.informatik.uni-erlangen.de (Postfix, from userid 10463) id E6B57440043; Sat, 11 Jul 2020 05:28:32 +0200 (CEST)
Date: Sat, 11 Jul 2020 05:28:32 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: Joseph Touch <touch@strayalpha.com>
Cc: "Salz, Rich" <rsalz=40akamai.com@dmarc.ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Challenge: was Re: Updated Nomcom 2020-2021: Result of random selection process
Message-ID: <20200711032832.GG49328@faui48f.informatik.uni-erlangen.de>
References: <159422819660.27889.6475902734358747001@ietfa.amsl.com> <b4f5a3cf-5fab-8188-926a-a4100f776610@comcast.net> <1112046E-04ED-4DB1-8766-4928AC5D15F5@akamai.com> <20200711002800.GC49328@faui48f.informatik.uni-erlangen.de> <17D66D97-9F29-470C-83CA-53C48F49D323@strayalpha.com> <20200711011915.GE49328@faui48f.informatik.uni-erlangen.de> <30972D6C-F7EC-4228-A736-2489CE04530B@strayalpha.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <30972D6C-F7EC-4228-A736-2489CE04530B@strayalpha.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/au5JDu7N2sDY1ARu3ssoGNrhspU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Jul 2020 03:28:40 -0000

On Fri, Jul 10, 2020 at 07:55:36PM -0700, Joseph Touch wrote:
> > What am i overlooking here ?
> 
> Luigi???s new affiliation disqualifies Tai.
> 
> If Luigi wants to step out, that???s his decision - but he doesn???t get to then control the fact that Tai gets put back in. That???s the ???but there is now a Huawei slot??? issue - so, to answer your first question, planet Earth.

   If a selected volunteer, upon reading the announcement with the list
   of selected volunteers, finds that two or more other volunteers have
   the same affiliation, then the volunteer should notify the Chair who
   will determine the appropriate action

I don't see any further constraints than letting it be up to the NomCom
chair to decide what appropriate action is.

Given how Luigi could have simply said "i withdraw from serving", an
interpretation like the one Michael and you are alluding to would just
create an incentive in similar future case for volunteers to not be fully
forthcoming as to their motivation to withdraw so as not to punish
 colleagues in a new employer they just joined. Thats quite silly. 

If i compare the silly EvilEmpire theories invented in support of the
argument vs. the simple rule that its NomCom chairs decision as i think
also the RFC says is IMHO the much more logical conclusion. And given
how the existing 2-only rule is already discrimination, its also a lot
more logical for the NomCom chair to be acting without paranoia.

But this is not how it ends. Now the demand is not to actually remove
only person (Luigi) who was forthcoming, trying to be a good IETF'er,
but also a second person (Tal). If you are getting enough support to
misread 7437, then at least acknowledge that in hindsight and
misunderstanding the rules like you propose to, Luigi and i think
NomCom chair as well would have simply concluded to keep Luigi and drop Tal
instead of dropping both of them.

Cheers
    Toerless

> > 
> 
> >> The right thing is to re-run the process and see what the result is.
> > 
> > rfc3797  section 5.1, paragraph 3.
> 
> Mike already spoke to this point.
> 
> >> Otherwise, as is being seen, one person can ???game??? who is on the committee. That???s exactly what the detailed automated process is intended to prevent.
> > 
> > And if 99% of NomCom qualified people are from one company,
> > we can't build a NomCom. Please do not use ridiculous theories
> > to justify changes in process or mishandling of the existing
> > rules.
> 
> Conflict of interest is based on whatever anyone (including me) thinks COULD be a motivation.
> 
> That concept is no more ridiculous than the automated system that???s been created to go out of our way to avoid it.
> 
> Joe

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