RE: Scenario C or Scenario O ? - I say let us go for C !

"Wijnen, Bert (Bert)" <bwijnen@lucent.com> Thu, 23 September 2004 20:54 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 QAA21994; Thu, 23 Sep 2004 16:54:20 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CAaiV-0001oI-AZ; Thu, 23 Sep 2004 17:01:28 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CAaQK-0001oy-2M; Thu, 23 Sep 2004 16:42:40 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CAaGM-00082s-5o for ietf@megatron.ietf.org; Thu, 23 Sep 2004 16:32:22 -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 QAA20612 for <ietf@ietf.org>; Thu, 23 Sep 2004 16:32:19 -0400 (EDT)
Received: from ihemail1.lucent.com ([192.11.222.161]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CAaNC-0001Rr-HY for ietf@ietf.org; Thu, 23 Sep 2004 16:39:27 -0400
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62]) by ihemail1.lucent.com (8.12.11/8.12.11) with ESMTP id i8NKVlCr029452 for <ietf@ietf.org>; Thu, 23 Sep 2004 15:31:48 -0500 (CDT)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2657.72) id <RLRKKVN6>; Thu, 23 Sep 2004 22:31:47 +0200
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B15503C79CDC@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: "'sob@harvard.edu'" <sob@harvard.edu>, ietf@ietf.org
Date: Thu, 23 Sep 2004 22:31:46 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
Subject: RE: Scenario C or Scenario O ? - I say let us go for C !
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.2 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002

> 
> Bert said:
> > From what I have seen/read sofar, my preference is to go for Scenario C. 
> > Yes, Scenario O seems somewhat simpler. 
> > Yes, Scenario O seems acceptable today.
> 
Scott answered
> just to be clear it is my opinion that
> Scenario O is significantly simpler
> and that Scenario C intruduces significant risks to the future of the
> IETF for no supportble reasons
> 
> I have seen no convincing justification from anyone to support an
> adoption of Scenario C 
> 

Besides my (wordy) response to you back on Sept 4th (or 3rd in US) 
as availabe at:
   http://www1.ietf.org/mail-archive/web/ietf/current/msg31057.html

Let me offer this summary:

To me it seems that starting a corporation is pretty straight forward
if I understand the report from our consultant correctly.
It seems we can do this without a huge corporate bureaucracy.
In other words: we can make this lightweight (when operational).
I understand we need to do some extra steps to get it started.

The advantages I see are:

- if done properly, this allows the IETF support function
  to be carried out by a SHARPLY FOCUSED operation.
  We won't get sidetracked into things that are non-IETF.

- if done properly, this allows for a very straight forward
  governance mechanism that is *directly* accountable to
  the IETF and where change control is clearly vested in that
  same community.  Again, the corporate solution is the
  lightweight and straightforward solution.

"Ability to focus on IETF support" is the big thing and tight 
change control is another advantage.I 

Bert

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