What we need done (Re: first steps (was The other parts of the report...))

Harald Tveit Alvestrand <harald@alvestrand.no> Sun, 12 September 2004 22:08 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA15344; Sun, 12 Sep 2004 18:08:45 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C6cbD-0000iy-M7; Sun, 12 Sep 2004 18:13:31 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C6cU6-000345-N5; Sun, 12 Sep 2004 18:06:10 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C6cTG-0002mY-LZ for ietf@megatron.ietf.org; Sun, 12 Sep 2004 18:05:18 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA14927 for <ietf@ietf.org>; Sun, 12 Sep 2004 18:05:15 -0400 (EDT)
Received: from eikenes.alvestrand.no ([158.38.152.233]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C6cXo-0000eA-EL for ietf@ietf.org; Sun, 12 Sep 2004 18:10:01 -0400
Received: from localhost (localhost.localdomain [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 3FECD61BB0; Mon, 13 Sep 2004 00:04:45 +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 09405-04; Mon, 13 Sep 2004 00:04:43 +0200 (CEST)
Received: from halvestr-w2k02.emea.cisco.com (localhost.localdomain [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 52E6F61AD4; Mon, 13 Sep 2004 00:04:42 +0200 (CEST)
Date: Sun, 12 Sep 2004 22:39:36 +0200
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: John C Klensin <john-ietf@jck.com>, scott bradner <sob@harvard.edu>, ietf@ietf.org
Message-ID: <DE760786F29ABDCA5BCD33FB@B50854F0A9192E8EC6CDA126>
In-Reply-To: <00A7150A4512700F34111641@scan.jck.com>
References: <20040911210653.A62C48958A@newdev.harvard.edu> <EFB15D2F62C4D0CBEC54E5A4@askvoll.hjemme.alvestrand.no> <00A7150A4512700F34111641@scan.jck.com>
X-Mailer: Mulberry/3.1.5 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Virus-Scanned: by amavisd-new at alvestrand.no
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Content-Transfer-Encoding: 7bit
Subject: What we need done (Re: first steps (was The other parts of the report...))
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
Content-Transfer-Encoding: 7bit


--On 12. september 2004 12:19 -0400 John C Klensin <john-ietf@jck.com> 
wrote:

> To further complicate things, I personally don't think the IETF
> has yet figured out enough about what it really wants from the
> secretariat part of the function and reached enough consensus on
> that to justify any RFP-writing.  In this respect, the material
> in The Report seems to me to be inadequate unless the definition
> of what the IETF wants from the secretariat is "whatever the
> IESG or its leadership decide they want on a given day".

permit me to respectfully disagree......

The things that we need done in the "clerk's office" aren't actually that 
novel. It's basic workplan management and document management, for the most 
part. Scale and the responsiveness of participants may be different from 
other organizations - but not THAT different.

And there's a whole lot of things other organizations do (outreach, 
exhibitions, membership management, dues processing) that we simply don't 
do.

Granted, we've grown a thicket of tradition and bizarre quirks over the 
years (for instance, we have archives of old I-Ds, and archive our mailing 
lists, but have no archives of old WG charters), but some of these are 
things that could benefit from a real "why do you need this?" look, and 
others are relatively easily implementable on more-or-less standard 
processing tools (I believe).

I suspect that the only way we can figure out if anyone can figure out what 
we want done from the descriptions we give is to ask them - we don't have 
any experience figuring out what the processes of an organization is, we 
just have experience with living inside this single instance.
(OK, some of us have experience from other orgs too....)

                   Harald




_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf