Re: NomCom eligibility & IETF 107

Michael StJohns <mstjohns@comcast.net> Fri, 13 March 2020 17:25 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 24C353A0F52 for <ietf@ietfa.amsl.com>; Fri, 13 Mar 2020 10:25:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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, 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 WZkXix7xjtDq for <ietf@ietfa.amsl.com>; Fri, 13 Mar 2020 10:25:10 -0700 (PDT)
Received: from resqmta-ch2-01v.sys.comcast.net (resqmta-ch2-01v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:33]) (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 B76EB3A0F56 for <ietf@ietf.org>; Fri, 13 Mar 2020 10:25:10 -0700 (PDT)
Received: from resomta-ch2-20v.sys.comcast.net ([69.252.207.116]) by resqmta-ch2-01v.sys.comcast.net with ESMTP id Co0vjV1YtYmJiCo3ZjL6qW; Fri, 13 Mar 2020 17:25:09 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=20190202a; t=1584120309; bh=3jX2IJJ26Mw/HRKB/XOX1gEqvmObMiqETgoh86PylrU=; h=Received:Received:Subject:To:From:Message-ID:Date:MIME-Version: Content-Type; b=Jx0oheobnzwWQYAJI+HjrMJ8P/+M7e08Co8XV7jM9nmSV37i0OQFfqg4HoUwwioZw uzZFMI5OU23byOX/LhfZioW5PJesjcbjHUkNVsloR7R9CMzAGMjLDm+VSsR+ggnhQ/ 3Qlk+QnpY05wDquMxk6qpMrLUayxF+vn+URZRhL1OYAzQPx+6PhyfwdhkGvlwLoLWJ L/8KnJ3oru3vCbR8zce+ojxlxXPajDqorRfudwFLQsRB5frrzWxnBDiNVylK4964pT DZNdRaz5ywFMRmPtDD59KTAjjNfw/J555Tr2r5HPPOSjE2E8+/WmwG/tQ6AFgUGzhB EyvhR3VB1Q9xg==
Received: from [192.168.1.115] ([71.163.188.115]) by resomta-ch2-20v.sys.comcast.net with ESMTPSA id Co3Tjg5G2TUlPCo3Tj2KGU; Fri, 13 Mar 2020 17:25:07 +0000
X-Xfinity-VAAS: =?utf-8?q?gggruggvucftvghtrhhoucdtuddrgedugedruddvjedguddttd?= =?utf-8?q?cutefuodetggdotefrodftvfcurfhrohhfihhlvgemucevohhmtggrshhtqdftvgh?= =?utf-8?q?sihdpqfgfvfdppffquffrtefokffrnecuuegrihhlohhuthemuceftddtnecunecu?= =?utf-8?q?jfgurhepuffvfhfhkffffgggjggtgfesthekredttdefjeenucfhrhhomhepofhit?= =?utf-8?q?ghhrggvlhcuufhtlfhohhhnshcuoehmshhtjhhohhhnshestghomhgtrghsthdrnh?= =?utf-8?q?gvtheqnecukfhppeejuddrudeifedrudekkedrudduheenucevlhhushhtvghrufh?= =?utf-8?q?iiigvpedtnecurfgrrhgrmhephhgvlhhopegludelvddrudeikedruddrudduhegn?= =?utf-8?q?pdhinhgvthepjedurdduieefrddukeekrdduudehpdhmrghilhhfrhhomhepmhhst?= =?utf-8?q?hhjohhhnhhssegtohhmtggrshhtrdhnvghtpdhrtghpthhtohepihgvthhfsehivg?= =?utf-8?q?htfhdrohhrgh?=
X-Xfinity-VMeta: sc=0.00;st=legit
Subject: Re: NomCom eligibility & IETF 107
To: ietf@ietf.org
References: <CALaySJ+kFVXrVAkYLaO6MaPqDA29MzXhVFcxG0c6hZcBs-LqnQ@mail.gmail.com> <20200313162255.GB8656@faui48f.informatik.uni-erlangen.de>
From: Michael StJohns <mstjohns@comcast.net>
Message-ID: <2c7a8602-0a8c-0762-baba-25a5232b6b40@comcast.net>
Date: Fri, 13 Mar 2020 13:25:02 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:68.0) Gecko/20100101 Thunderbird/68.5.0
MIME-Version: 1.0
In-Reply-To: <20200313162255.GB8656@faui48f.informatik.uni-erlangen.de>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/YB50KXqm3jcaFZW--byvtENICQs>
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, 13 Mar 2020 17:25:12 -0000

On 3/13/2020 12:22 PM, Toerless Eckert wrote:
> +1
>
> An exhaustive mathematical analysis performed by staring at the two option
> paragraps for 5 seconds each has made me come up with the following preference.
>
> On Fri, Mar 13, 2020 at 09:43:34AM -0400, Barry Leiba wrote:
>> One choice is to entirely ignore 107 for the purposes of NomCom
>> eligibility.  The last five meetings would then be 106, 105, 104, 103,
>> and 102, and one would have had to attend three of those to be
>> eligible this year.

Or to put it another way:

If you were eligible for the Nomcom or for any of the other 3 of 5 
meetings required positions at the conclusion of the 106th IETF meeting 
you will remain eligible until the corona virus threat has abated (as 
determined by the consensus of the IESG, IAB and LLC based on available 
public health guidance?).

I'd also suggest adding:

If the IETF succeeds in holding  in-person plenary meetings while there 
are still substantial numbers of company or country restrictions related 
to the virus, those meetings will count for the purposes of meetings 
attended, but will not cause any of the current "last 5" - 102-106 - to 
drop off the list.   E.g. if you had 2 of 5 meetings at the conclusion 
of IETF 106, and you attend IETF 108, you would be eligible, but any 
person eligible after 106 would remain eligible even if they didn't 
attend.   [When it looked like the IETF was going ahead, but without 
substantial numbers of participants due to the patchwork of 
restrictions, I had the above queued up as a suggestion - there also 
needs to be a return to steady state clause of some sort].

Mike