Re: [mmox] Chartering for requirements only
"Meadhbh Hamrick (Infinity)" <infinity@lindenlab.com> Fri, 27 February 2009 01:26 UTC
Return-Path: <infinity@lindenlab.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 BFC513A6AC3 for <mmox@core3.amsl.com>; Thu, 26 Feb 2009 17:26:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.513
X-Spam-Level:
X-Spam-Status: No, score=-3.513 tagged_above=-999 required=5 tests=[AWL=0.086, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 aI71IKZzy2+q for <mmox@core3.amsl.com>; Thu, 26 Feb 2009 17:26:37 -0800 (PST)
Received: from tammy.lindenlab.com (tammy.lindenlab.com [64.154.223.128]) by core3.amsl.com (Postfix) with ESMTP id BA6533A6832 for <mmox@ietf.org>; Thu, 26 Feb 2009 17:26:37 -0800 (PST)
Received: from regression.lindenlab.com (regression.lindenlab.com [10.1.16.8]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by tammy.lindenlab.com (Postfix) with ESMTP id EA74B1414005; Thu, 26 Feb 2009 17:26:59 -0800 (PST)
Message-Id: <9A542216-8DD4-4FB0-9961-8AC73EC3A7E2@lindenlab.com>
From: "Meadhbh Hamrick (Infinity)" <infinity@lindenlab.com>
To: Heiner Wolf <wolf.heiner@googlemail.com>
In-Reply-To: <5f303cb80902251309p48e4bc3p7496abdc7ac699a4@mail.gmail.com>
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Thu, 26 Feb 2009 17:26:59 -0800
References: <5f303cb80902251309p48e4bc3p7496abdc7ac699a4@mail.gmail.com>
X-Mailer: Apple Mail (2.930.3)
Cc: mmox@ietf.org
Subject: Re: [mmox] Chartering for requirements only
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: Fri, 27 Feb 2009 01:26:38 -0000
excellent insight, heiner! i would not be surprised if this is the direction we take. On Feb 25, 2009, at 1:09 PM, Heiner Wolf wrote: > Hi, > > I understand that the original intention was to make OGP public and > get comments. But if that's the purpose you probably should call the > WG OGP. > > We had a similar situation in the Instant Message and Presence WG, > where several vendors tried to talk about "their" protocol. Lisa > probably remembers. The situation was solved by chartering the IMPP WG > to create only requirements, then 2 new WGs worked on "their" protocol > (SIMPLE, XMPP). I bet we get a similar discussion. Maybe MMOX should > define requirements and an OGP WG may then work on the OGP way later. > This gives time for other developers to speak up and add learnings > from "their" worlds and protocols. Do we have people from Everquest, > WoW, There, EVE Online, Runescape, Google Earth here? We need them for > something thats called MMOX. We should give them time to speak up. > > BTW: we are building a virtual world based on XMPP chat rooms. There > are more, like IMVU, which use chat protocols for their virtual > worlds. The chat room is what you would call a region domain. > > This is quite a different angle, but an interesting one, because the > transport protocol is very simple and has few extensions.The > extensions carry the 3D stuff. An interesting feature of worlds which > are based on chat protocols is, that there is low in-band traffic. The > reason is, that off the shelf chat servers are not build for heavy > traffic. So, only notifications are transferrred in the chat protocol. > Assets use a separate data access protocol, usually HTTP. > > This simplistic view of people who use chat protocols for virtual > worlds could be useful in identifying "what you really need" for a VW > interop protocol. > > hw > -- > 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
- [mmox] Chartering for requirements only Heiner Wolf
- Re: [mmox] Chartering for requirements only Meadhbh Hamrick (Infinity)
- Re: [mmox] Chartering for requirements only Gareth Nelson
- Re: [mmox] Chartering for requirements only Kajikawa Jeremy
- Re: [mmox] Chartering for requirements only Morgaine
- Re: [mmox] Chartering for requirements only Jesrad
- Re: [mmox] Chartering for requirements only Lawson English
- Re: [mmox] Chartering for requirements only Morgaine
- Re: [mmox] Chartering for requirements only Lawson English
- Re: [mmox] Chartering for requirements only Meadhbh Hamrick (Infinity)
- Re: [mmox] Chartering for requirements only Jon Watte
- Re: [mmox] Chartering for requirements only Lawson English
- Re: [mmox] Chartering for requirements only Lawson English
- Re: [mmox] Chartering for requirements only Ann Otoole
- Re: [mmox] Chartering for requirements only Jon Watte
- Re: [mmox] Chartering for requirements only Jon Watte
- Re: [mmox] Chartering for requirements only Robert Gehorsam
- Re: [mmox] Chartering for requirements only Jon Watte
- Re: [mmox] Chartering for requirements only eh2th-mmox
- Re: [mmox] Chartering for requirements only Meadhbh Hamrick (Infinity)
- Re: [mmox] Chartering for requirements only Jon Watte
- Re: [mmox] Chartering for requirements only Lawson English
- Re: [mmox] Chartering for requirements only Jon Watte
- Re: [mmox] Chartering for requirements only Mystical Demina
- Re: [mmox] Chartering for requirements only Hurliman, John
- Re: [mmox] Chartering for requirements only Lawson English
- Re: [mmox] Chartering for requirements only Morgaine
- Re: [mmox] Chartering for requirements only Jon Watte
- Re: [mmox] Chartering for requirements only Morgaine
- Re: [mmox] Chartering for requirements only Frisby, Adam
- Re: [mmox] Chartering for requirements only Charles Krinke
- Re: [mmox] Chartering for requirements only Jon Watte
- Re: [mmox] Chartering for requirements only Meadhbh Hamrick (Infinity)
- Re: [mmox] Chartering for requirements only Hurliman, John
- Re: [mmox] Chartering for requirements only Jon Watte
- Re: [mmox] Chartering for requirements only Meadhbh Hamrick (Infinity)
- Re: [mmox] Chartering for requirements only Jon Watte
- Re: [mmox] Chartering for requirements only Meadhbh Hamrick (Infinity)
- Re: [mmox] Chartering for requirements only Jon Watte
- Re: [mmox] Chartering for requirements only Meadhbh Hamrick (Infinity)
- Re: [mmox] Chartering for requirements only Jon Watte
- Re: [mmox] Chartering for requirements only Meadhbh Hamrick (Infinity)
- Re: [mmox] Chartering for requirements only Jon Watte
- Re: [mmox] Chartering for requirements only Charles Krinke
- [mmox] Submission of scope/problem draft as IETF … David W Levine
- Re: [mmox] Submission of scope/problem draft as I… Jon Watte
- Re: [mmox] Submission of scope/problem draft as I… Morgaine
- Re: [mmox] Submission of scope/problem draft as I… Heiner Wolf
- Re: [mmox] Submission of scope/problem draft as I… Charles Krinke
- Re: [mmox] Submission of scope/problem draft as I… Dan Olivares
- Re: [mmox] Chartering for requirements only Hurliman, John
- Re: [mmox] Chartering for requirements only Jon Watte
- Re: [mmox] Submission of scope/problem draft as I… Jesrad
- Re: [mmox] Submission of scope/problem draft as I… Jon Watte
- Re: [mmox] Submission of scope/problem draft as I… Frisby, Adam
- Re: [mmox] Submission of scope/problem draft as I… Meadhbh Hamrick (Infinity)
- Re: [mmox] Submission of scope/problem draft as I… Jesrad
- Re: [mmox] Submission of scope/problem draft as I… Morgaine
- Re: [mmox] Submission of scope/problem draft as I… thomas kirk
- Re: [mmox] Submission of scope/problem draft as I… Jesrad
- Re: [mmox] Submission of scope/problem draft as I… Christian Scholz
- Re: [mmox] Submission of scope/problem draft as I… Christian Scholz
- Re: [mmox] Submission of scope/problem draft as I… thomas kirk