[Pesci-discuss] Re: PESCI, WGs and the consensus process

Harald Tveit Alvestrand <harald@alvestrand.no> Wed, 26 October 2005 13:03 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EUkwa-0003Xk-66; Wed, 26 Oct 2005 09:03:52 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EUkwZ-0003WJ-1h for pesci-discuss@megatron.ietf.org; Wed, 26 Oct 2005 09:03:51 -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 JAA17956 for <pesci-discuss@ietf.org>; Wed, 26 Oct 2005 09:03:35 -0400 (EDT)
Received: from eikenes.alvestrand.no ([158.38.152.233]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUl9h-0000nM-QT for pesci-discuss@ietf.org; Wed, 26 Oct 2005 09:17:27 -0400
Received: from localhost (eikenes.alvestrand.no [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 6C83D258043; Wed, 26 Oct 2005 15:03:01 +0200 (CEST)
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 17156-03; Wed, 26 Oct 2005 15:02:56 +0200 (CEST)
Received: from halvestr-w2k02.emea.cisco.com (eikenes.alvestrand.no [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 729EF25808E; Wed, 26 Oct 2005 15:02:55 +0200 (CEST)
Date: Wed, 26 Oct 2005 06:03:12 -0700
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Leslie Daigle <leslie@thinkingcat.com>
Message-ID: <7E8580B4B0A857FAD4CB807C@B50854F0A9192E8EC6CDA126>
In-Reply-To: <435E8177.8040206@thinkingcat.com>
References: <3F389A9BBE9989C57941FC03@B50854F0A9192E8EC6CDA126> <435E8177.8040206@thinkingcat.com>
X-Mailer: Mulberry/4.0.3 (Win32)
MIME-Version: 1.0
X-Virus-Scanned: by amavisd-new at alvestrand.no
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c
Cc: pesci-discuss@ietf.org
Subject: [Pesci-discuss] Re: PESCI, WGs and the consensus process
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>
Content-Type: multipart/mixed; boundary="===============1463421354=="
Sender: pesci-discuss-bounces@ietf.org
Errors-To: pesci-discuss-bounces@ietf.org


--On 25. oktober 2005 15:03 -0400 Leslie Daigle <leslie@thinkingcat.com> 
wrote:

>
> And so my question:  why is this different for PESCI?
>
> (Why) is it not applicable for MARID?

It might be. They certainly share the distinction of having failed to work 
out the problem in a WG.
At one point I thought that was what the DEA Directorate was supposed to 
be, but I haven't seen much from it, so I'm not sure what the theory of 
what it's supposed to accomplish is at the moment.

> And, if you see a distinction, come back and make sure the
> PESCI list doesn't fall into being treated as, or thinking
> it is, a WG.

There is one distinction.....

The theory of WGs is that it allows the people who have expertise to 
contribute to get together, while the people who don't have expertise to 
contribute can go do something else until it's result review time.

The subject of spam concerns directly everyone who uses email, and even 
more directly everyone who runs, develops or designs email systems.
The first group is significantly larger than the IETF; the second group has 
an overlap with the IETF, but the size of the overlap is debatable. 
Certainly MARID included a number of "old-time IETFers" as well as a number 
of people who hadn't been active in the IETF before.

In contrast:

The subject of how to run the IETF concerns directly everyone who *works* 
in the IETF - which is by definition, more or less, identical to the IETF 
community.

I'm not sure what conclusions to draw from this difference, but it *is* a 
difference.

                    Harald

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