
From john.hurliman@intel.com  Wed Jul  1 20:01:38 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 1A73128C103 for <mmox@core3.amsl.com>; Wed,  1 Jul 2009 20:01:38 -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 ukE2Javzhk1l for <mmox@core3.amsl.com>; Wed,  1 Jul 2009 20:01:37 -0700 (PDT)
Received: from mga03.intel.com (mga03.intel.com [143.182.124.21]) by core3.amsl.com (Postfix) with ESMTP id 473863A68AF for <mmox@ietf.org>; Wed,  1 Jul 2009 20:01:37 -0700 (PDT)
Received: from azsmga001.ch.intel.com ([10.2.17.19]) by azsmga101.ch.intel.com with ESMTP; 01 Jul 2009 20:01:58 -0700
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="4.42,330,1243839600"; d="scan'208";a="160747185"
Received: from rrsmsx602.amr.corp.intel.com ([10.31.0.33]) by azsmga001.ch.intel.com with ESMTP; 01 Jul 2009 20:01:58 -0700
Received: from rrsmsx506.amr.corp.intel.com ([10.31.0.39]) by rrsmsx602.amr.corp.intel.com ([10.31.0.33]) with mapi; Wed, 1 Jul 2009 21:01:58 -0600
From: "Hurliman, John" <john.hurliman@intel.com>
To: "mmox@ietf.org" <mmox@ietf.org>
Date: Wed, 1 Jul 2009 21:01:44 -0600
Thread-Topic: Rough draft of the Cable Beach Core protocol is online
Thread-Index: Acn6wW3dU4U64W0CSTSEo5ZZD7lf/A==
Message-ID: <62BFE5680C037E4DA0B0A08946C0933D912BC1E3@rrsmsx506.amr.corp.intel.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-cr-puzzleid: {EE171B88-B816-4C87-A2DE-0591D7BCD4AC}
x-cr-hashedpuzzle: A75c BFLA BKHs B/I4 C/rU DADx EXK0 EiMr FS/1 GT6o HaEz IppQ KE0S LLSy LrBP Lzre; 1; bQBtAG8AeABAAGkAZQB0AGYALgBvAHIAZwA=; Sosha1_v1; 7; {EE171B88-B816-4C87-A2DE-0591D7BCD4AC}; agBvAGgAbgAuAGgAdQByAGwAaQBtAGEAbgBAAGkAbgB0AGUAbAAuAGMAbwBtAA==; Thu, 02 Jul 2009 03:01:44 GMT; UgBvAHUAZwBoACAAZAByAGEAZgB0ACAAbwBmACAAdABoAGUAIABDAGEAYgBsAGUAIABCAGUAYQBjAGgAIABDAG8AcgBlACAAcAByAG8AdABvAGMAbwBsACAAaQBzACAAbwBuAGwAaQBuAGUA
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [mmox] Rough draft of the Cable Beach Core protocol is online
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, 02 Jul 2009 03:01:38 -0000

http://code.google.com/p/cablebeach/wiki/CableBeachCore1_0

>From the Cable Beach website:

Introduction

Virtual worlds are made up of a complex stack of services that operate toge=
ther to deliver a complete immersive experience. The approach that virtual =
worlds have taken so far is to build an entire vertical stack of services i=
ncluding user account management, content distribution servers, inventory h=
osting, simulation servers, simulation coordinators, and more. As virtual w=
orlds grow in both popularity and complexity, it is no longer always desira=
ble to only build so-called "walled gardens" of services. Cable Beach provi=
des the glue to bind virtual world services together, whether they exist al=
ongside one another in a data center or across the Internet run by differen=
t administrators that have no preexisting relationship. The primary focus o=
f the architecture is on the following:

    * Let service providers specialize in what they do best. To address the=
 growing scalability demands of the web, service providers have evolved int=
o providing narrow but high quality services. You wouldn't expect a social =
network to also provide the best search engine service on the web.
    * Use existing standards. Many of the challenges in virtual worlds are =
broad issues that are also being addressed by the web community. Instead of=
 creating new parallel solutions, Cable Beach attempts to leverage as much =
existing technology as it can to enable better compatibility with other arc=
hitectures, both today and in the future.
    * Give virtual world administrators more flexibility, not less. No use =
case is viewed as more or less valid than another, and the system does not =
favor any particular setup. Building a walled garden is just as easy as bui=
lding a completely decentralized world, or any combination of the two.=20

The core of Cable Beach is the definition of a world service, a virtual wor=
ld login protocol, and a standard method of defining virtual world services=
. The implementation available at this site consists of a server for a worl=
d service and another server for assets and filesystem services. Initially,=
 this implementation is targeting compatibility with the OpenSim project us=
ing a custom OpenSim extension called ModCableBeach. Additional connectors =
for other virtual world systems are in the planning phase.

---
John

From tommi.s.e.laukkanen@gmail.com  Sat Jul  4 05:31:07 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 30C1F3A6A4D for <mmox@core3.amsl.com>; Sat,  4 Jul 2009 05:31:07 -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 bx9iR-YHInGT for <mmox@core3.amsl.com>; Sat,  4 Jul 2009 05:31:06 -0700 (PDT)
Received: from mail-bw0-f207.google.com (mail-bw0-f207.google.com [209.85.218.207]) by core3.amsl.com (Postfix) with ESMTP id 2566B3A6359 for <mmox@ietf.org>; Sat,  4 Jul 2009 05:31:05 -0700 (PDT)
Received: by bwz3 with SMTP id 3so842797bwz.37 for <mmox@ietf.org>; Sat, 04 Jul 2009 05:31:27 -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=FK5rbNm3kR/lZ3xvsC/f610d1BoqhFNYr5O64PBUuCM=; b=URStVtR7j48JEazK52H1GiPS2QcmQZR26V96xNU8dCRcErczHEv8CEdNm/RBL1KWNh pTj/pk3NH8pOea/7QyrYoYdhlF6WVbhKwhvwrY6sJBBTS9IFd9KBMKuefIZwo281o48R 0Ak3gAaUBKvIYJgm/W8XX0VfaGYIyZqplRnoQ=
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=H0K/FfTqlnDOVPIJwpL6IJF4n0xonXgBHdd8Lqy0u5hWIj0Ue0oQ5t3aD/7Ky9n/ln NQOkVz+JtS3Oci9kxPohEWD46yTWtDY24mEGK3D0mUlnKS55BDnR4He+Xc2lmeV7dpHN ROHgcIbnVkC5XE5P80sCJMOAqhVoCYwIeneYM=
MIME-Version: 1.0
Received: by 10.204.52.136 with SMTP id i8mr2341032bkg.160.1246710687678; Sat,  04 Jul 2009 05:31:27 -0700 (PDT)
In-Reply-To: <c7bcbd620906210956l1a05fb81xb3dea005c902a564@mail.gmail.com>
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> <c7bcbd620906210956l1a05fb81xb3dea005c902a564@mail.gmail.com>
Date: Sat, 4 Jul 2009 15:31:26 +0300
Message-ID: <ad15b9430907040531j18caf370y2a9b400ace86394a@mail.gmail.com>
From: Tommi Laukkanen <tommi.s.e.laukkanen@gmail.com>
To: Jon Watte <jwatte@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
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: Sat, 04 Jul 2009 12:31:07 -0000

