Re: [Eligibility-discuss] Discussion at gendispatch?
Michael Richardson <mcr+ietf@sandelman.ca> Thu, 07 November 2019 22:57 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 1994D12085B for <eligibility-discuss@ietfa.amsl.com>; Thu, 7 Nov 2019 14:57:18 -0800 (PST)
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 58zjD1c8PQfs for <eligibility-discuss@ietfa.amsl.com>; Thu, 7 Nov 2019 14:57:15 -0800 (PST)
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 828271200D7 for <eligibility-discuss@ietf.org>; Thu, 7 Nov 2019 14:57:15 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 1ED983897B; Thu, 7 Nov 2019 17:54:15 -0500 (EST)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 5C3C45E4; Thu, 7 Nov 2019 17:57:12 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: John C Klensin <john-ietf@jck.com>, eligibility-discuss@ietf.org
In-Reply-To: <779A84AD78B58E0DD0729F1C@PSB>
References: <A809A60C-D235-479D-8239-85332AC0569B@episteme.net> <6.2.5.6.2.20191106061852.12a70190@elandnews.com> <1A26C4AF-E579-4215-AC2C-0E470616DC63@episteme.net> <779A84AD78B58E0DD0729F1C@PSB>
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: Thu, 07 Nov 2019 17:57:12 -0500
Message-ID: <25787.1573167432@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/eligibility-discuss/5_q_VheSqzgcsds04Z2sDEd8mJs>
Subject: Re: [Eligibility-discuss] Discussion at gendispatch?
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: Thu, 07 Nov 2019 22:57:18 -0000
John C Klensin <john-ietf@jck.com> wrote: > This is fine with me with, as is my wont, a few qualifications > and concerns: I think that you dip into the weeds, and it will attract rats/ratholes. > (1) Whether it should be possible to initiate a recall from a > petition all of whose signatories are remote or if we need to > require some signatures from people who are nomcom-qualified or > at least attend some meetings in person? Let me rephrase. 1) Are exclusively remotely-enfranchised people in a different category than onsite-enfranchised people? > (2) Whether people with some special historical status wrt the > IETF such as having been Nomcom-qualified at some point, having > RFCs published in the IETF Stream, having been a WG Chair or > member of the IAB or IESG, having attended some number of > meetings, etc., should have special status wrt signing recall > petitions? And, if so, what good does it do them or the > community? 2) whether previously onsite-enfranchised people should have some lower bar for becoming remotely-enfranchised? NEVER mind the detail of how WG chair, RFC, etc. contributes to being remotely-enfranchised. The question is whether there are two categories or three. > (3) Whether members of an I* body should be treated in some > special way wrt recalls. It has been pointed out that, if the > number of required signatures is reduced to 10, the IESG > doesn't need special provisions to initiate a recall all by > itself. But that turns the question around, to, e.g., whether > the members of an I* body (or more than one of them) should be > allowed to initiate a recall on their own or whether some > external signatures should be required. 3) are I* people enfranchised. > (4) Whether registration should be sufficient to count as remote > participation or whether, e.g., someone should be required to > sign into some WG sessions in Meetecho as a participant? If the > answer to this question is "yes", should signing at least some > WG blue sheets (rather than, e.g., paying the registration fee > and spending the week at the beach or bar) be required for > nomcom-eligibility 4) what is the definition of attendance/participation? (this is where WG chair,RFC, etc. could be discussed) > In addition, and drawing inspiration [1] from an ICANN call a > few of hours ago, we know from other bodies and even some IETF > experience that two ways to kill an idea are to either keep > changing the discussion venue or to deal with the report of one > committee by creating a new committee. Noting that the modern > incarnation of this effort was an IETF list discussion and I-D > posted in the first quarter of the year, a demand for a BOF, an > discussion of virtual BoFs that distracted almost everyone from > the issue(s), a discussion that was moved to this list (and, in > the process, nearly killed off), then an interim meeting that > took months to organize, I think any discussion at gendispatch > should (MUST?) be carefully scoped and constrained so as to > prevent yet another diversion. Hmm, interesting observation. I would like to add that restricting the discussion to recall (which has only happened once) also seems to be a way to put off discussion of enfranchisement for selection, rather than recall. -- ] Never tell me the odds! | ipv6 mesh networks [ ] Michael Richardson, Sandelman Software Works | IoT architect [ ] mcr@sandelman.ca http://www.sandelman.ca/ | ruby on rails [ -- Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works -= IPv6 IoT consulting =-
- [Eligibility-discuss] Discussion at gendispatch? Pete Resnick
- Re: [Eligibility-discuss] Discussion at gendispat… S Moonesamy
- Re: [Eligibility-discuss] Discussion at gendispat… Pete Resnick
- Re: [Eligibility-discuss] Discussion at gendispat… John C Klensin
- Re: [Eligibility-discuss] Discussion at gendispat… Pete Resnick
- Re: [Eligibility-discuss] Discussion at gendispat… John C Klensin
- Re: [Eligibility-discuss] Discussion at gendispat… Pete Resnick
- Re: [Eligibility-discuss] Discussion at gendispat… S Moonesamy
- Re: [Eligibility-discuss] Discussion at gendispat… Michael Richardson
- Re: [Eligibility-discuss] Discussion at gendispat… John C Klensin