Re: NomCom eligibility & IETF 107

"Andrew G. Malis" <agmalis@gmail.com> Fri, 13 March 2020 23:25 UTC

Return-Path: <agmalis@gmail.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 630623A1236 for <ietf@ietfa.amsl.com>; Fri, 13 Mar 2020 16:25:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 IdxrSbduyis2 for <ietf@ietfa.amsl.com>; Fri, 13 Mar 2020 16:25:56 -0700 (PDT)
Received: from mail-qk1-x72f.google.com (mail-qk1-x72f.google.com [IPv6:2607:f8b0:4864:20::72f]) (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 AFC473A1233 for <ietf@ietf.org>; Fri, 13 Mar 2020 16:25:56 -0700 (PDT)
Received: by mail-qk1-x72f.google.com with SMTP id c145so15655905qke.12 for <ietf@ietf.org>; Fri, 13 Mar 2020 16:25:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=sp/mls2t/bMHC6ccLyLsDXEOrnCn7YXLLOmrsvejlYk=; b=EXPvqxTwtufjcVaMpm4gYD2hPA/n2X2voQO31n0op53CH9XONJxv+7EGqh6VPqS87L oTCsCeU8zPvMV7u2TKnlZIJtMPQKdW+qFJj1Eqp/090r/fxHiKQsksuP+F1Oq0AlvuC5 CI4GG/B/HHsLU3zBMKlqFegvQpIawIDgRFs3v7xx7nE3W3i3j0BYx5GCBN8BTV6q/OAx 8wFD2CQh/UeVFDeo2oco7GpYL91hGcKyBkzFefKzGhBFfUxtqM1Ufqha7EAdZkhFD4oa GbzJ1kxzm7phEzPxoO95ZnBXLU7uq5XypTzPbYVhXdZsRMgoicjUImEW25MzwOW4pGMG KXcg==
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=sp/mls2t/bMHC6ccLyLsDXEOrnCn7YXLLOmrsvejlYk=; b=mIXiYqsaTMntA6oKwD2vv1krByELqo1tHk/2uHWG/1ATCDNWVonlFtVgC3mr4LtLHA 03lSwA1Cgy0/9rs384AkZaNT6SARb33ooVMWzCc9K4blZUuFXQUJot1C2pmFx8FDYM6x wRpflYxSJNNmi1R77MLkUtFFt77hpqg0DQbWd8R3iWc2EbTPPoQh4ayZkw1nB9dFBhSW tPNR3yeb4RAcm4J+dOYExfm2egJ8f1MXSEpYC2PhliCihQzvBsUyQXHu1qTXfhOdeDYg 86xFB0CLoYnqIAQY5cIOXGnF3hkHfLl591d8obmtwBTpDQjQRAzfQIGPSMYYO0Vg/Skp Zqrw==
X-Gm-Message-State: ANhLgQ3YBQyFmXxEWpiDM7oQ/tjt5/NsPHBCCvTNSJlZNAAGVFTlDbLv w/jyU2yaZRFUVmthsGpZ30gMFPmGevxNf+9aYuA=
X-Google-Smtp-Source: ADFU+vuQ/qaPiES1kbvBLDrlCfnGNra/l63unSJjKi4cjbZEmI8ONTJOIWelgBz211QsG+zNeEZ29eF2cDnay6uxsAg=
X-Received: by 2002:a37:9f42:: with SMTP id i63mr15896244qke.192.1584141955372; Fri, 13 Mar 2020 16:25:55 -0700 (PDT)
MIME-Version: 1.0
References: <CALaySJ+kFVXrVAkYLaO6MaPqDA29MzXhVFcxG0c6hZcBs-LqnQ@mail.gmail.com> <20200313162255.GB8656@faui48f.informatik.uni-erlangen.de> <20200313204317.GR21734@vurt.meerval.net>
In-Reply-To: <20200313204317.GR21734@vurt.meerval.net>
From: "Andrew G. Malis" <agmalis@gmail.com>
Date: Fri, 13 Mar 2020 19:25:44 -0400
Message-ID: <CAA=duU0jN0y12_HpzzK73BRD+x19ZQn74V=ju2_wwS-RUL_9Yw@mail.gmail.com>
Subject: Re: NomCom eligibility & IETF 107
To: Job Snijders <job@ntt.net>
Cc: Toerless Eckert <tte@cs.fau.de>, Barry Leiba <barryleiba@computer.org>, IETF discussion list <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000086196905a0c4ca38"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/EUqGS5CelOj7QBPV_D_HQ0WDvss>
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 23:25:59 -0000

I agree with Job, Even if we could hold IETF 108 as planned, I would expect
a large number of remote attendees just because people might still be wary
of travel. The time has come to determine a criteria for including remote
attendees for NOMCOM eligibility. The existing criteria is in-person
attendance for at least one day. My personal preference for the new
criteria would be in-person or remote participation in one or more working
group/BOF sessions and/or the plenary, as determined by electronic blue
sheets or by logging in to the conferencing system. That's just a
suggestion, I'm certainly open to other suggestions for the new criteria.

Cheers,
Andy


On Fri, Mar 13, 2020 at 4:44 PM Job Snijders <job@ntt.net> wrote:

> On Fri, Mar 13, 2020 at 05:22:55PM +0100, Toerless Eckert wrote:
> > 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.
> >
> > +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.
>
> As John, Randy, and others have noted in this thread - I think we in
> this discussion context simply assume IETF 108 will also be all remote.
> And in that potential future, if from a NOMCOM eligibility perspective
> both IETF 107 and 108 are 'ignored', where does that leave us?
>
> I think that if IETF 107 is to take place in some remote shape or
> virtual form, it should be possible to 'attend', and list of these
> attendees should somehow contribute towards eligibility for the NOMCOM.
>
> Kind regards,
>
> Job
>
>