Re: [ietf-nomcom] Fwd: New Version Notification for draft-dawkins-iesg-nomcom-advisor-iaoc-00.txt

S Moonesamy <sm+ietf@elandsys.com> Fri, 11 August 2017 21:41 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 E6B3E13252C for <ietf-nomcom@ietfa.amsl.com>; Fri, 11 Aug 2017 14:41:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.79
X-Spam-Level:
X-Spam-Status: No, score=-1.79 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, T_DKIM_INVALID=0.01] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=opendkim.org header.b=MiWD8g05; dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.com header.b=FDnSFCAn
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 SQQBzagSdNih for <ietf-nomcom@ietfa.amsl.com>; Fri, 11 Aug 2017 14:41:11 -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 172CF132561 for <ietf-nomcom@ietf.org>; Fri, 11 Aug 2017 14:41:11 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.227.83.78]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id v7BLewgG008054 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 11 Aug 2017 14:41:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1502487669; x=1502574069; bh=v7BROVAXnCJInw5KsnuUqbhImjVWCMlJOlie5sd289w=; h=Date:To:From:Subject:In-Reply-To:References; b=MiWD8g05yDpl/BnWMvsMtjMi/sRjwl1b2GA5oiJBfq/ML7Yf5BC2SYmqlHgAFy7fF /xZ5x+asuZF8I8lIPbZUqrbMD3SR0xpOFStDWUwxIlYiQDVmoVwXPqt74tqAKDpaKj HXwvQ1Ao5mLN2nUw51QNh4nFvxB4z4uPQsWWyiao=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1502487669; x=1502574069; i=@elandsys.com; bh=v7BROVAXnCJInw5KsnuUqbhImjVWCMlJOlie5sd289w=; h=Date:To:From:Subject:In-Reply-To:References; b=FDnSFCAnrHXMaQhuYQHsZeNr5yEkvEWLaNVP/+JF9nEpo8udhRkekFCZmUDcKtopb Td+x9l9wiUybZHljuNyfXT/h+vDpXPGuIKiJUQD8WyKkQ5LW/78/hfszdYF5moUean i3BQYZAuSEQla8FW8uEpN8ENoa79O1tNoIAxRelY=
Message-Id: <6.2.5.6.2.20170811142232.0ee31fc0@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 11 Aug 2017 14:34:57 -0700
To: John C Klensin <john@jck.com>, ietf-nomcom@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
In-Reply-To: <18658F3EEA38067A4230D855@PSB>
References: <CAKKJt-ckdcGE0_GXqRhVJkh+T8_odkD2QCOhfm-w1COWGRNcFw@mail.gmail.com> <18658F3EEA38067A4230D855@PSB>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-nomcom/AwdEXeR6lDzRMluYYcD_6HnNKrs>
Subject: Re: [ietf-nomcom] Fwd: New Version Notification for draft-dawkins-iesg-nomcom-advisor-iaoc-00.txt
X-BeenThere: ietf-nomcom@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 11 Aug 2017 21:41:12 -0000

Hi John,
At 10:01 03-08-2017, John C Klensin wrote:
>While I concur with those who have indicated that this draft is
>ok (or close) assuming that is what the community wants to do, I
>want to raise a question about the latter that may or may not be
>directly relevant to the document.
>
>As time has passed and the Nomcom has apparently become
>increasingly dependent on questionnaires, interviews, and
>Advisors rather than first-hand knowledge of possible candidates
>by the voting members, questions of influences on the Nomcom
>become increasingly important.  For the Nomcom to invite someone

Yes, it seems that Nomcom relies on the questionnaires and interviews 
instead of having first-hand knowledge of the possible candidates.

>So it seems to me that we should be at least considering:
>
>(1) Encouraging Nomcoms to ask whatever questions about
>operation, job requirements, etc., seem appropriate of various
>bodies without needing to rely on Liaisons or Advisors for that
>rule.

Is there an issue for which it would be more efficient for a person 
with knowledge of the inner workings to get the information from the 
IAOC?  If that is not the case, the healthy choice would be for 
Nomcom to ask questions about the job requirements and/or the 
operations of the body.

Regards,
S. Moonesamy