Re: [mmox] charter scope, thinking horizontally

Larry Masinter <masinter@adobe.com> Mon, 30 March 2009 00:07 UTC

Return-Path: <masinter@adobe.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 26C013A687D for <mmox@core3.amsl.com>; Sun, 29 Mar 2009 17:07:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.099
X-Spam-Level:
X-Spam-Status: No, score=-6.099 tagged_above=-999 required=5 tests=[AWL=0.500, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 tBjtj8Z1q5Gk for <mmox@core3.amsl.com>; Sun, 29 Mar 2009 17:07:50 -0700 (PDT)
Received: from psmtp.com (exprod6ob109.obsmtp.com [64.18.1.22]) by core3.amsl.com (Postfix) with ESMTP id 3B8763A681A for <mmox@ietf.org>; Sun, 29 Mar 2009 17:07:48 -0700 (PDT)
Received: from source ([192.150.8.22]) by exprod6ob109.postini.com ([64.18.5.12]) with SMTP ID DSNKSdANjfMgSasUf/RN6ArTfBQirqPwOMfH@postini.com; Sun, 29 Mar 2009 17:08:48 PDT
Received: from inner-relay-2.corp.adobe.com ([153.32.1.52]) by outbound-smtp-2.corp.adobe.com (8.12.10/8.12.10) with ESMTP id n2U08gE0001564; Sun, 29 Mar 2009 17:08:43 -0700 (PDT)
Received: from nacas02.corp.adobe.com (nacas02.corp.adobe.com [10.8.189.100]) by inner-relay-2.corp.adobe.com (8.12.10/8.12.10) with ESMTP id n2U08ftQ012751; Sun, 29 Mar 2009 17:08:41 -0700 (PDT)
Received: from nacas03.corp.adobe.com (10.8.189.121) by nacas02.corp.adobe.com (10.8.189.100) with Microsoft SMTP Server (TLS) id 8.1.340.0; Sun, 29 Mar 2009 17:08:41 -0700
Received: from nambx04.corp.adobe.com ([10.8.127.98]) by nacas03.corp.adobe.com ([10.8.189.121]) with mapi; Sun, 29 Mar 2009 17:08:41 -0700
From: Larry Masinter <masinter@adobe.com>
To: Jon Watte <jwatte@gmail.com>, Charles Krinke <charles.krinke@gmail.com>
Date: Sun, 29 Mar 2009 17:08:38 -0700
Thread-Topic: [mmox] charter scope, thinking horizontally
Thread-Index: AcmwyRjZmzUHUSHjRQaKAZc5g5dM0wAAQpyA
Message-ID: <8B62A039C620904E92F1233570534C9B0118CD4EE366@nambx04.corp.adobe.com>
References: <e0b04bba0903250007k6886383bja0a06884e8081ac7@mail.gmail.com> <e0b04bba0903272047u738513b9pc2dbe219dbce37e3@mail.gmail.com> <49CDC0BA.5070403@gmail.com> <f0b9e3410903280920o1e436337hb4c40a5b5f124876@mail.gmail.com> <49CE5BDC.5040808@gmail.com> <e0b04bba0903281057g943ce9cjdcce0fc2712a4ec3@mail.gmail.com> <49CF1B1E.4070506@gmail.com> <e0b04bba0903290138ifbfaf18p930f87d1e49e6dbb@mail.gmail.com> <1238321627.6757.20.camel@localhost> <8B62A039C620904E92F1233570534C9B0118CD4EE34E@nambx04.corp.adobe.com> <f0b9e3410903291043k3e58e72ci74f333ddb9a2ec88@mail.gmail.com> <49D0092D.3050206@gmail.com>
In-Reply-To: <49D0092D.3050206@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Cc: MMOX-IETF <mmox@ietf.org>
Subject: Re: [mmox] charter scope, thinking horizontally
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: Mon, 30 Mar 2009 00:07:51 -0000

> If a virtual world exposed a XMPP chat service, and SIP endpoints for 
> each avatar, using the protocols that already exist, then what else is 
> there to do to declare this working?
...
> The only one I can think of is properly tying presence into the SIP 
> call, such that the voice comes from the right 3D location (we use an 
> out-of-bound message for that right now).

Is there a standard way of relating avatar identity and personal
identity? Should these be distinct? Are the states of present/idle/location
from XMPP appropriate for avatar-in-world? Are there special
in-world states that would need to be mapped into XMPP presence
information ("in-world but dead" in a combat world, for example.)
Are there any issues with synchronizing XMPP messages and in-world
events?

I think to "declare this working", you'd have a document that described
how this would work, and multiple independent interoperable implementations,
with satisfactory interoperability.

Since I've not seen any jabber-with-avatar services actually working,
there are probably other technical questions that would arise during
the course of implementation.

And, of course, you'd have to decide as a group to settle on
XMPP and not IRC, not something based on OGP, (some profile of) 
SIP and not some other voice server, sharing service, etc.

It's always good to start with something you think is easy.

Larry