Re: Updating BCP 10 -- NomCom

John C Klensin <john-ietf@jck.com> Thu, 08 January 2015 15:59 UTC

Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1507E1A6F01 for <ietf@ietfa.amsl.com>; Thu, 8 Jan 2015 07:59:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.61
X-Spam-Level:
X-Spam-Status: No, score=-2.61 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 FhBDlB-szXkw for <ietf@ietfa.amsl.com>; Thu, 8 Jan 2015 07:59:46 -0800 (PST)
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 3FC651A8A92 for <ietf@ietf.org>; Thu, 8 Jan 2015 07:59:46 -0800 (PST)
Received: from [198.252.137.35] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1Y9FUu-000HQN-Vn; Thu, 08 Jan 2015 10:59:44 -0500
Date: Thu, 08 Jan 2015 10:59:36 -0500
From: John C Klensin <john-ietf@jck.com>
To: "Murray S. Kucherawy" <superuser@gmail.com>, ietf <ietf@ietf.org>
Subject: Re: Updating BCP 10 -- NomCom
Message-ID: <D54C3DE17A3E5C7B032F6FB4@JcK-HP8200.jck.com>
In-Reply-To: <CAL0qLwZk=k-CWLte_ChK9f1kzLwMOTRyi7AwFa8fLjBsextBcA@mail.gmail.com>
References: <CAL0qLwZk=k-CWLte_ChK9f1kzLwMOTRyi7AwFa8fLjBsextBcA@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.35
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/_jkbaPPuHFq2R2YgiID52pDhssQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Jan 2015 15:59:48 -0000


--On Wednesday, January 07, 2015 09:03 -0800 "Murray S.
Kucherawy" <superuser@gmail.com> wrote:

> The first change I'd like to propose is that the IAOC Liaison
> to the NomCom be codified.  It's currently only an unwritten
> common practice.

I think that is fine.  However, while I continue to be generally
opposed to firm rules, I think the whole role of the liaisons
needs work.  Because of the potential for damaging existing
working relationships, the presence of the liaisons (or
particular people in liaison roles) may have chilling effects on
whether the Nomcom gets input and how candid that input actually
is. In addition, liaisons might well be assumed to be biased in
favor of retaining a status quo that works for them.  Some
assurances to the community that, e.g., liaisons were expected
to answer questions and provide general advice about roles but
that they would be at least as isolated from input about, and
internal Nomcom discussion of, specific candidates as ordinary
participants in the IETF might, in that regard, be both helpful
to a Nomcom trying to solicit input and to general impressions
about the integrity of the process.

    john