Re: [ietf-nomcom] Experiment in "full transparency"
John C Klensin <john-ietf@jck.com> Tue, 17 October 2017 16:39 UTC
Return-Path: <john-ietf@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 8BEE013303A for <ietf-nomcom@ietfa.amsl.com>; Tue, 17 Oct 2017 09:39:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 xuNzcWKDcNHe for <ietf-nomcom@ietfa.amsl.com>; Tue, 17 Oct 2017 09:39:01 -0700 (PDT)
Received: from bsa2.jck.com (ns.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 28579133020 for <ietf-nomcom@ietf.org>; Tue, 17 Oct 2017 09:39:01 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1e4UtP-00053E-Ko; Tue, 17 Oct 2017 12:38:59 -0400
Date: Tue, 17 Oct 2017 12:38:53 -0400
From: John C Klensin <john-ietf@jck.com>
To: "Salz, Rich" <rsalz@akamai.com>
cc: NomComDiscussion <ietf-nomcom@ietf.org>
Message-ID: <DE6132DBB7813E23C606B56B@PSB>
In-Reply-To: <8CB73C9E-9BF2-4252-A98A-D5AA1FE597DC@akamai.com>
References: <6.2.5.6.2.20171016135236.12dcaa60@elandnews.com> <3E158B61-DCF7-485C-B350-DA14B2B8CBDA@akamai.com> <CAA=duU0aiLUzZAP3vmS2tTzxEinzc4hA0UFpd3_dprkjDHnqkg@mail.gmail.com> <CAA=duU31pL8qpqYVfEdsPXt5UcZxKKfTDotbBi6yRmmoC2UgWg@mail.gmail.c om> <FF365C9F-6CE1-41A5-82BB-F15CFB748492@akamai.com> <CAA=duU2k+8-+M2vj5Tk_czJA_VL0ZJ8Z8xhpo0zqu-JqY7mWNQ@mail.gmail.com> <8CB73C9E-9BF2-4252-A98A-D5AA1FE597DC@akamai.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-ietf@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/BG9yaodN2nWqgw_w0mmT7Tp1zpY>
Subject: Re: [ietf-nomcom] Experiment in "full transparency"
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: Tue, 17 Oct 2017 16:39:02 -0000
Rich, A general observation about some of your suggestions... There is a case to be made for an IESG (and IAB) that operate as a closed, friendly, and self-perpetuating club. It promotes stability and consistency of views and policies and helps out individuals and companies who like either the status quo or positioning themselves within it. If that is what one wants, then having a lot of liaisons who participate in every respect other that voting, especially when the typical Nomcom member is a little short on personal knowledge about the IETF and how it functions and about individual incumbents and other candidates is a great idea. Having the bodies for which people are being selected appoint voting Nomcom members might be even better. There is also a case to be made that a community member who fears retaliation from speaking out against a particular IESG member or identifies bad behavior by that person really doesn't have sufficient backbone to participate in the IETF and we (and the Nomcom don't really need to hear from them). Again, if that is what we want, loading up the Nomcom with liaisons whose confidentiality requirements are less clear than voting members and who might be able to hide the source of leaks just by heir numbers and for IESG-appointed Momcom members (like the liaisons, at least partially responsible to their appointing bodies) could be quite strong. However, I think we have been there. The so-called Kobe affair and our current organizational structure --including the Nomcom itself-- were the result of a self-perpetuating IAB which (perhaps inevitably) got out of touch with the community and that, the community concluded, could be "fixed" only by discarding and replacing the organizational structure and retiring most of the membership. Because I worry about those issues, I am concerned every time a Nomcom sets itself up so that only comments on individual candidates are solicited, making no provision for comments about the overall makeup of a body and how it is working with the community or important topics. I am concerned that we have too many liaisons and too few constraints on their behavior (particularly what they are expected or allowed to discuss with appointing bodies after they are appointed), the information to which they will have access. and their participation in interviews. I am even concerned about statements from bodies to which the Nomcom will make appointments about what those bodies want or need and what roles should be considered in evaluating candidates-- not because the statements are a bad idea, but because there is no obvious mechanism for other members of the community to review those statements and express dissenting views about what the community needs or should have. There is probably a good balance among those points of view, but I believe it is one the community should be discussing in an open way that addresses the actual choices, not by tweaking Nomcom membership without thinking through the likely consequences. best, john
- [ietf-nomcom] Experiment in "full transparency" S Moonesamy
- Re: [ietf-nomcom] Experiment in "full transparenc… Salz, Rich
- Re: [ietf-nomcom] Experiment in "full transparenc… Andrew G. Malis
- Re: [ietf-nomcom] Experiment in "full transparenc… Andrew G. Malis
- Re: [ietf-nomcom] Experiment in "full transparenc… Salz, Rich
- Re: [ietf-nomcom] Experiment in "full transparenc… Andrew G. Malis
- Re: [ietf-nomcom] Experiment in "full transparenc… Salz, Rich
- Re: [ietf-nomcom] Experiment in "full transparenc… S Moonesamy
- Re: [ietf-nomcom] Experiment in "full transparenc… John C Klensin
- Re: [ietf-nomcom] Experiment in "full transparenc… James Galvin
- Re: [ietf-nomcom] Experiment in "full transparenc… Salz, Rich
- Re: [ietf-nomcom] Experiment in "full transparenc… Salz, Rich
- Re: [ietf-nomcom] Experiment in "full transparenc… John C Klensin
- Re: [ietf-nomcom] Experiment in "full transparenc… Peter Yee
- Re: [ietf-nomcom] Experiment in "full transparenc… Salz, Rich
- Re: [ietf-nomcom] Experiment in "full transparenc… Stephen Farrell
- Re: [ietf-nomcom] Experiment in "full transparenc… Salz, Rich
- Re: [ietf-nomcom] Experiment in "full transparenc… John C Klensin
- Re: [ietf-nomcom] Experiment in "full transparenc… Stephen Farrell
- Re: [ietf-nomcom] Experiment in "full transparenc… S Moonesamy
- Re: [ietf-nomcom] Experiment in "full transparenc… Stephen Farrell
- Re: [ietf-nomcom] Experiment in "full transparenc… Spencer Dawkins at IETF