Re: [mmox] charter scope, thinking horizontally

Jon Watte <jwatte@gmail.com> Sun, 29 March 2009 23:49 UTC

Return-Path: <jwatte@gmail.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 D69EF3A687D for <mmox@core3.amsl.com>; Sun, 29 Mar 2009 16:49:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.579
X-Spam-Level:
X-Spam-Status: No, score=-2.579 tagged_above=-999 required=5 tests=[AWL=0.020, 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 GSu76z0whPhs for <mmox@core3.amsl.com>; Sun, 29 Mar 2009 16:49:10 -0700 (PDT)
Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.236]) by core3.amsl.com (Postfix) with ESMTP id 1F0EA3A67CC for <mmox@ietf.org>; Sun, 29 Mar 2009 16:49:09 -0700 (PDT)
Received: by rv-out-0506.google.com with SMTP id g37so811040rvb.5 for <mmox@ietf.org>; Sun, 29 Mar 2009 16:50:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=9MclCkLvzHCahTrLaWiuPSkD4kjFHLhmGMANvvPVMgs=; b=B/Q+Lfmi74P005SMupf9dxOOIL6M2z8f8EyHeXN/3PcMi+8jesclz1zVuZPo5Mg2eO tK6yF6pj7aiRLbSuLKpBkgJznxZfs9oiVN+yXaGrYfah2OKYDoKAOdtlAMMW+WoYTmnY WCwkAvKfoPTISDH6oVl8bwjA6I/1jkPy2/fJ4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=i6u5080i7RrjqZYgCaOZPF/SB3r9iz0AmHQHp8sQNxBro5XQWVPF2wqCwIdJ35EgiO yAXP1b2S34BxOjwMOCMNlvImFkbf9PM0TzEDsZdYkkJyOxOY3xI81Db1kJWKRYLNttkX l7WrkFmRZ9fIXn2sfzlrviPuL0Swgby21ZSLQ=
Received: by 10.115.18.3 with SMTP id v3mr3153908wai.141.1238370607144; Sun, 29 Mar 2009 16:50:07 -0700 (PDT)
Received: from ?192.168.1.101? (svn.mindcontrol.org [69.17.45.136]) by mx.google.com with ESMTPS id l37sm3916231waf.3.2009.03.29.16.50.06 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sun, 29 Mar 2009 16:50:06 -0700 (PDT)
Message-ID: <49D0092D.3050206@gmail.com>
Date: Sun, 29 Mar 2009 16:50:05 -0700
From: Jon Watte <jwatte@gmail.com>
User-Agent: Thunderbird 2.0.0.21 (Windows/20090302)
MIME-Version: 1.0
To: Charles Krinke <charles.krinke@gmail.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>
In-Reply-To: <f0b9e3410903291043k3e58e72ci74f333ddb9a2ec88@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
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: Sun, 29 Mar 2009 23:49:10 -0000

Charles Krinke wrote:
> I would concur. Making in-roads in getting chat working between more 
> virtual worlds is to everyone's advantage.

Well, theoretically that is already solved by XMPP, right?

Also, it turns out that OLIVE is very not focused on text chat at all; 
it is almost entirely designed for voice comms. Of course, we already do 
SIP interoperability, so it's unclear whether there's much to do that, 
either.

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? What, specifically, are the 
unsolved problems with regards to using XMPP and SIP in the context of 
virtual worlds?

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

Sincerely,

jw