Re: [Pesci-discuss] Growing concerns about PESCI

Leslie Daigle <leslie@thinkingcat.com> Tue, 25 October 2005 17:56 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EUT1m-0008Rm-Uy; Tue, 25 Oct 2005 13:56:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EUT1l-0008Rh-Dw for pesci-discuss@megatron.ietf.org; Tue, 25 Oct 2005 13:56:01 -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 NAA08984 for <pesci-discuss@ietf.org>; Tue, 25 Oct 2005 13:55:47 -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 1EUTEg-0004Hy-DH for pesci-discuss@ietf.org; Tue, 25 Oct 2005 14:09:28 -0400
Received: from [192.35.165.156] ([::ffff:128.107.248.220]) (AUTH: PLAIN leslie, SSL: TLSv1/SSLv3,256bits,AES256-SHA) by zeke.ecotroph.net with esmtp; Tue, 25 Oct 2005 13:55:19 -0400 id 01588063.435E7189.00005A8F
Message-ID: <435E7183.4080000@thinkingcat.com>
Date: Tue, 25 Oct 2005 13:55:15 -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: Marshall Eubanks <tme@multicasttech.com>
Subject: Re: [Pesci-discuss] Growing concerns about PESCI
References: <web-3031527@multicasttech.com>
In-Reply-To: <web-3031527@multicasttech.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Content-Transfer-Encoding: 7bit
Cc: John C Klensin <john-ietf@jck.com>, 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've respected your cc trim, but will observe that you
are assuming PESCI is a WG, which is not clear to me,
and it doesn't strike me this is a PESCI issue.

Marshall Eubanks wrote:
> Or, maybe I missed something, but is a design team ever *required* to act on points raised on the
> miling list ? IIRC IETF does not operate on votes.


I started writing that thought when I asked myself why I
would bother to contribute to the PESCI discuss mailing
list.  My time (like everyone else's on this list) is
valuable.  I *contribute* to WGs because it's a contribution
to an open WG effort, whether or not the design team picks up
on it.

If you want to say "it doesn't matter, it's all bits in the
wind until there's a final document proposal that goes through
last call", then that's fine:  it's your answer to my question.
But it also doesn't answer whether we need to bother with
WGs at all (for other topics).

Leslie.




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