Re: Challenge: was Re: Updated Nomcom 2020-2021: Result of random selection process
Michael StJohns <mstjohns@comcast.net> Fri, 10 July 2020 22:58 UTC
Return-Path: <mstjohns@comcast.net>
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 8CCD13A0C15 for <ietf@ietfa.amsl.com>; Fri, 10 Jul 2020 15:58:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcast.net
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 J4Zur-iUbxpN for <ietf@ietfa.amsl.com>; Fri, 10 Jul 2020 15:58:52 -0700 (PDT)
Received: from resqmta-ch2-11v.sys.comcast.net (resqmta-ch2-11v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:43]) (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 B01623A0C12 for <ietf@ietf.org>; Fri, 10 Jul 2020 15:58:52 -0700 (PDT)
Received: from resomta-ch2-19v.sys.comcast.net ([69.252.207.115]) by resqmta-ch2-11v.sys.comcast.net with ESMTP id u1n4jCDvluQNtu1yljRjvq; Fri, 10 Jul 2020 22:58:51 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=20190202a; t=1594421931; bh=i1d9uJOs/elRu6x/RghfNm2GW3pqossytzM9HA2+rao=; h=Received:Received:Subject:To:From:Message-ID:Date:MIME-Version: Content-Type; b=anDstSmztoOk75nSscbQJbJzXCRVFD9tj1PoygBddk3N977yNMS6F73oDCxWd/yvh X0qz1kJPfvGXEruxRAty7v19K3NEEJsGAglLX/V4NKVxwvZFqGd4JdDz/yYPpuayKr Gm+Pcr0287edYSDqGJW0DYX48wGJp7Y/7PI6iS5M+aGtoJE55RjZjB3uCt6YbOEEkR w9G9bQ0SDdRhlvfzbgF64gMo3JRXSIfF/erxgqJYhyYz/btu/07OxEoTVyWeERwhXG PqYjGIn7WvfCYAV0igpv+i4rmFRVI/ceXcALLQjtTjSq1loDSV6Wl57BKi9JL56tzw Q9IKoc7VV4ndw==
Received: from [192.168.1.115] ([71.163.188.115]) by resomta-ch2-19v.sys.comcast.net with ESMTPSA id u1yajRZi9NNZPu1ybjuYlL; Fri, 10 Jul 2020 22:58:49 +0000
X-Xfinity-VAAS: gggruggvucftvghtrhhoucdtuddrgeduiedrvddvgdduiecutefuodetggdotefrodftvfcurfhrohhfihhlvgemucevohhmtggrshhtqdftvghsihdpqfgfvfdppffquffrtefokffrnecuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenucfjughrpefuvfhfhffkffgfgggjtgesrgdtreertdefjeenucfhrhhomhepofhitghhrggvlhcuufhtlfhohhhnshcuoehmshhtjhhohhhnshestghomhgtrghsthdrnhgvtheqnecuggftrfgrthhtvghrnhepuedvfefgheeghfffgfelgeeukeelhefhjeekgeegvdevtefftdekudekfeeuudehnecukfhppeejuddrudeifedrudekkedrudduheenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhephhgvlhhopegludelvddrudeikedruddrudduhegnpdhinhgvthepjedurdduieefrddukeekrdduudehpdhmrghilhhfrhhomhepmhhsthhjohhhnhhssegtohhmtggrshhtrdhnvghtpdhrtghpthhtohepnhhomhgtohhmqdgthhgrihhrqddvtddvtdesihgvthhfrdhorhhgpdhrtghpthhtohepihgvthhfsehivghtfhdrohhrghdprhgtphhtthhopeihnhhirhdrihgvthhfsehgmhgrihhlrdgtohhm
X-Xfinity-VMeta: sc=-100.00;st=legit
Subject: Re: Challenge: was Re: Updated Nomcom 2020-2021: Result of random selection process
To: Yoav Nir <ynir.ietf@gmail.com>
Cc: ietf@ietf.org, NomCom Chair 2020 <nomcom-chair-2020@ietf.org>
References: <159422819660.27889.6475902734358747001@ietfa.amsl.com> <b4f5a3cf-5fab-8188-926a-a4100f776610@comcast.net> <892C3021-1B44-463C-B2C4-5070396EFD50@gmail.com>
From: Michael StJohns <mstjohns@comcast.net>
Message-ID: <c3de3ced-2995-dba2-6bf6-89d0659138be@comcast.net>
Date: Fri, 10 Jul 2020 18:58:39 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0
MIME-Version: 1.0
In-Reply-To: <892C3021-1B44-463C-B2C4-5070396EFD50@gmail.com>
Content-Type: multipart/alternative; boundary="------------59081EE37D64C6AE29D6C779"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/azK8yKOiyDpyNmM2JkzeZTay2z0>
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: Fri, 10 Jul 2020 22:58:55 -0000
On 7/10/2020 4:25 PM, Yoav Nir wrote: > WARNING: RFC lawyering follows. > > I’m not sure I agree. Two paragraphs in section 4.17 of RFC 7437 > govern this. > > The first is the second paragraph: > > No more than two volunteers with the same primary affiliation may be > selected for the nominating committee. The Chair reviews the primary > affiliation of each volunteer selected by the method in turn. If the > primary affiliation for a volunteer is the same as two previously > selected volunteers, that volunteer is removed from consideration and > the method is repeated to identify the next eligible volunteer. > > Clearly this is the procedure for the chair to follow if she detects > that the list contains more than two people with the same affiliation. > This is the procedure that was followed to remove Reshad Rahman, but > note that the RFC does not call this being disqualified; just “removed > from consideration”. This was not what happened with the Huawei > candidates. In that case, the relevant paragraph is the sixth paragraph: > > 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. > > This puts the determination of how to proceed in the hands of the > chair. She is not required to roll back the clock to simulate a > situation in which Luigi Iannone had filled in the volunteer form > correctly. You're mischaracterizing what happened I believe. Luigi was always a Huawei employee, but the chair did not have that information. Once the chair had that information, the results of the selection process needed to be corrected so they were based on reality - Note: not "changed". The whole process is designed to eliminate discretion from the selection process. While I agree that the document says the above, it does not mean that the chair may take any action they choose. E.g. there were three Huawei members - what if she kept Luigi and Tal and got rid of Xuesong? We still end up with two Huawei members. In any event, you need to look at more than just the above. The correct path is to take the list from all common knowledge and work from there. And that list built from the common knowledge (the volunteer list, plus associations plus the random seeds) has Luigi on it and Tal off of it. Per > It must be possible to repeat the selection method, either through > iteration or by restarting in such a way as to remain fair and > unbiased. This is necessary to replace selected volunteers should > they become unavailable after selection. and > If a single voting volunteer position on the nominating committee is > vacated, regardless of the circumstances, the committee may choose to > proceed with only nine voting volunteers at its own discretion. In > all other cases, a new voting member must be selected, and the Chair > must repeat the random selection process including an announcement of > the iteration prior to the actual selection as stated elsewhere in > this document. If Luigi declines to take the position, "the chair must repeat the random selection process" or work with 9 members. In general, that's meant continuing down the list, not going back and picking up someone who was already not selected. > I believe she has made such a determination, and has acted within the > mandate of RFC 7437. Luigi indicating he works for Huawei restructures the list and eliminates Tal. Luigi indicating he won't serve triggers 5.7. These are two separate events. This is not ambiguous. Mike > > Yoav
- Updated Nomcom 2020-2021: Result of random select… NomCom Chair 2020
- Challenge: was Re: Updated Nomcom 2020-2021: Resu… Michael StJohns
- Re: Challenge: was Re: Updated Nomcom 2020-2021: … Salz, Rich
- Re: Challenge: was Re: Updated Nomcom 2020-2021: … Mary B
- Re: Challenge: was Re: Updated Nomcom 2020-2021: … Kyle Rose
- Re: Challenge: was Re: Updated Nomcom 2020-2021: … John C Klensin
- Re: Challenge: was Re: Updated Nomcom 2020-2021: … Yoav Nir
- Re: Challenge: was Re: Updated Nomcom 2020-2021: … Samuel Weiler
- Re: Challenge: was Re: Updated Nomcom 2020-2021: … Toerless Eckert
- Re: Challenge: was Re: Updated Nomcom 2020-2021: … Martin Duke
- Re: Challenge: was Re: Updated Nomcom 2020-2021: … Michael StJohns
- Re: Challenge: was Re: Updated Nomcom 2020-2021: … Toerless Eckert
- Re: Challenge: was Re: Updated Nomcom 2020-2021: … Olafur Gudmundsson
- Re: Challenge: was Re: Updated Nomcom 2020-2021: … Toerless Eckert
- Re: Challenge: was Re: Updated Nomcom 2020-2021: … Joseph Touch
- Re: Challenge: was Re: Updated Nomcom 2020-2021: … Toerless Eckert
- Re: Challenge: was Re: Updated Nomcom 2020-2021: … Toerless Eckert
- Re: Challenge: was Re: Updated Nomcom 2020-2021: … Benjamin Kaduk
- Re: Challenge: was Re: Updated Nomcom 2020-2021: … Toerless Eckert
- Re: Challenge: was Re: Updated Nomcom 2020-2021: … Joseph Touch
- Re: Challenge: was Re: Updated Nomcom 2020-2021: … Benjamin Kaduk
- Re: Challenge: was Re: Updated Nomcom 2020-2021: … Toerless Eckert
- Re: Challenge: was Re: Updated Nomcom 2020-2021: … Toerless Eckert
- Re: Challenge: was Re: Updated Nomcom 2020-2021: … Melinda Shore
- Re: Challenge: was Re: Updated Nomcom 2020-2021: … Joseph Touch
- Re: Challenge: was Re: Updated Nomcom 2020-2021: … Toerless Eckert
- Re: Challenge: was Re: Updated Nomcom 2020-2021: … Toerless Eckert
- Re: Challenge: was Re: Updated Nomcom 2020-2021: … Yoav Nir
- Re: Challenge: was Re: Updated Nomcom 2020-2021: … Yoav Nir
- Re: Challenge: was Re: Updated Nomcom 2020-2021: … Yoav Nir
- Re: Challenge: was Re: Updated Nomcom 2020-2021: … Eliot Lear
- Re: Challenge: was Re: Updated Nomcom 2020-2021: … Toerless Eckert
- Re: Challenge: was Re: Updated Nomcom 2020-2021: … Toerless Eckert
- Re: Challenge: was Re: Updated Nomcom 2020-2021: … Michael StJohns
- Re: Challenge: was Re: Updated Nomcom 2020-2021: … Yoav Nir
- Re: Challenge: was Re: Updated Nomcom 2020-2021: … Yoav Nir
- Re: Challenge: was Re: Updated Nomcom 2020-2021: … Rob Sayre
- Re: Challenge: was Re: Updated Nomcom 2020-2021: … Toerless Eckert
- Re: Challenge: was Re: Updated Nomcom 2020-2021: … Brian E Carpenter
- Re: Challenge: was Re: Updated Nomcom 2020-2021: … Mike StJohns
- Re: Challenge: was Re: Updated Nomcom 2020-2021: … Victor Kuarsingh
- RE: Challenge: was Re: Updated Nomcom 2020-2021: … STARK, BARBARA H
- RE: Challenge: was Re: Updated Nomcom 2020-2021: … Vittorio Bertola
- Re: Challenge: was Re: Updated Nomcom 2020-2021: … Eliot Lear
- Re: Challenge: was Re: Updated Nomcom 2020-2021: … Michael StJohns
- RE: Challenge: was Re: Updated Nomcom 2020-2021: … STARK, BARBARA H
- Re: Challenge: was Re: Updated Nomcom 2020-2021: … Michael StJohns
- Challenge: Re: Challenge: was Re: Updated Nomcom … Toerless Eckert
- Re: Challenge: Re: Challenge: was Re: Updated Nom… Mike StJohns
- Re: Challenge: Re: Challenge: was Re: Updated Nom… John C Klensin
- Re: Challenge: Re: Challenge: was Re: Updated Nom… Toerless Eckert
- Re: Challenge: Re: Challenge: was Re: Updated Nom… Toerless Eckert
- Re: Challenge: Re: Challenge: was Re: Updated Nom… Benjamin Kaduk
- Re: Challenge: Re: Challenge: was Re: Updated Nom… Toerless Eckert
- Re: Challenge: was Re: Updated Nomcom 2020-2021: … Rob Sayre
- Re: Challenge: Re: Challenge: was Re: Updated Nom… John C Klensin
- Re: Challenge: Re: Challenge: was Re: Updated Nom… Toerless Eckert
- Re: Challenge: Re: Challenge: was Re: Updated Nom… S Moonesamy
- RE: Challenge: was Re: Updated Nomcom 2020-2021: … Mehmet Ersue
- Re: Challenge: Re: Challenge: was Re: Updated Nom… Samuel Weiler
- Re: Challenge: Re: Challenge: was Re: Updated Nom… Victor Kuarsingh
- Re: Challenge: Re: Challenge: was Re: Updated Nom… S Moonesamy
- Re: Challenge: Re: Challenge: was Re: Updated Nom… Victor Kuarsingh
- RE: Challenge: Re: Challenge: was Re: Updated Nom… STARK, BARBARA H
- Additional advisors (was: RE: Challenge: Re: Chal… Samuel Weiler
- Re: Challenge: Re: Challenge: was Re: Updated Nom… Warren Kumari
- Re: Additional advisors (was: RE: Challenge: Re: … John C Klensin
- Re: Additional advisors (was: RE: Challenge: Re: … Mary B
- Re: Additional advisors (was: RE: Challenge: Re: … Scott O. Bradner
- Re: Additional advisors (was: RE: Challenge: Re: … Victor Kuarsingh
- Re: Additional advisors (was: RE: Challenge: Re: … Michael Richardson
- Re: Additional advisors (was: RE: Challenge: Re: … Pete Resnick
- Re: Additional advisors (was: RE: Challenge: Re: … Scott O. Bradner
- Re: Additional advisors (was: RE: Challenge: Re: … John C Klensin
- Re: Additional advisors (was: RE: Challenge: Re: … Samuel Weiler
- Re: Additional advisors (was: RE: Challenge: Re: … Pete Resnick
- RE: Additional advisors (was: RE: Challenge: Re: … STARK, BARBARA H
- Re: Additional advisors (was: RE: Challenge: Re: … Randy Bush
- Re: Additional advisors Brian E Carpenter