Re: Last Call: draft-dawkins-nomcom-openlist (Nominating Committee Process: Open Disclosure of Willing Nominees) to BCP
John C Klensin <john-ietf@jck.com> Wed, 17 June 2009 16:04 UTC
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E12623A6905 for <ietf@core3.amsl.com>; Wed, 17 Jun 2009 09:04:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.385
X-Spam-Level:
X-Spam-Status: No, score=-2.385 tagged_above=-999 required=5 tests=[AWL=0.214, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JlooTFv-WVVa for <ietf@core3.amsl.com>; Wed, 17 Jun 2009 09:04:09 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id E968E3A6829 for <ietf@ietf.org>; Wed, 17 Jun 2009 09:04:08 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1MGxcX-000L0y-Ke; Wed, 17 Jun 2009 12:04:17 -0400
Date: Wed, 17 Jun 2009 12:04:17 -0400
From: John C Klensin <john-ietf@jck.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>, stbryant@cisco.com
Subject: Re: Last Call: draft-dawkins-nomcom-openlist (Nominating Committee Process: Open Disclosure of Willing Nominees) to BCP
Message-ID: <AFD693E123C1A1030D737C0B@PST.JCK.COM>
In-Reply-To: <4A390205.7070404@joelhalpern.com>
References: <20090605234511.3274D3A6B31@core3.amsl.com> <7AB0ADBF842DA348AFEF348E@PST.JCK.COM> <4A38EF2C.60305@cs.tcd.ie> <4A38F1D0.8040403@cisco.com> <4A390205.7070404@joelhalpern.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
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Wed, 17 Jun 2009 16:04:10 -0000
--On Wednesday, June 17, 2009 10:47 -0400 "Joel M. Halpern" <jmh@joelhalpern.com> wrote: > I really think we want to stay away from any statement which > implies anything about the nominees views about anyone. > I do not think it is reasonable or practical to try to include > disclaimers in the list of nominees about eveyr > misapprehension that readers of the list may form. > We ought not be making any public statement about the nominees > degree of willingness to serve, degree of desire for change or > stability, or any other opinion about the nominee. We are > simply letting folks know that the nominee exists. > > If we absolutely have to have a stronger disclaimer, I would > think it would need to be quite general, not specific about > nominees opinions on any one dimension. And certainly not a > list of thing on which the nominee is not expressing an > opinion in public. And a strong disclaimer, perhaps any disclaimer, that applies to all nominees would rapidly turn into boilerplate, i.e., a waste of time that almost no one reads and fewer take seriously. As we have seen in last year's round, there is nothing in the confidentiality requirements that prevents a nominee from posting anything he or she likes to the IETF list (or elsewhere). Presumably attacks on other candidates would be frowned upon, both by the community as a whole and by a Nomcom that was trying to evaluate whether the Nominee understood the IETF well enough to play well with others. And, if someone wanted to post a public note saying "I think Elmer Fudd is doing a really good job as Duck-hunting AD; I was asked to put my name in and did so but I'm really not interested in the role unless Elmer really doesn't want to serve another term", I think we should neither encourage nor discourage that in any of these documents. john
- Re: Fw: Last Call: draft-dawkins-nomcom-openlist … Jari Arkko
- Re: Fw: Last Call: draft-dawkins-nomcom-openlist … Spencer Dawkins
- Re: Last Call: draft-dawkins-nomcom-openlist (Nom… Dave CROCKER
- Fw: Last Call: draft-dawkins-nomcom-openlist (Nom… Spencer Dawkins
- Re: Fw: Last Call: draft-dawkins-nomcom-openlist … Joel M. Halpern
- Re: Fw: Last Call: draft-dawkins-nomcom-openlist … Doug Ewell
- Re: Last Call: draft-dawkins-nomcom-openlist (Nom… Bob Hinden
- Re: Fw: Last Call: draft-dawkins-nomcom-openlist … Harald Alvestrand
- RE: Last Call: draft-dawkins-nomcom-openlist (Nom… Pasi.Eronen
- Re: Last Call: draft-dawkins-nomcom-openlist (Nom… John C Klensin
- Re: Last Call: draft-dawkins-nomcom-openlist (Nom… Stephen Farrell
- Re: Last Call: draft-dawkins-nomcom-openlist (Nom… Stewart Bryant
- Re: Last Call: draft-dawkins-nomcom-openlist (Nom… Joel M. Halpern
- Re: Last Call: draft-dawkins-nomcom-openlist (Nom… Jari Arkko
- Re: Last Call: draft-dawkins-nomcom-openlist (Nom… John C Klensin
- Re: Last Call: draft-dawkins-nomcom-openlist (Nom… Jari Arkko
- Re: Last Call: draft-dawkins-nomcom-openlist (Nom… John C Klensin
- Re: Last Call: draft-dawkins-nomcom-openlist (Nom… Russ Housley
- Re: Last Call: draft-dawkins-nomcom-openlist (Nom… Spencer Dawkins
- Re: Last Call: draft-dawkins-nomcom-openlist (Nom… Thomas Narten
- Re: Last Call: draft-dawkins-nomcom-openlist (Nom… Andrew Sullivan