Re: NomCom eligibility & IETF 107

Michael Richardson <mcr+ietf@sandelman.ca> Fri, 13 March 2020 16:13 UTC

Return-Path: <mcr+ietf@sandelman.ca>
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 24FF93A0DCC for <ietf@ietfa.amsl.com>; Fri, 13 Mar 2020 09:13:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 zXFCmsgtsqPb for <ietf@ietfa.amsl.com>; Fri, 13 Mar 2020 09:12:59 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0D15C3A0D33 for <ietf@ietf.org>; Fri, 13 Mar 2020 09:12:58 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 1FC4D38985; Fri, 13 Mar 2020 12:11:39 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 9B821781; Fri, 13 Mar 2020 12:12:53 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Barry Leiba <barryleiba@computer.org>
cc: IETF discussion list <ietf@ietf.org>
Subject: Re: NomCom eligibility & IETF 107
In-Reply-To: <CALaySJ+kFVXrVAkYLaO6MaPqDA29MzXhVFcxG0c6hZcBs-LqnQ@mail.gmail.com>
References: <CALaySJ+kFVXrVAkYLaO6MaPqDA29MzXhVFcxG0c6hZcBs-LqnQ@mail.gmail.com>
X-Mailer: MH-E 8.6; nmh 1.7+dev; GNU Emacs 25.1.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature"
Date: Fri, 13 Mar 2020 12:12:53 -0400
Message-ID: <9539.1584115973@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/XD_X6grgOXwHf1Dx2YWV5TOFRJA>
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 16:13:13 -0000

Barry Leiba <barryleiba@computer.org> wrote:
    > The IESG would like the community’s input: How do *you* think 107
    > should be treated in regards to NomCom eligibility?  While we have
    > time to come up with a longer-term answer for this as a general
    > matter, we need to make a one-time decision about how to handle 107
    > now, before this year’s NomCom is formed.

I think that IETF107 should be counted as a remote meeting, therefore not
valid in the current rules for eligibility.

This is exactly how the IETF has treated remote attendees for the past twenty
years.  If there is interest in fixing that, I have a number of proposals.


    > 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.

Nope.

    > Another choice is to consider 107 to be a meeting that everyone has
    > attended, for the purpose of NomCom eligibility.  There, the last five
    > would still be 107 to 103, but 107 would be an automatic “yes” for
    > anyone who volunteers for the NomCom.

Nope.

I doubt missing one meeting will have a significant impact on the eligibility
of very many.

{now, I might read the long thread I see attached}

--
Michael Richardson <mcr+IETF@sandelman.ca>ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-