Hello

I gather from this and previous discussions that there are two wide
spread systems for global object indetification:

1) Handle System (from CNRI) - Global identifier to service resolving
network in analogy with DNS. Adding your data type to the network has
a cost. How does the cost scale with number of objects?

2) Extensible Resource Identifier (XRI) - The url for XRD document
containing service locations can be calculated from XRI identifier.

I guess these two approaches are in theory the two viable ways to do
global identifiers. Either build global resolving / register network
or include enough information in the identifier to resolve url
directly from it.

Are there other viable implementations? If not should we dive deeper
in comparing these two alternatives?

-tommi

From mike.dickson@hp.com  Sun Jul  5 10:01: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 E642F3A6A01 for <mmox@core3.amsl.com>; Sun,  5 Jul 2009 10:01:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.539
X-Spam-Level: 
X-Spam-Status: No, score=-106.539 tagged_above=-999 required=5 tests=[AWL=0.060, 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 hdeiXDrHJYUV for <mmox@core3.amsl.com>; Sun,  5 Jul 2009 10:01:40 -0700 (PDT)
Received: from g1t0028.austin.hp.com (g1t0028.austin.hp.com [15.216.28.35]) by core3.amsl.com (Postfix) with ESMTP id 2401F3A691A for <mmox@ietf.org>; Sun,  5 Jul 2009 10:01:40 -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 A82AC1C188; Sun,  5 Jul 2009 17:02:04 +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 C2CBD1001D; Sun,  5 Jul 2009 17:02:03 +0000 (UTC)
From: Mike Dickson <mike.dickson@hp.com>
To: Tommi Laukkanen <tommi.s.e.laukkanen@gmail.com>
In-Reply-To: <ad15b9430907040531j18caf370y2a9b400ace86394a@mail.gmail.com>
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> <c7bcbd620906210956l1a05fb81xb3dea005c902a564@mail.gmail.com> <ad15b9430907040531j18caf370y2a9b400ace86394a@mail.gmail.com>
Content-Type: text/plain
Organization: Bladesystems Infrastructure R&D
Date: Sun, 05 Jul 2009 12:01:57 -0500
Message-Id: <1246813317.4532.48.camel@mdickson-laptop>
Mime-Version: 1.0
X-Mailer: Evolution 2.26.1 
Content-Transfer-Encoding: 7bit
Cc: "mmox@ietf.org" <mmox@ietf.org>, Jon Watte <jwatte@gmail.com>, "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
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, 05 Jul 2009 17:01:41 -0000

Cost for the handle system is non-linear. Similar to DNS.  Once you
register a domain how many things get put under it is your own business.
The cost for the registration is pretty minimal.  Primarily to fund the
maintenance of the root servers.

I like the handle system because its been around for a while, proven to
scale reasonably well, etc.  There's support for metadata on the objects
referenced also so it also partly addresses what "type" of thing is
being referenced and what can/should be done with it.

Mike

On Sat, 2009-07-04 at 12:31 +0000, Tommi Laukkanen wrote:
> Hello
> 
> I gather from this and previous discussions that there are two wide
> spread systems for global object indetification:
> 
> 1) Handle System (from CNRI) - Global identifier to service resolving
> network in analogy with DNS. Adding your data type to the network has
> a cost. How does the cost scale with number of objects?
> 
> 2) Extensible Resource Identifier (XRI) - The url for XRD document
> containing service locations can be calculated from XRI identifier.
> 
> I guess these two approaches are in theory the two viable ways to do
> global identifiers. Either build global resolving / register network
> or include enough information in the identifier to resolve url
> directly from it.
> 
> Are there other viable implementations? If not should we dive deeper
> in comparing these two alternatives?
> 
> -tommi


