Re: [Pesci-discuss] Growing concerns about PESCI
"Marshall Eubanks" <tme@multicasttech.com> Tue, 25 October 2005 18:22 UTC
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
by megatron.ietf.org with esmtp (Exim 4.32)
id 1EUTRK-0004fy-2G; Tue, 25 Oct 2005 14:22:26 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
by megatron.ietf.org with esmtp (Exim 4.32) id 1EUTRJ-0004fg-94
for pesci-discuss@megatron.ietf.org; Tue, 25 Oct 2005 14:22:25 -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 OAA10492
for <pesci-discuss@ietf.org>; Tue, 25 Oct 2005 14:22:11 -0400 (EDT)
Received: from lennon.multicasttech.com
([63.105.122.7] helo=multicasttech.com ident=root)
by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUTeI-00057I-G3
for pesci-discuss@ietf.org; Tue, 25 Oct 2005 14:35:52 -0400
Received: from [70.179.105.193] (account <marshall_eubanks@multicasttech.com>)
by multicasttech.com (CommuniGate Pro WebUser 3.4.8)
with HTTP id 3031580; Tue, 25 Oct 2005 14:22:12 -0400
From: "Marshall Eubanks" <tme@multicasttech.com>
Subject: Re: [Pesci-discuss] Growing concerns about PESCI
To: Leslie Daigle <leslie@thinkingcat.com>, Marshall Eubanks
<tme@multicasttech.com>
X-Mailer: CommuniGate Pro Web Mailer v.3.4.8
Date: Tue, 25 Oct 2005 14:22:12 -0400
Message-ID: <web-3031580@multicasttech.com>
In-Reply-To: <435E7183.4080000@thinkingcat.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
Content-Transfer-Encoding: 8bit
Cc: John C Klensin <john-ietf@jck.com>, pesci-discuss@ietf.org, Harald
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 Tue, 25 Oct 2005 13:55:15 -0400 Leslie Daigle <leslie@thinkingcat.com> wrote: > > 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. > Oh, I just got tired of receiving two copies of every message. > 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). > No, that's not what I mean, more the opposite. I agree with you; I am not that humble, if I bother to post to a WG list, I expect at least cursory attention. My meaning was just that there is never a way to _enforce_ paying attention, or rather, to force changes in direction as a result of paying attention. (I worked in the Government, I know better.) However, I think that most of us can judge if good ideas are getting listened to or are being ignored. In my limited experience, if a WG is too "wired", people will either leave or complain. In this case, I would expect loud complaints. I happen to think that the WG model works surprisingly well, and that most of the time, WG members are listened to and can affect the course of events. Such openness may not be rigorously enforceable, but it can be approached asymptotically, which is really all that we can ask for. I would hope that PESCI would aspire to the same standard. > Leslie. > > > Marshall _______________________________________________ Pesci-discuss mailing list Pesci-discuss@ietf.org https://www1.ietf.org/mailman/listinfo/pesci-discuss
- [Pesci-discuss] Growing concerns about PESCI John C Klensin
- Re: [Pesci-discuss] Growing concerns about PESCI Harald Tveit Alvestrand
- RE: [Pesci-discuss] Growing concerns about PESCI Wijnen, Bert (Bert)
- Re: [Pesci-discuss] Growing concerns about PESCI John C Klensin
- Re: [Pesci-discuss] Growing concerns about PESCI Leslie Daigle
- Re: [Pesci-discuss] Growing concerns about PESCI Adrian Farrel
- Re: [Pesci-discuss] Growing concerns about PESCI Spencer Dawkins
- Re: [Pesci-discuss] Growing concerns about PESCI Marshall Eubanks
- Re: [Pesci-discuss] Growing concerns about PESCI Leslie Daigle
- Re: [Pesci-discuss] Growing concerns about PESCI Marshall Eubanks
- Re: [Pesci-discuss] Growing concerns about PESCI John C Klensin
- Re: [Pesci-discuss] Growing concerns about PESCI Spencer Dawkins
- Re: [Pesci-discuss] Growing concerns about PESCI Marshall Eubanks
- Re: [Pesci-discuss] Growing concerns about PESCI John C Klensin
- RE: [Pesci-discuss] Growing concerns about PESCI Pekka Savola
- [Pesci-discuss] stack overflow Dave Crocker
- Re: [Pesci-discuss] stack overflow Melinda Shore
- Re: [Pesci-discuss] stack overflow JFC (Jefsey) Morfin
- Re: [Pesci-discuss] Growing concerns about PESCI Brian E Carpenter
- [Pesci-discuss] Growing concerns about PESCI John C Klensin
- Re: [Pesci-discuss] Growing concerns about PESCI John C Klensin
- Re: [Pesci-discuss] Growing concerns about PESCI Brian E Carpenter
- Plenary [Re: [Pesci-discuss] Growing concerns abo… Brian E Carpenter
- Decision process [Re: [Pesci-discuss] stack overf… Brian E Carpenter
- Re: Plenary [Re: [Pesci-discuss] Growing concerns… Scott W Brim
- Re: [Pesci-discuss] Growing concerns about PESCI Scott W Brim
- Re: [Pesci-discuss] Growing concerns about PESCI Scott W Brim
- Re: [Pesci-discuss] stack overflow Scott W Brim
- Re: Decision process [Re: [Pesci-discuss] stack o… Melinda Shore
- Re: [Pesci-discuss] stack overflow Dave Crocker
- Re: Decision process [Re: [Pesci-discuss] stack o… Harald Tveit Alvestrand
- Re: Decision process [Re: [Pesci-discuss] stack o… JFC (Jefsey) Morfin
- Re: [Pesci-discuss] stack overflow Brian E Carpenter
- Re: Plenary [Re: [Pesci-discuss] Growing concerns… Sam Hartman
- Re: [Pesci-discuss] stack overflow Dave Crocker
- Re: [Pesci-discuss] Growing concerns about PESCI Leslie Daigle
- Re: [Pesci-discuss] Growing concerns about PESCI Scott W Brim
- Re: [Pesci-discuss] stack overflow Dave Crocker
- Re: [Pesci-discuss] Growing concerns about PESCI Leslie Daigle