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

Abdussalam Baryun <abdussalambaryun@gmail.com> Tue, 28 May 2019 17:54 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 B028512022E for <ietf@ietfa.amsl.com>; Tue, 28 May 2019 10:54:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level:
X-Spam-Status: No, score=-1.997 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, 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 1X-FsWS-WxHG for <ietf@ietfa.amsl.com>; Tue, 28 May 2019 10:54:52 -0700 (PDT)
Received: from mail-oi1-x22d.google.com (mail-oi1-x22d.google.com [IPv6:2607:f8b0:4864:20::22d]) (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 C49D612021B for <ietf@ietf.org>; Tue, 28 May 2019 10:54:52 -0700 (PDT)
Received: by mail-oi1-x22d.google.com with SMTP id a132so14993965oib.2 for <ietf@ietf.org>; Tue, 28 May 2019 10:54:52 -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=yCaVBbORd1SOOYIjMDfXOHAcHNQ5cT6kLRYA5th4drE=; b=ot/uT74D8jXKqBqQD/PcJjvhtoArSwUU6m1ksPaFodGj7BXaAVNqrw+YMAEasXbLzm H9h+ImiEz4WYwySl2d210jZ4LaVF443KmyWXoCx99+sTOgjoix7eZWjgs3nyrlufAwzg cp/e8N4DmcSKhO8rtEiP1X26K3u/KVAc+dPSoLTKkxn41ojEqJCkG7dbAp3MKAkQMHuZ rVcEHFf+PnsA9C/J9Y9TQY0/8LaoTGQSYX8MXUcMmS1S9cXuJgjgqzCOYR9zirfyQHty R/xTXdTpOVi3RxqKdAFkbPqZ9splTC+MfRmT7/OwSFL9jxv8CF3GNXyNdXrx7gA0rz85 wHSw==
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=yCaVBbORd1SOOYIjMDfXOHAcHNQ5cT6kLRYA5th4drE=; b=gnXnR2+af2YZCo9NaqwcyWB6T2IvpCc/q6t4jRIIS+xOQtqh3i5XcgzAV5st55ON8w OaugFcNIK9zm8nPjojkp8t2x4IqlY2HAofZdjFMciNUT8dKn8/G1mL/R3d3jDdp7GieK yP5nWdgDTXaGGrQTsnvqLyTOyVRInINiYzwiwnwfmcnKEbOq3VQNsrN3/RSxxtfdRZWQ 7Z5X/J9y/yziUrJT9Xo3V7kIzx6TveTT1swxCsxzdknCzD4pFP9bMeAmXxuUH84D6hQ+ ZSZaQfYv1KCbx7+Cc57O4ToObeTDyvgpE3yort7P5SuDGt8D9Uj+epZ+gUGxIbuptwRi 13Gw==
X-Gm-Message-State: APjAAAVQ1m3V7QAWI9Bs9MHehVyOYMa8/df5/gIE0urrSRvXA+XhnC3w AU4aRZ23FH/kPNmE17xVnhrJhEdL3ZLgQTm3zgg=
X-Google-Smtp-Source: APXvYqxoh6xa3rpjTjktIhm9AUEM3rN2Z7LxaOyKpVsS18yKzBC4kOY0dAPpC6t5t1y3uuohPqAmFA7rYqOZrSrJUMI=
X-Received: by 2002:aca:4750:: with SMTP id u77mr3537216oia.134.1559066092131; Tue, 28 May 2019 10:54:52 -0700 (PDT)
MIME-Version: 1.0
References: <CADnDZ88hUXDe+tmaOs0BmjHT+iei7cyYF2CeDZuczdS_PV9YFA@mail.gmail.com> <CAC8QAcdxLgPah=c0t2=CigYJsHwb87adVC_WFRUL1PqJ9SFewQ@mail.gmail.com>
In-Reply-To: <CAC8QAcdxLgPah=c0t2=CigYJsHwb87adVC_WFRUL1PqJ9SFewQ@mail.gmail.com>
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
Date: Tue, 28 May 2019 19:54:39 +0200
Message-ID: <CADnDZ89FeA7Q-+57fFntG9VbBJyYLyy85xHk-p2eA2o9bAUXCw@mail.gmail.com>
Subject: Re: [Eligibility-discuss] AD Sponsorship of draft-moonesamy-recall-rev
To: sarikaya@ieee.org
Cc: ietf <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000009a5a370589f65c53"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/uIcnf1y0ncl_BGKsRBU0DTFyFeM>
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: Tue, 28 May 2019 17:54:56 -0000

On Mon, May 27, 2019 at 4:59 PM Behcet Sarikaya <sarikaya2012@gmail.com>
wrote:

>
>
> On Mon, May 27, 2019 at 4:09 AM Abdussalam Baryun <
> abdussalambaryun@gmail.com> wrote:
>
>> 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 .
>>
>
> I am against remote participating fees. If imposed there might be many no
> shows in WG session presentations.
> Also people get into the remote use spontaneously.
>

I understand. Are you against it if the fee is 3 dollars per year? it can
help to identify participants because they will pay it, also it can be a
good idea to leave known participants (registered more than two meetings)
and WG-draft-authors without payment.

>
>
>> 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.
>>
>>
> I think a reasonable action is to reduce daily participation fees which is
> currently half of the full fee, i.e. the current fee is not proportional.
>

I agree but it is the meeting cost problem that increases that, so IETF
managers need to work on attracting more participants and I think that is
challenging.

AB

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