From dcrocker@bbiw.net  Sun Jul  5 10:49:47 2009
Return-Path: <dcrocker@bbiw.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 9DB0E3A6B88 for <mmox@core3.amsl.com>; Sun,  5 Jul 2009 10:49:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.442
X-Spam-Level: 
X-Spam-Status: No, score=-2.442 tagged_above=-999 required=5 tests=[AWL=-0.158, BAYES_00=-2.599, SARE_MILLIONSOF=0.315]
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 EixMzp4WWEqU for <mmox@core3.amsl.com>; Sun,  5 Jul 2009 10:49:46 -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 427D43A6846 for <mmox@ietf.org>; Sun,  5 Jul 2009 10:49:46 -0700 (PDT)
Received: from [127.0.0.1] (ppp-68-120-199-146.dsl.pltn13.pacbell.net [68.120.199.146]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id n65Ho2h3006763 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 5 Jul 2009 10:50:07 -0700
Message-ID: <4A50E7C9.1090208@bbiw.net>
Date: Sun, 05 Jul 2009 10:50:01 -0700
From: Dave CROCKER <dcrocker@bbiw.net>
Organization: Brandenburg InternetWorking
User-Agent: Thunderbird 2.0.0.22 (Windows/20090605)
MIME-Version: 1.0
To: mike.dickson@hp.com
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>	 <c7bcbd620906210956l1a05fb81xb3dea005c902a564@mail.gmail.com>	 <ad15b9430907040531j18caf370y2a9b400ace86394a@mail.gmail.com> <1246813317.4532.48.camel@mdickson-laptop>
In-Reply-To: <1246813317.4532.48.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, 05 Jul 2009 10:50:07 -0700 (PDT)
X-Mailman-Approved-At: Sun, 05 Jul 2009 11:01:15 -0700
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
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, 05 Jul 2009 17:49:47 -0000

Mike Dickson wrote:
> I like the handle system because its been around for a while, proven to
> scale reasonably well, etc.  


So, the metric I use for scaling, when talking about Internet standards, is many 
millions of independent users and at least many thousands of independent 
administrations, all participating in the same system.

In other words, a single integrated service that is operated by a very large 
number of independent groups and that is used by a couple of orders of magnitude 
more of independent groups and people.

I know there are large handle systems, but I don't know of any that satisfy 
these criteria.  (By "don't know" I am asking to be educated; I truly don't know 
that much about the range of installations for handle.)

For a system that does not already satisfy this requirement, the burden is to 
explain why the world should believe that the system will be able to.  And 
again, I mean that as a serious request, not an implied criticism or dismissal.

d/
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From mike.dickson@hp.com  Sun Jul  5 12:04:19 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 5FCB93A6C1E for <mmox@core3.amsl.com>; Sun,  5 Jul 2009 12:04:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.392
X-Spam-Level: 
X-Spam-Status: No, score=-106.392 tagged_above=-999 required=5 tests=[AWL=-0.107, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_MILLIONSOF=0.315, 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 qOXDtZNDuO8Q for <mmox@core3.amsl.com>; Sun,  5 Jul 2009 12:04:18 -0700 (PDT)
Received: from g1t0027.austin.hp.com (g1t0027.austin.hp.com [15.216.28.34]) by core3.amsl.com (Postfix) with ESMTP id 2D5A13A6B55 for <mmox@ietf.org>; Sun,  5 Jul 2009 12:04:18 -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 g1t0027.austin.hp.com (Postfix) with ESMTPS id BE1933823F; Sun,  5 Jul 2009 19:04:42 +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 4B1AE10020; Sun,  5 Jul 2009 19:04:42 +0000 (UTC)
From: Mike Dickson <mike.dickson@hp.com>
To: Dave CROCKER <dcrocker@bbiw.net>
In-Reply-To: <4A50E7C9.1090208@bbiw.net>
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> <c7bcbd620906210956l1a05fb81xb3dea005c902a564@mail.gmail.com> <ad15b9430907040531j18caf370y2a9b400ace86394a@mail.gmail.com> <1246813317.4532.48.camel@mdickson-laptop> <4A50E7C9.1090208@bbiw.net>
Content-Type: text/plain
Organization: Bladesystems Infrastructure R&D
Date: Sun, 05 Jul 2009 14:04:35 -0500
Message-Id: <1246820675.4532.55.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, 05 Jul 2009 19:04:19 -0000

On Sun, 2009-07-05 at 17:50 +0000, Dave CROCKER wrote:
> 
> Mike Dickson wrote:
> > I like the handle system because its been around for a while, proven to
> > scale reasonably well, etc.  
> 
> 
> So, the metric I use for scaling, when talking about Internet standards, is many 
> millions of independent users and at least many thousands of independent 
> administrations, all participating in the same system.

I can't think of alot of "systems" that would satisfy your definition
(other than perhaps the current web infrastructure w/DNS).  That being
said the factsheet from the handle site has some details. 

http://www.handle.net/factsheet.html

> In other words, a single integrated service that is operated by a very large 
> number of independent groups and that is used by a couple of orders of magnitude 
> more of independent groups and people.

Given the details in the fact sheet I'd say the handle system satisfies
that criteria. If you don't believe so I'd like to understand what you
think is missing.  

BTW, I don't actually work on/with the handle system.  I was aware of it
and it's the best example I know of that handles very large scale
resource resolution across the web.

> For a system that does not already satisfy this requirement, the burden is to 
> explain why the world should believe that the system will be able to.  And 
> again, I mean that as a serious request, not an implied criticism or dismissal.

Well, as I said I think as the fact sheet indicates IMO it already does.
if you don't think so it would be valuable to hear why. And to put
forward and alternative that you think is representative of your
requirements.

Mike



From jwatte@gmail.com  Sun Jul  5 14:41:02 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 204AE3A6ACA for <mmox@core3.amsl.com>; Sun,  5 Jul 2009 14:41:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.684
X-Spam-Level: 
X-Spam-Status: No, score=-1.684 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_33=0.6, SARE_MILLIONSOF=0.315]
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 U8cDW0gL6R+8 for <mmox@core3.amsl.com>; Sun,  5 Jul 2009 14:41:01 -0700 (PDT)
Received: from mail-pz0-f198.google.com (mail-pz0-f198.google.com [209.85.222.198]) by core3.amsl.com (Postfix) with ESMTP id 1BEE23A6803 for <mmox@ietf.org>; Sun,  5 Jul 2009 14:41:01 -0700 (PDT)
Received: by pzk36 with SMTP id 36so3809919pzk.29 for <mmox@ietf.org>; Sun, 05 Jul 2009 14:41:18 -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=kPzOCMG0V9kZl1VkgAc8WMa/px/xZA8AGvHGptHSNwY=; b=JwbqsJ1byp2tFa0ngLCyGrjRytX48eEvL+OpfwBwPkLKyRV+8ylu0fUfJYRNPBC9zz 0JLUXrvbB8+3c0xRl28/iiK/aA47VzsBpkb/HHCiETvANjf9UOiNS/0FubSJLNqSbZ9x Gpgpk+Jkh4i7YnAuu8Lhjc+gz67a4PP1H6hcs=
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=AZliYpQCCFTWHSn3XG9dtuSoIjEU/s2DS1vPICgWZh19BseLd5/thZyg6gPrlQ8ehC o9NTL+Txc6S1wqNQPYn7vW1DatoOF7gGccWiDGxI/ppMY5sWwZw0cggEyIBSD326ZaZS F26jExpko4ibFClXzJ2suvavIe/2r0YRKDVic=
Received: by 10.114.92.20 with SMTP id p20mr6224390wab.172.1246830077785; Sun, 05 Jul 2009 14:41:17 -0700 (PDT)
Received: from ?192.168.1.101? (svn.mindcontrol.org [69.17.45.136]) by mx.google.com with ESMTPS id n40sm10078311wag.65.2009.07.05.14.41.14 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sun, 05 Jul 2009 14:41:15 -0700 (PDT)
Message-ID: <4A511DF9.9000508@gmail.com>
Date: Sun, 05 Jul 2009 14:41:13 -0700
From: Jon Watte <jwatte@gmail.com>
User-Agent: Thunderbird 2.0.0.22 (Windows/20090605)
MIME-Version: 1.0
To: mike.dickson@hp.com
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>	<c7bcbd620906210956l1a05fb81xb3dea005c902a564@mail.gmail.com>	<ad15b9430907040531j18caf370y2a9b400ace86394a@mail.gmail.com>	<1246813317.4532.48.camel@mdickson-laptop> <4A50E7C9.1090208@bbiw.net> <1246820675.4532.55.camel@mdickson-laptop>
In-Reply-To: <1246820675.4532.55.camel@mdickson-laptop>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "mmox@ietf.org" <mmox@ietf.org>, Dave CROCKER <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, 05 Jul 2009 21:41:02 -0000

Mike Dickson wrote:
> On Sun, 2009-07-05 at 17:50 +0000, Dave CROCKER wrote:
>   
>> Mike Dickson wrote:
>>     
>>> I like the handle system because its been around for a while, proven to
>>> scale reasonably well, etc.  
>>>       
>> So, the metric I use for scaling, when talking about Internet standards, is many 
>> millions of independent users and at least many thousands of independent 
>> administrations, all participating in the same system.
>>     
>
> I can't think of alot of "systems" that would satisfy your definition
> (other than perhaps the current web infrastructure w/DNS).  That being
> said the factsheet from the handle site has some details. 
>
> http://www.handle.net/factsheet.html
>   

If I want my web servers to scale, I can easily buy all kinds of 
acceleration hardware -- edge-mounted CDNs, load balancers, caching 
proxies, 1000-core Java accelerators, you name it!
If I want my DNS to scale, there are several solutions I can buy to 
scale it to whatever load I need.
I can't find any product that will allow me to accelerate handle 
resolution. This, to me, is evidence that resolving URLs is at least an 
order of magnitude better supported than handles (and, in most 
likelihood, several orders of magnitude).

I believe that, if you need a unique ID for something, then using 
DNS+URL is the best way. You can legislate what you get at the end of 
that URL -- an XRD document, for example. Thus, code to deal with an 
entity becomes trivial, because every software stack in existence 
(including cell phones, Nintendo DS, and friends) all can fetch a URL 
and parse XML.

Meanwhile, resolving a handle to an actual object or service means that 
you first have to resolve the handle, and then turn that around and 
resolve a URL anyway.

The main reason for Handles to exist is that a document may "move." 
However, that "move" only matters if the domain of that object can't 
move with you. With modern DNS, that's basically a non-problem. Either 
put up a sub-domain for your coroprate, organization or vanity domain, 
or outsource it to someone who will stay around. Handle providers must 
also stay around, and given that the business is much smaller than the 
DNS business, the longevity of a handle provider is rather less assured 
IMO...

Sincerely,

jw




-- 

  Revenge is the most pointless and damaging of human desires.


From mike.dickson@hp.com  Sun Jul  5 15:33:27 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 102273A691D for <mmox@core3.amsl.com>; Sun,  5 Jul 2009 15:33:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.234
X-Spam-Level: 
X-Spam-Status: No, score=-106.234 tagged_above=-999 required=5 tests=[AWL=-0.235, BAYES_00=-2.599, J_CHICKENPOX_33=0.6, 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 MBGQ6eRI8WWF for <mmox@core3.amsl.com>; Sun,  5 Jul 2009 15:33:26 -0700 (PDT)
Received: from g1t0029.austin.hp.com (g1t0029.austin.hp.com [15.216.28.36]) by core3.amsl.com (Postfix) with ESMTP id 04B2728C146 for <mmox@ietf.org>; Sun,  5 Jul 2009 15:33:25 -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 g1t0029.austin.hp.com (Postfix) with ESMTPS id AC6C538096; Sun,  5 Jul 2009 22:33: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 1175F1001A; Sun,  5 Jul 2009 22:33:49 +0000 (UTC)
From: Mike Dickson <mike.dickson@hp.com>
To: Jon Watte <jwatte@gmail.com>
In-Reply-To: <4A511DF9.9000508@gmail.com>
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> <c7bcbd620906210956l1a05fb81xb3dea005c902a564@mail.gmail.com> <ad15b9430907040531j18caf370y2a9b400ace86394a@mail.gmail.com> <1246813317.4532.48.camel@mdickson-laptop> <4A50E7C9.1090208@bbiw.net> <1246820675.4532.55.camel@mdickson-laptop> <4A511DF9.9000508@gmail.com>
Content-Type: text/plain
Organization: Bladesystems Infrastructure R&D
Date: Sun, 05 Jul 2009 17:33:42 -0500
Message-Id: <1246833222.4532.83.camel@mdickson-laptop>
Mime-Version: 1.0
X-Mailer: Evolution 2.26.1 
Content-Transfer-Encoding: 7bit
Cc: "mmox@ietf.org" <mmox@ietf.org>, Dave CROCKER <dcrocker@bbiw.net>
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, 05 Jul 2009 22:33:27 -0000

On Sun, 2009-07-05 at 21:41 +0000, Jon Watte wrote:
> Mike Dickson wrote:
> > I can't think of alot of "systems" that would satisfy your definition
> > (other than perhaps the current web infrastructure w/DNS).  That being
> > said the factsheet from the handle site has some details. 
> >
> > http://www.handle.net/factsheet.html
> >   
> 
> If I want my web servers to scale, I can easily buy all kinds of 
> acceleration hardware -- edge-mounted CDNs, load balancers, caching 
> proxies, 1000-core Java accelerators, you name it!
> If I want my DNS to scale, there are several solutions I can buy to 
> scale it to whatever load I need.
> I can't find any product that will allow me to accelerate handle 
> resolution. This, to me, is evidence that resolving URLs is at least an 
> order of magnitude better supported than handles (and, in most 
> likelihood, several orders of magnitude).

I'm not the best person to defend the handle.net technology. The proxy
service is however a standard servlet thingy so all the normal ways you
scale this type of app apply.  

> 
> I believe that, if you need a unique ID for something, then using 
> DNS+URL is the best way. You can legislate what you get at the end of 
> that URL -- an XRD document, for example. Thus, code to deal with an 
> entity becomes trivial, because every software stack in existence 
> (including cell phones, Nintendo DS, and friends) all can fetch a URL 
> and parse XML.

Queries to the handle proxy server are formatted as standard url's.
There are mechanism to request return values in RDF/XML, RDF/N3, and
JSON. The handle server was in fact designed for the web. All the use
cases above that you mention would seem to apply. 

I think perhaps you're over simplifying some of the steps however.  Your
DNS+URL example still assumes some piece of software outside of the DNS
has to resolve the URL down to a piece of likely non-static XML that
gets returned.  That's exactly what the handle system is trying to do.  

I suppose there's some value in XRD vis its use in OAuth and OpenID. I
just don't want to see a viable option (the handle service) discarded
without a look to see how it might apply.

> The main reason for Handles to exist is that a document may "move." 
> However, that "move" only matters if the domain of that object can't 
> move with you. With modern DNS, that's basically a non-problem. Either 
> put up a sub-domain for your coroprate, organization or vanity domain, 
> or outsource it to someone who will stay around. Handle providers must 
> also stay around, and given that the business is much smaller than the 
> DNS business, the longevity of a handle provider is rather less assured 
> IMO...

I'm not at all convinced that your DNS example is a non-problem.
Companies merge all the time and how name spaces migrate or merge is a
real problem. 

Mike

> Sincerely,
> 
> jw
> 
> 
> 
> 


From jwatte@gmail.com  Mon Jul  6 11:40:33 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 CE88F3A6BE0 for <mmox@core3.amsl.com>; Mon,  6 Jul 2009 11:40:33 -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 p0gnfQjFpWyJ for <mmox@core3.amsl.com>; Mon,  6 Jul 2009 11:40:32 -0700 (PDT)
Received: from mail-px0-f175.google.com (mail-px0-f175.google.com [209.85.216.175]) by core3.amsl.com (Postfix) with ESMTP id E478C3A6D2B for <mmox@ietf.org>; Mon,  6 Jul 2009 11:40:32 -0700 (PDT)
Received: by pxi5 with SMTP id 5so137106pxi.29 for <mmox@ietf.org>; Mon, 06 Jul 2009 11:39:06 -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=afU4FgvXF4tCgwAmg5F+rnFcv1yxqzgFox8LyrgQadA=; b=tUbbYIEwsy49DIF++jgSLehQtDNYTZyhNc68DtZ087QGfGvvCtU1Q9QRha1LPt3O68 zIPYxEVZlLX6Bdghcgwl5Jb/+0RDH4I6jbnpF2sRiNYcl+6khyJszjt/+D555hAhgj5v Ip500Qc01dYrWkl9JDymsf5AA+DhNjyYXRtEI=
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=OoaHcu3lqx1/KxvZ5Ks7YEWUVNxjz0P+aE/Wd3+hhNvhVpFKYleOB7j4+usVYwJwLU C1racUjGeNXfz62hs5ObAxT45rGwHGoM0AnpISvQDWWyaSxptvN9yn/AMRJe9Q2XPjUq DXZz65OCkq3+8TEribhWxTlCML+oacZFq0X/w=
Received: by 10.140.134.15 with SMTP id h15mr1551840rvd.146.1246903947593; Mon, 06 Jul 2009 11:12:27 -0700 (PDT)
Received: from ?10.10.111.233? (smtp.forterrainc.com [208.64.184.34]) by mx.google.com with ESMTPS id g31sm342813rvb.11.2009.07.06.11.12.25 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 06 Jul 2009 11:12:26 -0700 (PDT)
Message-ID: <4A523E8A.8000400@gmail.com>
Date: Mon, 06 Jul 2009 11:12:26 -0700
From: Jon Watte <jwatte@gmail.com>
User-Agent: Thunderbird 2.0.0.22 (Windows/20090605)
MIME-Version: 1.0
To: mike.dickson@hp.com
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>	 <c7bcbd620906210956l1a05fb81xb3dea005c902a564@mail.gmail.com>	 <ad15b9430907040531j18caf370y2a9b400ace86394a@mail.gmail.com>	 <1246813317.4532.48.camel@mdickson-laptop> <4A50E7C9.1090208@bbiw.net>	 <1246820675.4532.55.camel@mdickson-laptop> <4A511DF9.9000508@gmail.com> <1246833222.4532.83.camel@mdickson-laptop>
In-Reply-To: <1246833222.4532.83.camel@mdickson-laptop>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "mmox@ietf.org" <mmox@ietf.org>, Dave CROCKER <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: Mon, 06 Jul 2009 18:40:33 -0000

Mike Dickson wrote:
> I'm not at all convinced that your DNS example is a non-problem.
> Companies merge all the time and how name spaces migrate or merge is a
> real problem. 
>   

My question to you is: Do you think that it is a technical problem to 
keep a DNS domain alive, if there were an incentive to do so? My 
assertion is that it isn't. Thus, if you structure your URL well 
(typically use a custom DNS for all your asset URLs) then they can 
survive for as long as you want them to.

http://assets.jonwattesvirtualworldserver.net/uuid/abf3-dd4c-baadf00d-123456789abcdef0

Assuming I want to pay the $10/year for 
"jonwattesvirtualworldserver.net" then this will survive forever.

Admittedly, my main concern with the handle system is not technical, but 
the fact that it costs $100 to get started, and then $50/year, which is 
5x-10x more than it costs with a DNS based solution (both solutions need 
additional web hosting, too).

Sincerely,

jw





-- 

  Revenge is the most pointless and damaging of human desires.


From dhc2@dcrocker.net  Mon Jul  6 13:16:07 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 B3F7B3A6D3F for <mmox@core3.amsl.com>; Mon,  6 Jul 2009 13:16:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.442
X-Spam-Level: 
X-Spam-Status: No, score=-2.442 tagged_above=-999 required=5 tests=[AWL=-0.157, BAYES_00=-2.599, SARE_MILLIONSOF=0.315]
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 OqeV5o2Ht1aL for <mmox@core3.amsl.com>; Mon,  6 Jul 2009 13:16:06 -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 DB09F3A68A2 for <mmox@ietf.org>; Mon,  6 Jul 2009 13:16:05 -0700 (PDT)
Received: from [127.0.0.1] (ppp-68-120-199-146.dsl.pltn13.pacbell.net [68.120.199.146]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id n66KGJDZ024860 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 6 Jul 2009 13:16:25 -0700
Message-ID: <4A525B95.4000007@dcrocker.net>
Date: Mon, 06 Jul 2009 13:16:21 -0700
From: Dave CROCKER <dhc2@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Thunderbird 2.0.0.22 (Windows/20090605)
MIME-Version: 1.0
To: mike.dickson@hp.com
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>	 <c7bcbd620906210956l1a05fb81xb3dea005c902a564@mail.gmail.com>	 <ad15b9430907040531j18caf370y2a9b400ace86394a@mail.gmail.com> <1246813317.4532.48.camel@mdickson-laptop>
In-Reply-To: <1246813317.4532.48.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]); Mon, 06 Jul 2009 13:16:25 -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: Mon, 06 Jul 2009 20:16:07 -0000

Mike Dickson wrote:
> I like the handle system because its been around for a while, proven to
> scale reasonably well, etc.  


So, the metric I use for scaling, when talking about Internet standards, is many
millions of independent users and at least many thousands of independent
administrations, all participating in the same system.

In other words, a single integrated service that is operated by a very large
number of independent groups and that is used by a couple of orders of magnitude
more of independent groups and people.

I know there are large handle systems, but I don't know of any that satisfy
these criteria.  (By "don't know" I am asking to be educated; I truly don't know
that much about the range of installations for handle.)

For a system that does not already satisfy this requirement, the burden is to
explain why the world should believe that the system will be able to.  And
again, I mean that as a serious request, not an implied criticism or dismissal.

d/
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From cs@comlounge.net  Mon Jul  6 14:31:04 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 A350F3A6C9F for <mmox@core3.amsl.com>; Mon,  6 Jul 2009 14:31:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.26
X-Spam-Level: 
X-Spam-Status: No, score=-0.26 tagged_above=-999 required=5 tests=[AWL=1.739,  BAYES_00=-2.599, J_CHICKENPOX_36=0.6]
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 XDBWX6UCtCZp for <mmox@core3.amsl.com>; Mon,  6 Jul 2009 14:31:03 -0700 (PDT)
Received: from post.comlounge.net (post.comlounge.net [85.214.59.142]) by core3.amsl.com (Postfix) with ESMTP id 2B88C3A68A3 for <mmox@ietf.org>; Mon,  6 Jul 2009 14:31:02 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by post.comlounge.net (Postfix) with ESMTP id 5FDFD1CE030D; Mon,  6 Jul 2009 23:30:53 +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 u-os5xkxhSXF; Mon,  6 Jul 2009 23:30:52 +0200 (CEST)
Received: from [192.168.2.113] (p5B3D6B1D.dip.t-dialin.net [91.61.107.29]) by post.comlounge.net (Postfix) with ESMTP id BC1E11CE01C8; Mon,  6 Jul 2009 23:30:51 +0200 (CEST)
Message-ID: <4A526D09.6000701@comlounge.net>
Date: Mon, 06 Jul 2009 23:30:49 +0200
From: Christian Scholz <cs@comlounge.net>
User-Agent: Thunderbird 2.0.0.22 (Windows/20090605)
MIME-Version: 1.0
To: Jon Watte <jwatte@gmail.com>
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>		<c7bcbd620906210956l1a05fb81xb3dea005c902a564@mail.gmail.com>		<ad15b9430907040531j18caf370y2a9b400ace86394a@mail.gmail.com>		<1246813317.4532.48.camel@mdickson-laptop>	<4A50E7C9.1090208@bbiw.net>		<1246820675.4532.55.camel@mdickson-laptop>	<4A511DF9.9000508@gmail.com>	<1246833222.4532.83.camel@mdickson-laptop> <4A523E8A.8000400@gmail.com>
In-Reply-To: <4A523E8A.8000400@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Cc: "mmox@ietf.org" <mmox@ietf.org>, Dave CROCKER <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: Mon, 06 Jul 2009 21:31:04 -0000

Jon Watte schrieb:
> Mike Dickson wrote:
>> I'm not at all convinced that your DNS example is a non-problem.
>> Companies merge all the time and how name spaces migrate or merge is a
>> real problem.   
> 
> My question to you is: Do you think that it is a technical problem to 
> keep a DNS domain alive, if there were an incentive to do so? My 
> assertion is that it isn't. Thus, if you structure your URL well 
> (typically use a custom DNS for all your asset URLs) then they can 
> survive for as long as you want them to.
> 
> http://assets.jonwattesvirtualworldserver.net/uuid/abf3-dd4c-baadf00d-123456789abcdef0 

I think here there is also the general topic of data portability which 
is important. If I own some stuff I might want to take it with me which 
might mean to change URLs. As long as an asset is always copied into a 
context IMHO there shouldn't be a problem with URLs.

Now it is a policy decision if you always copy it or just use it by 
reference (which IMHO makes no difference in non-copyability btw) but if 
you use the latter you already have that problem on the web today. On 
social networks though more stuff seems to be copied (or actually 
re-uploaded all the time) so even if the first place you put it goes 
down the others still have it (and you yourself should be able to copy 
your own stuff around as you wish to anyway).

> Assuming I want to pay the $10/year for 
> "jonwattesvirtualworldserver.net" then this will survive forever.
> 
> Admittedly, my main concern with the handle system is not technical, but 
> the fact that it costs $100 to get started, and then $50/year, which is 
> 5x-10x more than it costs with a DNS based solution (both solutions need 
> additional web hosting, too).

I agree here. As long as this is not a free service it won't get 
traction and we actually see this with XRI. Besides that you'd need to 
explain all this to people and too many levels of indirection are not 
too easy to understand in general.

The question IMHO is if we need to care today if they will be popular 
tomorrow as long they are URIs. Then it should be easily replaceable 
without even changing any specs.

-- 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 tommi.s.e.laukkanen@gmail.com  Mon Jul  6 22:46:44 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 CDF303A6C47 for <mmox@core3.amsl.com>; Mon,  6 Jul 2009 22:46:44 -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 mJ+ZrhnqxbWS for <mmox@core3.amsl.com>; Mon,  6 Jul 2009 22:46:44 -0700 (PDT)
Received: from mail-fx0-f218.google.com (mail-fx0-f218.google.com [209.85.220.218]) by core3.amsl.com (Postfix) with ESMTP id D88753A69FE for <mmox@ietf.org>; Mon,  6 Jul 2009 22:46:43 -0700 (PDT)
Received: by fxm18 with SMTP id 18so4634874fxm.37 for <mmox@ietf.org>; Mon, 06 Jul 2009 22:45:39 -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=azuRW5RiAjFHCrWTWlv5sfimyQ3LrwEMc1Wfde2/l0w=; b=bxpGsmpDgkUXNjgBcPlDLDVYj02czbei87dcWceitccyPSF/3xMNUUqUYhgdFMjjcg su6mmTLwmBXz8OYE9BcDZWh6okf6n1UFc2tH/aAnsBsvtnoo+H0+XcAV0dGmDKNSW6dE uOlUQWuVtywt/zsTIL5W46qY0NTrKNQhv+q2Y=
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=oDQp2qTS73OuE8N0xyqIkDKErbJo83dItfDOa6eb9n3CCkclcYeT22XgtgrD5QsLGk Ayq/LWaa7oyh1WfBBxCnlposswSdgDX41qmpFLBkRwoYrmibErG6XkAKTZXBT+tqs1tt PR6olueSkkNyA539d8Xhktf2oPw/e4/hLtJsU=
MIME-Version: 1.0
Received: by 10.204.51.210 with SMTP id e18mr5386993bkg.69.1246945537901; Mon,  06 Jul 2009 22:45:37 -0700 (PDT)
In-Reply-To: <4A526D09.6000701@comlounge.net>
References: <ad15b9430906190018g6e585f0ei8fc83c073056a7bd@mail.gmail.com> <c7bcbd620906210956l1a05fb81xb3dea005c902a564@mail.gmail.com> <ad15b9430907040531j18caf370y2a9b400ace86394a@mail.gmail.com> <1246813317.4532.48.camel@mdickson-laptop> <4A50E7C9.1090208@bbiw.net> <1246820675.4532.55.camel@mdickson-laptop> <4A511DF9.9000508@gmail.com> <1246833222.4532.83.camel@mdickson-laptop> <4A523E8A.8000400@gmail.com> <4A526D09.6000701@comlounge.net>
Date: Tue, 7 Jul 2009 08:45:37 +0300
Message-ID: <ad15b9430907062245g768c0e2y1438bd4425489dbb@mail.gmail.com>
From: Tommi Laukkanen <tommi.s.e.laukkanen@gmail.com>
To: Christian Scholz <cs@comlounge.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "mmox@ietf.org" <mmox@ietf.org>, Jon Watte <jwatte@gmail.com>, Dave CROCKER <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: Tue, 07 Jul 2009 05:46:44 -0000

To my understanding Handle Systems main problem is how costly it is to
scale it to accommodate all objects in global metaverse which could be
several order of magnitudes more than DNS system needs to support
currently.Handle System could also be too centralized in business
sense giving monopoly like status for the body governing it.

DNS based solution like XRI on the other hand has the problem of
building identifiers with information content. If this information
changes say, the object is sold to company XYZ from company ABC, then
the company ABC then has to agree to host the identity of the object
they sold as long as needed. This could be worked a round by creating
specific identify provider service domains so that the domain name
would not reflect ownership but just the identity provider.

-tommi

From jwatte@gmail.com  Tue Jul  7 09:25:03 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 76EA228C4EC for <mmox@core3.amsl.com>; Tue,  7 Jul 2009 09:25:03 -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 F-RAZ749Y1ij for <mmox@core3.amsl.com>; Tue,  7 Jul 2009 09:25:02 -0700 (PDT)
Received: from mail-px0-f175.google.com (mail-px0-f175.google.com [209.85.216.175]) by core3.amsl.com (Postfix) with ESMTP id 6CF0328C4E0 for <mmox@ietf.org>; Tue,  7 Jul 2009 09:23:56 -0700 (PDT)
Received: by pxi5 with SMTP id 5so753506pxi.29 for <mmox@ietf.org>; Tue, 07 Jul 2009 09:23:37 -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=YiRs84dJosWbHvfCrqvPgr3hR3xdkilpjNhF9wZrDK0=; b=aFrBz0Oa4Dxcm7RCLiX0xbqqueAg+FlXSNknd/CC+JJDH/UpgmyZ4v4m7BRkrCUNP7 i0v7foCSnxYa6mXeSH6cX9gPoLYFzaGt1RAXmf8V4cnBSmjzuyKZcYL8VmiMI+xxpeWb QJh+/WcqTgUkh5iXXy33LhZ5V2XmZ9fCYB7eM=
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=G9EvoylVNXTARChwm1z9fFJkr/V4+c0D6M32inrIs9owsribfwgQ1fk63jinNk7bWL QAUmFQ2mE1YT9fltjHBYcwf4tktd8fz+poW3zfyW08RjiZ3JdArt3dh3s6d7JLgWw1uH qrcI59QLfLvs0iRbwdc1pZzMSDqjO3N3FpVGk=
Received: by 10.140.187.10 with SMTP id k10mr2499683rvf.23.1246983817067; Tue, 07 Jul 2009 09:23:37 -0700 (PDT)
Received: from ?10.10.111.233? (smtp.forterrainc.com [208.64.184.34]) by mx.google.com with ESMTPS id g31sm4888772rvb.41.2009.07.07.09.23.35 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 07 Jul 2009 09:23:36 -0700 (PDT)
Message-ID: <4A537687.2050304@gmail.com>
Date: Tue, 07 Jul 2009 09:23:35 -0700
From: Jon Watte <jwatte@gmail.com>
User-Agent: Thunderbird 2.0.0.22 (Windows/20090605)
MIME-Version: 1.0
To: Tommi Laukkanen <tommi.s.e.laukkanen@gmail.com>
References: <ad15b9430906190018g6e585f0ei8fc83c073056a7bd@mail.gmail.com>	 <c7bcbd620906210956l1a05fb81xb3dea005c902a564@mail.gmail.com>	 <ad15b9430907040531j18caf370y2a9b400ace86394a@mail.gmail.com>	 <1246813317.4532.48.camel@mdickson-laptop> <4A50E7C9.1090208@bbiw.net>	 <1246820675.4532.55.camel@mdickson-laptop>	 <4A511DF9.9000508@gmail.com>	 <1246833222.4532.83.camel@mdickson-laptop>	 <4A523E8A.8000400@gmail.com> <4A526D09.6000701@comlounge.net> <ad15b9430907062245g768c0e2y1438bd4425489dbb@mail.gmail.com>
In-Reply-To: <ad15b9430907062245g768c0e2y1438bd4425489dbb@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "mmox@ietf.org" <mmox@ietf.org>, Dave CROCKER <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: Tue, 07 Jul 2009 16:25:03 -0000

Tommi Laukkanen wrote:
> they sold as long as needed. This could be worked a round by creating
> specific identify provider service domains so that the domain name
> would not reflect ownership but just the identity provider.
>   

... Which is more or less what the Handle system does ...
And round and round we go :-)

