Re: [Pesci-discuss] Growing concerns about PESCI

"Spencer Dawkins" <spencer@mcsr-labs.org> Tue, 25 October 2005 17:31 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EUSe7-0000MR-Om; Tue, 25 Oct 2005 13:31:37 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EUSe5-0000LU-9h; Tue, 25 Oct 2005 13:31:33 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA07407; Tue, 25 Oct 2005 13:31:19 -0400 (EDT)
Received: from sccrmhc14.comcast.net ([63.240.77.84]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUSr2-0003WH-DB; Tue, 25 Oct 2005 13:44:59 -0400
Received: from s73602 (s73602.china.huawei.com[192.35.166.32]) by comcast.net (sccrmhc14) with SMTP id <2005102517310801400rp8lte>; Tue, 25 Oct 2005 17:31:12 +0000
Message-ID: <090a01c5d989$d46b35b0$20a623c0@china.huawei.com>
From: "Spencer Dawkins" <spencer@mcsr-labs.org>
To: <pesci-discuss@ietf.org>
References: <2D6A134D3C8C93F22B716D96@scan.jck.com> <94658BD071BC97A0EAA1F038@B50854F0A9192E8EC6CDA126><FB89B35D67102FF1B8C55EE8@scan.jck.com> <435E6321.2020205@thinkingcat.com>
Subject: Re: [Pesci-discuss] Growing concerns about PESCI
Date: Tue, 25 Oct 2005 10:30:35 -0700
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Content-Transfer-Encoding: 7bit
Cc: ietf@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

> The big difference is -- there is absolutely no piece of IETF
> standards process that *requires* that the "design team" listen to any
> of the points provided on the "-discuss" list.  There is a tacit
> requirement, in that one presumes the appropriate AD will be recalled if
> the result is clearly and obviously out of step with what the community
> asks, but that's a high-risk negative motivation.
>
> So, a genuine question:  is PESCI blurring lines, or does
> this suggest that we have in fact given up on WGs/our process?

I think *I* have (given up on using the WG process for process evolution). I 
am not sure at all that *we* have.

My reasons were pretty well summarized in the Paris plenary discussions 
(expecting the IESG to spend significant time on process evolution, 
especially when proposals involving major IESG restructuring were on the 
table).

I have expressed some of the same concerns on PESCI-discuss that John 
included in his note, so I'm not saying that current-PESCI is either perfect 
or the only alternative.

> Leslie.

Spencer 


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