[Pesci-discuss] pesci-next-steps general approach
"JFC (Jefsey) Morfin" <jefsey@jefsey.com> Sun, 26 February 2006 01:18 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FDAXz-0000JW-UN; Sat, 25 Feb 2006 20:18:03 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FDAXy-0000JR-NP for pesci-discuss@ietf.org; Sat, 25 Feb 2006 20:18:02 -0500
Received: from montage.altserver.com ([63.247.74.122]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FDAXx-0003Ta-H6 for pesci-discuss@ietf.org; Sat, 25 Feb 2006 20:18:02 -0500
Received: from ver78-2-82-241-91-24.fbx.proxad.net ([82.241.91.24] helo=JFCM.afrac.org) by montage.altserver.com with esmtpa (Exim 4.52) id 1FDAXw-0007tq-OB for pesci-discuss@ietf.org; Sat, 25 Feb 2006 17:18:01 -0800
Message-Id: <6.2.3.4.2.20060226010153.05bf8d50@mail.jefsey.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.3.4
Date: Sun, 26 Feb 2006 02:17:51 +0100
To: pesci-discuss@ietf.org
From: "JFC (Jefsey) Morfin" <jefsey@jefsey.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"; x-avg-checked="avg-ok-334E3637"
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - montage.altserver.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - jefsey.com
X-Source:
X-Source-Args:
X-Source-Dir:
X-Spam-Score: 0.1 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Subject: [Pesci-discuss] pesci-next-steps general approach
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
The proposed Draft actually lead to the list in part 3. I am embrassed about it. I read it as a "bottom-up" thinking, where a bootstrap would have a "top-down" thinking. I mean that the basis is "what are the tasks we currently face?". While an initial thinking would be "what are our intended deliverables, how will we manage to deliver them?". I feel the intent more as a fix than a re-build? Both are changes. I felt Brian wanted something more a re-build mechanism than a fix? I know it is not easy, but I would rather say: - what do we want to deliver? - how could we do it? Here the different propositions the same. - what does experience has to say? - what is the solution we want? - how do we transition to it? considering the whole IETF at the same time. Considering the IESG first and other issues afterward will lead to organise new responses to current needs, possibly organising new non-IESG solutions, the step further may change, asking for a new IESG change again? For example, what if the best solution is the end of the IESG and a totally new IETF structure. How could we consider this with this process? Or may be I did not understood the complete idea? jfc _______________________________________________ Pesci-discuss mailing list Pesci-discuss@ietf.org https://www1.ietf.org/mailman/listinfo/pesci-discuss
- [Pesci-discuss] pesci-next-steps general approach JFC (Jefsey) Morfin