Re: List of volunteers for the 2021-2022 NomCom

tom petch <daedulus@btconnect.com> Tue, 29 June 2021 08:30 UTC

Return-Path: <daedulus@btconnect.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 766193A2B1F for <ietf@ietfa.amsl.com>; Tue, 29 Jun 2021 01:30:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.239
X-Spam-Level:
X-Spam-Status: No, score=-2.239 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, MSGID_FROM_MTA_HEADER=0.001, NICE_REPLY_A=-0.338, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=btconnect.onmicrosoft.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 RIzk4lcM3E9I for <ietf@ietfa.amsl.com>; Tue, 29 Jun 2021 01:30:29 -0700 (PDT)
Received: from EUR04-HE1-obe.outbound.protection.outlook.com (mail-eopbgr70122.outbound.protection.outlook.com [40.107.7.122]) (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 50CA43A2B1D for <ietf@ietf.org>; Tue, 29 Jun 2021 01:30:28 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=hfKzHotPYZXIoHf4HZB8fT4vkNA23dhtMU+OQftcFiajAIRWAGqHrDsoZL1ZmDVYuQaWwZlNtWFU6o50FAChFPLwpETe5ly/rbSH9Po/UKgaAvc/SIyXiu1CyaK4lny+Rh6vm42iW3n2lDm3/zJxVqclf3x8abX4bpz24mQbvU1BKCUiZ+sWeh2X/ubVCXNnZWpaz7OJab9r3ycDiIiGOEB6o72Cakn3kOtAkga6zalZgVTqwlc6mHkULF0JmMBmhsAI/qmQ/0Yl3a5pE7is5a6f/FpurA+zlRqtTUqeHDmDQLLqWBgLmnFIhiolcBGMds7XaS4NpR6RlAHzOIk6cg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=ryksZ0Oo6VnVhOznPloACoygMIMXLLCKWmUy8fCt//E=; b=cj7lMpqriQ3cEW9cM6ibFSQLW8gwumZ1Nx7Sa7wOk9xli/iH40lrNkw6EubELaOm1IbkQre88nkkrQ0r3oJSYrdQBr799cRCMd/3qOaceuG6rWfeJbYPdbf9oi6j/dLsxiHReJNoQfbr9JLc1vsjwUcuBNMFdHljM7r6/Uj+tUvxDUOVhCupwGaigmuBvncbwmy6jgRJrCNQAKjjNnI9jVlMeZ6Fi8FvtMijKtq0t5isb+fxMz47USz0gKDreAvOl2jhF4d1TGt8j5MHXkiWsXi+xpxQJKgqBceGGH+HgDWbk+vgLwDNMm+50lmnoFc2ULb6z7Msq9R0W5HdIlyuFQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=btconnect.com; dmarc=pass action=none header.from=btconnect.com; dkim=pass header.d=btconnect.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btconnect.onmicrosoft.com; s=selector2-btconnect-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=ryksZ0Oo6VnVhOznPloACoygMIMXLLCKWmUy8fCt//E=; b=H0+hvVuuIbEEnGJWB0olc8qVoti9S4bCwmX5LSCaBoSIQhpzPrRm4XPkjlK6bTpBfK0OWzDSLBiBp0NvZD2kFuRQi6kx9kl+aMJx76r/JcP1LohbycfvIkRLlFnE+62DH8BAX6Ckl3Kja5T3RwPvo/2/JCbwx8LD2k9ae+hy1gM=
Authentication-Results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=btconnect.com;
Received: from VI1PR07MB6704.eurprd07.prod.outlook.com (2603:10a6:800:18b::8) by VI1PR07MB6559.eurprd07.prod.outlook.com (2603:10a6:800:18b::9) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4287.21; Tue, 29 Jun 2021 08:30:26 +0000
Received: from VI1PR07MB6704.eurprd07.prod.outlook.com ([fe80::10f5:d159:cfea:1b95]) by VI1PR07MB6704.eurprd07.prod.outlook.com ([fe80::10f5:d159:cfea:1b95%3]) with mapi id 15.20.4287.022; Tue, 29 Jun 2021 08:30:26 +0000
Subject: Re: List of volunteers for the 2021-2022 NomCom
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, "STARK, BARBARA H" <bs7652@att.com>, ietf@ietf.org
References: <c2148075-606d-8aa9-d7b4-71aa92a09fae@comcast.net> <1E2C4254-FE64-4862-8650-D5BA8A8CF86D@gmail.com> <3975.1624807060@localhost> <CAP8yD=tKs6jeMs-ZGUYoAWJqTAWTx5EzciEwsZGUrV9v8MFX4A@mail.gmail.com> <LO2P265MB0399544A2F5CC973B22CB9CBC2049@LO2P265MB0399.GBRP265.PROD.OUTLOOK.COM> <71ca761b-5987-3c5e-83f2-20a661e6a14f@joelhalpern.com> <22399.1624829128@localhost> <ccacbe24-cdd5-1707-03cb-a2e09ae801a9@comcast.net> <CABmDk8nvDD9tM-ybaw+fZcEHZ14S84f9MFaT8vrTrtX+EgEXbQ@mail.gmail.com> <18f319d8-01d9-efb3-c576-aace73d88f76@comcast.net> <CABmDk8kCnz=5ZZyXO21pc9PX1mdgcC58D3JOWqOZj9PauhzWWg@mail.gmail.com> <PAXPR07MB799920E3F2E0D3E9689DC67592039@PAXPR07MB7999.eurprd07.prod.outlook.com> <DM6PR02MB6924D54491A71231C0FABB24C3039@DM6PR02MB6924.namprd02.prod.outlook.com> <86844c81-140c-893a-01fc-f80acb5a763e@gmail.com>
From: tom petch <daedulus@btconnect.com>
Message-ID: <60DADA19.4010403@btconnect.com>
Date: Tue, 29 Jun 2021 09:30:17 +0100
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:38.0) Gecko/20100101 Thunderbird/38.5.0
In-Reply-To: <86844c81-140c-893a-01fc-f80acb5a763e@gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
X-ClientProxiedBy: LO4P123CA0303.GBRP123.PROD.OUTLOOK.COM (2603:10a6:600:196::20) To VI1PR07MB6704.eurprd07.prod.outlook.com (2603:10a6:800:18b::8)
MIME-Version: 1.0
X-MS-Exchange-MessageSentRepresentingType: 1
Received: from [192.168.1.65] (86.143.250.86) by LO4P123CA0303.GBRP123.PROD.OUTLOOK.COM (2603:10a6:600:196::20) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.20.4264.18 via Frontend Transport; Tue, 29 Jun 2021 08:30:25 +0000
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: 49008972-b8d7-4062-da20-08d93ad824cd
X-MS-TrafficTypeDiagnostic: VI1PR07MB6559:
X-Microsoft-Antispam-PRVS: <VI1PR07MB65596F1F7C3B55F02ED10FBEC6029@VI1PR07MB6559.eurprd07.prod.outlook.com>
X-MS-Oob-TLC-OOBClassifiers: OLM:10000;
X-MS-Exchange-SenderADCheck: 1
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info: jDUEZV1OSrAZbb2BwMigxLWsIaWYRSW6xsRtAA9pyW8Mjmtcp+IgqLdnXRNzDGoCwm4oHIG3Ok68fJaRjsye8bsDigYmM0rna8cJTIqRI2OdikpofvzzpSWFjaOhvZkeuim3KSAoJhVmmgap/7WghV5tduYu4vwiuH+Tl3YXt7wntzgPO1bA0AdL2UemwwCZ8fMzj6s+SMYKzqwoXACmvXWKlpd40HKBiyn7cLxzqR15oG1QIOQSb2dBnrZDY92i5wuWfXXoT8vHAxprKyFK6NKM5au1KZIdrn0D8sF/pP247vi1VRNnfDP3yKMh11sLUWQdnAiEtRZSH1JGVDv3ah0tm9mDvUfk9DbnS+7B49qSxWUc1EaUEtSc8Mq2yYsuS7FZA9pYVXD8UArcrlqxBKUxgZsrPnUsokfIWwI6FUjh13j53MDaSeAr1U3ZcDx2/pxwVjxRfjunASy4mqQRrjIToXavD02Pwb0fApC+YA94ZNdTR81VBFEeHClQXUo8DAIaGkUeQrSoitx4LBJS6PQSo2dDNaCkT5DdEAP24zCQGQlO0T7dNtRTYGDB4IMg8Y5CWg0w4w4sf61FhOt+uPCoGEpbZeNW2NNdrcPVCENipcT4r49i2VmJ0zlBIJR63+oEeYtLT7I6a8q6BrcmEPqGHuA6n+cA2IY4KesI3HesMr4c1MT5yRVwRE5qxygjRa9kb5gTc4UEKjbWS2OA2g==
X-Forefront-Antispam-Report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:VI1PR07MB6704.eurprd07.prod.outlook.com; PTR:; CAT:NONE; SFS:(346002)(396003)(366004)(136003)(376002)(39860400002)(6486002)(87266011)(956004)(2616005)(8936002)(2906002)(52116002)(66574015)(186003)(8676002)(16576012)(36756003)(478600001)(316002)(6666004)(83380400001)(66476007)(38100700002)(33656002)(38350700002)(110136005)(66946007)(86362001)(26005)(66556008)(53546011)(5660300002); DIR:OUT; SFP:1102;
X-MS-Exchange-AntiSpam-MessageData-ChunkCount: 1
X-MS-Exchange-AntiSpam-MessageData-0: 9Ok8rhg3v24WbbbyTtyta+b82tuhs1BNgp0mCtkhjzIe5yPUNey6XR5t1CDDJs34QPYGk3387EV8mY/ReORI6QeFjD4MBu7//zh6nn0In5jMVfreDuJuZ1YKHfMFrfaPO1iOZaIwsoaIDlm1Tl3kdzYDB7pZWn8NgcgEvbtwqKu4wmUbwdbXdFiQWnOvNvekI0+0ILGrkir8F43Xuj5wYHJHKkiqEbYBeCc8yE91PjVjiSVndzM6myBKeOXjFdpU0D+SY12OxNGHrN9bu6u2CuerP9saTy9GnRm9ofLUbhycoiI0n8NnvmAUcGQBFEb3rMd5w6bCFi7wjWlDD36tmjrGj+DZmepIAHZULSth0XpjHd/uZ1501QWE8He+4Tg86tL4CaFLowIPftHDy9wbMgRvJwNvJFbYJVwvxGKQxtWq76txFiY5KF19Y2YKdBh+ta8gbzRYOrCCSOtw6ZBEb4YW3Jijj5PSSg2tKYF0ehnLc0OfENxVHh51pt/ZbrmTxuO3+nnPsUSduIpCN4MYajZjJavHCzRiBnqRktWVSmu4cwuCxki07Au51t8A1L2eXMFCmNsskJV9OyRT1lsnLJ1i7k2LaPPE5L3Qyhqy8UGpZztG8AQnG4z7qfhWtzCzjIgpMp+1s5eVQNl9utXMiUHflF/KSKe6XE6L9MtYz3nikrmVy22eH4ydnpZ2ci9O/NL0mHWb+MnocLWx8O6URvwvITU+wotoOomQXQDKWT9a3hLEz+/EMComRoYptffQiFtnT6R6SlnoIqOhplioSLIkVuP6IyzQ8hQHHXKwCBW3rjU5XVkPpQwoYdzWKkjMvjBGqyWlVHIGqKsiynyG2/92WbMFlRnY1sMHGhMNUp8yXbGGY5gIPIRJ3KFFfv/UZ3uQlRySbrQegRb53vCNG1JSFEe36kkYzXSvvdOUFuooBdX3GdhrK7Rsa5HKR1xie5MQmdiNBb4yqQN0SIMKCQmGXeANpoc8H9dgb/lMpJWENpGx6QxKNTg/E3ogiRVg84Jyw6LFKqeJjBY06qxWeEFtb9t9PFEqnuISbGG3PGHFpf4ujTntYZrf4KVNjumS9/GDzZC8WGxlAMs/WUy7eS/GOsfHAyXAOu7cuA9hVaWVzP2ANXXbqOQ75+LrNDqTIvnUY16BJgBd7hsPIjRf128jGN+MCooO02wdVGV629YgmoSdFfI3lUM+Br77evwNBMQlbPiW3bgm1ruo104c4ol1YQERwUoIu4YnFAslhgt8v21yNNFnKJptl74s4HoFFamlHUqWCoKBMKhsDjiHtqhh3FU4qipl5pGEMfWrGY5iEgHB/dPU8gjN/OAayNtS
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 49008972-b8d7-4062-da20-08d93ad824cd
X-MS-Exchange-CrossTenant-AuthSource: VI1PR07MB6704.eurprd07.prod.outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 29 Jun 2021 08:30:26.3852 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: cf8853ed-96e5-465b-9185-806bfe185e30
X-MS-Exchange-CrossTenant-MailboxType: HOSTED
X-MS-Exchange-CrossTenant-UserPrincipalName: M5GPHOT9peFBeupAsafJifYH+yq0EQBmdQLjDiCaj5KFq3vJlKYhVBUxcuPUTi7F0ahW/l424VZMXjBoVWsXQg==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR07MB6559
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/SWMztx82AYKB65zXz1E2G0w896Y>
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: Tue, 29 Jun 2021 08:30:32 -0000

