IETF Logo Mail Archive

Re: [Eligibility-discuss] enfranchising mostly-remote participants

Michael Richardson <mcr+ietf@sandelman.ca> Tue, 29 October 2019 02:44 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: eligibility-discuss@ietfa.amsl.com
Delivered-To: eligibility-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7AA1212013A for <eligibility-discuss@ietfa.amsl.com>; Mon, 28 Oct 2019 19:44:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 Cs9Xx4X36TZT for <eligibility-discuss@ietfa.amsl.com>; Mon, 28 Oct 2019 19:44:32 -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 94436120047 for <eligibility-discuss@ietf.org>; Mon, 28 Oct 2019 19:44:32 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id CA14C3897A; Mon, 28 Oct 2019 22:41:48 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 374643BF0; Mon, 28 Oct 2019 22:44:31 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "Salz, Rich" <rsalz@akamai.com>
cc: "eligibility-discuss@ietf.org" <eligibility-discuss@ietf.org>
In-Reply-To: <A5F075E4-D74E-4AF0-A8D8-BDF37A8EE8E2@akamai.com>
References: <19743.1572014559@localhost> <A7577125-8E9F-46E9-8918-F1197B521208@akamai.com> <30298.1572275585@localhost> <A5F075E4-D74E-4AF0-A8D8-BDF37A8EE8E2@akamai.com>
X-Mailer: MH-E 8.6; nmh 1.7+dev; GNU Emacs 24.5.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: Mon, 28 Oct 2019 22:44:31 -0400
Message-ID: <25365.1572317071@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/eligibility-discuss/VfGXksE1BcuGjoNqzvCxNf7APzQ>
Subject: Re: [Eligibility-discuss] enfranchising mostly-remote participants
X-BeenThere: eligibility-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <eligibility-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/eligibility-discuss>, <mailto:eligibility-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/eligibility-discuss/>
List-Post: <mailto:eligibility-discuss@ietf.org>
List-Help: <mailto:eligibility-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eligibility-discuss>, <mailto:eligibility-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Oct 2019 02:44:35 -0000

Salz, Rich <rsalz@akamai.com> wrote:
    >> Do you mean, how often do IESG seats need to be filled during a nomcom-term,
    >> or do you mean, how often do NOMCOM members need to be replaced?

    > I meant the latter.

I'm unaware of a nomcom that replaced a member.

In one that I was involved (as a voting member), one member simply fell off
the planet.  We proceeded with 9 members according RFC7437 section 5.7,
second last paragraph.

Otherwise, the selection process is run again.
If that has occured, I'm unaware of it.

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

v2.23.0 | Report a Bug | By Email