Re: [mmox] IETF policy question
"Mystical Demina" <MysticalDemina@xrgrid.com> Thu, 26 March 2009 01:09 UTC
Return-Path: <MysticalDemina@xrgrid.com>
X-Original-To: mmox@core3.amsl.com
Delivered-To: mmox@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0F4F03A68C2 for <mmox@core3.amsl.com>; Wed, 25 Mar 2009 18:09:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.287
X-Spam-Level:
X-Spam-Status: No, score=-2.287 tagged_above=-999 required=5 tests=[AWL=0.312, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PcCz5P0BIWCr for <mmox@core3.amsl.com>; Wed, 25 Mar 2009 18:09:36 -0700 (PDT)
Received: from k2smtpout03-01.prod.mesa1.secureserver.net (k2smtpout03-01.prod.mesa1.secureserver.net [64.202.189.171]) by core3.amsl.com (Postfix) with SMTP id CB76E3A680A for <mmox@ietf.org>; Wed, 25 Mar 2009 18:09:35 -0700 (PDT)
Received: (qmail 12818 invoked from network); 26 Mar 2009 01:10:28 -0000
Received: from unknown (HELO TWEEDY001.kevin-tweedy.com) (68.178.225.179) by k2smtpout03-01.prod.mesa1.secureserver.net (64.202.189.171) with ESMTP; 26 Mar 2009 01:10:27 -0000
Received: from KEVINPC ([173.49.10.182]) by kevin-tweedy.com with MailEnable ESMTP; Wed, 25 Mar 2009 18:10:20 -0700
From: Mystical Demina <MysticalDemina@xrgrid.com>
To: mmox@ietf.org
References: <5f303cb80903251620k163ede14y38e8785d94a417b3@mail.gmail.com>
In-Reply-To: <5f303cb80903251620k163ede14y38e8785d94a417b3@mail.gmail.com>
Date: Wed, 25 Mar 2009 21:10:21 -0400
Message-ID: <7EB8CBA6B67A41F694A4D3D91B947CB4@KEVINPC>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
Thread-Index: AcmtoD5lkOCxKHFhReScaFLYmP2VwQAD1law
X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6001.18049
Subject: Re: [mmox] IETF policy question
X-BeenThere: mmox@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Massively Multi-participant Online Games and Applications <mmox.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mmox>, <mailto:mmox-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmox>
List-Post: <mailto:mmox@ietf.org>
List-Help: <mailto:mmox-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmox>, <mailto:mmox-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Mar 2009 01:09:37 -0000
But I think you are wrong about the other 57 platforms out there. Don't they all need to have a teleport location specification so that can jump between their own virtual worlds time they are able to interoperate. And if they all move forward using the same specification the foundation is set for when a client can interoperate with different virtual worlds. But more than that, you suggest all 57 virtual worlds wait till they can all talk together. I will suggest to you the market will not wait for that. To me it better to have simple solution and grow it, than have no solution. But that is my opinion, maybe others feel different. Kevin -----Original Message----- From: mmox-bounces@ietf.org [mailto:mmox-bounces@ietf.org] On Behalf Of Heiner Wolf Sent: Wednesday, March 25, 2009 7:20 PM To: mmox@ietf.org Subject: [mmox] IETF policy question Hi, Assumed there are multiple systems with incompatible architecture, each sophisticated and with it's own protocols. Assumed that we as a WG do not know enough about the general problem space. Assumed that there are sub-groups which know enough about their problem and have working solutions. What would the IETF do? 1. task one of the sub-groups to standardize one of the protocol/architecture variants, although it might leave a large part of the community out of the loop, while having at least a hope to defeat fragmentation in the future ...or... 2. do not standardize at IETF level, which might be good for the competition of ideas and allows the community to learn more about the general problem space, but preserves fragmentation unless the market cleans it up. I am really undecided, but there is probably BCP in the IETF. Best -- Dr. Heiner Wolf wolf.heiner@gmail.com www.wolfspelz.de www.virtual-presence.org _______________________________________________ mmox mailing list mmox@ietf.org https://www.ietf.org/mailman/listinfo/mmox
- Re: [mmox] IETF policy question Charles Krinke
- [mmox] IETF policy question Heiner Wolf
- Re: [mmox] IETF policy question Mystical Demina
- Re: [mmox] IETF policy question Heiner Wolf
- Re: [mmox] IETF policy question Morgaine
- Re: [mmox] IETF policy question Jon Watte
- Re: [mmox] IETF policy question Morgaine
- Re: [mmox] IETF policy question Heiner Wolf
- Re: [mmox] IETF policy question Lisa Dusseault
- Re: [mmox] IETF policy question Marshall Eubanks
- Re: [mmox] IETF policy question Dave CROCKER