
From infinity@lindenlab.com  Tue Jun  2 15:51:44 2009
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 2C0343A6D9B for <mmox@core3.amsl.com>; Tue,  2 Jun 2009 15:51:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.508
X-Spam-Level: 
X-Spam-Status: No, score=-1.508 tagged_above=-999 required=5 tests=[AWL=0.469,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
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 aa6nBS-nOhel for <mmox@core3.amsl.com>; Tue,  2 Jun 2009 15:51:43 -0700 (PDT)
Received: from mail-gx0-f166.google.com (mail-gx0-f166.google.com [209.85.217.166]) by core3.amsl.com (Postfix) with ESMTP id 500B13A6DC5 for <mmox@ietf.org>; Tue,  2 Jun 2009 15:51:43 -0700 (PDT)
Received: by gxk10 with SMTP id 10so14829039gxk.13 for <mmox@ietf.org>; Tue, 02 Jun 2009 15:51:41 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.100.110.9 with SMTP id i9mr375458anc.130.1243983100950; Tue,  02 Jun 2009 15:51:40 -0700 (PDT)
Date: Tue, 2 Jun 2009 15:51:40 -0700
Message-ID: <3a880e2c0906021551l76476e51j7af261d62e2f41e8@mail.gmail.com>
From: Infinity Linden <infinity@lindenlab.com>
To: sldev <sldev@lists.secondlife.com>, "mmox@ietf.org" <mmox@ietf.org>,  opensim-dev@lists.berlios.de
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: [mmox] OGPX Request for Participation
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, 02 Jun 2009 22:51:44 -0000

Some people might have heard that Open Grid Protocol (OGP)
standardization efforts have been proceeding under the auspices of the
IETF (Internet Engineering Task Force.) Last spring we formed the MMOX
mailing list and BoF (Birds of a Feather) session to discuss
standardization efforts across a number of different virtual worlds
technology. At the MMOX BoF, a smaller number of people indicated an
interest in focusing on the "second life-like" worlds currently
deployed / described by Second Life(tm), OpenSim, PyOGP and RealXtend
(to name a few.) The objective of this new group, called OGPX, is to
define use cases, interoperability profiles and protocol for OGP.

The mailing list for this group, ogpx@ietf.org, is open and anyone may
participate (though we ask that discussion be limited to OGP and
related topics; the MMOX list is still active for the purpose of more
general VW standardization discussions.) You can subscribe to the OGPX
list by visiting https://www.ietf.org/mailman/listinfo/ogpx . Current
discussion topics include Reverse HTTP (RHTTP), LLSD / LLIDL and OGP.

So... if you're interested in what's going on in OGP, this is the
place to find out.

Readers may also be interested in the set of published internet drafts:

* OGP : Intro and Requirements (
http://tools.ietf.org/html/draft-hamrick-ogp-intro-00 )
* LLSD / LLIDL ( http://www.ietf.org/internet-drafts/draft-hamrick-llsd-00.txt )
* Reverse HTTP ( http://tools.ietf.org/html/draft-lentczner-rhttp-00 )
* OGP : Foundations ( http://tools.ietf.org/html/draft-lentczner-ogp-base-00 )
* OGP : Authentication ( http://tools.ietf.org/html/draft-hamrick-ogp-auth-00 )

also... a draft charter for the OGPX group has been published to the
mailing list and is archived at:

http://www.ietf.org/mail-archive/web/ogpx/current/msg00005.html

please don't hesitate to subscribe if you're interested. you don't
have to be an OGP partisan. HyperGrid folk who want to know what we're
doing are welcome; all i ask is we keep the trash talk to a minimum
and keep the discussion focused to OGP.

-sincerely
-meadhbh hamrick (aka infinity linden)

From infinity@lindenlab.com  Tue Jun 16 06:46:11 2009
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 584533A6AA4 for <mmox@core3.amsl.com>; Tue, 16 Jun 2009 06:46:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.63
X-Spam-Level: 
X-Spam-Status: No, score=-1.63 tagged_above=-999 required=5 tests=[AWL=0.347,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
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 eDhGIZWZx0Ea for <mmox@core3.amsl.com>; Tue, 16 Jun 2009 06:46:10 -0700 (PDT)
Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.246]) by core3.amsl.com (Postfix) with ESMTP id 11C7128C180 for <mmox@ietf.org>; Tue, 16 Jun 2009 06:46:06 -0700 (PDT)
Received: by an-out-0708.google.com with SMTP id c3so2050839ana.4 for <mmox@ietf.org>; Tue, 16 Jun 2009 06:45:58 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.100.126.15 with SMTP id y15mr10582160anc.71.1245159958832;  Tue, 16 Jun 2009 06:45:58 -0700 (PDT)
Date: Tue, 16 Jun 2009 06:45:58 -0700
Message-ID: <3a880e2c0906160645m641347b9pa9abc62c73d3864@mail.gmail.com>
From: Infinity Linden <infinity@lindenlab.com>
To: mmox@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: [mmox] testing one two three ...
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 13:46:11 -0000

had some reports of MMOX not working. testing it out.

for the record, remember that MMOX is still active for the discussion
of virtual worlds in general. discussion of "second life-like" systems
using OGP has been moved to the ogpx@ietf.org.

-cheers
-meadhbh

From cs@comlounge.net  Tue Jun 16 13:38:14 2009
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 D7A333A6A49 for <mmox@core3.amsl.com>; Tue, 16 Jun 2009 13:38:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.11
X-Spam-Level: ***
X-Spam-Status: No, score=3.11 tagged_above=-999 required=5 tests=[AWL=-4.891,  BAYES_00=-2.599, J_CHICKENPOX_36=0.6, 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 nPmQrgGnuoBY for <mmox@core3.amsl.com>; Tue, 16 Jun 2009 13:38:14 -0700 (PDT)
Received: from post.comlounge.net (post.comlounge.net [85.214.59.142]) by core3.amsl.com (Postfix) with ESMTP id A4B1E3A6824 for <mmox@ietf.org>; Tue, 16 Jun 2009 13:38:13 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by post.comlounge.net (Postfix) with ESMTP id 9D7036F4019 for <mmox@ietf.org>; Tue, 16 Jun 2009 22:38:23 +0200 (CEST)
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 aac2lrTF-Xed for <mmox@ietf.org>; Tue, 16 Jun 2009 22:38:22 +0200 (CEST)
Received: from [192.168.2.101] (p5B3D7257.dip.t-dialin.net [91.61.114.87]) by post.comlounge.net (Postfix) with ESMTP id 677B46F4016 for <mmox@ietf.org>; Tue, 16 Jun 2009 22:38:22 +0200 (CEST)
Message-ID: <4A3802C3.6000507@comlounge.net>
Date: Tue, 16 Jun 2009 22:38:27 +0200
From: Christian Scholz <cs@comlounge.net>
User-Agent: Thunderbird 2.0.0.21 (Windows/20090302)
MIME-Version: 1.0
To: "mmox@ietf.org" <mmox@ietf.org>
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 8bit
Subject: [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:38:14 -0000

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


From john.hurliman@intel.com  Tue Jun 16 13:43:04 2009
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 interes=
ted to see what specific technologies you propose for service discovery. We=
've been eyeballing XRD, but it's difficult to gauge what the current statu=
s of this standard is.

John

> -----Original Message-----
> From: mmox-bounces@ietf.org [mailto:mmox-bounces@ietf.org] On Behalf=20
> 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,=20
> part
> 1
>=20
> Hi there!
>=20
> This list seems to be quite quiet but I hope we can at least revive some
> discussion in it   :-)
>=20
> 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.
>=20
> So let me sketch out some ideas.
>=20
> 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.
>=20
> Now this apparently hasn't worked out and maybe it actually does not
> need to.
>=20
> 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?
>=20
> 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.
>=20
> 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.
>=20
> 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.
>=20
> 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.).
>=20
> 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.
>=20
> 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.
>=20
> 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.
>=20
> 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
>=20
> 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.
>=20
> 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.
>=20
> -- Christian
>=20
>=20
> --
> COM.lounge GmbH
> http://comlounge.net
> Hanbrucher Strasse 33, 52064 Aachen
> Amtsgericht Aachen HRB 15170
> Gesch=E4ftsf=FChrer: Dr. Ben Scheffler, Christian Scholz
>=20
> email: info@comlounge.net
> fon: +49-241-4007300
> fax: +49-241-97900850
>=20
> personal email: cs@comlounge.net personal blog: http://mrtopf.de/blog
> personal podcasts: http://openweb-podcast.de,
> http://datawithoutborders.net
>=20
> _______________________________________________
> mmox mailing list
> mmox@ietf.org
> https://www.ietf.org/mailman/listinfo/mmox

From cs@comlounge.net  Tue Jun 16 14:46:51 2009
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 9B3B23A6BF0 for <mmox@core3.amsl.com>; Tue, 16 Jun 2009 14:46:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 4.088
X-Spam-Level: ****
X-Spam-Status: No, score=4.088 tagged_above=-999 required=5 tests=[AWL=-3.913,  BAYES_00=-2.599, J_CHICKENPOX_36=0.6, 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 vfSj+GCiIPgi for <mmox@core3.amsl.com>; Tue, 16 Jun 2009 14:46:50 -0700 (PDT)
Received: from post.comlounge.net (post.comlounge.net [85.214.59.142]) by core3.amsl.com (Postfix) with ESMTP id 4E79A3A6A6F for <mmox@ietf.org>; Tue, 16 Jun 2009 14:46:50 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by post.comlounge.net (Postfix) with ESMTP id 8867F1CE02A4; Tue, 16 Jun 2009 23:46:59 +0200 (CEST)
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 XbdU1zK7ypfU; Tue, 16 Jun 2009 23:46:58 +0200 (CEST)
Received: from [192.168.2.101] (p5B3D7257.dip.t-dialin.net [91.61.114.87]) by post.comlounge.net (Postfix) with ESMTP id 2A4B71CE024B; Tue, 16 Jun 2009 23:46:58 +0200 (CEST)
Message-ID: <4A3812D7.6030407@comlounge.net>
Date: Tue, 16 Jun 2009 23:47:03 +0200
From: Christian Scholz <cs@comlounge.net>
User-Agent: Thunderbird 2.0.0.21 (Windows/20090302)
MIME-Version: 1.0
To: "Hurliman, John" <john.hurliman@intel.com>
References: <4A3802C3.6000507@comlounge.net> <62BFE5680C037E4DA0B0A08946C0933D910C10C6@rrsmsx506.amr.corp.intel.com>
In-Reply-To: <62BFE5680C037E4DA0B0A08946C0933D910C10C6@rrsmsx506.amr.corp.intel.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Cc: "mmox@ietf.org" <mmox@ietf.org>
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 21:46:51 -0000

Hurliman, John schrieb:
> 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.

Well, I don't care about the state ;-) For my experiment I will 
implement what's there and will change if needed and changes are made.
But I will mail around to find out what the state is.

Great to hear that Cable Beach is doing something along those lines 
already, maybe we can make some interop test once I also have something 
implemented.

-- Christian

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


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


From mike.dickson@hp.com  Tue Jun 16 14:52:50 2009
Return-Path: <mike.dickson@hp.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 9B63828C1BC for <mmox@core3.amsl.com>; Tue, 16 Jun 2009 14:52:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 j8M7fT0dgJi3 for <mmox@core3.amsl.com>; Tue, 16 Jun 2009 14:52:50 -0700 (PDT)
Received: from g1t0028.austin.hp.com (g1t0028.austin.hp.com [15.216.28.35]) by core3.amsl.com (Postfix) with ESMTP id EA2AA28C1BA for <mmox@ietf.org>; Tue, 16 Jun 2009 14:52:49 -0700 (PDT)
Received: from g5t0012.atlanta.hp.com (g5t0012.atlanta.hp.com [15.192.0.49]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by g1t0028.austin.hp.com (Postfix) with ESMTPS id 924D51C06A; Tue, 16 Jun 2009 21:53:00 +0000 (UTC)
Received: from [192.168.1.139] (conr-adsl-209-169-71-194.consolidated.net [209.169.71.194]) by g5t0012.atlanta.hp.com (Postfix) with ESMTPSA id C7E8E10003; Tue, 16 Jun 2009 21:52:59 +0000 (UTC)
From: Mike Dickson <mike.dickson@hp.com>
To: "Hurliman, John" <john.hurliman@intel.com>
In-Reply-To: <62BFE5680C037E4DA0B0A08946C0933D910C10C6@rrsmsx506.amr.corp.intel.com>
References: <4A3802C3.6000507@comlounge.net> <62BFE5680C037E4DA0B0A08946C0933D910C10C6@rrsmsx506.amr.corp.intel.com>
Content-Type: text/plain
Organization: Bladesystems Infrastructure R&D
Date: Tue, 16 Jun 2009 16:52:50 -0500
Message-Id: <1245189170.16199.15.camel@mdickson-laptop>
Mime-Version: 1.0
X-Mailer: Evolution 2.26.1 
Content-Transfer-Encoding: 7bit
Cc: "mmox@ietf.org" <mmox@ietf.org>
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
Reply-To: mike.dickson@hp.com
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 21:52:50 -0000

John,

  Can you send a pointer to any info on the Cable Beach work?  I've seen
a simple summary page on the OpenSim site but I'm curious if anything
more detailed exists.

Thanks!

Mike

On Tue, 2009-06-16 at 20:42 +0000, Hurliman, John wrote:
> 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
> 
> >


From john.hurliman@intel.com  Wed Jun 17 17:27:27 2009
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 5AAF03A6EDB for <mmox@core3.amsl.com>; Wed, 17 Jun 2009 17:27:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[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 RMZ33V35WFyi for <mmox@core3.amsl.com>; Wed, 17 Jun 2009 17:27:26 -0700 (PDT)
Received: from mga03.intel.com (mga03.intel.com [143.182.124.21]) by core3.amsl.com (Postfix) with ESMTP id 2DA8E3A6808 for <mmox@ietf.org>; Wed, 17 Jun 2009 17:27:26 -0700 (PDT)
Received: from azsmga001.ch.intel.com ([10.2.17.19]) by azsmga101.ch.intel.com with ESMTP; 17 Jun 2009 17:27:38 -0700
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="4.42,240,1243839600"; d="scan'208";a="155816102"
Received: from rrsmsx604.amr.corp.intel.com ([10.31.0.170]) by azsmga001.ch.intel.com with ESMTP; 17 Jun 2009 17:27:38 -0700
Received: from rrsmsx506.amr.corp.intel.com ([10.31.0.39]) by rrsmsx604.amr.corp.intel.com ([10.31.0.170]) with mapi; Wed, 17 Jun 2009 18:27:37 -0600
From: "Hurliman, John" <john.hurliman@intel.com>
To: "mike.dickson@hp.com" <mike.dickson@hp.com>
Date: Wed, 17 Jun 2009 18:27:34 -0600
Thread-Topic: [mmox] An attempt to revive this group: Service Disovery, part 1
Thread-Index: Acnu1YS9HGTRsv1ET/Cvgk2YQ2M/IwA1ZSNg
Message-ID: <62BFE5680C037E4DA0B0A08946C0933D9112D25A@rrsmsx506.amr.corp.intel.com>
References: <4A3802C3.6000507@comlounge.net> <62BFE5680C037E4DA0B0A08946C0933D910C10C6@rrsmsx506.amr.corp.intel.com> <1245189170.16199.15.camel@mdickson-laptop>
In-Reply-To: <1245189170.16199.15.camel@mdickson-laptop>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "mmox@ietf.org" <mmox@ietf.org>
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: Thu, 18 Jun 2009 00:27:27 -0000

The homepage for the project is <http://cablebeach.googlecode.com/> and the=
 future home of the draft is <http://code.google.com/p/cablebeach/wiki/Cabl=
eBeachCore1_0>, although the code is much further along than the documentat=
ion. There is a short introduction and motivation/vision statements on the =
homepage, along with a tech demo video to give you an idea of the user expe=
rience. I should have a video of the Cable Beach talk at Metaverse U and ac=
companying slides to put on the site soon.

John

> -----Original Message-----
> From: Mike Dickson [mailto:mike.dickson@hp.com]
> Sent: Tuesday, June 16, 2009 2:53 PM
> To: Hurliman, John
> Cc: Christian Scholz; mmox@ietf.org
> Subject: Re: [mmox] An attempt to revive this group: Service Disovery,=20
> part 1
>=20
> John,
>=20
>   Can you send a pointer to any info on the Cable Beach work?  I've
> seen a simple summary page on the OpenSim site but I'm curious if
> anything more detailed exists.
>=20
> Thanks!
>=20
> Mike
>=20
> On Tue, 2009-06-16 at 20:42 +0000, Hurliman, John wrote:
>> 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.
>>=20
>> John
>>=20
>>>

From tommi.s.e.laukkanen@gmail.com  Fri Jun 19 00:18:38 2009
Return-Path: <tommi.s.e.laukkanen@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 5B5E53A6A56 for <mmox@core3.amsl.com>; Fri, 19 Jun 2009 00:18:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 GZ2X9NObpg2q for <mmox@core3.amsl.com>; Fri, 19 Jun 2009 00:18:37 -0700 (PDT)
Received: from mail-bw0-f213.google.com (mail-bw0-f213.google.com [209.85.218.213]) by core3.amsl.com (Postfix) with ESMTP id 27B023A6A29 for <mmox@ietf.org>; Fri, 19 Jun 2009 00:18:36 -0700 (PDT)
Received: by bwz9 with SMTP id 9so1563303bwz.37 for <mmox@ietf.org>; Fri, 19 Jun 2009 00:18:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type:content-transfer-encoding; bh=sj6k+7Bj1hpoWHdiDgxWrI/HwXDGoUGsK35RYK2WxUg=; b=mJmmjHAHtKeGaaYkW4K55IIk6r6ziOqMZcC0zHUoP+Zzww6qdtS5TcwjerVq0JM7bw dza3CuNJgJuxJ2LIVtI+cnb4nJ11mY9S3yPhewLYJmaDQxmINkoMIF3fAs9CdDVVDMks imV8YuObgZqEaoRw/dUb8qhPQw3OC15uxbMTY=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=Ek/L6WYx97nmRpEifji/8gtrhBxrawGtAz8rA7KJiWPesK5WgnVPyl3vvTZhHlUzZM EK/kbmeimz/BVOYCDColn2CDje0yLUlNGEJ7LUlB+7u0yUidSrYMPIu3CqmSdNsl717q wA08xvwmSxw2CEeN4SCApLHoPCx8oMeWC80E8=
MIME-Version: 1.0
Received: by 10.204.58.9 with SMTP id e9mr2311122bkh.15.1245395927548; Fri, 19  Jun 2009 00:18:47 -0700 (PDT)
Date: Fri, 19 Jun 2009 10:18:47 +0300
Message-ID: <ad15b9430906190018g6e585f0ei8fc83c073056a7bd@mail.gmail.com>
From: Tommi Laukkanen <tommi.s.e.laukkanen@gmail.com>
To: mmox@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: [mmox] Global Object Identification
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, 19 Jun 2009 07:18:38 -0000

Dear All

Anyone have suggestion how we can achieve indisputable universal
identification of objects. It would be a good start for
interoperation.

Respectfully,
Tommi of bubblecloud.org

From mike.dickson@hp.com  Fri Jun 19 07:19:13 2009
Return-Path: <mike.dickson@hp.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 DE5453A6B8B for <mmox@core3.amsl.com>; Fri, 19 Jun 2009 07:19:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 0bx56RlCDOLv for <mmox@core3.amsl.com>; Fri, 19 Jun 2009 07:19:13 -0700 (PDT)
Received: from g4t0014.houston.hp.com (g4t0014.houston.hp.com [15.201.24.17]) by core3.amsl.com (Postfix) with ESMTP id E846B3A692D for <mmox@ietf.org>; Fri, 19 Jun 2009 07:19:12 -0700 (PDT)
Received: from g5t0012.atlanta.hp.com (g5t0012.atlanta.hp.com [15.192.0.49]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by g4t0014.houston.hp.com (Postfix) with ESMTPS id 1283C24130; Fri, 19 Jun 2009 14:19:18 +0000 (UTC)
Received: from [192.168.1.139] (conr-adsl-209-169-71-194.consolidated.net [209.169.71.194]) by g5t0012.atlanta.hp.com (Postfix) with ESMTPSA id 9F6EE10002; Fri, 19 Jun 2009 14:19:17 +0000 (UTC)
From: Mike Dickson <mike.dickson@hp.com>
To: Tommi Laukkanen <tommi.s.e.laukkanen@gmail.com>
In-Reply-To: <ad15b9430906190018g6e585f0ei8fc83c073056a7bd@mail.gmail.com>
References: <ad15b9430906190018g6e585f0ei8fc83c073056a7bd@mail.gmail.com>
Content-Type: text/plain
Organization: Bladesystems Infrastructure R&D
Date: Fri, 19 Jun 2009 09:19:10 -0500
Message-Id: <1245421150.26216.50.camel@mdickson-laptop>
Mime-Version: 1.0
X-Mailer: Evolution 2.26.1 
Content-Transfer-Encoding: 7bit
Cc: "mmox@ietf.org" <mmox@ietf.org>
Subject: Re: [mmox] Global Object Identification
X-BeenThere: mmox@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: mike.dickson@hp.com
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, 19 Jun 2009 14:19:14 -0000

How about the CNRI handle system?

http://www.handle.net/


On Fri, 2009-06-19 at 07:18 +0000, Tommi Laukkanen wrote:
> Dear All
> 
> Anyone have suggestion how we can achieve indisputable universal
> identification of objects. It would be a good start for
> interoperation.
> 
> Respectfully,
> Tommi of bubblecloud.org
> _______________________________________________
> mmox mailing list
> mmox@ietf.org
> https://www.ietf.org/mailman/listinfo/mmox


From infinity@lindenlab.com  Fri Jun 19 14:08:32 2009
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 240D53A6A03 for <mmox@core3.amsl.com>; Fri, 19 Jun 2009 14:08:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.661
X-Spam-Level: 
X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[AWL=0.317,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
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 5SrWYkl4ba8Q for <mmox@core3.amsl.com>; Fri, 19 Jun 2009 14:08:31 -0700 (PDT)
Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.241]) by core3.amsl.com (Postfix) with ESMTP id 1F6573A68BC for <mmox@ietf.org>; Fri, 19 Jun 2009 14:08:31 -0700 (PDT)
Received: by an-out-0708.google.com with SMTP id c3so842669ana.4 for <mmox@ietf.org>; Fri, 19 Jun 2009 14:08:42 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.100.46.3 with SMTP id t3mr4495464ant.94.1245445722393; Fri, 19  Jun 2009 14:08:42 -0700 (PDT)
In-Reply-To: <ad15b9430906190018g6e585f0ei8fc83c073056a7bd@mail.gmail.com>
References: <ad15b9430906190018g6e585f0ei8fc83c073056a7bd@mail.gmail.com>
Date: Fri, 19 Jun 2009 14:08:42 -0700
Message-ID: <3a880e2c0906191408m66e87830w6094987335fb6c16@mail.gmail.com>
From: Infinity Linden <infinity@lindenlab.com>
To: Tommi Laukkanen <tommi.s.e.laukkanen@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: mmox@ietf.org
Subject: Re: [mmox] Global Object Identification
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, 19 Jun 2009 21:08:32 -0000

Historically, systems like Second Life and OpenSim have used UUIDs to
identify objects. As a number of us started thinking about
interoperability, the idea of the "naked UUID" (i.e. - a UUID that
exists without context) would pose a problem. I think there's general
agreement that moving to a system where you use URIs to identify
objects is "a good idea." The idea being that if you have a URL,
you'll always know where to go to get meta-information about the
object (if not the digital representation of the object itself.)

I think there's been discussion about "rebooting" the digital asset
sub-system to make it a better fit for a distributed virtual world
(and more scalable) to include the use of URIs to address objects,
what classes of objects should be defined in the specification, and
how one extends the list of defined object classes. In previous drafts
of the charter, there was an objective for this listed as "OGP Virtual
World Primitive Object Format." A title like "Digital Asset Addressing
and Definition" might be a better title.

But the take-away is, there's been some thought about this. John
Hurliman has been working on a full-on asset service. OpenSim and
Second Life  (and probably realXtend and others) would benefit from a
well defined asset service that uses URIs for references, perhaps
using the existing asset classes defined by SL/OpenSim and maybe
realXtend.

-cheers
-meadhbh

On Fri, Jun 19, 2009 at 12:18 AM, Tommi
Laukkanen<tommi.s.e.laukkanen@gmail.com> wrote:
> Dear All
>
> Anyone have suggestion how we can achieve indisputable universal
> identification of objects. It would be a good start for
> interoperation.
>
> Respectfully,
> Tommi of bubblecloud.org
> _______________________________________________
> mmox mailing list
> mmox@ietf.org
> https://www.ietf.org/mailman/listinfo/mmox
>

From mike.dickson@hp.com  Fri Jun 19 14:26:40 2009
Return-Path: <mike.dickson@hp.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 82EB53A6BFF for <mmox@core3.amsl.com>; Fri, 19 Jun 2009 14:26:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 pchndeHNLv4O for <mmox@core3.amsl.com>; Fri, 19 Jun 2009 14:26:37 -0700 (PDT)
Received: from g5t0008.atlanta.hp.com (g5t0008.atlanta.hp.com [15.192.0.45]) by core3.amsl.com (Postfix) with ESMTP id B031A3A6B86 for <mmox@ietf.org>; Fri, 19 Jun 2009 14:26:37 -0700 (PDT)
Received: from g5t0012.atlanta.hp.com (unknown [15.192.0.16]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by g5t0008.atlanta.hp.com (Postfix) with ESMTPS id 12C64242EE; Fri, 19 Jun 2009 21:26:49 +0000 (UTC)
Received: from [192.168.1.139] (conr-adsl-209-169-71-194.consolidated.net [209.169.71.194]) by g5t0012.atlanta.hp.com (Postfix) with ESMTPSA id 9910610002; Fri, 19 Jun 2009 21:26:49 +0000 (UTC)
From: Mike Dickson <mike.dickson@hp.com>
To: Infinity Linden <infinity@lindenlab.com>
In-Reply-To: <3a880e2c0906191408m66e87830w6094987335fb6c16@mail.gmail.com>
References: <ad15b9430906190018g6e585f0ei8fc83c073056a7bd@mail.gmail.com> <3a880e2c0906191408m66e87830w6094987335fb6c16@mail.gmail.com>
Content-Type: text/plain
Organization: Bladesystems Infrastructure R&D
Date: Fri, 19 Jun 2009 16:26:41 -0500
Message-Id: <1245446801.9567.12.camel@mdickson-laptop>
Mime-Version: 1.0
X-Mailer: Evolution 2.26.1 
Content-Transfer-Encoding: 7bit
Cc: "mmox@ietf.org" <mmox@ietf.org>
Subject: Re: [mmox] Global Object Identification
X-BeenThere: mmox@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: mike.dickson@hp.com
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, 19 Jun 2009 21:26:40 -0000

I mentioned it in a separate message, but have you had a look at the
NCRI handle service for this. It really seems spot on.  There is the
need to address how digital assets map into it and what metadata is
useful to carry around but the handle service was designed specifically
to handle the secure resolution of URI's to "providers".

Mike

On Fri, 2009-06-19 at 21:08 +0000, Infinity Linden wrote:
> Historically, systems like Second Life and OpenSim have used UUIDs to
> identify objects. As a number of us started thinking about
> interoperability, the idea of the "naked UUID" (i.e. - a UUID that
> exists without context) would pose a problem. I think there's general
> agreement that moving to a system where you use URIs to identify
> objects is "a good idea." The idea being that if you have a URL,
> you'll always know where to go to get meta-information about the
> object (if not the digital representation of the object itself.)
> 
> I think there's been discussion about "rebooting" the digital asset
> sub-system to make it a better fit for a distributed virtual world
> (and more scalable) to include the use of URIs to address objects,
> what classes of objects should be defined in the specification, and
> how one extends the list of defined object classes. In previous drafts
> of the charter, there was an objective for this listed as "OGP Virtual
> World Primitive Object Format." A title like "Digital Asset Addressing
> and Definition" might be a better title.
> 
> But the take-away is, there's been some thought about this. John
> Hurliman has been working on a full-on asset service. OpenSim and
> Second Life  (and probably realXtend and others) would benefit from a
> well defined asset service that uses URIs for references, perhaps
> using the existing asset classes defined by SL/OpenSim and maybe
> realXtend.
> 
> -cheers
> -meadhbh
> 
> On Fri, Jun 19, 2009 at 12:18 AM, Tommi
> Laukkanen<tommi.s.e.laukkanen@gmail.com> wrote:
> > Dear All
> >
> > Anyone have suggestion how we can achieve indisputable universal
> > identification of objects. It would be a good start for
> > interoperation.
> >
> > Respectfully,
> > Tommi of bubblecloud.org
> > _______________________________________________
> > mmox mailing list
> > mmox@ietf.org
> > https://www.ietf.org/mailman/listinfo/mmox
> >
> _______________________________________________
> mmox mailing list
> mmox@ietf.org
> https://www.ietf.org/mailman/listinfo/mmox


From imaze.rhiano@gmail.com  Fri Jun 19 16:35:17 2009
Return-Path: <imaze.rhiano@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 8472E3A6A4E for <mmox@core3.amsl.com>; Fri, 19 Jun 2009 16:35:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 LPhSDyQ68Rpk for <mmox@core3.amsl.com>; Fri, 19 Jun 2009 16:35:16 -0700 (PDT)
Received: from mail-fx0-f212.google.com (mail-fx0-f212.google.com [209.85.220.212]) by core3.amsl.com (Postfix) with ESMTP id 6A73A3A693E for <mmox@ietf.org>; Fri, 19 Jun 2009 16:35:16 -0700 (PDT)
Received: by fxm8 with SMTP id 8so378191fxm.37 for <mmox@ietf.org>; Fri, 19 Jun 2009 16:35:27 -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=UnZjrqEi6BXkMrLV/uV5jmIHQgW2+ika3V4Ux8Ny3Vk=; b=msbvPTpX8pzi7P6dfcw44iDpoyCPrnLHaISNDvH9VeP0uQLXz2HJdg2aBHhhr00sZh GCVDg7+kaxnzHT692nYoJhZaQzMAf8AQS4ad6KBBvO6EZMI5AnIfWz+aYkqzX5kSBS4m y1JiXyngDJV1fC46tUyQk1S2ONJibIjjxdLuo=
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=hfX0qiqKd3Ju3PaEWA8XqKgF2zEMDI3W6Rt9qrVl7RimjwUBGxN/hjBDoAVvatJN8I EEqGuVfn08WQCk3cUv+vFr2kSD0uZS5V9uaILboBwPTbdmDzyZ79ZVD/yYabVD3fYGUS 5IHpW+LrGZMDG/yV9ogDc4VGuWfdmlywYwchg=
Received: by 10.103.220.18 with SMTP id x18mr2227124muq.24.1245454526972; Fri, 19 Jun 2009 16:35:26 -0700 (PDT)
Received: from ?192.168.0.100? (85-23-9-21-Karjasilta-TR1.suomi.net [85.23.9.21]) by mx.google.com with ESMTPS id t10sm6252823muh.30.2009.06.19.16.35.24 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 19 Jun 2009 16:35:24 -0700 (PDT)
Message-ID: <4A3C20B5.4060602@gmail.com>
Date: Sat, 20 Jun 2009 02:35:17 +0300
From: Imaze Rhiano <imaze.rhiano@gmail.com>
User-Agent: Thunderbird 2.0.0.21 (Windows/20090302)
MIME-Version: 1.0
To: Tommi Laukkanen <tommi.s.e.laukkanen@gmail.com>
References: <ad15b9430906190018g6e585f0ei8fc83c073056a7bd@mail.gmail.com>
In-Reply-To: <ad15b9430906190018g6e585f0ei8fc83c073056a7bd@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: mmox@ietf.org
Subject: Re: [mmox] Global Object Identification
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, 19 Jun 2009 23:35:17 -0000

Hi!

Sorry about noobish question, but what is wrong with GUID?

Tommi Laukkanen kirjoitti:
> Dear All
>
> Anyone have suggestion how we can achieve indisputable universal
> identification of objects. It would be a good start for
> interoperation.
>
> Respectfully,
> Tommi of bubblecloud.org
> _______________________________________________
> mmox mailing list
> mmox@ietf.org
> https://www.ietf.org/mailman/listinfo/mmox
>
>   


From infinity@lindenlab.com  Fri Jun 19 18:03:32 2009
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 A264F3A6BC8 for <mmox@core3.amsl.com>; Fri, 19 Jun 2009 18:03:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.363
X-Spam-Level: 
X-Spam-Status: No, score=-1.363 tagged_above=-999 required=5 tests=[AWL=0.614,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
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 fWQY66b0zId8 for <mmox@core3.amsl.com>; Fri, 19 Jun 2009 18:03:31 -0700 (PDT)
Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.30]) by core3.amsl.com (Postfix) with ESMTP id A75EC3A6849 for <mmox@ietf.org>; Fri, 19 Jun 2009 18:03:31 -0700 (PDT)
Received: by yw-out-2324.google.com with SMTP id 3so902656ywj.49 for <mmox@ietf.org>; Fri, 19 Jun 2009 18:03:43 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.100.208.9 with SMTP id f9mr4723333ang.55.1245459822892; Fri,  19 Jun 2009 18:03:42 -0700 (PDT)
In-Reply-To: <4A3C20B5.4060602@gmail.com>
References: <ad15b9430906190018g6e585f0ei8fc83c073056a7bd@mail.gmail.com> <4A3C20B5.4060602@gmail.com>
Date: Fri, 19 Jun 2009 18:03:42 -0700
Message-ID: <3a880e2c0906191803o1da1305bh35759421fcb71fe9@mail.gmail.com>
From: Infinity Linden <infinity@lindenlab.com>
To: Imaze Rhiano <imaze.rhiano@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: mmox@ietf.org
Subject: Re: [mmox] Global Object Identification
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: Sat, 20 Jun 2009 01:03:32 -0000

nothing's wrong with GUIDs if you have one asset service. that way
when you get a GUID/UUID for an asset, you go to that one asset
service and say "okay.. gimme the (meta)data for this asset." it's a
little more difficult if you have more than one asset service cause
the UUID itself doesn't tell you what service to go to in order to
find an asset's (meta)data.

in order to find asset (meta)data from a GUID, you either have to have
a global registry where you can do UUID to asset service mapping or
you ship around the UUID and the location of the asset service. The
latter is essentially what we're talking about in OGP where asset caps
will probably look something like
http://example.com/assets/EBBD86E3-A274-4CD1-A86A-405AABCB7BF9 , where
"http://example.com/assets/" is the location of the service and
"EBBD86E3-A274-4CD1-A86A-405AABCB7BF9" is the UUID of the asset.

On Fri, Jun 19, 2009 at 4:35 PM, Imaze Rhiano<imaze.rhiano@gmail.com> wrote:
> Hi!
>
> Sorry about noobish question, but what is wrong with GUID?
>
> Tommi Laukkanen kirjoitti:
>>
>> Dear All
>>
>> Anyone have suggestion how we can achieve indisputable universal
>> identification of objects. It would be a good start for
>> interoperation.
>>
>> Respectfully,
>> Tommi of bubblecloud.org
>> _______________________________________________
>> mmox mailing list
>> mmox@ietf.org
>> https://www.ietf.org/mailman/listinfo/mmox
>>
>>
>
> _______________________________________________
> mmox mailing list
> mmox@ietf.org
> https://www.ietf.org/mailman/listinfo/mmox
>

From dhc2@dcrocker.net  Sun Jun 21 04:31:32 2009
Return-Path: <dhc2@dcrocker.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 956703A6BFE for <mmox@core3.amsl.com>; Sun, 21 Jun 2009 04:31:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 5UC7wybBrCgZ for <mmox@core3.amsl.com>; Sun, 21 Jun 2009 04:31:31 -0700 (PDT)
Received: from sbh17.songbird.com (unknown [IPv6:2001:470:1:76:0:ffff:4834:7147]) by core3.amsl.com (Postfix) with ESMTP id 2D9453A698D for <mmox@ietf.org>; Sun, 21 Jun 2009 04:31:31 -0700 (PDT)
Received: from [127.0.0.1] (adsl-68-122-40-191.dsl.pltn13.pacbell.net [68.122.40.191]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id n5LBVZx9030576 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 21 Jun 2009 04:31:41 -0700
Message-ID: <4A3E1A16.2070509@dcrocker.net>
Date: Sun, 21 Jun 2009 04:31:34 -0700
From: Dave CROCKER <dhc2@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Thunderbird 2.0.0.21 (Windows/20090302)
MIME-Version: 1.0
To: mike.dickson@hp.com
References: <ad15b9430906190018g6e585f0ei8fc83c073056a7bd@mail.gmail.com>	<3a880e2c0906191408m66e87830w6094987335fb6c16@mail.gmail.com> <1245446801.9567.12.camel@mdickson-laptop>
In-Reply-To: <1245446801.9567.12.camel@mdickson-laptop>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Sun, 21 Jun 2009 04:31:41 -0700 (PDT)
Cc: "mmox@ietf.org" <mmox@ietf.org>
Subject: Re: [mmox] Global Object Identification
X-BeenThere: mmox@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: dcrocker@bbiw.net
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, 21 Jun 2009 11:31:32 -0000

Mike Dickson wrote:
> I mentioned it in a separate message, but have you had a look at the
> NCRI handle service for this. It really seems spot on.  There is the
> need to address how digital assets map into it and what metadata is
> useful to carry around but the handle service was designed specifically
> to handle the secure resolution of URI's to "providers".


While there aren't many system/paradigm choices, here, there's more than one.

So it will probably help to have a brief summary of what the functional
requirements and constraints are, and then a mapping to the candidates.

(Saying URI, for example, doesn't really answer many technical questions,
although it typically means the top of the scoping hierarchy is defined by a
domain name.)

d/

-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net


From mike.dickson@hp.com  Sun Jun 21 09:29:07 2009
Return-Path: <mike.dickson@hp.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 3082228C105 for <mmox@core3.amsl.com>; Sun, 21 Jun 2009 09:29:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 qOBYNzSpGkYM for <mmox@core3.amsl.com>; Sun, 21 Jun 2009 09:29:06 -0700 (PDT)
Received: from g5t0007.atlanta.hp.com (g5t0007.atlanta.hp.com [15.192.0.44]) by core3.amsl.com (Postfix) with ESMTP id 65E0B28C101 for <mmox@ietf.org>; Sun, 21 Jun 2009 09:29:06 -0700 (PDT)
Received: from g5t0012.atlanta.hp.com (unknown [15.192.0.16]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by g5t0007.atlanta.hp.com (Postfix) with ESMTPS id 9264014225; Sun, 21 Jun 2009 16:29:18 +0000 (UTC)
Received: from [192.168.1.139] (conr-adsl-209-169-71-194.consolidated.net [209.169.71.194]) by g5t0012.atlanta.hp.com (Postfix) with ESMTPSA id 23CA010010; Sun, 21 Jun 2009 16:29:18 +0000 (UTC)
From: Mike Dickson <mike.dickson@hp.com>
To: "dcrocker@bbiw.net" <dcrocker@bbiw.net>
In-Reply-To: <4A3E1A16.2070509@dcrocker.net>
References: <ad15b9430906190018g6e585f0ei8fc83c073056a7bd@mail.gmail.com> <3a880e2c0906191408m66e87830w6094987335fb6c16@mail.gmail.com> <1245446801.9567.12.camel@mdickson-laptop> <4A3E1A16.2070509@dcrocker.net>
Content-Type: text/plain
Organization: Bladesystems Infrastructure R&D
Date: Sun, 21 Jun 2009 11:29:15 -0500
Message-Id: <1245601755.7174.3.camel@mdickson-laptop>
Mime-Version: 1.0
X-Mailer: Evolution 2.26.1 
Content-Transfer-Encoding: 7bit
Cc: "mmox@ietf.org" <mmox@ietf.org>
Subject: Re: [mmox] Global Object Identification
X-BeenThere: mmox@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: mike.dickson@hp.com
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, 21 Jun 2009 16:29:07 -0000

I was simply addressing a question about existing technologies for
resolving digital assets with one I was aware of.  I think the handle
system is well suited to the problem but I completely agree, having some
requirements down will help inform that decision.  

URI implies to me resources on the web (as opposed to local only where a
simple UUID might be sufficient).  But yes, again the details are what
matters and having some guidance vis requirements is really needed.

Mike

On Sun, 2009-06-21 at 11:31 +0000, Dave CROCKER wrote:
> 
> Mike Dickson wrote:
> > I mentioned it in a separate message, but have you had a look at the
> > NCRI handle service for this. It really seems spot on.  There is the
> > need to address how digital assets map into it and what metadata is
> > useful to carry around but the handle service was designed specifically
> > to handle the secure resolution of URI's to "providers".
> 
> 
> While there aren't many system/paradigm choices, here, there's more than one.
> 
> So it will probably help to have a brief summary of what the functional
> requirements and constraints are, and then a mapping to the candidates.
> 
> (Saying URI, for example, doesn't really answer many technical questions,
> although it typically means the top of the scoping hierarchy is defined by a
> domain name.)
> 
> d/
> 


From jwatte@gmail.com  Sun Jun 21 09:56:09 2009
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 31F473A6814 for <mmox@core3.amsl.com>; Sun, 21 Jun 2009 09:56:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 35vpCExep0Up for <mmox@core3.amsl.com>; Sun, 21 Jun 2009 09:56:08 -0700 (PDT)
Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.240]) by core3.amsl.com (Postfix) with ESMTP id 4756C3A694E for <mmox@ietf.org>; Sun, 21 Jun 2009 09:56:08 -0700 (PDT)
Received: by an-out-0708.google.com with SMTP id c3so1135830ana.4 for <mmox@ietf.org>; Sun, 21 Jun 2009 09:56:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=5jw11LFS73KcTXtCLms18JPpoUyXW46YvEl/2ICu8XY=; b=p/4V+uFXJ3w7s9+7UBDWjM4nfLZch418J8nPL0f5Bt/RktOeCVquJv2hr/mJXK6KQI gAvckWlzkxvN6einu9QnsC77ul0rUTCw8gmpSppeRN9wjLC1DWBI4O7k6CFhhZbbKm7j 2y9BJHNmjCd+V/B8e+1LjjGRUhN7BLNnux5P8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=jN+2d+prSQVibBhOi4yo8SbFwCT9AuCBBdx+LR83DGhnQPMEuHK4A6q24wCxdZgAT0 SzEEkLCd1BYIHOQsJY7QvWkxQgLRf6xXI8uhnEu9VsUKYjbh0FGKkCyonYZ1oDz0AABW 5JwaYwfjqTECcOlo4vdVXpViazsVF6ytofrxo=
MIME-Version: 1.0
Received: by 10.100.9.18 with SMTP id 18mr6729309ani.122.1245603380899; Sun,  21 Jun 2009 09:56:20 -0700 (PDT)
In-Reply-To: <1245601755.7174.3.camel@mdickson-laptop>
References: <ad15b9430906190018g6e585f0ei8fc83c073056a7bd@mail.gmail.com> <3a880e2c0906191408m66e87830w6094987335fb6c16@mail.gmail.com> <1245446801.9567.12.camel@mdickson-laptop> <4A3E1A16.2070509@dcrocker.net> <1245601755.7174.3.camel@mdickson-laptop>
Date: Sun, 21 Jun 2009 09:56:20 -0700
Message-ID: <c7bcbd620906210956l1a05fb81xb3dea005c902a564@mail.gmail.com>
From: Jon Watte <jwatte@gmail.com>
To: mike.dickson@hp.com
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "mmox@ietf.org" <mmox@ietf.org>, "dcrocker@bbiw.net" <dcrocker@bbiw.net>
Subject: Re: [mmox] Global Object Identification
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, 21 Jun 2009 16:56:09 -0000

I would assume that in an interoperable world, there is no "local
only" object ID. Or, more likely, if an internal ID is needed, it's up
to each host to manage these, and translate when talking to the
outside world.

Also, I'd think that mapping URI to "resource on the internet" is
right -- VWs are internet constructs, by and large.

Sincerely,

Jw


On 6/21/09, Mike Dickson <mike.dickson@hp.com> wrote:
> I was simply addressing a question about existing technologies for
> resolving digital assets with one I was aware of.  I think the handle
> system is well suited to the problem but I completely agree, having some
> requirements down will help inform that decision.
>
> URI implies to me resources on the web (as opposed to local only where a
> simple UUID might be sufficient).  But yes, again the details are what
> matters and having some guidance vis requirements is really needed.
>
> Mike
>
> On Sun, 2009-06-21 at 11:31 +0000, Dave CROCKER wrote:
>>
>> Mike Dickson wrote:
>> > I mentioned it in a separate message, but have you had a look at the
>> > NCRI handle service for this. It really seems spot on.  There is the
>> > need to address how digital assets map into it and what metadata is
>> > useful to carry around but the handle service was designed specifically
>> > to handle the secure resolution of URI's to "providers".
>>
>>
>> While there aren't many system/paradigm choices, here, there's more than
>> one.
>>
>> So it will probably help to have a brief summary of what the functional
>> requirements and constraints are, and then a mapping to the candidates.
>>
>> (Saying URI, for example, doesn't really answer many technical questions,
>> although it typically means the top of the scoping hierarchy is defined by
>> a
>> domain name.)
>>
>> d/
>>
>
> _______________________________________________
> mmox mailing list
> mmox@ietf.org
> https://www.ietf.org/mailman/listinfo/mmox
>


-- 

--
Americans might object: there is no way we would sacrifice our living
standards for the benefit of people in the rest of the world.
Nevertheless, whether we get there willingly or not, we shall soon
have lower consumption rates, because our present rates are
unsustainable.
