Re: [ogpx] Unique identities (was: Names, Identity and Protocol elements)

Joshua Bell <josh@lindenlab.com> Mon, 22 March 2010 02:54 UTC

Return-Path: <josh@lindenlab.com>
X-Original-To: ogpx@core3.amsl.com
Delivered-To: ogpx@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B90883A677E for <ogpx@core3.amsl.com>; Sun, 21 Mar 2010 19:54:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.432
X-Spam-Level:
X-Spam-Status: No, score=0.432 tagged_above=-999 required=5 tests=[AWL=-1.322, BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001]
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 DQZ+EpU9pJtS for <ogpx@core3.amsl.com>; Sun, 21 Mar 2010 19:54:15 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by core3.amsl.com (Postfix) with ESMTP id 76CA43A6860 for <ogpx@ietf.org>; Sun, 21 Mar 2010 19:54:14 -0700 (PDT)
Received: by wyb29 with SMTP id 29so2292004wyb.31 for <ogpx@ietf.org>; Sun, 21 Mar 2010 19:54:27 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.216.160.213 with SMTP id u63mr1961980wek.128.1269226467673; Sun, 21 Mar 2010 19:54:27 -0700 (PDT)
In-Reply-To: <e0b04bba1003201935v5d3db2e8y48831f65a9663d7b@mail.gmail.com>
References: <20100320133911.GA9372@alinoe.com> <e0b04bba1003201935v5d3db2e8y48831f65a9663d7b@mail.gmail.com>
Date: Sun, 21 Mar 2010 19:54:27 -0700
Message-ID: <f72742de1003211954u4c9d15e1xb271e7737846dc5a@mail.gmail.com>
From: Joshua Bell <josh@lindenlab.com>
To: ogpx <ogpx@ietf.org>
Content-Type: multipart/alternative; boundary="0016e6541b04bec7de04825ad0e7"
Subject: Re: [ogpx] Unique identities (was: Names, Identity and Protocol elements)
X-BeenThere: ogpx@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Virtual World Region Agent Protocol - IETF working group <ogpx.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ogpx>, <mailto:ogpx-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ogpx>
List-Post: <mailto:ogpx@ietf.org>
List-Help: <mailto:ogpx-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ogpx>, <mailto:ogpx-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Mar 2010 02:54:15 -0000

On Sat, Mar 20, 2010 at 7:35 PM, Morgaine <morgaine.dinova@googlemail.com>wrote:

> Note however that you don't need to chisel bits off UUIDs in order to tag
> them with provider information.  Do it cleanly, by leaving the UUIDs safe
> and untouched as full 128-bit entities as they are supposed to be, but
> associate them with a separate unique provider field.  After all, there is
> no need for single-field atomicity nor the whole unique identity fitting
> into 128 bits.  Cramming the 2-part information into 128 bits is premature
> optimization, and is actually unhelpful since the provider field should be
> separable.
>

Further, the protocol would ideally be reasonably opaque about the contents,
much as email addresses are a constrained form of WHATEVER@DOMAIN and HTTP
URLs are a constrained form of http://DOMAIN/WHATEVER - it's up to the
authority (the domain) to decide whether it's using autoincrementing row
numbers, UUIDs, human readable names, punycode, etc.

I probably said this last year, but I'm a fan of using URLs whenever
possible. This lets us avoid defining a new global registry for these
Authorities - we already have one (i.e. DNS).

This also avoids having the protocol dictate implementation details to
service providers. And I'm a REALLY big fan of that.

Joshua