Sincerely,

jw




-- 

  Revenge is the most pointless and damaging of human desires.


From mike.dickson@hp.com  Tue Jul  7 09:38:21 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 7F56E28C4C4 for <mmox@core3.amsl.com>; Tue,  7 Jul 2009 09:38:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.504
X-Spam-Level: 
X-Spam-Status: No, score=-106.504 tagged_above=-999 required=5 tests=[AWL=0.095, 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 pFmNhQspiorE for <mmox@core3.amsl.com>; Tue,  7 Jul 2009 09:38:20 -0700 (PDT)
Received: from g1t0029.austin.hp.com (g1t0029.austin.hp.com [15.216.28.36]) by core3.amsl.com (Postfix) with ESMTP id B3CAC28C4BF for <mmox@ietf.org>; Tue,  7 Jul 2009 09:38:20 -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 g1t0029.austin.hp.com (Postfix) with ESMTPS id AC1A3385F0; Tue,  7 Jul 2009 16:38: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 E52AE10009; Tue,  7 Jul 2009 16:37:59 +0000 (UTC)
From: Mike Dickson <mike.dickson@hp.com>
To: Jon Watte <jwatte@gmail.com>
In-Reply-To: <4A537687.2050304@gmail.com>
References: <ad15b9430906190018g6e585f0ei8fc83c073056a7bd@mail.gmail.com> <c7bcbd620906210956l1a05fb81xb3dea005c902a564@mail.gmail.com> <ad15b9430907040531j18caf370y2a9b400ace86394a@mail.gmail.com> <1246813317.4532.48.camel@mdickson-laptop>	<4A50E7C9.1090208@bbiw.net> <1246820675.4532.55.camel@mdickson-laptop>		<4A511DF9.9000508@gmail.com> <1246833222.4532.83.camel@mdickson-laptop>		<4A523E8A.8000400@gmail.com> <4A526D09.6000701@comlounge.net> <ad15b9430907062245g768c0e2y1438bd4425489dbb@mail.gmail.com> <4A537687.2050304@gmail.com>
Content-Type: text/plain
Organization: Bladesystems Infrastructure R&D
Date: Tue, 07 Jul 2009 11:37:48 -0500
Message-Id: <1246984668.4532.118.camel@mdickson-laptop>
Mime-Version: 1.0
X-Mailer: Evolution 2.26.1 
Content-Transfer-Encoding: 7bit
Cc: "mmox@ietf.org" <mmox@ietf.org>, Dave CROCKER <dcrocker@bbiw.net>
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: Tue, 07 Jul 2009 16:38:21 -0000

On Tue, 2009-07-07 at 16:23 +0000, Jon Watte wrote:
> Tommi Laukkanen wrote:
> > they sold as long as needed. This could be worked a round by creating
> > specific identify provider service domains so that the domain name
> > would not reflect ownership but just the identity provider.
> >   
> 
> ... Which is more or less what the Handle system does ...
> And round and round we go :-)

