Re: [Pesci-discuss] principles for decision-making

Sam Hartman <hartmans-ietf@mit.edu> Sun, 06 November 2005 16:57 UTC

Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EYnpd-0004XO-B6; Sun, 06 Nov 2005 11:57:25 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EYnpb-0004XC-3E for pesci-discuss@megatron.ietf.org; Sun, 06 Nov 2005 11:57:23 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07711 for <pesci-discuss@ietf.org>; Sun, 6 Nov 2005 11:56:58 -0500 (EST)
Received: from pp109-223.bctel.ca ([209.52.109.223] helo=carter-zimmerman.mit.edu) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EYo52-0007Du-G1 for pesci-discuss@ietf.org; Sun, 06 Nov 2005 12:13:20 -0500
Received: by carter-zimmerman.mit.edu (Postfix, from userid 8042) id ED8D6E006E; Sun, 6 Nov 2005 11:57:27 -0500 (EST)
To: Jari Arkko <jari.arkko@piuha.net>
Subject: Re: [Pesci-discuss] principles for decision-making
References: <BF8CF6A3.3317%mshore@cisco.com> <tslu0ew9w3m.fsf@cz.mit.edu> <43679B5F.8030201@piuha.net>
From: Sam Hartman <hartmans-ietf@mit.edu>
Date: Sat, 05 Nov 2005 19:00:53 -0500
In-Reply-To: <43679B5F.8030201@piuha.net> (Jari Arkko's message of "Tue, 01 Nov 2005 18:44:15 +0200")
Message-ID: <tslfyqalk5m.fsf@cz.mit.edu>
User-Agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Spam-Score: 3.0 (+++)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Cc: "pesci-discuss@ietf.org" <pesci-discuss@ietf.org>
X-BeenThere: pesci-discuss@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Process Evolution Study Committee of the IETF discussion <pesci-discuss.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pesci-discuss>, <mailto:pesci-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/pesci-discuss>
List-Post: <mailto:pesci-discuss@ietf.org>
List-Help: <mailto:pesci-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pesci-discuss>, <mailto:pesci-discuss-request@ietf.org?subject=subscribe>
Sender: pesci-discuss-bounces@ietf.org
Errors-To: pesci-discuss-bounces@ietf.org

>>>>> "Jari" == Jari Arkko <jari.arkko@piuha.net> writes:

    Jari> I'm also in for "rough consensus" (sometimes we try to make
    Jari> it too smooth) as well as "running code" (we need more of
    Jari> that).

    Jari> However, I'd like to make an observation that there may be
    Jari> different decision processes depending on the type of
    Jari> decision involved. I believe very much that on our basic
    Jari> technical work RCRC should apply. But we already apply
    Jari> different principles in different parts of the
    Jari> organization. For instance, nomcom has its special
    Jari> procedures. IESG has its special procedures -- not sure how
    Jari> I should classify them, would "absolute consensus" or
    Jari> "voting" describe the final IESG review model better than
    Jari> RCRC? And I'm fine with having these specific processes. 

I think the IESG actually follows RC RC although we've defined an
explicit measure of what rough is for documents at least.  Rough is
two ADs left out on an override vote.

I do agree that special processes for some things such as process
change may be appropriate.  I think the community would need to agree
to these processes.  I also think that ultimately the community needs
to at least have a consensus to consent to a process change.  We might
decide that community level line item editing of process changes is
something that doesn't work, but at least a community consensus call
at the end seems important.

--Sam


_______________________________________________
Pesci-discuss mailing list
Pesci-discuss@ietf.org
https://www1.ietf.org/mailman/listinfo/pesci-discuss