Re: future of identifiers

Patrik Fältström <> Tue, 29 October 2013 16:30 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id E1A4E21E809E for <>; Tue, 29 Oct 2013 09:30:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.3
X-Spam-Status: No, score=-2.3 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, NO_RELAYS=-0.001]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id DuLBYknDtoX9 for <>; Tue, 29 Oct 2013 09:30:46 -0700 (PDT)
Received: from ( [IPv6:2a02:80:3ffe::176]) by (Postfix) with ESMTP id 5EC9011E81B9 for <>; Tue, 29 Oct 2013 09:30:46 -0700 (PDT)
Received: from (unknown [IPv6:2001:13c7:7003:89:412b:1f27:b2f8:c2e4]) by (Postfix) with ESMTPSA id C8EB41FEA9; Tue, 29 Oct 2013 17:30:43 +0100 (CET)
Content-Type: multipart/signed; boundary="Apple-Mail=_8838B33F-0D9B-48E8-A369-DD733B944368"; protocol="application/pgp-signature"; micalg="pgp-sha1"
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1816\))
Subject: Re: future of identifiers
From: Patrik Fältström <>
In-Reply-To: <>
Date: Tue, 29 Oct 2013 12:30:36 -0400
Message-Id: <>
References: <> <> <> <>
To: Eliot Lear <>
X-Mailer: Apple Mail (2.1816)
Cc: Paul Hoffman <>, " Discussion" <>
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 29 Oct 2013 16:30:47 -0000

On 29 okt 2013, at 12:23, Eliot Lear <> wrote:

> On 10/29/13 5:16 PM, Paul Hoffman wrote:
>> On Oct 29, 2013, at 9:03 AM, Patrik Fältström <> wrote:
>>> I think it is important to not restart discussions already held regarding different requirements on identifiers, requirements that in turn lead to various alternatives on how they are allocated, managed and resolved. I do not think one can have one identifier that fits all. Instead multiple kind of identifiers are needed. Because of requirements on uniqueness (absolute, low risk of collisions or not needed at all), persistence, human readable/understandable, whether allocation and resolution should be designed for read (lookups) or write (allocation), what the identifier is to be used for (see id/loc discussions).
>> Having sat through many of those discussions with Patrik 15 years ago: +1
> And having chaired NSRG, + 1/2.  That is- it's always fair to look at
> new developments, but let's at least be aware of what was covered by
> others and build on their success (or avoid their failures).

Just to make my point clear. I absolutely do believe more thinking is needed. What was done 15 years ago never finished. I claim partly because we did not know the answers to all questions.

My only point is that I think it would be sad to restart the discussion from zero. We both good and bad experience if we look back in history. We made mistakes then, but we also have successes. I here talk about URI-related discussions, whois++ (etc), Dublin Core, OID and what not.

Same with the 10+(?) years of ID/Loc split discussions. Lots and lots of experience. 

And of course the experience enterprises like Facebook, Twitter etc have from their what I would call private namespaces.