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

S Moonesamy <sm+ietf@elandsys.com> Sat, 29 June 2013 17:44 UTC

Return-Path: <sm@elandsys.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 4953E11E8186 for <ietf-nomcom@ietfa.amsl.com>; Sat, 29 Jun 2013 10:44:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 pOZa+znif-A3 for <ietf-nomcom@ietfa.amsl.com>; Sat, 29 Jun 2013 10:44:16 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 1461011E8191 for <ietf-nomcom@ietf.org>; Sat, 29 Jun 2013 10:44:15 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.128.158]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r5THhxIW029933 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 29 Jun 2013 10:44:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1372527851; bh=OruZyUBTozrfMbbzQs/rMo/QpvNiXVWkxScgqltV+jA=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=pZifpx7zMuFtnEueq46XsQf0xZgHtfWmuZl4OS6kQjeG/shCwjiS91JgtKL60AtQ9 s7MDiIgkjWTeYKBrExEkULgA7zOq7brLefqqZpgfdBCc3X5q7A91k+NkHubUFP7x/e rYY8ulUCKktQ9ThCZC9cHA6emziYco4wt15sQzhc=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1372527851; i=@elandsys.com; bh=OruZyUBTozrfMbbzQs/rMo/QpvNiXVWkxScgqltV+jA=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=nURJKEkgSAvHOvHdIRcfNZ07xVQBhQtyiQ11Z4KhMii6m+zG/QJp2EVRhHdzOgWij PE5jnhdmGxfhhCJfZknl6lonu/RriwLvvPdGfpyYLEczXGSuSsyjNOJoZ4UK9FiwTF Dbx2JqV0sVVdwwWGu9dTKORrOUlRJkhwqe1drOpE=
Message-Id: <6.2.5.6.2.20130629022022.0b9566e0@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sat, 29 Jun 2013 10:43:26 -0700
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
From: S Moonesamy <sm+ietf@elandsys.com>
In-Reply-To: <CADnDZ88zC8PCY9rLZA3btffhiKT7YdxjrE6QTKYbm1gxqDwTbA@mail.g mail.com>
References: <CADnDZ88zC8PCY9rLZA3btffhiKT7YdxjrE6QTKYbm1gxqDwTbA@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
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: Sat, 29 Jun 2013 17:44:17 -0000

Hi Abdussalam,
At 22:18 28-06-2013, Abdussalam Baryun wrote:
>I think the draft still needs more details, for example, the Abstract
>says to give remote contributors eligible to serve but how many
>remote, it is not-reasonable/not-practical to have most remote, and it
>is not fare/diverse to have all not remote. Furthermore, you did not

I will work on the text in the Introduction section and change the 
Abstract accordingly.

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

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

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

>AB> you need to define *remote contributor* in the draft. When the

I received similar feedback from other people.

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

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

>Where are the five meetings (is it a f2f meeting?)and what kind of
>contributing you are asking?

The five meetings are defined in RFC 3777.

>I really want to focus questions related to the new draft not other
>issues. Therefore, I think the draft needs to involve what was
>discussed on the list (feedback). Updating this RFC procedure may need

I take all feedback about a draft into account.

Regards,
S. Moonesamy