Re: [Pesci-discuss] Growing concerns about PESCI

John C Klensin <john-ietf@jck.com> Tue, 25 October 2005 19:39 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EUUeK-0003hV-EX; Tue, 25 Oct 2005 15:39:56 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EUUeH-0003hN-Pl for pesci-discuss@megatron.ietf.org; Tue, 25 Oct 2005 15:39:54 -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 PAA14924 for <pesci-discuss@ietf.org>; Tue, 25 Oct 2005 15:39:39 -0400 (EDT)
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUUrH-0007Q9-Nc for pesci-discuss@ietf.org; Tue, 25 Oct 2005 15:53:21 -0400
Received: from [209.187.148.215] (helo=scan.jck.com) by bs.jck.com with esmtp (Exim 4.34) id 1EUUeE-000M4y-4m; Tue, 25 Oct 2005 15:39:50 -0400
Date: Tue, 25 Oct 2005 15:39:50 -0400
From: John C Klensin <john-ietf@jck.com>
To: Marshall Eubanks <tme@multicasttech.com>, Leslie Daigle <leslie@thinkingcat.com>, pesci-discuss@ietf.org
Subject: Re: [Pesci-discuss] Growing concerns about PESCI
Message-ID: <BA8CE111C79B286DB2446031@scan.jck.com>
In-Reply-To: <web-3031669@multicasttech.com>
References: <web-3031669@multicasttech.com>
X-Mailer: Mulberry/4.0.4 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
Content-Transfer-Encoding: 7bit
Cc:
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


--On Tuesday, 25 October, 2005 15:29 -0400 Marshall Eubanks
<tme@multicasttech.com> wrote:

>> Marshall, may I suggest that your note contains the internal
>> contradiction that is a significant part of the problem I'm
>> seeing here, and maybe part of the one Leslie is seeing as
>> well.
> 
> Reading through this, I am beginning to share your concerns. I
> can understand short-circuiting certain aspects of the process
> (such as the time to appear at Plenary), but I think that
> having a confusing process  is very dangerous. Is this
> going to be a new model for IETF processes ? If so,  what is
> it  exactly ? Is it  documented ? Did it pass any  form of
> review ?

Those all seem to be key questions.  And each of them gets more
important going forward: were the plan for PESCI to report in
Vancouver perhaps get out a quick rev to the I-D immediately
thereafter, and then shut down to be replaced by a normal
process, I wouldn't be worried enough to raise these issues at
this point.  But that does not appear to be the plan.

> It is also dangerous  to throw out a solution that works,
> albeit with flaws,  for one that has never been implemented
> but appears to be easier. It may not be.
> 
> In this particular case, I think that one risk is that the
> effort might collapse into a morass of arguing about process -
> really, arguing about how to argue. Such short cuts may
> deliver neither agreement nor speed.

Agreed.  And the concern about, and risk of, touching off an
argument about how to argue was exactly why I decided to say
nothing for the last several months.  At this point, the issues
with the process being followed --rather than speculation about
what that process might be-- seem to be significant enough to
risk a meta-meta-discussion.

    john


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