Re: On the difference between scenarios A and B in Carl's report

Geoff Huston <gih@apnic.net> Tue, 07 September 2004 22:52 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 SAA15655; Tue, 7 Sep 2004 18:52:23 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C4osf-0001p0-9b; Tue, 07 Sep 2004 18:56:05 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C4oaK-0000HW-DI; Tue, 07 Sep 2004 18:37:08 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C4oQ2-0004yB-Ju for ietf@megatron.ietf.org; Tue, 07 Sep 2004 18:26:30 -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 SAA13956 for <ietf@ietf.org>; Tue, 7 Sep 2004 18:26:27 -0400 (EDT)
Received: from kahuna.telstra.net ([203.50.0.6]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C4oTX-0001MN-OV for ietf@ietf.org; Tue, 07 Sep 2004 18:30:09 -0400
Received: from gihz1.apnic.net (dhcp4.potaroo.net [203.10.60.4]) by kahuna.telstra.net (8.12.3/8.11.3) with ESMTP id i87MPjwQ015737 for <ietf@ietf.org>; Wed, 8 Sep 2004 08:25:55 +1000 (EST) (envelope-from gih@apnic.net)
Message-Id: <6.0.1.1.2.20040908081349.020ee038@kahuna.telstra.net>
X-Sender: gih@kahuna.telstra.net
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Wed, 08 Sep 2004 08:25:51 +1000
To: ietf@ietf.org
From: Geoff Huston <gih@apnic.net>
In-Reply-To: <p0611042abd6278e16b16@[10.20.30.249]>
References: <129F9C12EAF23C28123178C5@B50854F0A9192E8EC6CDA126> <98BC694FC738F25CDDD1F057@scan.jck.com> <D861C55CC192D6F9BC2304DD@B50854F0A9192E8EC6CDA126> <p0611042abd6278e16b16@[10.20.30.249]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Subject: Re: On the difference between scenarios A and B in Carl's 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: 8b30eb7682a596edff707698f4a80f7d

>At 7:57 PM +0200 9/6/04, Harald Tveit Alvestrand wrote:
>>It seems to me that we are rapidly converging on one point of total IETF 
>>consensus:
>>
>>  Putting the IETF administrative function under ISOC requires a documented
>>  IETF-ISOC agreement (call it an MoU, a contract or something else - it IS
>>  a document, it IS an agreement and it DOES have two parties).
>>
>>Agreed?


Its easy to identify the first party to this MoU - its ISOC, but, in a 
formal sense,  who would be the second party? I'm not sure the division I 
work has a MoU with the CEO, nor do I think in terms of organizational 
sociology that the divisions of an entity are normally bound together with 
MoUs.

It appears to me that if we are heading down the contract / MoU path we 
have already implicitly set up the IETF as its own entity, and are now 
undertaking an outsourcing function to sub-contract activities to another 
entity.

I've also gained the impression that there is some hesitancy in taking such 
a step and assigning such role labels to the IETF and to ISOC and what we 
might be looking for here is something subtly different, which is a public 
undertaking on the part of ISOC regarding its commitment to the IETF role, 
and a public undertaking on the part of the IETF as to recognition of 
certain obligations on its part to ISOC.

    Geoff




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