Re: NomCom 2020 Announcement of Selections

"Joel M. Halpern" <jmh@joelhalpern.com> Sat, 23 January 2021 21:11 UTC

Return-Path: <jmh@joelhalpern.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 0671A3A09E1 for <ietf@ietfa.amsl.com>; Sat, 23 Jan 2021 13:11:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.381
X-Spam-Level:
X-Spam-Status: No, score=-2.381 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, NICE_REPLY_A=-0.262, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.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 ig2yNzCVQAoJ for <ietf@ietfa.amsl.com>; Sat, 23 Jan 2021 13:11:52 -0800 (PST)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) (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 B737E3A09E0 for <ietf@ietf.org>; Sat, 23 Jan 2021 13:11:52 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 4DNTMr3zCnz1p0DV for <ietf@ietf.org>; Sat, 23 Jan 2021 13:11:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1611436312; bh=B+1H3eFI0oik1+UB8vj+9FTcdjN2qztBKmJWAlamsKY=; h=Subject:To:References:From:Date:In-Reply-To:From; b=iY6bQla/A2/YFQMEzZZGv0FdjzFxt3Ml5iSPs9U3Z8ybMZUGLlJ9llrO+X4dNObg6 5fIVYI8+iJPmYIdv6QhT5tcgQKXvVxXUSl2rQtTl2PdvLLWNk5dn/BVzKJPlMmlWiQ XPT53KW6XVT4PlcI0lW+ngHutsXU9U1NTJBlNJZc=
X-Quarantine-ID: <s17bOjfzkYps>
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from [192.168.128.43] (unknown [50.225.209.66]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 4DNTMr0tHZz1ntnr for <ietf@ietf.org>; Sat, 23 Jan 2021 13:11:52 -0800 (PST)
Subject: Re: NomCom 2020 Announcement of Selections
To: IETF discussion list <ietf@ietf.org>
References: <289B641E-F445-407F-9A7D-FCDEA9698F7C@akamai.com> <437bfe25-185c-4637-ae9a-59a6ccaade99@dogfood.fastmail.com> <BA07FAFAE7BBE5C47BCB7F58@PSB> <d9d77478-7b4f-4f04-98fa-4e3b99b78055@dogfood.fastmail.com> <f5d550e2-57e1-a682-53c4-d338086e7f32@pi.nu> <CANMZLAZTOAfSkcTx8K=zfmM+YeUkiG3Ty99cbkoOygAQg16vcg@mail.gmail.com> <90393DA88B7884E3384D5F8E@PSB> <c64b2307-c252-41e4-9ebf-a7cfede58c6e@dogfood.fastmail.com> <8BC130D5-E424-43AA-B756-47D95A1A7ED0@akamai.com> <1FB3EB72CF9C88B06B34F7BE@PSB>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <b964a346-3862-ee4d-8b84-268170613e5a@joelhalpern.com>
Date: Sat, 23 Jan 2021 16:11:51 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.6.1
MIME-Version: 1.0
In-Reply-To: <1FB3EB72CF9C88B06B34F7BE@PSB>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/4GRpDt_0SmY15oYhIvHVNfRKjmk>
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, 23 Jan 2021 21:11:54 -0000

One small aspect of this conversation struck me as needing 
clarification.  there is repeated reference to re-appointing incumbents.

In my view, and I think this is also the view the community has 
expressed, there are significant differences among reappointing 
incumbents who have served 1 term, 2 terms, and three or more terms. 
While sometimes frustrating, I do understand and generally support the 
bias in favor of reappointing incumbents who have done a competent job 
and only served on term.  In contrast, at best it indicates community 
problems when we are reappointing incumbents who have already served 
three terms.

Yours,
Joel

On 1/23/2021 1:31 PM, John C Klensin wrote:
> 
> 
> --On Saturday, January 23, 2021 14:48 +0000 "Salz, Rich"
> <rsalz@akamai.com> wrote:
> 
>>
>>
>>    *   And - if the problem is that the nomcom selected without
>> sufficient weight given to diversity, then considering a
>> selection that would have made Rich appointed (that's the
>> opposite of disappointed, right?) with the result is a
>> reasonable request in response to Rich's stated disappointment.
>>
>> I assume you're making a joke about "the opposite". But
>> to be clear, if Nomcom picked me instead of Carl, the end
>> result would have been the same, of course, and I would still
>> be disappointed. One mitigating factor is that my
>> questionnaire was public and I tried to show how diversity is
>> an ongoing moral concern for me and people could bring it up
>> if I did not follow through.  It's possible that all other
>> IETF Chair candidates feel the same, of course, and I'm not
>> saying they don't, just that we don't know.
>>
>> If I were picked, however, I'd be unlikely to say anything
>> because I have to work closely with the rest of the slate, and
>> starting off by saying "I'm disappointed this is who we
>> have" would be stupid, for hopefully obvious reasons.
> 
> Indeed.  But that is almost equally true if you expect to
> continue to work in the IETF (which I hope and assume you will)
> if you posted your preferred slate with the implication that you
> think your candidates would be better choices --on a one by one
> basis -- than those selected.  In addition, I think we are
> better off moving forward to improve on things for the future
> rather than poking at the details of what might have been.   See
> below.
> 
>>    *   Throwing our hands up and saying "it involves people, we
>> can't talk about it" is way problematic if we intend to do
>> more than wring our hands and cast generic aspersions of
>> systemic sexism and racism at the IETF.
> 
> I hope nothing I said sounded to you like your quotation above.
> At the risk of casting a different soft of vague aspersions, too
> much decision-making over the years (inside and outside the
> IETF) has been contaminated by personal resentments and
> animosities.  Avoiding doing things that might encourage more of
> them seems like a reasonable precaution.
> 
>> We can talk about it without commenting on specific people.
> 
> Exactly and that is the core of what I was suggesting.  The idea
> of opening comments to the next Nomcom now was only intended as
> a supplement for those who really did feel a need to comment on
> individuals.
> 
>> For example, having a very finely-tuned random number
>> generator used to pick volunteers from a self-selected pool
>> doesn't change the fact that every picked volunteer will be
>> self-selected. Having jobs that most people think require four
>> years to be able to do correctly, means that people are
>> unlikely to volunteer if they see an incumbent's name on the
>> list.
> 
> Right.  And having job descriptions that can be satisfied only
> by those who either (i) work for large organizations that are
> willing to give up most of their time for that period while
> supplying salary, travel, and other support or (ii) who has
> independent means they are willing and able to dedicate that way
> also rather significantly affects who is willing to volunteer...
> and the diversity of the volunteers.
> 
>     john
> 
>