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

Abdussalam Baryun <abdussalambaryun@gmail.com> Mon, 27 May 2019 09:08 UTC

Return-Path: <abdussalambaryun@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 9D54C1200C4 for <ietf@ietfa.amsl.com>; Mon, 27 May 2019 02:08:40 -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_HELO_NONE=0.001, SPF_PASS=-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 ucn8r7XtcDU4 for <ietf@ietfa.amsl.com>; Mon, 27 May 2019 02:08:38 -0700 (PDT)
Received: from mail-ot1-x343.google.com (mail-ot1-x343.google.com [IPv6:2607:f8b0:4864:20::343]) (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 3C7C212004B for <ietf@ietf.org>; Mon, 27 May 2019 02:08:38 -0700 (PDT)
Received: by mail-ot1-x343.google.com with SMTP id s19so14211804otq.5 for <ietf@ietf.org>; Mon, 27 May 2019 02:08:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to:cc; bh=43xD88ECHeu512/MoKYpz0+snHjWNPRZ/tjB2oMerec=; b=GG4b3+X9ve9vJJTOb+1eeyWZgvOaQk9R9k6Ue8N9oWD++rOUsN/EGkfUfQgMzrN99+ NaHc07EXF2c8lyjBg6Bl3mgKqWJ+ivffw5RONxYMadxlUm+5GVLQYdSP1HrgRA1/cetV GABFymV1fHgpR4YZeVPuFtS2f7657H7EfEZkP2KzznjRHNl8y/hNAoBsYqWRo8lDHelX 2N6Q0eJybUaG/5eUuu60jR5jXSFCFb/fFPxuDV+w5FX/3a8qMOTQ9+rJvPuRIQNxc6e2 oaXn8UNqzgm3jtn79r/e3S7kqQXzaoAqwJ37lKjtRVSdcqTBwqeeshQx/B4ZBHqxBYLC yoqg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=43xD88ECHeu512/MoKYpz0+snHjWNPRZ/tjB2oMerec=; b=Ji5DOizpR8i+4Zrr3zcluzQzp4yqgUGjM7+TNBoKnumpFSEuT59jNp3T6dCsUQKBfT 3mLdIyc+A7NG3/wvV5d0Z9wOwkIIOkhHYEABicvqd2S3It6UEnNH6Rov1DdqWDZ2jXJv 7bkpBX04NJbhRfrf7M6+4nVorKvXUjpRbqQEYRn28LCP5GlXDLMe6K870E6TCfmW9b3X KBP2zSx7HmW2RBxRLlc3uLtDbD8SGJRT3N9oasapZqktpwpe5iYrHiNIrv2MYwk3OAof hpGwfFu2+uAdMCL/EAWswAWzs4g+ukQ1Ell95Hz5u105EK3E9HSX5KTd7GzGkDBU5mdi 6SRQ==
X-Gm-Message-State: APjAAAWlQG0iEHrzlnD0GttMvGDULdVWufMOQuANiZqXa9fRJPDLW7Eg VMQx8c+VZZzUJoFwQKfObbCl7Z5LxgdkF7tRlPRPrmAR
X-Google-Smtp-Source: APXvYqxmXwsutmRP3uomSegAnE6cf+6pFXWtRRgEVLetVErtYK2FCodP8OqsCiOQ85jNJXA+SSaMAii8CQcHhm2MPpM=
X-Received: by 2002:a9d:7c95:: with SMTP id q21mr50338787otn.44.1558948117441; Mon, 27 May 2019 02:08:37 -0700 (PDT)
MIME-Version: 1.0
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
Date: Mon, 27 May 2019 11:08:16 +0200
Message-ID: <CADnDZ88hUXDe+tmaOs0BmjHT+iei7cyYF2CeDZuczdS_PV9YFA@mail.gmail.com>
Subject: Re: [Eligibility-discuss] AD Sponsorship of draft-moonesamy-recall-rev
To: ietf <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000c370e10589dae4cd"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/fFvWONwgz85xiGhqcUdjZjWxr68>
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: Mon, 27 May 2019 09:08:41 -0000

I think this issue of fees is complicated in IETF and makes participants
less, however, there are good reasons to make suitable fees for
participation. I would think that adding remote participation fees is good,
because it will make IETF more serious in its responsibilities toward
remote participants . One of the IETF problem is that it does not want to
recognise participants as members or with titles as it only does for IETF
ADs and WG chairs. If the IETF does change that then yes it will solve the
main problem and make its fees reasonable with rights.



On Sun, May 26, 2019 at 11:02 AM Loganaden Velvindron <loganaden@gmail.com>
wrote:

>
> 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.
>

I agree, it should be reasonable and gain rights,


>
> 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 ?
>

I think it is a great idea, and important for IETF.

Best Regards
AB