Re: [ietf-nomcom] BCP 10 Update, adding an IAOC Advisor to the Nominating Committee
John C Klensin <john-ietf@jck.com> Thu, 24 August 2017 23:05 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 5A1B91329B2 for <ietf-nomcom@ietfa.amsl.com>; Thu, 24 Aug 2017 16:05:39 -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 U8tqU6M4lNLe for <ietf-nomcom@ietfa.amsl.com>; Thu, 24 Aug 2017 16:05:37 -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 91E911329C2 for <ietf-nomcom@ietf.org>; Thu, 24 Aug 2017 16:05:36 -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 1dl1Bu-000FMZ-Fy; Thu, 24 Aug 2017 19:05:34 -0400
Date: Thu, 24 Aug 2017 19:05:28 -0400
From: John C Klensin <john-ietf@jck.com>
To: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
cc: NomCom-Discussion <ietf-nomcom@ietf.org>, Alexey Melnikov <aamelnikov@fastmail.fm>
Message-ID: <8D0453C3C2E54A22171A86E7@PSB>
In-Reply-To: <CAKKJt-dDHV-wQkat083dKohH1_n32mB51wqQCv7mK6VFA3WMjQ@mail.gmail.com>
References: <CAKKJt-cd2-tS=3QnvRcsDKcZ8=o5Z98wUr-=tp8OeP9J1M0M8g@mail.gmail.com> <4622.1502292425@obiwan.sandelman.ca> <CAKKJt-fxhFnnK3T2nVj2bD=Ve7z6L0oJFjYFqBb59TusJDwFzQ@mail.gmail.com> <1250df52-b5b3-4f71-bab1-790d156af1e9@nostrum.com> <5f26388a-93aa-7133-6973-de669a9bb2f4@gmail.com> <CAA=duU2hn-6=OzvZrfuz0agvzxvV0euXP4nsnjdksUpsnAyfJQ@mail.gmail.com> <6e62d88a-ba0e-18eb-3a45-88851b6e7c46@joelhalpern.com> <CAKKJt-dJ2Z1wsqXveg7+PR13d2bH61pHR753gEamwqWv4f+hKQ@mail.gmail.com> <0c83a20d-325b-d928-a157-638fcaf81adf@cs.tcd.ie> <CAKKJt-dsUt-bwtFiDY3Lek52QnmJT6z4O9+Bv3Py1He1vMW3-A@mail.gmail.com> <F313896EC3A928CD74DD7271@PSB> <CAKKJt-dDHV-wQkat083dKohH1_n32mB51wqQCv7mK6VFA3WMjQ@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-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/gTKezGoOrX3_in3kshdQ0Z5SY48>
Subject: Re: [ietf-nomcom] BCP 10 Update, adding an IAOC Advisor to the Nominating Committee
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, 24 Aug 2017 23:05:39 -0000
Spencer, --On Thursday, August 24, 2017 16:54 -0500 Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> wrote: > Hi, John, and CC Alexey, who is shepherding this draft, >... >> However, as I've tried to say before, I'm worried about a >> different problem in this case, which is whether, as the >> individual knowledge of Nomcom members goes down, the presence >> of all of those liaisons could have undue influence by any of: >... > I have seen your e-mail about that, and I think I understand > this issue pretty well. > > I agree that how the Nomcom reviews positions and nominees has > changed pretty massively since 1992. > > The problem with problems with Nomcom is, it's really hard to > know what problems have been encountered over the years, > unless one or more Nomcom chairs reveals a problem that they > encountered. > > Some do that, pretty publicly, but even in those cases, people > outside the Nomcom don't have the details that would be > helpful in solving problems. > > I might reasonably point out that there's been an "IAOC > liaison" on every Nomcom from 2009-2010 to 2014-2015, but > maybe we've just been lucky - I just don't know. > > So, here's what I'm thinking. > > Tl;dr > > Alissa (as Gen-AD) is out on leave until October (although she > did surface for an informal telechat earlier today). > > I'm not comfortable proposing more than minor changes, until > she can participate in that discussion. > > When she returns, I'll tell her what I'm hearing (and that I > can't dismiss that concern out of hand). That's on my calendar > as a reminder. Seems completely sensible. > The long part ... > > The last time we made a Nomcom process change that was more > than a paragraph long, what Russ did, was convene about ten > years worth of Nomcom past chairs to exchange, maintaining as > much confidentiality as they could (so, no names), > descriptions of problems they'd encountered. Common problems > went into > https://tools.ietf.org/html/draft-dawkins-nomcom-3777-issues-0 > 0, and that formed the basis of most of the BCP changes I > authored (most notoriously, > https://datatracker.ietf.org/doc/rfc5680/). That's why we had > some confidence that we were talking about real problems. >... > Maybe all the problems that were identified then have gone > away without BCP changes, or maybe more recent Nomcom chairs > have encountered different problems that are worth thinking > about, but (inserting by reference every conversation you and > I have ever had about how hard it is to get BCPs right the > first time), if we've already had problems that recur often > enough to justify BCP updates, I'd like to understand them. Yes. But I think there is a source of data that might be hard to capture and invisible to Nomcom chairs. That doesn't mean it isn't there or isn't valid. I've heard, several times, from IETF participants (just participants with no leadership responsibilities, although my list includes a few WG chairs), in conversations that typically occur after Nomcom appointments are announced. The conversations went something like the following: > How could they possibly reappoint X, he is terrible, mistreated the WG, and systematically ignored everyone who disagreed with him. < Did you discuss those issues and examples with the Nomcom. > No, I hoped someone else would do so. < Why not? If you don't raise the issues, how can you expect others to do so? > Y was the liaison (or even X's co-AD), I think they are buddies, and ADs protect each other anyway, so I'm afraid of retaliation... from X if X is reappointed and from Y and maybe the rest of the IESG is X is not. I have no confidence in Y's ability to keep my comments, or the fact that I made them, away from X or other IESG members. < <selection of bad words> I've heard similar things four or five times. Not a huge number, but enough to cause me to believe that there is a problem and that others may be hearing the same things. I've heard similar things before Nomcoms have made their selections but then I just suggest private conversations with Nomcom chairs... something that would be visible to those chairs if they occurred (and I have no way to know whether they did or not). john
- [ietf-nomcom] BCP 10 Update, adding an IAOC Advis… Spencer Dawkins at IETF
- Re: [ietf-nomcom] BCP 10 Update, adding an IAOC A… Michael Richardson
- Re: [ietf-nomcom] BCP 10 Update, adding an IAOC A… S Moonesamy
- Re: [ietf-nomcom] BCP 10 Update, adding an IAOC A… Spencer Dawkins at IETF
- Re: [ietf-nomcom] BCP 10 Update, adding an IAOC A… Spencer Dawkins at IETF
- Re: [ietf-nomcom] BCP 10 Update, adding an IAOC A… Michael Richardson
- Re: [ietf-nomcom] BCP 10 Update, adding an IAOC A… Spencer Dawkins at IETF
- Re: [ietf-nomcom] BCP 10 Update, adding an IAOC A… Spencer Dawkins at IETF
- Re: [ietf-nomcom] BCP 10 Update, adding an IAOC A… Brian E Carpenter
- Re: [ietf-nomcom] BCP 10 Update, adding an IAOC A… Andrew G. Malis
- Re: [ietf-nomcom] BCP 10 Update, adding an IAOC A… Spencer Dawkins at IETF
- Re: [ietf-nomcom] BCP 10 Update, adding an IAOC A… Joel Halpern
- Re: [ietf-nomcom] BCP 10 Update, adding an IAOC A… Spencer Dawkins at IETF
- Re: [ietf-nomcom] BCP 10 Update, adding an IAOC A… Scott O. Bradner
- Re: [ietf-nomcom] BCP 10 Update, adding an IAOC A… Stephen Farrell
- Re: [ietf-nomcom] BCP 10 Update, adding an IAOC A… Joel M. Halpern
- Re: [ietf-nomcom] BCP 10 Update, adding an IAOC A… Brian E Carpenter
- Re: [ietf-nomcom] BCP 10 Update, adding an IAOC A… Spencer Dawkins at IETF
- Re: [ietf-nomcom] BCP 10 Update, adding an IAOC A… John C Klensin
- Re: [ietf-nomcom] BCP 10 Update, adding an IAOC A… Stephen Farrell
- Re: [ietf-nomcom] BCP 10 Update, adding an IAOC A… Spencer Dawkins at IETF
- Re: [ietf-nomcom] BCP 10 Update, adding an IAOC A… John C Klensin
- Re: [ietf-nomcom] BCP 10 Update, adding an IAOC A… Spencer Dawkins at IETF
- Re: [ietf-nomcom] BCP 10 Update, adding an IAOC A… John C Klensin
- Re: [ietf-nomcom] BCP 10 Update, adding an IAOC A… Stephen Farrell
- Re: [ietf-nomcom] BCP 10 Update, adding an IAOC A… John C Klensin
- Re: [ietf-nomcom] BCP 10 Update, adding an IAOC A… Spencer Dawkins at IETF