Re: NomCom eligibility & IETF 107

"Salz, Rich" <rsalz@akamai.com> Sun, 15 March 2020 20:50 UTC

Return-Path: <rsalz@akamai.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 A02F53A1C13 for <ietf@ietfa.amsl.com>; Sun, 15 Mar 2020 13:50:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=akamai.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 cR-zi301bB0S for <ietf@ietfa.amsl.com>; Sun, 15 Mar 2020 13:50:38 -0700 (PDT)
Received: from mx0a-00190b01.pphosted.com (mx0a-00190b01.pphosted.com [IPv6:2620:100:9001:583::1]) (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 944EC3A1C16 for <ietf@ietf.org>; Sun, 15 Mar 2020 13:50:38 -0700 (PDT)
Received: from pps.filterd (m0050093.ppops.net [127.0.0.1]) by m0050093.ppops.net-00190b01. (8.16.0.42/8.16.0.42) with SMTP id 02FKmvjQ020370; Sun, 15 Mar 2020 20:50:33 GMT
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=from : to : subject : date : message-id : references : in-reply-to : content-type : content-id : content-transfer-encoding : mime-version; s=jan2016.eng; bh=cVeMChdgaOr89P2cSylpzfrXzLF5Yv73fiSEtpma+uo=; b=DRTEAsvnQy9VzL3o4NyIMIaH0ubT/19KNoEzN4JjJFzQFr5DeLsCHfyKB/PBPu/5ztof h02KuMj/93I+CN0cFlpb/Lx4KhE1qdH7idHCbHs3TpO/zUky31pV5vH0sy2mONDHUQ+1 I4HJg3K81MymyKZw4Q0uVQcNgsOKAOEveBiaf6NT02Y5GK59/WfQA93QqPabdyts1Fdb 5JtamKWTefuI9uNwOIEgMaqGO6q5L9glQ5N1OOQyktJuTJN2/ICxSMalz4cwwvdhNGbw WHlvXXbtMpMxDUSPl4QVrndAEk8NSCZAnt9UPeZdtrE4uKI/a9RLnwFozlGz2bC7zXKK Ug==
Received: from prod-mail-ppoint4 (prod-mail-ppoint4.akamai.com [96.6.114.87] (may be forged)) by m0050093.ppops.net-00190b01. with ESMTP id 2yrqdu60xd-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Sun, 15 Mar 2020 20:50:33 +0000
Received: from pps.filterd (prod-mail-ppoint4.akamai.com [127.0.0.1]) by prod-mail-ppoint4.akamai.com (8.16.0.27/8.16.0.27) with SMTP id 02FKlAoq015770; Sun, 15 Mar 2020 16:50:32 -0400
Received: from email.msg.corp.akamai.com ([172.27.123.32]) by prod-mail-ppoint4.akamai.com with ESMTP id 2yrtkw52jk-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Sun, 15 Mar 2020 16:50:32 -0400
Received: from USMA1EX-DAG1MB1.msg.corp.akamai.com (172.27.123.101) by usma1ex-dag1mb4.msg.corp.akamai.com (172.27.123.104) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Sun, 15 Mar 2020 16:50:31 -0400
Received: from USMA1EX-DAG1MB1.msg.corp.akamai.com ([172.27.123.101]) by usma1ex-dag1mb1.msg.corp.akamai.com ([172.27.123.101]) with mapi id 15.00.1497.006; Sun, 15 Mar 2020 16:50:31 -0400
From: "Salz, Rich" <rsalz@akamai.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Jim Fenton <fenton@bluepopcorn.net>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: NomCom eligibility & IETF 107
Thread-Topic: NomCom eligibility & IETF 107
Thread-Index: AQHV+T17YIte9GVOtUSJhAMBWIG3LKhKTuyAgAAEugD//9CYAA==
Date: Sun, 15 Mar 2020 20:50:30 +0000
Message-ID: <C74F3510-9A23-416F-81E1-5FF3C5B18A63@akamai.com>
References: <CALaySJ+kFVXrVAkYLaO6MaPqDA29MzXhVFcxG0c6hZcBs-LqnQ@mail.gmail.com> <81f4e6aa-6188-640a-5e7e-de4478feb02d@bluepopcorn.net> <c98f379c-7ca2-666d-5d8b-e8041c263526@gmail.com>
In-Reply-To: <c98f379c-7ca2-666d-5d8b-e8041c263526@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/16.35.20030802
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.19.114.27]
Content-Type: text/plain; charset="utf-8"
Content-ID: <1A7AFBED54564345A1FEFD0EDBD2C342@akamai.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.138, 18.0.572 definitions=2020-03-15_03:2020-03-12, 2020-03-15 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 mlxscore=0 mlxlogscore=801 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-2002250000 definitions=main-2003150114
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.138, 18.0.572 definitions=2020-03-15_03:2020-03-12, 2020-03-15 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 malwarescore=0 mlxscore=0 phishscore=0 clxscore=1011 impostorscore=0 priorityscore=1501 lowpriorityscore=0 suspectscore=0 bulkscore=0 adultscore=0 mlxlogscore=783 spamscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2003020000 definitions=main-2003150114
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/gDQMyE3fVfZ-0KGcEqVWlw_oSrU>
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: Sun, 15 Mar 2020 20:50:40 -0000

>    Unfortunately I have to disagree. We know for a fact that some companies
    have actively encouraged employees to volunteer for NomCom in the past.
    That's been happening over many years with a variety of companies. I fear
    this would happen even more with an even lower barrier.
  
What is wrong with actively encouraging NomCom volunteers?  Do you think they'll all vote the same?  What's not covered by the limit on same employer rules?

A random choice out of a self-selected pool will not give a random set of members.  It will give a random subset from that self-selected pool.