Re: NomCom eligibility & IETF 107

Barry Leiba <barryleiba@computer.org> Thu, 02 April 2020 14:03 UTC

Return-Path: <barryleiba.mailing.lists@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 2F6D13A12FB for <ietf@ietfa.amsl.com>; Thu, 2 Apr 2020 07:03:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.647
X-Spam-Level:
X-Spam-Status: No, score=-1.647 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 zv_36pCP3AwS for <ietf@ietfa.amsl.com>; Thu, 2 Apr 2020 07:03:29 -0700 (PDT)
Received: from mail-oi1-f175.google.com (mail-oi1-f175.google.com [209.85.167.175]) (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 9D0B93A136C for <ietf@ietf.org>; Thu, 2 Apr 2020 07:03:17 -0700 (PDT)
Received: by mail-oi1-f175.google.com with SMTP id d3so2888370oic.1 for <ietf@ietf.org>; Thu, 02 Apr 2020 07:03:17 -0700 (PDT)
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; bh=2IkrtEnuZsRsFVD6QUKdC1uCjtNYxMfVDDJxe9lUhKE=; b=VbPkyBaBZcuED+jduUjIDTaOp6nskSsecBVXcY6jG937iSLicvHswNbINsT2Qm7Ut+ wAQBMlJte2rARZQ+EQ5KiAceOK47CxFf0SDr+EdLqxublbnoLFnJ1GWuROyaDQITfqg5 WNNmnAtpULLSsxmcxRqHGyVr56OIqkx8RNHZ+uDcC6V8YoaHNw6FvnzULsXRaKNDcwB1 wMCHW8kmGxG/L3QoVfscgd68bIkn1vGvz2djIRoyfAIyxVcDXSNUGm5neTqvkaP2pKde kmYyLhxwJBUu1ijDM4JTzaGNJbPYJZfyikoZoCeyvUiGf1wjBiJQr5XU2Cv9PyTvUJpj Kdvw==
X-Gm-Message-State: AGi0PuYpjTZTE9iuRAYtQ+btHA5J73pN3FcUkyde03TIGMjpwAmtgM2b mX76SyuWPl0SNnzXRPCDrT1D2C6rolW/2H7JJF4Ndpg5
X-Google-Smtp-Source: APiQypKCyajeRzLwDThPWzttSuwygnnQ5e52OjmWEzHJuxLLZqIxYnaRmS+ZfstlOPIsuSiW4mndPp3AeKub6qdYwTc=
X-Received: by 2002:a54:4482:: with SMTP id v2mr2385350oiv.114.1585836196312; Thu, 02 Apr 2020 07:03:16 -0700 (PDT)
MIME-Version: 1.0
References: <CALaySJ+kFVXrVAkYLaO6MaPqDA29MzXhVFcxG0c6hZcBs-LqnQ@mail.gmail.com> <CAC4RtVAhfFLYwzqw6Qch3BpuMvqjZPzFJ5o1iTOwR+yqH8j-Aw@mail.gmail.com> <CAC4RtVCzMPGuunYZBCSh90ddY2kKJ_Hqnot0s1jmhNQ7qT0xkg@mail.gmail.com> <89730DD8-0451-4658-A0CD-83A85E2055FE@episteme.net> <0C31D020-46FA-424E-8FFD-64BBE8F952E9@cooperw.in> <1E702B62-9982-48F2-B8D6-F4F80A8DE168@episteme.net> <20200331184236.GT18021@localhost> <CALaySJ+_+-kf+3nta8LwMiwPmqPmRdOgC7KAnDfeDgx0ThVa-w@mail.gmail.com> <CALaySJ+27gcT6x5BcKU1YHHv+xeaXDnxPU0yhtBSULb36VpFWA@mail.gmail.com>
In-Reply-To: <CALaySJ+27gcT6x5BcKU1YHHv+xeaXDnxPU0yhtBSULb36VpFWA@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
Date: Thu, 2 Apr 2020 10:03:05 -0400
Message-ID: <CAC4RtVBy7iVT4NVLw14+=a1ksWrg35q+dsKfs+9r2poiVo3wkg@mail.gmail.com>
Subject: Re: NomCom eligibility & IETF 107
To: IETF discussion list <ietf@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Y5JTQQGWfFYn2qKZzHrlwlixvWw>
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, 02 Apr 2020 14:03:31 -0000

The IESG has listened to the discussion and has reconsidered.  We have
posted an Internet draft:
https://datatracker.ietf.org/doc/draft-iesg-nomcom-eligibility-2020/

Murray will be the shepherding AD, and will request a four-week last
call later today, to end on 30 April, the deadline we had set for
comments.  The following week (7 May) will have an IESG telechat, and
we would expect to have the document on that telechat agenda for
approval.

The substantive bit in the document is as I described in the message below.

Barry, for the IESG

On Tue, Mar 31, 2020 at 3:37 PM Barry Leiba <barryleiba@computer.org> wrote:
>
> While we are sorting this out, and whether we publish an Internet
> draft or not, I would like to know this:
>
> As I (Barry, not the IESG as a whole) currently read the rough
> consensus, considering what people have said the reasons you all have
> given, and the discussion of those reasons, I see things falling
> toward option 1.  Specifically, looking at RFC 8713, Section 4.14, FOR
> THIS NOMCOM CYCLE ONLY and SETTING NO PRECEDENT, I would replace the
> first two paragraphs this way:
>
>    Members of the IETF community must have attended at least three of
>    the last five in-person IETF meetings in order to volunteer.
>
>    The five meetings are the five most recent in-person meetings that
>    ended prior to the date on which the solicitation for NomCom
>    volunteers was submitted for distribution to the IETF community.
>    For the 2020-2021 Nominating Committee those five meetings are
>    IETFs 102, 103, 104, 105, and 106.
>
> The question I will ask is this: Is there anyone who *can't live with
> that outcome*?
>
> That question is not asking what you *prefer*; I've read all of those,
> and I am still collecting that input further.  But for the purpose of
> this question, does anyone think that outcome is so bad that you can't
> accept it?  If you can live with it, there's no need to respond.  Just
> let me know if you can't.
>
> Barry
>