Re: NomCom eligibility & IETF 107

Donald Eastlake <d3e3e3@gmail.com> Thu, 26 March 2020 18:46 UTC

Return-Path: <d3e3e3@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 869C93A087B for <ietf@ietfa.amsl.com>; Thu, 26 Mar 2020 11:46:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.848
X-Spam-Level:
X-Spam-Status: No, score=-1.848 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_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=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 ikRxJ43iCkQ0 for <ietf@ietfa.amsl.com>; Thu, 26 Mar 2020 11:46:31 -0700 (PDT)
Received: from mail-il1-x12a.google.com (mail-il1-x12a.google.com [IPv6:2607:f8b0:4864:20::12a]) (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 117C43A080F for <ietf@ietf.org>; Thu, 26 Mar 2020 11:46:30 -0700 (PDT)
Received: by mail-il1-x12a.google.com with SMTP id t11so6432454ils.1 for <ietf@ietf.org>; Thu, 26 Mar 2020 11:46:30 -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:content-transfer-encoding; bh=5oyy9qYiVABf5XSd9uTeGyCkZvwllGn/1/qsPumgwdE=; b=K7Xzg8NdQj1MB4mHLc+jDOLxf+0Sgy0JzbrHulI1jDXPgYks/7sfXlfr30BkzCM064 8COl4Rq0jCo/Xw4XV9H4ic4EVLorNqtc+fRUmq4nATUlSD1LhVCCcOS0WLVB5ZEOR4PV em4Wgd8yQV+Z67LYznPdnRgRkzOdtEwBCH1oTO35yZXDEGgmBunmfjz9tn+1W/tKjeja 6s3TO6wvVKTfqHBwCRLZ/dx+GD7IeZyu7aEUv2JYcp+fgBJsbrtVqFAIqIFgSFUpI7p3 vqbX+3Utavh6D5OwyxnH6jnEGo5xXiKl8W05/ihiFosmtpdw1QMCKzId4th4R+rGvJXD bFSw==
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:content-transfer-encoding; bh=5oyy9qYiVABf5XSd9uTeGyCkZvwllGn/1/qsPumgwdE=; b=Nmczxn1VpM5w3V02yMOe085a2kT+PBvdBqbfeEXOQnCfTEha5UXJ5Js/UT9cyxxFQP uaH3mcre6/esVroZmdTQBD7V73fGkpyINDZnSffCm+agp1hml1atoQR4qWXMBlfca10l AoNERWH+SnRTQI8MNUIcBMRjxOMD60Em7o3dl/Q9o+rsc/TDOgSNHpULiHVMkmd0fXN6 FA4x6dAfaJel2tquXPtJS4f26+pnqP7L6pQUdDdZIpm8uW03MhQdnEJqVp98zVDKiwcM a14PXMVqdMcnbnfAOMVuntriokhLYI0Y0ma839K8IJ/3ZuK1rfp6+1CYgZ2l8dZ6N3ZU z91A==
X-Gm-Message-State: ANhLgQ3pa7if9N6yifxxoUCBTHEdTnXstyAUfVM97rBkAOET+pIgHs93 EHph4Oau7+lkIgHCbGdRbtbRPSTGocU+3OuK+w2TEQ==
X-Google-Smtp-Source: ADFU+vtlZL+CLCwpJEV51eLQ3OmHvMyIHVyYtaAvM4ctfPkxYKIh5ZtU/kon7F6w3I8+RJ3D8Oe2s+5/qgV1+clJaZI=
X-Received: by 2002:a92:9a4d:: with SMTP id t74mr10550300ili.168.1585248389967; Thu, 26 Mar 2020 11:46:29 -0700 (PDT)
MIME-Version: 1.0
References: <CALaySJ+kFVXrVAkYLaO6MaPqDA29MzXhVFcxG0c6hZcBs-LqnQ@mail.gmail.com> <CAC4RtVAhfFLYwzqw6Qch3BpuMvqjZPzFJ5o1iTOwR+yqH8j-Aw@mail.gmail.com>
In-Reply-To: <CAC4RtVAhfFLYwzqw6Qch3BpuMvqjZPzFJ5o1iTOwR+yqH8j-Aw@mail.gmail.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Thu, 26 Mar 2020 14:46:17 -0400
Message-ID: <CAF4+nEEGbh6fU508n2o5j_9HZ8LQ37nfj46QST6a24WQpG7igg@mail.gmail.com>
Subject: Re: NomCom eligibility & IETF 107
To: Barry Leiba <barryleiba@computer.org>
Cc: IETF discussion list <ietf@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/JPJQkY93oeaDKX9L0Li-YIjyQ4k>
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: Thu, 26 Mar 2020 18:46:34 -0000

I support ignoring IETF 107 for Nomcom eligibility. That is,
eligibility would be 3 out of 106, 105, 104, 103, and 102.

If it were only the case that, quite rarely, an isolated IETF meeting
could not take place face-to-face, that policy of ignoring the meeting
for eligibility seems adequate. But it looks like it may be 2 or more
IETF meetings in a row, so some better long term solution is called
for.

I should perhaps also mention my opposition to the belief that many
seem to have that bigger and bigger eligibility pools for nomcom
volunteers are always better as long as they have some vague
connection to the IETF. In my opinion the nomcom worked fine in its
early days when the pool was commonly in the 40's. These days it is
almost always over 100 people, which is plenty. The most important
goal of the nomcom is to select good officials for IETF so it is also
important that the people selected be willing to put in the time and
are reasonably familiar with the IETF. And, to avoid excessive
inertia, you have to bar current holders of the offices being selected
from voting membership.

(One thing no one has mentioned in this thread is the relationship to
IETF finances. Isn't the IETF partly funded by meeting registration
fees? If virtual IETF meetings become more common, there should be a
means of charging at least some remote participants. (Just to give an
example, I'd favor free jabber access and audio stream listening but a
significant registration fee (like 1/3 of the attendee fee) to be able
to speak remotely or to speak and be seen (meetecho). I'd be much more
comfortable with having people who remotely participant and pay that
remote registration fee having that count towards nomcom
eligibility...))

Thanks,
Donald
===============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 2386 Panoramic Circle, Apopka, FL 32703 USA
 d3e3e3@gmail.com

On Wed, Mar 25, 2020 at 7:16 PM Barry Leiba <barryleiba@computer.org> wrote:
>
> If you haven't already weighed in on this, please post your comment
> here, in this thread on <ietf@ietf.org>rg>, by 30 April 2020.
>
> Thanks,
> Barry, for the IESG
>
> On Fri, Mar 13, 2020 at 9:44 AM Barry Leiba <barryleiba@computer.org> wrote:
> >
> > The cancellation of the in-person IETF 107 meeting raises the issue of
> > how that meeting affects NomCom (Nominating Committee) eligibility.
> > This is especially important because a new NomCom will be formed
> > between now and IETF 108, giving us all a fairly short time to figure
> > out what to do.
> >
> > For convenient reference, the current rules for an IETF participant to
> > be eligible to be a voting member of a NomCom (Section 4.14 of RFC
> > 8713) require attendance in person at three of the last five meetings.
> > Normally, for the upcoming NomCom, that would mean three of the
> > following five meetings: 107 (Vancouver), 106 (Singapore), 105
> > (Montréal), 104 (Prague), 103 (Bangkok). A new participant who had
> > been to 105 and 106 would become eligible by attending 107.  An
> > occasional participant who had been to 103 and 105 would also become
> > eligible by attending 107. On the other side, someone who had attended
> > 102, 104, and 105 would lose eligibility by NOT attending 107.
> >
> > 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.
> >
> > 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.
> >
> > 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.
> >
> > Perhaps there are other workable options.  Please let us know what you
> > think by responding to this message thread.  And to be absolutely
> > clear: whatever we, as a community, decide now, with fairly short lead
> > time, is for the 2020-2021 NomCom cycle only.  Any longer-term
> > decisions might be different and will need to be done through a more
> > formal, consensus-based process, which we also hope to initiate in the
> > near future.
> >
> > Thanks in advance for the discussion we’re sure to have on this.
> >
> > Barry, for the IESG
> >
>