Re: [mmox] Global Object Identification

Mike Dickson <mike.dickson@hp.com> Sun, 21 June 2009 16:29 UTC

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