Re: [ietf-nomcom] Changing the candidate selection model
SM <sm@resistor.net> Fri, 19 June 2009 21:10 UTC
Return-Path: <sm@resistor.net>
X-Original-To: ietf-nomcom@core3.amsl.com
Delivered-To: ietf-nomcom@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A54513A68BC for <ietf-nomcom@core3.amsl.com>; Fri, 19 Jun 2009 14:10:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.679
X-Spam-Level:
X-Spam-Status: No, score=-2.679 tagged_above=-999 required=5 tests=[AWL=-0.080, 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 085KVmBjOWwg for <ietf-nomcom@core3.amsl.com>; Fri, 19 Jun 2009 14:10:39 -0700 (PDT)
Received: from ns1.qubic.net (ns1.qubic.net [208.69.177.116]) by core3.amsl.com (Postfix) with ESMTP id A14E53A6824 for <ietf-nomcom@ietf.org>; Fri, 19 Jun 2009 14:10:39 -0700 (PDT)
Received: from subman.resistor.net ([10.0.0.1]) (authenticated bits=0) by ns1.qubic.net (8.14.4.Alpha0/8.14.4.Alpha0) with ESMTP id n5JLAdYK013109 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 19 Jun 2009 14:10:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1245445848; x=1245532248; bh=UR9LcOQ/Ys6UR+lZMLPgJHoQ7LQdum6kXg8Jw65qvgU=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type; b=DIp6sX9sU3jjrKOtJrnQriYVfOOQwynbpG1f7N85LtQ0k80TlkkI36UEZEHDsoJ6T NZ/++7Mkvb3LxgKlCOsyv4lrdOpZBvsOUTg3rn/J1YG94oWm6MjYud7XoCtnCugc2L aQpVjfzFX/AY8xU1elTbd49VtUEFSpqXDZDDOFfQ=
DomainKey-Signature: a=rsa-sha1; s=mail; d=resistor.net; c=simple; q=dns; b=eJcXZn/06vWokpjpJy6jxbq7TkYt/gW5buF85IkRBgzlehnlL68XBapTEnlk5AGlN 3hPmoBn0pvhI/KC29nCYHtNgS0Ecx/ZxNqyt0Qp6Kj7nycuYwT+z7x24KFgKAE8SSLn jlXBTTAH5/DuRfPOJUH5MokM+NYIreK//EHbN4c=
Message-Id: <6.2.5.6.2.20090619123239.03040128@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 19 Jun 2009 14:07:49 -0700
To: "Joel M. Halpern" <jmh@joelhalpern.com>
From: SM <sm@resistor.net>
In-Reply-To: <4A3B910D.5080606@joelhalpern.com>
References: <FF562A73757F9F6294CCD4D5@PST.JCK.COM> <4A1D5086.9080702@joelhalpern.com> <36E1A7176AF78A864F74EAC6@PST.JCK.COM> <6c9fcc2a0906182149q4ae1e57bs39b24d4561281634@mail.gmail.com> <4A3B910D.5080606@joelhalpern.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Cc: NomComDiscussion <ietf-nomcom@ietf.org>
Subject: Re: [ietf-nomcom] Changing the candidate selection model
X-BeenThere: ietf-nomcom@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions of possible revisions to the NomCom process <ietf-nomcom.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Fri, 19 Jun 2009 21:10:40 -0000
Hi Joel, At 06:22 19-06-2009, Joel M. Halpern wrote: >John suggested in one of his notes that approving the current >open-list change would be a distraction from evaluating his >proposal. I would strongly disagree. Having an open list fulfills our innate curiosity. If the open-list change goes through, it will delay John's proposal as the community will wait to see the results. These micro-changes, which may have major effects, have brought up questions about the process. There was a comment about whether a sentence in draft-dawkins-nomcom-openlist should have used a "must" instead of a "should". This highlights the frame of mind in reading that document. We are accustomed to using RFC 2119 key words in documenting protocols. Is this document a protocol or to put it differently, will we reach the best outcome by following a protocol? Even draft-dawkins-nomcom-openlist has exceptions. In my opinion, this shows that we cannot craft narrow rules as we also have to consider the circumstances. Is there an ideal candidate for the opening? If there were, we would be choosing a stereotype which would prevent any change in the body from within. That can be good if we want to go on with business as usual. But that creates a disconnect between the community and the body. The feedback from the community demonstrates that most participants keep away from process issues. We only have to look at the NomCom roll call each year to see that it is a particular subset of the community. Regards, -sm
- Re: [ietf-nomcom] Changing the candidate selectio… Eric Rosen
- [ietf-nomcom] Changing the candidate selection mo… John C Klensin
- Re: [ietf-nomcom] Changing the candidate selectio… Joel M. Halpern
- Re: [ietf-nomcom] Changing the candidate selectio… SM
- Re: [ietf-nomcom] Changing the candidate selectio… Fred Baker
- Re: [ietf-nomcom] Changing the candidate selectio… SM
- Re: [ietf-nomcom] Changing the candidate selectio… John C Klensin
- Re: [ietf-nomcom] Changing the candidate selectio… Joel M. Halpern
- Re: [ietf-nomcom] Changing the candidate selectio… Barry Leiba
- Re: [ietf-nomcom] Changing the candidate selectio… Joel M. Halpern
- Re: [ietf-nomcom] Changing the candidate selectio… Bernie Hoeneisen
- Re: [ietf-nomcom] Changing the candidate selectio… Joel M. Halpern
- Re: [ietf-nomcom] Changing the candidate selectio… SM
- Re: [ietf-nomcom] Changing the candidate selectio… Christian Huitema
- Re: [ietf-nomcom] Changing the candidate selectio… Spencer Dawkins
- Re: [ietf-nomcom] Changing the candidate selectio… Spencer Dawkins
- Re: [ietf-nomcom] Changing the candidate selectio… John C Klensin
- Re: [ietf-nomcom] Changing the candidate selectio… Eric Rosen
- Re: [ietf-nomcom] Changing the candidate selectio… John C Klensin
- Re: [ietf-nomcom] Changing the candidate selectio… John C Klensin