Venue for post-IETF 107 Nomcom eligibility discussion (was: Re: NomCom eligibility & IETF 107)

Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Mon, 16 March 2020 15:51 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 29DAC3A0C0B; Mon, 16 Mar 2020 08:51:54 -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 OAYhoF9zNBsI; Mon, 16 Mar 2020 08:51:52 -0700 (PDT)
Received: from mail-lj1-x230.google.com (mail-lj1-x230.google.com [IPv6:2a00:1450:4864:20::230]) (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 A7AF23A0C6F; Mon, 16 Mar 2020 08:51:51 -0700 (PDT)
Received: by mail-lj1-x230.google.com with SMTP id w1so19260238ljh.5; Mon, 16 Mar 2020 08:51:51 -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=1LvEGqRUnNWFOPVVFi6eVvOcWcysg20t7GLONohMTvg=; b=ikjZnSCutS9d4Kl/fOQ2rLnUV4Ro5TwHFXaUhFiusy1nvId3bCqew4JA6O0EtQM0ot Hyxy6qtOX1940wshTcnTpGhviTdYc9o3XGysL+KRL99/h//RPes9mweYSSBNsEUsh632 dKvnnMUWl2E8w57yvTT0WhqPDkj7TgLzGmwdo2PVm49bds67b/AlOT1JdwJ0yOk94qVV INQub87DMZUQNzM5Qqc6aq0Sy46OSvEo8lkeD4ua9dpc5tdytJAeFaOhC9zEg6z134fV 2/KSyy8qUKLWnRVtiyfMKp0Tzhb0n0AQBUAiSEWs2nhwwELBnqbOHED8dJYwAEMlGnvC i3Nw==
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=1LvEGqRUnNWFOPVVFi6eVvOcWcysg20t7GLONohMTvg=; b=iK6p91XwUQuaU+MDdxhScCChDioHXWl4ja16p3UEauzseBUcvs9ROcuC7A5USXvDT7 UT5UmYhEgCwTmZW2AlZMOyBsqJwhJ6EBsogrVsv0Jglb03hgTSArRVjygJkPIimsHrzE yF+BLR1SJxhNnqO2OORgabmI8I1jbk9QuWwEh7YDHBKfoxp0C5ieAyG+MStf4AjXF9oz iYu8enYocnEQTjD5UEt5Pj+UqZmnUnnAXfYrVj3z4M7/SayTfurX1UDZyOhqGcKwQY2n tTUOnWeALKgljXdKmIDn2faoPBTt97orMbcAgMeayxtZf5pyR9xh6LPDmCaZMA8GSVxn es/A==
X-Gm-Message-State: ANhLgQ1+okX/1Lv5ZkfVCFmKwsMlS/+czp0W5CbXVgf2gsZaPFrzawU6 06B1oeP8VBbRqLXS58DeBh19uQdEYmd2VPfJEHSRaAPo1R4=
X-Google-Smtp-Source: =?utf-8?q?ADFU+vsUulB8+7kzUkzAvk8yLX9sw0hdJNJZP4iZeVAa?= =?utf-8?q?JmTfXsQCTM6RCMgfAgWTrJV/I1BEiZSqUbn5xkhpndEtKmg=3D?=
X-Received: by 2002:a2e:804b:: with SMTP id p11mr6891ljg.50.1584373909549; Mon, 16 Mar 2020 08:51:49 -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> <CAA=duU0jN0y12_HpzzK73BRD+x19ZQn74V=ju2_wwS-RUL_9Yw@mail.gmail.com> <CALaySJ+r2OrFVbZj=3fTRUapkDkxap2T-p+QzNfaqK4N0c+haQ@mail.gmail.com>
In-Reply-To: <CALaySJ+r2OrFVbZj=3fTRUapkDkxap2T-p+QzNfaqK4N0c+haQ@mail.gmail.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Mon, 16 Mar 2020 10:51:23 -0500
Message-ID: <CAKKJt-eR8V=1mfvkww+DMOhzsUizkDvPyiaoHSy94DYDYor+EA@mail.gmail.com>
Subject: Venue for post-IETF 107 Nomcom eligibility discussion (was: Re: NomCom eligibility & IETF 107)
To: gendispatch-chairs@ietf.org, Alissa Cooper <alissa@cooperw.in>
Cc: IETF discussion list <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000011f62705a0facc98"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/GNsjtMtWUK7imubK6nzKYu_X8Og>
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: Mon, 16 Mar 2020 15:52:05 -0000

Replying to Barry's note, but the intended audience is the GEN AD and
GenDispatch chairs ...

On Fri, Mar 13, 2020 at 6:55 PM Barry Leiba <barryleiba@computer.org> wrote:

> Just a reminder: for the purpose of THIS discussion, we just need to
> figure out what to do for THIS NomCom selection, which will happen before
> IETF 108.  Of course, that NomCom might have to sort out how to do its work
> completely remotely, but that’s its job, not ours.
>
> For the longer term, we need to decide if and how to give NomCom
> eligibility for remote participation, but let’s please not try to do that
> in THIS discussion.  There will be a GenDispatch session on 23 March, and I
> strongly encourage people to get time on the agenda and make a proposal
> there for work on that topic.
>

For what it's worth, there's already an "IETF-Nomcom" discussion mailing
list, intended for just such conversations, at
https://www.ietf.org/mailman/listinfo/ietf-nomcom.

Is there a recommendation whether we use that list, or gendispatch, or
something else? I'm assuming everyone is hoping for more than just a new
thread on the IETF discussion list ...

Best,

Spencer