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

John C Klensin <john-ietf@jck.com> Sun, 26 May 2019 02:24 UTC

Return-Path: <john-ietf@jck.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 29B9E120086; Sat, 25 May 2019 19:24:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.106
X-Spam-Level:
X-Spam-Status: No, score=-1.106 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RDNS_NONE=0.793, URIBL_BLOCKED=0.001] autolearn=no 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 T6KbGSTiusAU; Sat, 25 May 2019 19:24:41 -0700 (PDT)
Received: from bsa3.jck.com (unknown [65.175.133.137]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EEE7512001E; Sat, 25 May 2019 19:24:40 -0700 (PDT)
Received: from hp5.int.jck.com ([198.252.137.153] helo=JcK-HP5.jck.com) by bsa3.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1hUipn-000L43-2S; Sat, 25 May 2019 22:24:27 -0400
Date: Sat, 25 May 2019 22:24:22 -0400
From: John C Klensin <john-ietf@jck.com>
To: Theodore Ts'o <tytso@mit.edu>, Pete Resnick <resnick@episteme.net>
cc: IETF Discussion <ietf@ietf.org>, eligibility-discuss@ietf.org
Subject: Re: [Eligibility-discuss] AD Sponsorship of draft-moonesamy-recall-rev
Message-ID: <A754A84567E9C14C2B777F3E@JcK-HP5.jck.com>
In-Reply-To: <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> <20190525230825.GB10378@mit.edu>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/QR2Pdesq7S_6lDwg6Uys8euyqag>
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: Sun, 26 May 2019 02:24:42 -0000

Ted,

FWIW, I've suggested this several times for a variety of
reasons, including suggestions that the fee be adjusted if
needed to reflect the differences between industrialized and
less- developed countries.  Money on the table is not a really
good measure of actual intent to participate (rather than, e.g.,
to troll) but it would certainly help.

  john


--On Saturday, 25 May, 2019 19:08 -0400 Theodore Ts'o
<tytso@mit.edu> wrote:

> 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