Re: NomCom eligibility & IETF 107

Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Wed, 01 April 2020 00:25 UTC

Return-Path: <spencerdawkins.ietf@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 306703A0E1C for <ietf@ietfa.amsl.com>; Tue, 31 Mar 2020 17:25:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.197
X-Spam-Level:
X-Spam-Status: No, score=-0.197 tagged_above=-999 required=5 tests=[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 0fW8GEGxQzrM for <ietf@ietfa.amsl.com>; Tue, 31 Mar 2020 17:25:13 -0700 (PDT)
Received: from mail-lj1-x22e.google.com (mail-lj1-x22e.google.com [IPv6:2a00:1450:4864:20::22e]) (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 504143A0E18 for <ietf@ietf.org>; Tue, 31 Mar 2020 17:25:13 -0700 (PDT)
Received: by mail-lj1-x22e.google.com with SMTP id n17so23946278lji.8 for <ietf@ietf.org>; Tue, 31 Mar 2020 17:25:13 -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=92sPkQRL3SFiQVCLxByBXczpQEidlstHpspakoJY+Tg=; b=tq0yFbC0R98R7R6mchzQHEW4XtnWEmB7dJDJDWED1Kt0DWd6rYcXev/w5peHmKAjvF OKuBpMcyYfRReL7OyQ3D8rmcd0PDc5fkeio4BufyAff26+z2FgCCvuZykIMWgCO9y2ys p26LU50hHEVszllGsEpXCli/hIIPrcMn/YChcWc6q45Koht5EfwNl6foaeieOwa9YFIO 8hu3bFNZvYDOO1dowajjipRCYpT7Zd6hN96Lui3b39CLfwwEJGtOjKukpVaShQOobcRu 9AdWQ4b10G8uGpeqsvpPTWDqUBpJuIvdB7c8IFGNwDHFegmL7M0jL+o9VYx47NzcQ+GG peew==
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=92sPkQRL3SFiQVCLxByBXczpQEidlstHpspakoJY+Tg=; b=Krh0AfOu6sWSEYbyFqlG/Fd23gxEgoZn9lM71+ceWBvnDNj9aD5jNJ65EaOrdQw4iQ V+VNv+dgzOMlmmXdgBD1dSzN2X2HYLjMZGmbBWqq/y1MnccCt9Pf4VcaNqTgKmduK894 2jgY6g405dxzDUl5D8Ar20YTlqXN5aZUu+jtamFVOGFx18y+Cum0GVMKpDzsVPo5Hf+Z M3y070Qs9FINZAROROoUpjPoFGd0gj3/K3fwmai22lX1dy1Lp1LvGQ4AOiTQpFU545FY fPooQ6iA0Zg049wVDNfNrP071MtZyl6oHZ9GJfaTsZa1HOQnPhGkdmPPcIU44N0facz1 nuLg==
X-Gm-Message-State: AGi0PubsEVbSYRYim4euX4UtHLTJDxEix0fLraeD2afaXJ8yIC0wa3Ha E7LtOtmxScTYq+54rjTPLQ0nlA+CRDPlcTZ0YJi2XDzw
X-Google-Smtp-Source: APiQypKZAjmQYz3RWvqn3gobLHvbmKNIXHGIQmyqpSKxVoVC8fLBf45jutKpg1dNvS7y5Ik0VODS3M5GsrRHjHg7lu0=
X-Received: by 2002:a05:651c:23b:: with SMTP id z27mr3788790ljn.125.1585700711382; Tue, 31 Mar 2020 17:25:11 -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: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Tue, 31 Mar 2020 19:24:45 -0500
Message-ID: <CAKKJt-db9ys5nPQEUyocNm3VcR5ZDeSP_GTE1Gmp17tUxjMe1w@mail.gmail.com>
Subject: Re: NomCom eligibility & IETF 107
To: Barry Leiba <barryleiba@computer.org>
Cc: IETF discussion list <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000009f41a005a22fb77c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/o2ZNfW7HTt7S0DqN0yFcLcHHc-s>
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: Wed, 01 Apr 2020 00:25:16 -0000

Hi, Barry,

On Tue, Mar 31, 2020 at 2: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.
>

Bike, meet shed.

I'd suggest this for the last sentence:

   Because no IETF 107 in-person was held, 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*?
>

I could live with that, either with or without my suggested text, of course.

Best,

Spencer


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