IETF Logo Mail Archive

Re: [mmox] Global Object Identification

Jon Watte <jwatte@gmail.com> Mon, 06 July 2009 18:40 UTC

Return-Path: <jwatte@gmail.com>
X-Original-To: mmox@core3.amsl.com
Delivered-To: mmox@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 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.

v2.23.0 | Report a Bug | By Email