IETF Logo Mail Archive

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

Joseph Touch <touch@strayalpha.com> Sat, 11 July 2020 02:55 UTC

Return-Path: <touch@strayalpha.com>
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 84D863A0C45 for <ietf@ietfa.amsl.com>; Fri, 10 Jul 2020 19:55:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.319
X-Spam-Level:
X-Spam-Status: No, score=-1.319 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, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=strayalpha.com
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 Oxp7qmNfm14g for <ietf@ietfa.amsl.com>; Fri, 10 Jul 2020 19:55:45 -0700 (PDT)
Received: from server217-4.web-hosting.com (server217-4.web-hosting.com [198.54.116.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7F8813A0CE2 for <ietf@ietf.org>; Fri, 10 Jul 2020 19:55:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=strayalpha.com; s=default; h=To:References:Message-Id: Content-Transfer-Encoding:Cc:Date:In-Reply-To:From:Subject:Mime-Version: Content-Type:Sender:Reply-To:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=v4x6rEmdNQfV77EmBjPewIvUq+K6PirA9mt27eUUC+s=; b=0+dGMCZ0Qf6UEro7P08g/zRcF lBmOvzTEvwRUCjbuNwBDF83ZJFKwl9su8Jpdr8hAhlarVW8TiYq6oY+17R0+2YHyearch44BHq7kr 6cuoidsQ4IVYTxCoHRNkLRRNEJSXevZVZ5TnxSJW3CfxmJMACW3yrAXRaMPTvLuHBYcexOd3OYtBQ VcW2SNKkP0Yfg48ouOG4oLnh5axn2pD+PKVTKMaI6iNrYkt7cGel0pZE5q6J8hm/VOoFQN46jnPzW 6xMn+9PUtdBB/TysGRSeXyqBA1nPFqZpzfVN6+PllItbk/rjgAkMcfFPAOuDymvTWf5Go5dUFP4ZW 2TeE7KeVw==;
Received: from cpe-172-250-225-198.socal.res.rr.com ([172.250.225.198]:62973 helo=[192.168.1.14]) by server217.web-hosting.com with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.93) (envelope-from <touch@strayalpha.com>) id 1ju5ft-004DZV-4G; Fri, 10 Jul 2020 22:55:41 -0400
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
Subject: Re: Challenge: was Re: Updated Nomcom 2020-2021: Result of random selection process
From: Joseph Touch <touch@strayalpha.com>
In-Reply-To: <20200711011915.GE49328@faui48f.informatik.uni-erlangen.de>
Date: Fri, 10 Jul 2020 19:55:36 -0700
Cc: "Salz, Rich" <rsalz=40akamai.com@dmarc.ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <30972D6C-F7EC-4228-A736-2489CE04530B@strayalpha.com>
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>
To: Toerless Eckert <tte@cs.fau.de>
X-Mailer: Apple Mail (2.3608.80.23.2.2)
X-OutGoing-Spam-Status: No, score=-1.0
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server217.web-hosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - strayalpha.com
X-Get-Message-Sender-Via: server217.web-hosting.com: authenticated_id: touch@strayalpha.com
X-Authenticated-Sender: server217.web-hosting.com: touch@strayalpha.com
X-Source:
X-Source-Args:
X-Source-Dir:
X-From-Rewrite: unmodified, already matched
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/luR7Hy5AfWZVwTAE8Gh-Wyf1tks>
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 02:55:47 -0000


> On Jul 10, 2020, at 6:19 PM, Toerless Eckert <tte@cs.fau.de> wrote:
> 
> On Fri, Jul 10, 2020 at 05:44:34PM -0700, Joseph Touch wrote:
>> 
>> 
>>> On Jul 10, 2020, at 5:28 PM, Toerless Eckert <tte@cs.fau.de> wrote:
>>> 
>>> I think Mike did a good job in confusing the facts, and maybe the
>>> explanations from NomCom
>> 
>> IMO, Mike is correct.
>> 
>> I think the intent here is simple: there aren???t Huawei slots; when someone from a given company steps out, that doesn???t mean someone from that company steps in.
> 
> Of course not, but: 
> On which planet did this happen ?
> How do you come to interpret what happened in that way ?
> Luigi declined to serve. Thats all.
> 
> 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.

>> 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

v2.23.0 | Report a Bug | By Email