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

"Wijnen, Bert (Bert)" <bwijnen@lucent.com> Thu, 23 September 2004 09:59 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 FAA27584; Thu, 23 Sep 2004 05:59:35 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CAQUn-0004G8-ED; Thu, 23 Sep 2004 06:06:37 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CAQJx-0000IF-2d; Thu, 23 Sep 2004 05:55:25 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CAQIF-0008Dm-7O for ietf@megatron.ietf.org; Thu, 23 Sep 2004 05:53:39 -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 FAA27315 for <ietf@ietf.org>; Thu, 23 Sep 2004 05:53:36 -0400 (EDT)
Received: from ihemail2.lucent.com ([192.11.222.163]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CAQP0-00047Z-F0 for ietf@ietf.org; Thu, 23 Sep 2004 06:00:38 -0400
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62]) by ihemail2.lucent.com (8.12.11/8.12.11) with ESMTP id i8N9r69d017325 for <ietf@ietf.org>; Thu, 23 Sep 2004 04:53:06 -0500 (CDT)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2657.72) id <RLRKK1BG>; Thu, 23 Sep 2004 11:53:05 +0200
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B15503C79CB6@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: ietf@ietf.org
Date: Thu, 23 Sep 2004 11:53:00 +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: 7baded97d9887f7a0c7e8a33c2e3ea1b
Subject: 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: cab78e1e39c4b328567edb48482b6a69

So what we need is more people from the IETF community to speak up
and tell us what they think. This is an important decision we (as IETF)
need to make, and we better make it sooner than later. 

I am surprised to see so few people react. So may I ask: 

  ALL IETFers, PLEASE DO REVIEW the scenario O and C writeups
  and please do send your feedback so that we (as IETF) can make
  a sound decision that is supported by the majority of our community.

Maybe it was/is not clear yet where I stand myself.

So here it is:

>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.

But I seriously believe that in the long run, a Scenario C is the better
and more solid option.

My personal view on this is that if we just look at TODAY, then I can say
that I can live with scenario O. But in the future, we could end up in the
same or a similar boat as where we are today (see my response to Scott
Bradner on 4th of Sept to this list for details). At that future time I may
not be around anymore. But I want to create the "best future for my children"
so to speak. That is why I am prepared to take the risks that we have
described in Scenario C. We need to work more on that to understand them
better and to take precautions and measure to mitigate them. We need to
work/discuss with ISOC what that means in terms of our continued close 
relationship (ISOC, IETF and also IASF) and clearly document that. We all
have the same goals when it comes to standardizing the Internet Protocols.

Most important to me... we better choose one of the scenarios, so we
can start working on the details and implementation!

Again, please post your comments/concerns and/or preferences.

Thanks,
Bert

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