Re: first steps (was The other parts of the report...)

Harald Tveit Alvestrand <harald@alvestrand.no> Sun, 12 September 2004 14:22 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 KAA17776; Sun, 12 Sep 2004 10:22:12 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C6VJe-0001dM-3Q; Sun, 12 Sep 2004 10:26:54 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C6VCD-0005FC-NK; Sun, 12 Sep 2004 10:19:13 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C6VAS-0004LH-OF for ietf@megatron.ietf.org; Sun, 12 Sep 2004 10:17:24 -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 KAA17431 for <ietf@ietf.org>; Sun, 12 Sep 2004 10:17:22 -0400 (EDT)
Received: from eikenes.alvestrand.no ([158.38.152.233]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C6VEw-0001XL-Tu for ietf@ietf.org; Sun, 12 Sep 2004 10:22:04 -0400
Received: from localhost (localhost.localdomain [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 7286661BE0; Sun, 12 Sep 2004 16:16:51 +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 00891-06; Sun, 12 Sep 2004 16:16:50 +0200 (CEST)
Received: from [192.168.1.4] (145.80-202-211.nextgentel.com [80.202.211.145]) by eikenes.alvestrand.no (Postfix) with ESMTP id E6BD461BAC; Sun, 12 Sep 2004 16:16:49 +0200 (CEST)
Date: Sun, 12 Sep 2004 16:16:49 +0200
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: scott bradner <sob@harvard.edu>, ietf@ietf.org
Message-ID: <EFB15D2F62C4D0CBEC54E5A4@askvoll.hjemme.alvestrand.no>
In-Reply-To: <20040911210653.A62C48958A@newdev.harvard.edu>
References: <20040911210653.A62C48958A@newdev.harvard.edu>
X-Mailer: Mulberry/3.1.6 (Linux/x86)
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format="flowed"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
X-Virus-Scanned: by amavisd-new at alvestrand.no
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Content-Transfer-Encoding: quoted-printable
Subject: 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.1 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Content-Transfer-Encoding: quoted-printable


--On lørdag, september 11, 2004 17:06:53 -0400 scott bradner 
<sob@harvard.edu> wrote:

> imo it would least disruptive to follow option #3 (combo path)
> and try to negotiate a sole source contract with Foretec/CNRI for
> what Carl called the clerk function and maybe some other functions
> (imo it would be better to outsorce the management of the mailing
> lists and their archives to a company in that business)


One thing that worries me about the "piecemeal" approach with some 
functions under sole source is that for a long time we've been operating 
with all functions in one body (except for RFC Editor and IANA). There are 
some economies of scale with integrating those functions.

If we follow the combo path, we also commit ourselves to breaking the 
function into multiple pieces - which may discriminate against a solution 
where other suppliers of services may be able to do "the whole thing" more 
effectively than they can do parts of it.

How much is this a problem?


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