Re: [Eligibility-discuss] AD Sponsorship of draft-moonesamy-recall-rev

"Pete Resnick" <resnick@episteme.net> Sat, 25 May 2019 22:33 UTC

Return-Path: <resnick@episteme.net>
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 4B6EC120045; Sat, 25 May 2019 15:33:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 KU0g44FYsnyC; Sat, 25 May 2019 15:33:44 -0700 (PDT)
Received: from episteme.net (episteme.net [216.169.5.102]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7B1D512007C; Sat, 25 May 2019 15:33:44 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by episteme.net (Postfix) with ESMTP id AC6C580FB4F8; Sat, 25 May 2019 17:33:41 -0500 (CDT)
Received: from episteme.net ([127.0.0.1]) by localhost (episteme.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id egx7GbJ9O72b; Sat, 25 May 2019 17:33:38 -0500 (CDT)
Received: from [172.16.1.18] (episteme.net [216.169.5.102]) by episteme.net (Postfix) with ESMTPSA id E290580FB4E9; Sat, 25 May 2019 17:33:38 -0500 (CDT)
From: Pete Resnick <resnick@episteme.net>
To: Suresh Krishnan <suresh.krishnan@gmail.com>
Cc: S Moonesamy <sm+ietf@elandsys.com>, chair@ietf.org, IETF Discussion <ietf@ietf.org>, John C Klensin <john-ietf@jck.com>, eligibility-discuss@ietf.org
Date: Sat, 25 May 2019 17:33:38 -0500
X-Mailer: MailMate (1.12.5r5632)
Message-ID: <EC966FE1-C1EE-453F-A66E-61B007293792@episteme.net>
In-Reply-To: <82E6BD6B-41F4-4827-8E18-3FF63511DFEA@gmail.com>
References: <6.2.5.6.2.20190509041736.0d6d4548@elandsys.com> <f5834466-8f40-42bd-82d8-4dcb7d418859@www.fastmail.com> <6.2.5.6.2.20190509105617.0c08ef60@elandnews.com> <e854adaf-1ead-41d0-95bf-df56cb5a5914@www.fastmail.com> <6.2.5.6.2.20190514234822.0bc461f0@elandnews.com> <15BCE05FEA1EEA6AD0E7E5BD@PSB> <6.2.5.6.2.20190516103829.11f9fb18@elandnews.com> <E85C84CF-DB0B-410E-A0B2-A7C7E705E469@kaloom.com> <6.2.5.6.2.20190518141450.1163e590@elandnews.com> <82E6BD6B-41F4-4827-8E18-3FF63511DFEA@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/eligibility-discuss/2stIoS7Fl3cLAzVPfUBNOT1OL4g>
Subject: Re: [Eligibility-discuss] AD Sponsorship of draft-moonesamy-recall-rev
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: Sat, 25 May 2019 22:33:47 -0000

On 24 May 2019, at 18:54, Suresh Krishnan wrote:

>  One of the things that has kept the recall petitions rare is that 
> that the people who initiate the petition need to have some 
> accountability for doing so (I would call this “skin in the game” 
> [0] but it does not translate well across cultures). Otherwise there 
> will be no bar to filing frivolous petitions. This brings me to the 
> elephant in the room. It is fairly trivial for someone to sign up 10 
> remote participant identities to initiate a recall petition without 
> incurring much effort, for the *sole purpose* of starting a recall 
> petition. I would like to see some suggestions as to how we can ensure 
> that this would not happen.

It is not "fairly trivial" to sign up 10 remote participants for 3 out 
of the last 5 meetings just to game the system; that takes at least a 
year's worth of planning. That requirement (which has always been in the 
document) seems plenty high to prevent completely frivolous petitions. 
And note that even if there were frivolous petitions (and I think it is 
highly unlikely), this would simply be a DOS attack on recall 
committees, not a way to remove an AD or IAB member.

Even if you think that the one year of planning is not enough to 
discourage silliness, there are other potential simple solutions (e.g., 
half of the petitioners must be non-remote registrants, etc.).

I think the concerns here are overdone.

pr
-- 
Pete Resnick http://www.episteme.net/
All connections to the world are tenuous at best