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

Iyedi Goma <iyedigoma@gmail.com> Sun, 26 May 2019 10:14 UTC

Return-Path: <iyedigoma@gmail.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 ECF5A120052; Sun, 26 May 2019 03:14:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 1atphPJDj_wz; Sun, 26 May 2019 03:14:21 -0700 (PDT)
Received: from mail-qk1-x736.google.com (mail-qk1-x736.google.com [IPv6:2607:f8b0:4864:20::736]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ADD4C12015B; Sun, 26 May 2019 03:14:21 -0700 (PDT)
Received: by mail-qk1-x736.google.com with SMTP id z6so13920294qkl.10; Sun, 26 May 2019 03:14:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=pmdHZP6idih1ICBrgTKUUw93zAIDnEwBSANqbEKFbyI=; b=foIQaH23KvtSGrCMbuI7m7yCzbX5IbmAEsmrcrXrAM8Mcr6h/BtvmqYB03nxYOI/BU 3wvkjE9f1uQOWjc9I2HU6Ab/8lhbB3n60Y5qv0q/o1xjf0vaxxxyi3BaBwGm7XLOSmMs zkOj+U467Gu1aLJRf378hQYPnj7dIoepg180+Y97z3+Mi4OEbA1f+9ANW7cs+dcUr5TH RolMhvIk1u7RYW4PJ83931QhDPtpH1e37oSUW638uyVZp15Qq6xybeghAh+VPH4wAxqa 5NSC85niQ/yG8jRFuLZRZ7mjYy+8Fh3VqgPFvZu2YuA9CJjBOn8+sFBElH/YC3vR4l+q Wqng==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=pmdHZP6idih1ICBrgTKUUw93zAIDnEwBSANqbEKFbyI=; b=hXR4hzOXpH1Jmd4JtSGpehkTA1tLFw0ByiR10oTfi/M1NxvlPgATyCXOHO94lHnrQW X3nBApwD2VV3wIncPz+O4Fyl5KkVw1grv+XsaO4MpPDXFTBDNVlIixps8pwplPuzi6kY jFWmAHH+6bfXCuwdgplCmBH9Fe9uV/qJyEfh2LSUaIVvLTjmG4IeB6EECTSIhbR3c238 ZyswZgj7r0ONpVD0wN9DKtg/dd74NOTOYAj+W5IxC8xCi4f7aWTqkUwhulFkGjR5Zg9u 8/HVC+tSrapdQv7cgqwFOxbVx2fuQYRHxH7ir6Aa7m04JAQwnCvATsonVpMyqC/Yd6Lw Dz9A==
X-Gm-Message-State: APjAAAUC/J/Q3UysaC7TrSMFM0ZKdifbLRS7C676nCGraeEt0IiUHj11 f8n6ndvtvIYwvr0bSOisVZN9mgEDhUTFPjvSkk8=
X-Google-Smtp-Source: APXvYqwuRegBBMii262HEy0b3kb6FxSZLDVWZvP8EIg4/od8GIyLXdyFUg2sGyeIGkwTPSvf1O6AADIl7vR2TBWWk3g=
X-Received: by 2002:a0c:c14d:: with SMTP id i13mr74629203qvh.244.1558865660825; Sun, 26 May 2019 03:14:20 -0700 (PDT)
MIME-Version: 1.0
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> <CAOp4FwTOU481VW0XsWGFOL52+gT2zEL37ut0ysROVWiysyfOVA@mail.gmail.com>
In-Reply-To: <CAOp4FwTOU481VW0XsWGFOL52+gT2zEL37ut0ysROVWiysyfOVA@mail.gmail.com>
From: Iyedi Goma <iyedigoma@gmail.com>
Date: Sun, 26 May 2019 11:14:08 +0100
Message-ID: <CAAqM9kGdyZ-beZG=8jMu0apfeE1aJuqB7Gq5+LdxWTv1XrwgRg@mail.gmail.com>
Subject: Re: [Eligibility-discuss] AD Sponsorship of draft-moonesamy-recall-rev
To: Loganaden Velvindron <loganaden@gmail.com>
Cc: Theodore Ts'o <tytso@mit.edu>, IETF Discussion <ietf@ietf.org>, S Moonesamy <sm+ietf@elandsys.com>, eligibility-discuss@ietf.org, chair@ietf.org, John C Klensin <john-ietf@jck.com>, Pete Resnick <resnick@episteme.net>
Content-Type: multipart/alternative; boundary="000000000000f759bc0589c7b1c2"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/TY4zXnSXh9fHNlBV1Ll_7ux9rnY>
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 10:14:24 -0000

hello Loganaden
thanks for raising this point



Le dim. 26 mai 2019 à 09:55, Loganaden Velvindron <loganaden@gmail.com> a
écrit :

>
>
> On Sun, May 26, 2019 at 3:09 AM 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.
>>
>>
>> [Speaking as the organizer of an ietf remote hub from Mauritius]
>
> We've been contributed patches for TLS 1.3, IPv6, DNS, http451 in open
> source
> projects during the IETF hackathons. We're also working on a few drafts.
> We have a lot
> of high school and university students among ourselves.
>
> We're OK with paying the registration fees provided that they are
> reasonable.
>
> There are countries such as Madagascar who are trying to organize their
> own IETF
> hubs but their Cost of living is lower than us. What is reasonable to us
> might be expensive
> to them.
>
> Could there be a remote registration fee calculated per country ?
>
>
>