Re: [ietf-nomcom] Fwd: New Version Notification for draft-dawkins-iesg-nomcom-advisor-iaoc-00.txt
John C Klensin <john@jck.com> Thu, 03 August 2017 17:01 UTC
Return-Path: <john@jck.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 DD9411320CF for <ietf-nomcom@ietfa.amsl.com>; Thu, 3 Aug 2017 10:01:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
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 dgeuaOP01N7D for <ietf-nomcom@ietfa.amsl.com>; Thu, 3 Aug 2017 10:01:47 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0E7411320C9 for <ietf-nomcom@ietf.org>; Thu, 3 Aug 2017 10:01:47 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john@jck.com>) id 1ddJVJ-0005eY-GK; Thu, 03 Aug 2017 13:01:45 -0400
Date: Thu, 03 Aug 2017 13:01:37 -0400
From: John C Klensin <john@jck.com>
To: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>, NomCom-Discussion <ietf-nomcom@ietf.org>
cc: Alexey Melnikov <aamelnikov@fastmail.fm>
Message-ID: <18658F3EEA38067A4230D855@PSB>
In-Reply-To: <CAKKJt-ckdcGE0_GXqRhVJkh+T8_odkD2QCOhfm-w1COWGRNcFw@mail.gmail.com>
References: <CAKKJt-ckdcGE0_GXqRhVJkh+T8_odkD2QCOhfm-w1COWGRNcFw@mail.gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-nomcom/H16fknIhVrsvobBVT-gjr5ogPVU>
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: Thu, 03 Aug 2017 17:01:49 -0000
--On Wednesday, August 2, 2017 16:30 -0500 Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> wrote: > Dear Nomcom Process Devotees, > > Alissa has asked me to put together a short(!) draft that will > remind future Nomcoms to request IAOC to provide an Advisor. > > Details are below. > > I'd like to discuss this draft on this mailing list initially. > > Please comment and question as appropriate. Spencer, 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 from a particular body to attend a meeting or call to offer advice on specific issues (consistent with RFC 7437 Section 4.3, second paragraph), a standing Advisor (or Liaison) role is another matter and, other than the technical considerations about oversight of the Nomcom process and the "sitting member" requirements that you describe in Section 4 of the I-D, it is not clear that you (and the draft) anticipate any difference in practice. My concern about all of these roles is the potential for the appearance of undue influence. Is a particular Liaison or Advisor likely to defend a colleague in the same organization? Or exaggerate faults to get rid of one who is personally unpopular with the Liaison or Advisor (or even the whole body)? Is the presence of an incumbent likely to have a chilling effect on a community member who wants to make a well-thought-out argument for, e.g., throwing as many of the incumbents out as possible and starting over on that body? (I know the answer to the latter is "yes", the only questions are how widespread and important it is).) When the Nomcom was first designed and the community assumed that a significant number, perhaps most, of its members would have sufficient experience with likely candidates, that was, itself, a safeguard against abuses. Now, that is not so clear. 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. (2) Trying to figure out how to isolate Liaisons and Advisors from input (especially informal input) to the Nomcom about the membership, operations at a personal level, and possible candidates for their (and probably other) bodies and to do so in a way that increases community confidence that the Nomcom is seeking out and considering all of the information it wants or needs rather than even potentially being unduly influenced by representatives of bodies to which it is making appointments. While I agree with the observations about allowing an IAD to influence appointments to the body that hires and oversees him or her, very nearly the same observation could apply to allowing an IAB or IESG member to influence choices of people he or she will ultimately need to work, with, who will support or impede their agendas, etc. (3) Encourage the Nomcom to invite Liaisons or Advisors to only participate in discussions for which they are directly and obviously relevant and, in the interest of transparency and increased confidence in the process, document those choices for the community (4) More than 20 years into the current model, perhaps many of the same arguments apply to "sitting members" of other bodies that you have made for the IAOC appointee. Similarly, perhaps it is time to consider whether the job of overseeing the propriety of the Nomcom process ought to be linked with giving the Nomcom advice about particular bodies or even particular candidates or appointments. best, john
- [ietf-nomcom] Fwd: New Version Notification for d… Spencer Dawkins at IETF
- Re: [ietf-nomcom] Fwd: New Version Notification f… Brian E Carpenter
- Re: [ietf-nomcom] New Version Notification for dr… Bradner, Scott
- Re: [ietf-nomcom] Fwd: New Version Notification f… Adrian Farrel
- Re: [ietf-nomcom] New Version Notification for dr… Bradner, Scott
- Re: [ietf-nomcom] New Version Notification for dr… Andrew G. Malis
- Re: [ietf-nomcom] New Version Notification for dr… Bradner, Scott
- Re: [ietf-nomcom] New Version Notification for dr… Andrew G. Malis
- Re: [ietf-nomcom] Fwd: New Version Notification f… John C Klensin
- Re: [ietf-nomcom] Fwd: New Version Notification f… Spencer Dawkins at IETF
- Re: [ietf-nomcom] Fwd: New Version Notification f… Spencer Dawkins at IETF
- Re: [ietf-nomcom] Fwd: New Version Notification f… S Moonesamy