RE: [Pesci-discuss] For whom it may concern..

"Joel M. Halpern" <joel@stevecrocker.com> Thu, 10 November 2005 17:37 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 1EaGMJ-00046k-Tw; Thu, 10 Nov 2005 12:37:11 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EaGMI-00046f-Fr for pesci-discuss@megatron.ietf.org; Thu, 10 Nov 2005 12:37:10 -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 MAA20680 for <pesci-discuss@ietf.org>; Thu, 10 Nov 2005 12:36:39 -0500 (EST)
Received: from mail.shinkuro.com ([216.194.124.237] helo=execdsl.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EaGcV-0001Ry-Ea for pesci-discuss@ietf.org; Thu, 10 Nov 2005 12:53:56 -0500
Received: from [209.52.108.166] (HELO JMHLap3.stevecrocker.com) by execdsl.com (CommuniGate Pro SMTP 4.2.7) with ESMTP id 12766962 for pesci-discuss@ietf.org; Thu, 10 Nov 2005 10:35:28 -0700
Message-Id: <6.2.1.2.0.20051110123452.02e5e5d0@mail.stevecrocker.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.1.2
Date: Thu, 10 Nov 2005 12:36:45 -0500
To: pesci-discuss@ietf.org
From: "Joel M. Halpern" <joel@stevecrocker.com>
Subject: RE: [Pesci-discuss] For whom it may concern..
In-Reply-To: <011a01c5e614$2d80d740$de6d34d1@instant802.com>
References: <Pine.LNX.4.64.0511101755130.23850@netcore.fi> <011a01c5e614$2d80d740$de6d34d1@instant802.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
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

I believe that process proposals need to be an exception to this.
As far as I can tell, the community will never reach rough consensus on any 
of the major process changes.
(It was hard enough to get rough consensus on minor changes.)
As I said at the meeting, while such an absence can be used as an excuse 
for not making any major changes, that would seem to be an inappropriate 
response.

Yours,
Joel M. Halpern

At 11:31 AM 11/10/2005, Margaret Wasserman wrote:


>
> > We already have a lot of those.  John Klensin's review team; Harald's
> > two-level.  Alex Zinin's early review.  Maybe others I forgot.
> >
> > It's not the lack of specific proposals on a specific problem space,
> > it's the lack of follow-through.
> >
> > Based on what I've seen,
> >   - it's not realistic to assume that the IESG will drive forward such
> > a proposal, and
> >   - it's not realistic to assume the author of such a proposal would
> > drive it through all by him/herself.
>
>This can be said of virtually all proposals in the IETF (including technical
>ones).  Without a critical mass of people who are willing to work on a given
>proposal, the proposal won't go forward.
>
>I don't see why process proposals should be an exception to this...
>
>Margaret
>
>
>
>
>_______________________________________________
>Pesci-discuss mailing list
>Pesci-discuss@ietf.org
>https://www1.ietf.org/mailman/listinfo/pesci-discuss


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