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

"Spencer Dawkins" <spencer@mcsr-labs.org> Fri, 24 September 2004 11:36 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 HAA02087; Fri, 24 Sep 2004 07:36:09 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CAoTy-00087B-W6; Fri, 24 Sep 2004 07:43:23 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CAoIa-0005Sx-HF; Fri, 24 Sep 2004 07:31:36 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CAoID-0005O7-3W for ietf@megatron.ietf.org; Fri, 24 Sep 2004 07:31:13 -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 HAA01782 for <ietf@ietf.org>; Fri, 24 Sep 2004 07:31:12 -0400 (EDT)
Received: from rwcrmhc12.comcast.net ([216.148.227.85]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CAoP1-00081z-Ub for ietf@ietf.org; Fri, 24 Sep 2004 07:38:26 -0400
Received: from dfnjgl21 (c-24-1-99-5.client.comcast.net[24.1.99.5]) by comcast.net (rwcrmhc12) with SMTP id <20040924113031014001rhlde> (Authid: sdawkins@comcast.net); Fri, 24 Sep 2004 11:30:31 +0000
Message-ID: <0a4d01c4a229$eefa5ac0$0400a8c0@DFNJGL21>
From: "Spencer Dawkins" <spencer@mcsr-labs.org>
To: <ietf@ietf.org>
References: <7D5D48D2CAA3D84C813F5B154F43B15503C79CB6@nl0006exch001u.nl.lucent.com> <p06020468bd7876d4f071@[192.168.2.2]>
Date: Fri, 24 Sep 2004 06:30:44 -0500
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Spam-Score: 0.8 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Content-Transfer-Encoding: 7bit
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
Reply-To: Spencer Dawkins <spencer@mcsr-labs.org>
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.8 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Content-Transfer-Encoding: 7bit

From: "Margaret Wasserman" <margaret@thingmagic.com>
To: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>; <ietf@ietf.org>
Sent: Thursday, September 23, 2004 8:36 AM
Subject: Re: Scenario C or Scenario O ? - I say let us go for C !


>
> Hi Bert,
>
> Both you and Ted have posted preferences for Scenario C that, to me, 
> seem to say "We will eventually have to go to Scenario C, anyway, so 
> we should undertake that effort today rather than leaving it for 
> later."  This might be a compelling argument if it were clear to me 
> that we will need to move to Scenario C in the future.  Could you 
> explain why you think that would be desireable?  What are the 
> practical advantages that you see to having two separate 
> corporations (ISOC and the IASF), one responsible for fund raising 
> and some standards-related tasks, and the other responsible for our 
> administrative support?

There was also the assumption that if we go with O and it turns out 
that we should have gone with C, it will be just as slow and painful 
getting to this point again as it was the first time.

Why would this be true? It's at least as likely that we would say "we 
should have made the other choice" and start moving to C - a shorter 
distance that it is now.

My non-random sample of second marriages is that they tend to either 
last or end more quickly than first marriages. That's a bad analogy, 
but I think the principle applies ("we've been here before and 
changing things was the right thing to do, so why wait now?").

Spencer 



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