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

"Theodore Ts'o" <tytso@mit.edu> Sat, 25 May 2019 23:09 UTC

Return-Path: <tytso@mit.edu>
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 2F07A120045; Sat, 25 May 2019 16:09:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-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 qxtlBpHPk2hn; Sat, 25 May 2019 16:09:15 -0700 (PDT)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3F1FE12002F; Sat, 25 May 2019 16:09:14 -0700 (PDT)
Received: from callcc.thunk.org ([66.31.38.53]) (authenticated bits=0) (User authenticated as tytso@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id x4PN8Pck001024 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Sat, 25 May 2019 19:08:28 -0400
Received: by callcc.thunk.org (Postfix, from userid 15806) id 55494420481; Sat, 25 May 2019 19:08:25 -0400 (EDT)
Date: Sat, 25 May 2019 19:08:25 -0400
From: Theodore Ts'o <tytso@mit.edu>
To: Pete Resnick <resnick@episteme.net>
Cc: Suresh Krishnan <suresh.krishnan@gmail.com>, John C Klensin <john-ietf@jck.com>, chair@ietf.org, S Moonesamy <sm+ietf@elandsys.com>, eligibility-discuss@ietf.org, IETF Discussion <ietf@ietf.org>
Message-ID: <20190525230825.GB10378@mit.edu>
References: <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> <EC966FE1-C1EE-453F-A66E-61B007293792@episteme.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <EC966FE1-C1EE-453F-A66E-61B007293792@episteme.net>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/eligibility-discuss/ZXW-PA5vUIuXTLFUwGer7FlqFKQ>
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 23:09:17 -0000

On Sat, May 25, 2019 at 05:33:38PM -0500, Pete Resnick wrote:
> 
> 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.).

Another thing perhaps to consider would be to start charging at least
some amount of money to register as a remote participation.  That
money can be used to fund and improve the remote participation tools.
(Since remote participants would become paying customers, there would
be an expectation that quality provided to the remote participants
would have meet a minimum quality bar --- which is a feature, not a
bug.)

People can disagree about how likely that redchan or gab.com
participants would try to game the system in the future (perhaps it's
not likely, but the Linux Kernel development community has not been
immune from their interest), but requiring a real registration fee
would no doubt decrease that risk.  Futhermore, since we've already
decided that it's OK to require a registration fee for in-person
attendance, requiring something similar for remote participants ---
since the claim is that they should have all of the rights and
responsibilities pertaining thereto --- would seem only fair.

Just a thought.

						- Ted