[Pesci-discuss] Re: draft-davies-pesci-next-steps-00.txt
Pekka Savola <pekkas@netcore.fi> Sun, 19 March 2006 15:45 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FL06O-0006F4-7R; Sun, 19 Mar 2006 10:45:56 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FL06M-0005sa-5N for pesci-discuss@ietf.org; Sun, 19 Mar 2006 10:45:54 -0500
Received: from netcore.fi ([193.94.160.1]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FL06L-00075v-Mv for pesci-discuss@ietf.org; Sun, 19 Mar 2006 10:45:54 -0500
Received: from netcore.fi (localhost [127.0.0.1]) by netcore.fi (8.12.8/8.12.8) with ESMTP id k2JFjqHa028530 for <pesci-discuss@ietf.org>; Sun, 19 Mar 2006 17:45:52 +0200
Received: from localhost (pekkas@localhost) by netcore.fi (8.12.8/8.12.8/Submit) with ESMTP id k2JFjpWl028527 for <pesci-discuss@ietf.org>; Sun, 19 Mar 2006 17:45:52 +0200
Date: Sun, 19 Mar 2006 17:45:51 +0200
From: Pekka Savola <pekkas@netcore.fi>
To: pesci-discuss@ietf.org
In-Reply-To: <44055963.4020304@zurich.ibm.com>
Message-ID: <Pine.LNX.4.64.0603191741050.26745@netcore.fi>
References: <E1FEEbS-0006vO-Cl@stiedprstage1.ietf.org> <44055963.4020304@zurich.ibm.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
X-Virus-Scanned: ClamAV 0.88/1338/Sun Mar 19 02:04:12 2006 on otso.netcore.fi
X-Virus-Status: Clean
X-Spam-Status: No, score=-1.4 required=5.0 tests=ALL_TRUSTED autolearn=failed version=3.1.0
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on otso.netcore.fi
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Subject: [Pesci-discuss] Re: draft-davies-pesci-next-steps-00.txt
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>
Errors-To: pesci-discuss-bounces@ietf.org
A couple of comments: 2.1. Change Process Proposal The teams should function with an open discussion list, in the same way that the PESCI team has done. The output of each team should be tested against the IETF consensus in the normal fashion; we believe that if there is clear IETF consensus that the proposal makes sense, the IESG (and the ISOC Board of Trustees) will respect that consensus and approve of it. ==> the consensus judged by _whom_? Did you mean rough consensus, btw? 3. Immediate Tasks for the Change Process This review should include: .... (9 bullets of stuff...) ==> this seems a very extensive task, with several separable pieces. The list seems to be written in such a way that I got the impression the "first team" should do all of the above. This doesn't seem productive at all. Is this (again) the case of, "by the way, could you please rewrite RFC2026 and all our process docs while you're at it.. THANKS!" ? -- Pekka Savola "You each name yourselves king, yet the Netcore Oy kingdom bleeds." Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings _______________________________________________ Pesci-discuss mailing list Pesci-discuss@ietf.org https://www1.ietf.org/mailman/listinfo/pesci-discuss
- [Pesci-discuss] [Fwd: I-D ACTION:draft-davies-pes… Brian E Carpenter
- [Pesci-discuss] Re: I-D ACTION:draft-davies-pesci… Brian E Carpenter
- [Pesci-discuss] Re: draft-davies-pesci-next-steps… Pekka Savola
- Re: [Pesci-discuss] Re: draft-davies-pesci-next-s… Brian E Carpenter
- Re: [Pesci-discuss] Re: draft-davies-pesci-next-s… Pekka Savola
- Re: [Pesci-discuss] Re: draft-davies-pesci-next-s… Brian E Carpenter