Re: [Pesci-discuss] Growing concerns about PESCI

Leslie Daigle <leslie@thinkingcat.com> Wed, 02 November 2005 04:28 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 1EXAEV-00069X-M5; Tue, 01 Nov 2005 23:28:19 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EXAEU-00068T-4d for pesci-discuss@megatron.ietf.org; Tue, 01 Nov 2005 23:28:18 -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 XAA09073 for <pesci-discuss@ietf.org>; Tue, 1 Nov 2005 23:27:57 -0500 (EST)
Received: from zeke.ecotroph.net ([69.31.8.124]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EXAT0-0003mD-H5 for pesci-discuss@ietf.org; Tue, 01 Nov 2005 23:43:18 -0500
Received: from [172.20.101.216] ([::ffff:128.107.248.220]) (AUTH: PLAIN leslie, SSL: TLSv1/SSLv3,256bits,AES256-SHA) by zeke.ecotroph.net with esmtp; Tue, 01 Nov 2005 23:27:44 -0500 id 01588029.43684041.00001DB9
Message-ID: <4368403C.4060507@thinkingcat.com>
Date: Tue, 01 Nov 2005 23:27:40 -0500
From: Leslie Daigle <leslie@thinkingcat.com>
User-Agent: Mozilla Thunderbird 1.0.7 (Macintosh/20050923)
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> <4362B932.7010709@thinkingcat.com> <20051029120257.GI4960@sbrim-wxp01>
In-Reply-To: <20051029120257.GI4960@sbrim-wxp01>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a2c12dacc0736f14d6b540e805505a86
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

(Catching up on a few days' mail) -- that's closer,
and we should take this up in person in a few days' time.


Leslie.

Scott W Brim wrote:
> On Fri, Oct 28, 2005 07:50:10PM -0400, Leslie Daigle allegedly wrote:
> 
>>I really hate to beat a dead horse, but not quite so
>>much as I hate being misunderstood.
> 
> 
> Boy, do I know that feeling!
> 
> 
>>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.
> 
> 
> OK, that all makes sense.  Is the point, here and below, that there is
> nothing to measure the output of the "design team" against?  If so, I
> agree that there's nothing external.  The draft sets up its own goals
> and measures.  Now the community has to make an evaluation, first of
> those measures.  In fact, the point of bringing up all those
> principles is to clarify the community's conceptual framework for
> evaluating both the PESCI work and what will come after.  Am I any
> closer to understanding what you're saying?  Time to let this go and
> do it in person?
> 
> Scott
> 
> 
>>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