On 28/06/2021 23:09, Brian E Carpenter wrote:
> Thanks for the data. Comments in line:
>
> On 29-Jun-21 04:48, STARK, BARBARA H wrote:
>> I believe the registration checkbox is probably the most relevant difference. I’ve gone through some of my records from last year. Note these are from personal records and these statistics are not formal, not approved by the 2020 NomCom, and not subject to anyone else’s validation. But since they don’t provide personal info, and I think this may be useful, I’m supplying these statistics.
>>
>>
>>
>> NomCom 2020
>>
>> Qualified people who volunteered by email: 74
>>
>> Qualified people who volunteered by IETF 108 registration (and not by email): 61
>>
>> Qualified people who volunteered by IETF 107 registration (pre-COVID cancellation, not by 108, not by email) and replied positively to my “still interested?” email: 8
>>
>> Total: 143
>
> (FWIW, I believe that *qualified* volunteers was a bit lower.)
>> Since most people have already registered for IETF, it would be too late to get people through a registration box this year if we were to re-open volunteering and add the box. I deeply doubt that re-opening volunteering for a week would get more than maybe 10 people, because it would be limited to mechanisms that have already been used to reach people (i.e., emails on general lists and potentially to WGs). Therefore, I recommend against re-opening the volunteer process.
>
> Certainly, if we ignored the elephant in the room (that most participants
> are not on the ietf-announce or this list) we'd get very poor results. The message would need to go to everybody in the mailman whitelist and would need some pretty strong motivational language, since we'd be trying to reach people who usually don't care about all this admin stuff. But IMHO this is a decision for the NomCom Chair to take.

