Re: [Eligibility-discuss] NomCom eligibility & IETF 107 (fwd) Scott Mansfield: RE: NomCom eligibility & IETF 107

Victor Kuarsingh <victor@jvknet.com> Tue, 31 March 2020 16:01 UTC

Return-Path: <victor@jvknet.com>
X-Original-To: eligibility-discuss@ietfa.amsl.com
Delivered-To: eligibility-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7AD203A2353 for <eligibility-discuss@ietfa.amsl.com>; Tue, 31 Mar 2020 09:01:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.004
X-Spam-Level:
X-Spam-Status: No, score=0.004 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=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=jvknet-com.20150623.gappssmtp.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 avpr99tAf_UT for <eligibility-discuss@ietfa.amsl.com>; Tue, 31 Mar 2020 09:01:24 -0700 (PDT)
Received: from mail-wr1-x435.google.com (mail-wr1-x435.google.com [IPv6:2a00:1450:4864:20::435]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4CFB63A2372 for <eligibility-discuss@ietf.org>; Tue, 31 Mar 2020 09:01:24 -0700 (PDT)
Received: by mail-wr1-x435.google.com with SMTP id j17so26593195wru.13 for <eligibility-discuss@ietf.org>; Tue, 31 Mar 2020 09:01:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jvknet-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Gm0qml4sEGXLaOgdzTfq5zD55a8epdDZ0ubdbVRiUhY=; b=exjUQF9iD9xgzzSSgFloGRV0dvHoAWZe1M9hVtrQwwm+ZgR1YEBtHiVahfMtStnNg9 My4/ghSrdBoFGUp+FMCr7RqP/hMXetM+id0vXp5hIBvBPey6o/bKlWkMc1k85NgvUIbk n6cxRVoJYjv3seGBTO4I0+0DIwFA0sIfx6FQzVD26rkvrKTIBekuWEUwwrp37bXgUGGp jNi6BQFH8kb8+nRg/Un0Va5AyamO+jGTtZu1wyaUCQVFonEHj5I712wqr5W4M+qE/bCh W2PwlEHTPWmQpfik45glGOoexqq9iM3ycj7qPVq7BBrYyZ43PrRpuGw3LT6t8zdA8Nb9 Qwnw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Gm0qml4sEGXLaOgdzTfq5zD55a8epdDZ0ubdbVRiUhY=; b=i1viMzTjj9ZHIumWvmEWDtrRsdwP2kCxpF6u5+iw4yE36/NngawNeSNsCJJpaod/Wi sbhzxrE90EhB7bL1NkQ0NQ4QWfOJQLWu3CmjAfu2E2rdWb+xrJ+oJyLmzOadfaSPAj3a A+/4s3mb8vQrZCo6dYMi15tsXsFx2khItdDf1X1B6P1MpzWPGvkUYuXeyUMYvRbWN189 Mpl6eaw6a8a2GhklM2SiZqPtO7UyCwMb7SZTS/OPtfhTGz/1/O0bzro9+D4yEMiCuuLK HZEQeA6y2FJ/uV1iKi4psi1cS64CFAjm9pm3rMNG8He95ShqINAWeUYmubt8r8iTaDlS g+TQ==
X-Gm-Message-State: ANhLgQ0VmpClGi17z/t6qbLyZoCix/zLiAGjtCi7c/AIRArFH9RqyGoL rWiWkJ5gC9HNQzjri90ElfFuoa9iStNjcHTeVdc2kw==
X-Google-Smtp-Source: ADFU+vveQFihO81gVTBWDxlKXQRDxr6LOoWZ4jF/VDky9AUlxWGPSVqZmOA7mzwEos2y76rbSSp7ds1hy/34LfGUei0=
X-Received: by 2002:adf:a54a:: with SMTP id j10mr22062744wrb.188.1585670482336; Tue, 31 Mar 2020 09:01:22 -0700 (PDT)
MIME-Version: 1.0
References: <28433.1585520758@localhost> <CAJc3aaNs2DipcSAdddB1PayPSFN+zRPDwyKog_LhjTu4B95afg@mail.gmail.com> <28427.1585618693@localhost>
In-Reply-To: <28427.1585618693@localhost>
From: Victor Kuarsingh <victor@jvknet.com>
Date: Tue, 31 Mar 2020 12:01:11 -0400
Message-ID: <CAJc3aaPkfAAhPLwPhKfikjhg=15AopFntGJefhLd7t9=a-fJkQ@mail.gmail.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Cc: eligibility-discuss@ietf.org
Content-Type: multipart/alternative; boundary="000000000000d4b30405a228ade9"
Archived-At: <https://mailarchive.ietf.org/arch/msg/eligibility-discuss/OF57T8FIczqX78I9MQXObifkABQ>
Subject: Re: [Eligibility-discuss] NomCom eligibility & IETF 107 (fwd) Scott Mansfield: RE: NomCom eligibility & IETF 107
X-BeenThere: eligibility-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <eligibility-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/eligibility-discuss>, <mailto:eligibility-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/eligibility-discuss/>
List-Post: <mailto:eligibility-discuss@ietf.org>
List-Help: <mailto:eligibility-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eligibility-discuss>, <mailto:eligibility-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 31 Mar 2020 16:01:27 -0000

Michael,



On Mon, Mar 30, 2020 at 9:38 PM Michael Richardson <mcr+ietf@sandelman.ca>
wrote:

>
> Victor Kuarsingh <victor@jvknet.com> wrote:
>     > On Sun, Mar 29, 2020 at 6:26 PM Michael Richardson <
> mcr+ietf@sandelman.ca>
>     > wrote:
>
>     >> My two cents...
>     >>
>     >> < SNIP >
>     >>
>     >> My suggestions:
>     >> 1) Drop the 3/5 face-to-face requirement for the upcoming nomcom
> (since we
>     >> don't really have a process for virtual participation yet)
>     >>
>
>     > If we took the proposal of just ignoring the. IETF107 meeting and
> took the
>     > rest (2 of 4 meetings from IETF103 - IETF106), would that not be
> valid and
>     > hold closest to the intention of the current process? (understanding
> we
>     > need to update the process in light of recent events for future
>     > Nomcoms).
>
> The criteria is 3 of 5 right?
> If you "ignore" IETF107 (it happened btw, the IESG and IAB got changed),
> then
> you have to change the criteria, which seems a bigger change to me than
> deciding that IETF107 and that either nobody was present or some people
> were present.
>
>     > I was just thinking that we keep it as simple as possible for now to
> seat
>     > this Nomcom and give ourselves more time to then make more
>     > substantive changes to the eligibility.  Making other changes (large
> or
>     > small), are likely to have unintended impacts so I think trying to
> avoid
>     > that may be best (IMO).
>
> I believe that there won't be more than three people who needed the IETF107
> point to qualify for the nomcom.  If we counted IETF107 as happaned, and
> nobody was there, then that would be truest to the criteria.
>
>
I may have mis-understood what you were intending (after reading your
response).  Just for clarity.

Are you suggesting either of the following?

- (1) We keep 3 out of 5 for IETF103 - 107 and just ignore 107 which means
you really needed 3 out of 4?

- (2) We keep 3 out of 5 for IETF103 - 107 and assume everyone got 107

- (3) We keep 3 out of the 5 IETF103 - 107 and fine a way to assess
"attendance" for 107?


If you are suggesting 1, that is closest to what I proposed (but does raise
the bar post attendance as folks deciding on attendance for those previous
IETF meetings - should they have wanted to be a Nomcom member - could miss
out now that 107 would not have been a way to get a third meeting).

If you are suggesting 2, that would change the definition of "attendance".
Same for (3).

If I totally blundered understanding what you were suggesting, sorry about
that.

As for my first point, making it 2 of 4 (IETF 103 - 106), allows the same
definition which was understood before IETF 107 to hold, maintain the same
bar for that attendance and does not retroactively impact anyone who made
previous attendance decisions for this nomcom.  It just assumes 107
attendance was not possible (which it was not for "in-person") and removes
it from the equation.

I see this as the best way to avoid the most challenges since it would not
exclude anyone who could have attended 107.

regards,

Victor K