Re: 2nd Last Call: draft-dawkins-nomcom-openlist (Nominating Committee Process: Open Disclosure of Willing Nominees) to BCP
"Joel M. Halpern" <jmh@joelhalpern.com> Mon, 10 August 2009 20:24 UTC
Return-Path: <jmh@joelhalpern.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 619803A6901 for <ietf@core3.amsl.com>; Mon, 10 Aug 2009 13:24:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.47
X-Spam-Level:
X-Spam-Status: No, score=-3.47 tagged_above=-999 required=5 tests=[AWL=0.129, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 WuknMnqHIglN for <ietf@core3.amsl.com>; Mon, 10 Aug 2009 13:24:54 -0700 (PDT)
Received: from hermes.mail.tigertech.net (hermes.mail.tigertech.net [64.62.209.72]) by core3.amsl.com (Postfix) with ESMTP id 90CBA28C167 for <ietf@ietf.org>; Mon, 10 Aug 2009 13:24:54 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hermes.tigertech.net (Postfix) with ESMTP id ACF3443044A for <ietf@ietf.org>; Mon, 10 Aug 2009 13:24:58 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at hermes.tigertech.net
Received: from [10.10.10.101] (pool-71-161-51-13.clppva.btas.verizon.net [71.161.51.13]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by hermes.tigertech.net (Postfix) with ESMTP id 2215B430448 for <ietf@ietf.org>; Mon, 10 Aug 2009 13:24:57 -0700 (PDT)
Message-ID: <4A808219.5070506@joelhalpern.com>
Date: Mon, 10 Aug 2009 16:24:57 -0400
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Thunderbird 2.0.0.22 (Windows/20090605)
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: 2nd Last Call: draft-dawkins-nomcom-openlist (Nominating Committee Process: Open Disclosure of Willing Nominees) to BCP
References: <20090810202023.B961E28C0FE@core3.amsl.com>
In-Reply-To: <20090810202023.B961E28C0FE@core3.amsl.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
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: Mon, 10 Aug 2009 20:24:55 -0000
While we can wordsmith the proposed resolution from now till doomsday, what has been suggested seems good enough. I can certainly live with it. Please, approve this document for publication as an BCP. Yours, Joel M. Halpern The IESG wrote: > The IESG has received a request from an individual submitter to consider > the following document: > > - 'Nominating Committee Process: Open Disclosure of Willing Nominees' > <draft-dawkins-nomcom-openlist-06.txt> as a BCP > > The first IETF Last Call on this document caused significant discussion. > Several issues were raised and resolved. The most recent version of the > document includes these resolutions. One issue was not resolved, but > this the most recent version of the document proposes a solution to that > open issue. This second IETF Last Call is focused on that single open > issue. > > The previous version of this document included a statement that said > there MUST NOT be lobby or campaign activities. Important points made > during the previous IETF Last Call include: > > 1) It was pointed out that the only enforcement mechanism available is > for NomCom to do something if it happens. If public statements of > support are perceived to work, then we have changed the process in > a way that we want to avoid. > > 2) Refusal to consider people just because someone else made a > public statement of support seems unwise. That would be a serious > DOS attack. > > 3) We should have MUST NOT precisely because we can't enforce the > rules, so they need to look strong. > > Please consider these perspectives when reviewing the most recent > version of the document, which addresses this open issue in two > ways. First, Nominees are told that lobbying and campaigning > are considered unacceptable behavior. Second, there is a > recognition that NomCom cannot be expected to completely ignore > any lobby or campaign effort that might occur; however, NomCom > ought to consider the judgment of any nominee that encourages > or supports such activities. > > The IESG plans to make a decision in the next few weeks, and solicits > final comments on this action. Please send substantive comments to the > ietf@ietf.org mailing lists by 2009-09-07. Exceptionally, > comments may be sent to iesg@ietf.org instead. In either case, please > retain the beginning of the Subject line to allow automated sorting. > > The file can be obtained via > http://www.ietf.org/internet-drafts/draft-dawkins-nomcom-openlist-06.txt > > > IESG discussion can be tracked via > https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=18213&rfc_flag=0 > > _______________________________________________ > IETF-Announce mailing list > IETF-Announce@ietf.org > https://www.ietf.org/mailman/listinfo/ietf-announce >
- Re: 2nd Last Call: draft-dawkins-nomcom-openlist … Joel M. Halpern
- Re: 2nd Last Call: draft-dawkins-nomcom-openlist … Jari Arkko
- Re: 2nd Last Call: draft-dawkins-nomcom-openlist … Dave CROCKER
- Re: 2nd Last Call: draft-dawkins-nomcom-openlist … Lars Eggert
- Re: 2nd Last Call: draft-dawkins-nomcom-openlist … Bob Hinden