I see invitations to volunteer for NomCom on many WG lists but do not 
find them encouraging.  The sense I get is of the WG Chair reluctantly 
doing what they feel obliged to do and then posting a further call 
because the first was so unsuccesful:-(  In particular, the issue of 
diversity does not really get a look in but, as this thread shows, it is 
a significant one.  The announcement e-mail is not bad, but could do 
better IMHO.

Tom Petch

>     Brian
>
>>
>> RFC8713 builds in massive amounts of process that NomCom has to follow – dependencies of things that have to be done before the next thing can be done, mandatory periods between certain announcements/events, etc. Shifting volunteer selection can potentially impact all the future dates, due to dependencies. Therefore, I recommend against re-opening volunteering. I recommend against impacting the NomCom Chair’s timeline for an effort that is unlikely to cause any significant increase in volunteers.
>>
>>
>>
>> Some less well-documented personal observations:
>>
>> - Most volunteers from the big router companies came in shortly after the first announcement. I strongly suspect that internal company emails go
> around encouraging people to volunteer. I doubt this happens in other companies (or at least not to the same extent).
>>
>> - The WG emails **are** effective. Outside of the registration checkbox, they were the most effective tool in getting people from outside Routing area (and not from one of the main router vendors) to volunteer.
>>
>> - An interesting side-effect of most volunteers coming from the big router vendors is that NomCom experience last year was heavily from Routing Area participants and other Areas were not so well represented.
>>
>>
>>
>> I would recommend having a checkbox for IETF 114 (next year).
>>
>>
>>
>> Barbara
>>
>>
>>
>> Maybe I am mistaken, but I perceived one change for this NomCom round :
> we used to be able to volunteer for the NomCom by just clicking a box in the registration process, and I didn’t see this option this year.
>>
>> Instead I had to send an email to be registered (a process somewhat automated later).
>>
>> It is possible that this change of habit has disrupted the flow of NomCom applications.
>>
>> One way of knowing would be to resume the NomCom box in the next registration cycle and see if we get different outcomes.
>>
>> Best regards,
>>
>> Julien.
>>
>>
>>
>> On Sun, Jun 27, 2021 at 8:12 PM Michael StJohns <mstjohns@comcast.net <mailto:mstjohns@comcast.net>> wrote:
>>
>>      On 6/27/2021 8:00 PM, Mary B wrote:
>>
>>          [MB] Per the process, I don't think that it allows more than *2*  from a single company.  So, I think the problem isn't as bad
> as some perceive.  Personally, I see the bigger problem as the fact that *many* that were qualified didn't volunteer.  [/MB]
>>
>>      The problem (IMNSHO) is that, statistically, if you (company) have a large enough proportion of the pool, you have a pretty much guaranteed probability of having 2 members.   If you have 2 members for every nomcom, you can have a disproportionate impact in the overall composition of the leadership of the IETF over time.
>>
>>      FWIR, Huawei has had 2 Nomcom members for most of the last 5-8 Nomcoms.  Cisco, Ericsson and Juniper have also had substantial representation.
>>
>>      That may represent personal diversity, but it does not represent commercial diversity.
>>
>> [MB]  So, yeah, this is not a new problem and is reflective of the
> fact that folks from some companies have more support for their IETF work
> than others. So, perhaps, we reduce it to 1 from a single company. But, again, that's not a process change we can push through in time for this Nomcom.  The bigger problem in my view is still the fact that a lot of
> folks that might be qualified haven't volunteered.   [/MB]
>>
>>      Later, Mike
>>
>>
>>
>
> .
>