Re: [ietf-nomcom] The Nominating Committee Process: Eligibility

S Moonesamy <sm+ietf@elandsys.com> Fri, 28 June 2013 11:51 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 B922D21F8D10 for <ietf-nomcom@ietfa.amsl.com>; Fri, 28 Jun 2013 04:51:39 -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 t3tCLjl5CO69 for <ietf-nomcom@ietfa.amsl.com>; Fri, 28 Jun 2013 04:51:33 -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 9799F21F8653 for <ietf-nomcom@ietf.org>; Fri, 28 Jun 2013 04:51:19 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.132.118]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r5SBouE7004442 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 28 Jun 2013 04:51:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1372420276; bh=6RrU1FmcuybjUo+f4tIilfFtbuRYeYn9XiCkGeDVcR8=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=MtUz76S/yN8GmC4phzfQiBk+EVVqg9+eedha4K14kVbKZlPQJCMXitXz39JbzjctX Q+oG/16/yZyrckWtx89dR5EytoDqnbLOi7xWJFAKGJ9yTYdvqpVYulgghGn40EQV/y 9SPw7mV+6WXsUhfkVXJ90K8qV7oVGW9dx3HOKmZA=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1372420276; i=@elandsys.com; bh=6RrU1FmcuybjUo+f4tIilfFtbuRYeYn9XiCkGeDVcR8=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=2E15HqO9MBbuQL+FYCETdYE6bs00QkW9b2tERiDnp/eCyq781kH/ExDL9OpyPVNyf eXBmrPZVZqhPeN+hV96hw5SDsGY5fDwG4rKjbcdERKmBQDVythvs84zqxKLo9G0RvW IOJRKXflDjXTIz/4MuKFuFVuZ/Zbzt5OXkermzlM=
Message-Id: <6.2.5.6.2.20130628040056.0cf0a5e0@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 28 Jun 2013 04:50:28 -0700
To: John C Klensin <john@jck.com>, adrian@olddog.co.uk
From: S Moonesamy <sm+ietf@elandsys.com>
In-Reply-To: <A4C2CA82275758877EFBB706@JcK-HP8200.jck.com>
References: <6.2.5.6.2.20130625152043.0d65aad0@elandnews.com> <51CA1A54.7080004@stevecrocker.com> <6.2.5.6.2.20130625153339.0d642d00@resistor.net> <51CA1EA5.8040903@stevecrocker.com> <8C48B86A895913448548E6D15DA7553B92660C@xmb-rcd-x09.cisco.com> <6.2.5.6.2.20130625162728.0d645228@elandnews.com> <8C48B86A895913448548E6D15DA7553B9267AD@xmb-rcd-x09.cisco.com> <6.2.5.6.2.20130625184003.0c545fb0@elandnews.com> <51CA68A2.8080304@joelhalpern.com> <6.2.5.6.2.20130625210953.0deb8c48@resistor.net> <51CAEDED.3070607@stevecrocker.com> <6.2.5.6.2.20130626085011.0c47d550@elandnews.com> <51CB267F.20900@dcrocker.net> <01d101ce7295$9f726150$de5723f0$@olddog.co.uk> <6.2.5.6.2.20130626115547.0d736b78@elandnews.com> <A4C2CA82275758877EFBB706@JcK-HP8200.jck.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf-nomcom@ietf.org
Subject: Re: [ietf-nomcom] The Nominating Committee Process: Eligibility
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: Fri, 28 Jun 2013 11:51:39 -0000

At 05:30 27-06-2013, John C Klensin wrote:
>         * those who have some desire or expectation of being
>         tapped for leadership roles for which Nomcom membership
>         would make them ineligible.

There is the cultural factor here.  Some people with the desire or 
expectation of being tapped for a role will not step forward to say 
so or provide information to indicate their desire or expectation.

>         * those who have withdrawn from active IETF
>         participation (including physical presence) due to lack
>         of time, commitments elsewhere, or general disgust.

I don't know how significant the general disgust is.  I would 
describe it as a silent group which could protest.  This is where 
things can be unpredictable.

>There are other groups too, but I don't know how large they are.
>I am pretty confident that few, if any, of the people from the
>above groups are likely to volunteer for the Nomcom unless we
>figure out how to lower the time commitment (or at least the f2f
>commitment) required.  As with the more traditional leadership

Yes.

>positions, reversing the trends of recent years and reducing the
>time and other commitments would be likely to broaden the
>candidate pool.  By contrast, and by analogy to the "don't
>expect people from one group to be able to fully understand and
>represent the perspective of another" part of the diversity
>discussion, a very large Nomcom time commitment is likely to
>reduce the people on the Nomcom who understand the value of
>considering people for the IESG, IAB, and IAOC who are be
>committed to limiting the time commitment of those roles.

The message from the floor a few months ago was "body X is not 
representative of us".  There was a message about affiliation last 
year.  The observation was that:

   'the top four companies on this list have contributed more than half of
    the NomCom volunteers. The top three have contributed twice as many
    (44) as all of the entities that contributed only one (22).'

and the opinion was that:

   'the NomCom would benefit from having many "independent" members.  While
    that could happen (yay, randomness), the odds here don't look great.'

There were appearances of biased voting membership previously.

If the time commitment and funding are the limiting factors the IETF 
can end up with another situation similar to the Transport AD one.

Regards,
S. Moonesamy