Indeed :-)

It seems to me the key issue is one of requirements.  If you believe
that global asset identifiers require stable ids that are persistent
over time, then you'll likely lean to handles or inventing something
similar.  That extra capability has costs associated with it, however
it's achieved.

I personally think the stable id thing is important.  One reason that
haven't seen discussed is the ability to support different sorts of
access to the data being referenced.  If I'm a content developer I may
want a way to know that an object is an original versus a copy. That is,
since you can provide some control over how assets in the handle repo
get updated you can insure to some degree that the handle references the
real thing and not a copy someone made.  There are other ways to insure
that of course (watermarks, etc).  It's a use case though that I think
needs to be explored when deciding what mechanism to use to refer to
assets.

Mike



From tommi.s.e.laukkanen@gmail.com  Fri Jul 10 22:37:57 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 13FFC3A672F for <mmox@core3.amsl.com>; Fri, 10 Jul 2009 22:37:57 -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=[AWL=0.000,  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 Z0jghOuiJw6u for <mmox@core3.amsl.com>; Fri, 10 Jul 2009 22:37:56 -0700 (PDT)
Received: from mail-bw0-f212.google.com (mail-bw0-f212.google.com [209.85.218.212]) by core3.amsl.com (Postfix) with ESMTP id 1AD503A63EB for <mmox@ietf.org>; Fri, 10 Jul 2009 22:37:55 -0700 (PDT)
Received: by bwz8 with SMTP id 8so54885bwz.37 for <mmox@ietf.org>; Fri, 10 Jul 2009 22:38: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:content-type :content-transfer-encoding; bh=rLLidJVFE3GBuJZwG+V63pUN4tAcx0TvmuBkDzYKxU8=; b=esGku4vMD3bESMykrIxsbkvpSafACmDlHDp+vNz/VINAixRctC5zbJlgNIWTrezNdR D26HmBcgsMSkcVDcRt+dnkr7VqBFIV6OEy1O09A8WaP9yrcfA/fTiwlME1Wdhp5MCzkG QuvTOrhBwnH08tgxB17/Hn27VE4ds1ETdSA4s=
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 :content-type:content-transfer-encoding; b=rnjfauXZU6BLanQWByKX5TVDeiWCgxkCFHUxoxFFHSOYZMLd5BcTDMhMfRrEDkumv1 StTyCYWTM/kRGRz+uUtHbBWV5FhlpqPK36prr99mEoN2uUPnN8whLn9diw5MUz7PDXp0 HSn92PBf1J2+/jE/LOaqAdVgNgna0yFIbXV3s=
MIME-Version: 1.0
Received: by 10.204.57.138 with SMTP id c10mr2645991bkh.56.1247290701759; Fri,  10 Jul 2009 22:38:21 -0700 (PDT)
In-Reply-To: <1246984668.4532.118.camel@mdickson-laptop>
References: <ad15b9430906190018g6e585f0ei8fc83c073056a7bd@mail.gmail.com> <4A50E7C9.1090208@bbiw.net> <1246820675.4532.55.camel@mdickson-laptop> <4A511DF9.9000508@gmail.com> <1246833222.4532.83.camel@mdickson-laptop> <4A523E8A.8000400@gmail.com> <4A526D09.6000701@comlounge.net> <ad15b9430907062245g768c0e2y1438bd4425489dbb@mail.gmail.com> <4A537687.2050304@gmail.com> <1246984668.4532.118.camel@mdickson-laptop>
Date: Sat, 11 Jul 2009 08:38:21 +0300
Message-ID: <ad15b9430907102238v4808949fq50ac6e687033dee6@mail.gmail.com>
From: Tommi Laukkanen <tommi.s.e.laukkanen@gmail.com>
To: "mmox@ietf.org" <mmox@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
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, 11 Jul 2009 05:37:57 -0000

What would be the procedure to write down a summary of topics
discussed like this global identification issue. Is there a wiki page
somewhere for this list or should we work on a document. Where would
this document be stored then? Can we arrange polls or votes to get
clear picture how opinions are divided?

regards,
Tommi Laukkanen
