Re: [mmox] The Story So Far...

Christian Scholz <cs@comlounge.net> Wed, 18 February 2009 00:25 UTC

Return-Path: <cs@comlounge.net>
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 0B7863A6982 for <mmox@core3.amsl.com>; Tue, 17 Feb 2009 16:25:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.999
X-Spam-Level:
X-Spam-Status: No, score=-0.999 tagged_above=-999 required=5 tests=[AWL=1.600, 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 RxPse6DztqWk for <mmox@core3.amsl.com>; Tue, 17 Feb 2009 16:25:28 -0800 (PST)
Received: from post.comlounge.net (post.comlounge.net [85.214.59.142]) by core3.amsl.com (Postfix) with ESMTP id 4965A3A69CC for <mmox@ietf.org>; Tue, 17 Feb 2009 16:25:27 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by post.comlounge.net (Postfix) with ESMTP id 007481CE037A; Wed, 18 Feb 2009 01:25:34 +0100 (CET)
Received: from post.comlounge.net ([127.0.0.1]) by localhost (h1346004.stratoserver.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gMv8uV4qSebs; Wed, 18 Feb 2009 01:25:33 +0100 (CET)
Received: from [192.168.178.40] (pD9EBEAE0.dip.t-dialin.net [217.235.234.224]) by post.comlounge.net (Postfix) with ESMTP id E31B21CE0378; Wed, 18 Feb 2009 01:25:32 +0100 (CET)
Message-ID: <499B557A.2010106@comlounge.net>
Date: Wed, 18 Feb 2009 01:25:30 +0100
From: Christian Scholz <cs@comlounge.net>
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: "Hurliman, John" <john.hurliman@intel.com>
References: <1E40CE05-15D1-4970-9B0F-CD4AD11A074A@lindenlab.com> <62BFE5680C037E4DA0B0A08946C0933D501FDC38@rrsmsx506.amr.corp.intel.com> <B8A94709-07E4-4FF8-B321-A4123E9DC633@lindenlab.com> <62BFE5680C037E4DA0B0A08946C0933D501FDCC8@rrsmsx506.amr.corp.intel.com>
In-Reply-To: <62BFE5680C037E4DA0B0A08946C0933D501FDCC8@rrsmsx506.amr.corp.intel.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: "mmox@ietf.org" <mmox@ietf.org>
Subject: Re: [mmox] The Story So Far...
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: Wed, 18 Feb 2009 00:25:29 -0000

Hi!

Hurliman, John schrieb:

> 
> The agent domain concept takes several independent services (identity, presence, inventory) and lumps them together into a single trust domain. This inhibits the development of a widely distributed ecosystem like we find on the web today, and is really only convenient for large virtual world service providers that already have a vertical stack of services. It also drags in the assumption that there must be a backend communication layer between services such as inventory and simulation regions.

Speaking of the web: There are already a lot of social networks out 
there which are right now going to work on interoperability regarding 
profile data, activity streams, authentication and general authorization 
(based on efforts like OAuth (now also here at IETF), OpenID, 
OpenSocial, PortableContacts, XRDS-Simple etc.).

It would be great if these efforts can be integrated so that we don't 
have the problem in the end to bring web and virtual world together 
although both have basically the same idea of distributed services (and 
even partly the same services).

So let me ask in the question: Is this of general interest for this 
group to try to bridge that web/VW gap as well?

I think it would be of value because many of the protocols are already 
in use and thus are understood, have library support and so on.

That being said IMHO the Agent Domain really could be far more separated 
into separate services. All you maybe need is one starting point for 
your identity and some service catalogue which lists where all the other 
services are, either your individual ones (where is my profile, where 
are my group memberships) or service level ones (where is the region 
info, which login methods do you support).

-- Christian


-- 
Christian Scholz
Blog: http://mrtopf.de/blog
Company: http://comlounge.net
Podcasts: http://datawithoutborders.net, http://openweb-podcast.de