Re: [mmox] Global Object Identification

Dave CROCKER <dhc2@dcrocker.net> Sun, 21 June 2009 11:31 UTC

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