Re: [ietf-nomcom] Comments For I-D: draft-moonesamy-nomcom-eligibility-00)

Abdussalam Baryun <abdussalambaryun@gmail.com> Sun, 30 June 2013 19:10 UTC

Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf-nomcom@ietfa.amsl.com
Delivered-To: ietf-nomcom@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 10CAD21F9C3E for <ietf-nomcom@ietfa.amsl.com>; Sun, 30 Jun 2013 12:10:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Dx5GtZjnQChs for <ietf-nomcom@ietfa.amsl.com>; Sun, 30 Jun 2013 12:10:52 -0700 (PDT)
Received: from mail-pd0-x229.google.com (mail-pd0-x229.google.com [IPv6:2607:f8b0:400e:c02::229]) by ietfa.amsl.com (Postfix) with ESMTP id 74B3B21F8FBE for <ietf-nomcom@ietf.org>; Sun, 30 Jun 2013 12:10:52 -0700 (PDT)
Received: by mail-pd0-f169.google.com with SMTP id y10so2073773pdj.0 for <ietf-nomcom@ietf.org>; Sun, 30 Jun 2013 12:10:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=EmMaocAqj7Hg9V1fzJG4e1/9b29M/9Fpzk9v+lOpPS4=; b=lFBv4lKoBToHrRjRhHIqN8/gZWp9dfSWqiT9feM4nGyXWGvPeqCW2IrOtb8LquJ5cL SieR3Pfuda34rC5Jcr3I63gRu5I7xs6UJr6jJKSsHeyJwC3dATXAq8fXMr4qLQ753CGw iWAKbobGqvlmepd6de30taOxXJhGsy+ddyX+ZraitANrhJZECXykSMXaRBa6+2KEZdYE YsWV6rzC40xiStPJwEI3OtOHN71Osvpkeg4EUUXPEN8B0USGDrJAiMYB3FobKVakAORH uar2DWylixMRdCeWeOhI6OnUXCNm76uUaopibXCP/vzgZgm5pqtOWP47spudyIrv4du7 O/VQ==
MIME-Version: 1.0
X-Received: by 10.66.147.167 with SMTP id tl7mr20761250pab.40.1372619452210; Sun, 30 Jun 2013 12:10:52 -0700 (PDT)
Received: by 10.68.250.133 with HTTP; Sun, 30 Jun 2013 12:10:52 -0700 (PDT)
In-Reply-To: <6.2.5.6.2.20130629022022.0b9566e0@elandnews.com>
References: <CADnDZ88zC8PCY9rLZA3btffhiKT7YdxjrE6QTKYbm1gxqDwTbA@mail.gmail.com> <6.2.5.6.2.20130629022022.0b9566e0@elandnews.com>
Date: Sun, 30 Jun 2013 21:10:52 +0200
Message-ID: <CADnDZ8-SZ4EE2so8AtEPX81eptifuzDajKJX_7tdXyD2aNDZhA@mail.gmail.com>
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: S Moonesamy <sm+ietf@elandsys.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf-nomcom@ietf.org
Subject: Re: [ietf-nomcom] Comments For I-D: draft-moonesamy-nomcom-eligibility-00)
X-BeenThere: ietf-nomcom@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Discussions of possible revisions to the NomCom process <ietf-nomcom.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-nomcom>
List-Post: <mailto:ietf-nomcom@ietf.org>
List-Help: <mailto:ietf-nomcom-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 30 Jun 2013 19:10:53 -0000

Hi Moonesamy,

I support this work and my comments below;

On 6/29/13, S Moonesamy <sm+ietf@elandsys.com> wrote:

>>mention diversity in the draft related to members selected.
>
> The text in the draft is about IETF participants who were at the
> meeting site and IETF participants who were not at the meeting
> site.  The draft mentioned that some IETF participants cannot be in
> the room at the meeting site as they cannot afford the cost of
> travelling to that location.

IETF People are in the IETF-Rooms either physically or
virtually/remote, so all participants that SHOULD get this I-D's
Eligibility they SHOULD attend rooms physicaly/remotely for the five
meetings. The IETF has to get a system ready to register
remote-participants attending ROOMS, but we may need a condition on
how many rooms that thoes participants SHOULD attend and/or for how
long.

Please note that people may not attend meetings because their special
needs, you may add this important reason that the IETF needs to look
at giving chance to disabilities.

>
>>AB> I prefer if you refer me, or the discussion list chair can refer
>>me to somewhere we can discuss this new draft. Please note that I was
>>told not to post more discuss messages on this list, so the chair or
>>you are required to respond on this issue related to discussing the
>>draft, because this may be my last post regarding this I-D.
>
> I suggest using the ietf-nomcom@ietf.org mailing list for discussions
> of possible revisions of the NomCom process.

Thanks,

>
>>AB> the update may need an informational draft (or better
>>introduction) like what [1] is doing, so if we know the information on
>>process challenges we will know the best practice. I like the [1]
>>draft I think it needs to be renewed including remote members
>>possibilities.
>
> I am not the author of that draft.  The draft I submitted is
> unrelated to that draft.

It is ok, I recommend using the information or the challenges
mentioned, but If it was not renewed then I will do it,

>>Section 2> The section is not reasonable because you changed with no
>>strong reasons. Why you want to change totally, I recommend to add
>>idea not change. As to give opportunity to additional memebrs that are
>>remote. These additional memebrs will have a special condition. This
>>way you don't change the conditions for the current procedure of
>>selecting f2f memebrs, and you may limit the number of remote
>>contributors maybe 10 % of the total memebrs.
>
> The why is mentioned in the Introduction Section of the draft.  The
> draft updates RFC 3777.

I ment that you should not update the way to select, but only update
that way of selecting new remote memebrs to the f2f attending memebrs.

>
>>AB> suggest in Section 2> I suggest not to update the text of the RFC
>>but to add new rule for selecting few remote participants.
>
> I have been looking into that.

Ok, so I understand that you will do something for this special type
of memebr selected. So the nomcom memebrs will not be all the same
type, most selected the old way and some memebrs (remote) as selected
in a special way.

I recommend you request to join one author of RFC3777 to co-author
with you this work to because we may get more history issues that
thoes authors went through,

AB