Re: Last Call: draft-dawkins-nomcom-openlist (NominatingCommittee Process: Open Disclosure of Willing Nominees) to BCP

Thomas Narten <narten@us.ibm.com> Tue, 28 July 2009 17:57 UTC

Return-Path: <narten@us.ibm.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 1A1AA3A6CD1 for <ietf@core3.amsl.com>; Tue, 28 Jul 2009 10:57:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.932
X-Spam-Level:
X-Spam-Status: No, score=-5.932 tagged_above=-999 required=5 tests=[AWL=0.667, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 4ca4v64dG1xs for <ietf@core3.amsl.com>; Tue, 28 Jul 2009 10:57:38 -0700 (PDT)
Received: from e4.ny.us.ibm.com (e4.ny.us.ibm.com [32.97.182.144]) by core3.amsl.com (Postfix) with ESMTP id 2BD243A6D00 for <ietf@ietf.org>; Tue, 28 Jul 2009 10:57:38 -0700 (PDT)
Received: from d01relay07.pok.ibm.com (d01relay07.pok.ibm.com [9.56.227.147]) by e4.ny.us.ibm.com (8.14.3/8.13.1) with ESMTP id n6SH9kRP007771 for <ietf@ietf.org>; Tue, 28 Jul 2009 13:09:46 -0400
Received: from d03av01.boulder.ibm.com (d03av01.boulder.ibm.com [9.17.195.167]) by d01relay07.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id n6SHFNFV2019550 for <ietf@ietf.org>; Tue, 28 Jul 2009 13:15:24 -0400
Received: from d03av01.boulder.ibm.com (loopback [127.0.0.1]) by d03av01.boulder.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id n6SHFMoY031005 for <ietf@ietf.org>; Tue, 28 Jul 2009 11:15:23 -0600
Received: from cichlid.raleigh.ibm.com (sig-9-49-154-100.mts.ibm.com [9.49.154.100]) by d03av01.boulder.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id n6SHFL1G030922 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 28 Jul 2009 11:15:22 -0600
Received: from cichlid.raleigh.ibm.com (localhost [127.0.0.1]) by cichlid.raleigh.ibm.com (8.14.3/8.12.5) with ESMTP id n6SHFKnO026281; Tue, 28 Jul 2009 13:15:20 -0400
Message-Id: <200907281715.n6SHFKnO026281@cichlid.raleigh.ibm.com>
To: Spencer Dawkins <spencer@wonderhamster.org>
Subject: Re: Last Call: draft-dawkins-nomcom-openlist (NominatingCommittee Process: Open Disclosure of Willing Nominees) to BCP
In-reply-to: <A50CB5A08CD64BEDB4767EE546357C64@china.huawei.com>
References: <20090727120916.C5636F24032@odin.smetech.net> <A50CB5A08CD64BEDB4767EE546357C64@china.huawei.com>
Comments: In-reply-to "Spencer Dawkins" <spencer@wonderhamster.org> message dated "Tue, 28 Jul 2009 14:44:43 +0200."
Date: Tue, 28 Jul 2009 13:15:20 -0400
From: Thomas Narten <narten@us.ibm.com>
Cc: ietf@ietf.org, ietf-nomcom@ietf.com
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: Tue, 28 Jul 2009 17:57:39 -0000

"Spencer Dawkins" <spencer@wonderhamster.org> writes:

> Although 3777 doesn't use 2119 conventions (so I'm not introducing any 
> reliance on these conventions in my update, I believe the use of "may" in 
> the current text

>   <t>The list of nominees willing to be considered for positions under 
> review
>    in the current NomCom cycle is not confidential.
>    The NomCom may publish a list of names of nominees who are willing to be 
> considered
>    for positions under review to the community,
>    in order to obtain feedback from the community on these nominees.
>   </t>

I'll just observer that there is a spectrum between "confidential" and
"not confidential" and "public".

Saying "not confidential" may result in the list not actually being
published publically, but being a very open non-secret. I.e, for all
practical purposes, public even without being formally published (say)
on the nomcom page.

And, what about candidates for which the nomcom decides their name
should not be publically posted. Their names are not "confidential"
per the above and presumably anyone else (or the nomcom) can name
them. The end result may well be that there is no way not to have a
name be made public.

> > For allowing NomCom to suppress names ...
> > ... I judge the consensus to allow it.  That is, the community does not 
> > want to tie the NomCom hands as there may be cases where it is the right 
> > thing to do.

> This was not addressed in the current text. I'm adding

>   <t>The NomCom may choose not to include some names in the public list, if 
> this is the
>    right thing to do, in NomCom's opinion.
>   </t>

The "if this is the right thing to do" is asking for trouble, since
those words are more a statement of principle or morality than the
nomcom just deciding it has good reason not to publish a particular
name.

Can we please drop everything after the comma? (I'm not sure how to
reword it, since I think the only point that needs to be made is that
the nomcom as discretion not to publish names, for whatever reason.)

Thomas