Re: [mmox] An attempt to revive this group: Service Disovery, part 1

"Hurliman, John" <john.hurliman@intel.com> Tue, 16 June 2009 20:43 UTC

Return-Path: <john.hurliman@intel.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 EF6D73A6C01 for <mmox@core3.amsl.com>; Tue, 16 Jun 2009 13:43:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.199
X-Spam-Level:
X-Spam-Status: No, score=-1.199 tagged_above=-999 required=5 tests=[AWL=-5.200, BAYES_00=-2.599, J_CHICKENPOX_36=0.6, RCVD_IN_DNSWL_MED=-4, URIBL_WS_SURBL=10]
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 7-v17WAupQ2E for <mmox@core3.amsl.com>; Tue, 16 Jun 2009 13:43:03 -0700 (PDT)
Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by core3.amsl.com (Postfix) with ESMTP id B119C3A6C5A for <mmox@ietf.org>; Tue, 16 Jun 2009 13:43:03 -0700 (PDT)
Received: from orsmga001.jf.intel.com ([10.7.209.18]) by orsmga102.jf.intel.com with ESMTP; 16 Jun 2009 13:31:05 -0700
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="4.42,231,1243839600"; d="scan'208";a="525340435"
Received: from rrsmsx603.amr.corp.intel.com ([10.31.0.57]) by orsmga001.jf.intel.com with ESMTP; 16 Jun 2009 13:42:30 -0700
Received: from rrsmsx601.amr.corp.intel.com (10.31.0.151) by rrsmsx603.amr.corp.intel.com (10.31.0.57) with Microsoft SMTP Server (TLS) id 8.1.358.0; Tue, 16 Jun 2009 14:42:38 -0600
Received: from rrsmsx506.amr.corp.intel.com ([10.31.0.39]) by rrsmsx601.amr.corp.intel.com ([10.31.0.151]) with mapi; Tue, 16 Jun 2009 14:42:38 -0600
From: "Hurliman, John" <john.hurliman@intel.com>
To: Christian Scholz <cs@comlounge.net>, "mmox@ietf.org" <mmox@ietf.org>
Date: Tue, 16 Jun 2009 14:42:34 -0600
Thread-Topic: [mmox] An attempt to revive this group: Service Disovery, part 1
Thread-Index: AcnuwmulF9FVTExoQoi6EY9j00b+nwAAHAxw
Message-ID: <62BFE5680C037E4DA0B0A08946C0933D910C10C6@rrsmsx506.amr.corp.intel.com>
References: <4A3802C3.6000507@comlounge.net>
In-Reply-To: <4A3802C3.6000507@comlounge.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [mmox] An attempt to revive this group: Service Disovery, part 1
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: Tue, 16 Jun 2009 20:43:05 -0000

This sounds right along the lines of what Cable Beach is doing. I'm interested to see what specific technologies you propose for service discovery. We've been eyeballing XRD, but it's difficult to gauge what the current status of this standard is.

John

> -----Original Message-----
> From: mmox-bounces@ietf.org [mailto:mmox-bounces@ietf.org] On Behalf 
> Of Christian Scholz
> Sent: Tuesday, June 16, 2009 1:38 PM
> To: mmox@ietf.org
> Subject: [mmox] An attempt to revive this group: Service Disovery, 
> part
> 1
> 
> Hi there!
> 
> This list seems to be quite quiet but I hope we can at least revive some
> discussion in it   :-)
> 
> In order to do so, I wanted to send out some ideas on what actually
> could be discussed here based on some thoughts and interests which
> have been circulating here before.
> 
> So let me sketch out some ideas.
> 
> First of all what has been tried here in the past seems to me to find
> consensus on a virtual worlds protocol which reaches from everything a
> virtual world does including communications, identity, social
> connections, 3D formats, simulation protocols and much more.
> 
> Now this apparently hasn't worked out and maybe it actually does not
> need to.
> 
> The question is maybe more on which subsets of such a protocol could
> be worked on together while also including as much as existing
> components as possible?
> 
> So my idea of a virtual world is actually quite simple: It's a social
> network. It's a social network with 3D services attached. Some might
> even be just 2D worlds. But technically a virtual world contains most
> of the things we usually find in social networks.
> 
> Having a 3D environment of course enables a lot of new things and
> depending on the type of environment maybe even the community is
> influenced and creates certain behaviour, commerce etc.
> 
> Now after thinking a bit about it I wonder if we also really want to
> reduce all that variety of environments we have today to one single
> experience or format/protocol. I think we don't. There is lots left to
> invent in this space and there are already a lot of existing and
> exciting services out there all being driven by their unique approach
> to the problem.
> 
> Moreover of course there is some strong business interest to not
> recreate the whole environment as esp. 3D related projects tend to me
> a lot more resource hungry than e.g. implementing a REST API (think of
> 3D clients, protocol benchmarking etc.).
> 
> So what maybe can be done more easily than standardizing a complete 3D
> virtual worlds environment is to try on discussing certain components
> to make this whole framework a bit more modular.
> 
> In the past I talked already a bit about service discovery and how
> services and users can advertise what services and data they own and
> where they are. Add some authorization layer to it and you have a
> initial idea of modularity.
> 
> In my next email I would like to introduce some existing protocols or
> such being worked on which could be helpful in that area. I also would
> like to introduce a basic concept on how these can work together.
> 
> Besides that I met with Heiner Wolf at the Barcamp in Cologne and we
> discussed something along a VW protocol and what some use cases could
> be, you can find the notes at
> http://socialconnect.info/trac/wiki/vw_protokoll
> 
> I also started a prototype of some VW based on Ogre not so much for
> inventing new 3D protocols but for testing the integration between
> virtual worlds and normal web based social networks. Once I win my
> fight against integrating Python, Ogre and some GUI I will hopefully
> present it to you.
> 
> But that's maybe enough for my first email. I hope that MMOX is not
> dead because I see it as one of the few places where at least some
> vendors came together and started discussion. I'd really to keep this
> discussion alive but maybe not so much centered around what each party
> is willing to change or not to change but maybe more focused on
> general exchange of ideas or experience. Maybe some common ground can
> develop on that.
> 
> -- Christian
> 
> 
> --
> COM.lounge GmbH
> http://comlounge.net
> Hanbrucher Strasse 33, 52064 Aachen
> Amtsgericht Aachen HRB 15170
> Geschäftsführer: Dr. Ben Scheffler, Christian Scholz
> 
> email: info@comlounge.net
> fon: +49-241-4007300
> fax: +49-241-97900850
> 
> personal email: cs@comlounge.net personal blog: http://mrtopf.de/blog
> personal podcasts: http://openweb-podcast.de,
> http://datawithoutborders.net
> 
> _______________________________________________
> mmox mailing list
> mmox@ietf.org
> https://www.ietf.org/mailman/listinfo/mmox