Re: [Pesci-discuss] Growing concerns about PESCI

Leslie Daigle <leslie@thinkingcat.com> Fri, 28 October 2005 23:50 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 1EVdzU-00081v-NP; Fri, 28 Oct 2005 19:50:32 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EVdzS-00080A-A1 for pesci-discuss@megatron.ietf.org; Fri, 28 Oct 2005 19:50:31 -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 TAA27651 for <pesci-discuss@ietf.org>; Fri, 28 Oct 2005 19:50:12 -0400 (EDT)
Received: from zeke.blacka.com ([69.31.8.124] helo=zeke.ecotroph.net) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EVeD6-00010s-F1 for pesci-discuss@ietf.org; Fri, 28 Oct 2005 20:04:37 -0400
Received: from [192.168.0.101] ([::ffff:64.102.254.33]) (AUTH: PLAIN leslie, SSL: TLSv1/SSLv3,256bits,AES256-SHA) by zeke.ecotroph.net with esmtp; Fri, 28 Oct 2005 19:50:14 -0400 id 01588087.4362B936.000023AE
Message-ID: <4362B932.7010709@thinkingcat.com>
Date: Fri, 28 Oct 2005 19:50:10 -0400
From: Leslie Daigle <leslie@thinkingcat.com>
User-Agent: Mozilla Thunderbird 1.0.2 (Macintosh/20050317)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Scott W Brim <swb@employees.org>
Subject: Re: [Pesci-discuss] Growing concerns about PESCI
References: <web-3031527@multicasttech.com> <435E7183.4080000@thinkingcat.com> <2D6A134D3C8C93F22B716D96@scan.jck.com> <94658BD071BC97A0EAA1F038@B50854F0A9192E8EC6CDA126> <FB89B35D67102FF1B8C55EE8@scan.jck.com> <435E6321.2020205@thinkingcat.com> <20051027151316.GC1704@sbrim-wxp01>
In-Reply-To: <20051027151316.GC1704@sbrim-wxp01>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a
Content-Transfer-Encoding: 7bit
Cc: pesci-discuss@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

I really hate to beat a dead horse, but not quite so
much as I hate being misunderstood.

A bit of my message that you chose not to quote and
therefore I assume overlooked:

> On the "-discuss" list, the lead of the design team has asked
> folks to hash through issues, review the document, and contribute
> brain trust. 


Why are people talking on this list?  In a WG, one contributes
to the WG effort, which has a *charter*, and if the design
team fails to listen to the WG, it is (one hopes) fired,
and the WG finds a different way to solve its chartered
problem.  *That's* why we post to WG lists, right?  We're
part of the work.

Here, we're all just yakking.

Which is fine, as long as we *all* remember that.

Some people are here because they care about the outcome,
and will discuss it in any available venue.  Fine.

Some people are *not* here, even though they care about
the outcome, because they know this list is just a "-discuss"
list.

Which is fine, as long as we *all* remember that, too.

Leslie.

Scott W Brim wrote:
> (limiting to pesci-discuss)
> 
> On Tue, Oct 25, 2005 12:53:53PM -0400, Leslie Daigle allegedly wrote:
> 
>>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.
> 
> 
> First, there is no piece of IETF standards process that requires a WG
> design team to listen to WG discussion either.  They can reject it, in
> which case their solution will likely be rejected.  Second, since
> PESCI has no power, what is the concern?  
> 
> 
>>So, a genuine question:  is PESCI blurring lines, or does
>>this suggest that we have in fact given up on WGs/our process?
> 
> 
> I don't know that PESCI blurs lines, but it clearly doesn't fit in the
> existing ones.  However, that doesn't have to mean that we have given
> up on our process yet.  I certainly hope not :-).
> 

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