Re: Internet-draft for URN NID "name"

Keith Moore <moore@cs.utk.edu> Fri, 19 January 2007 18:55 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1H7yu2-0001Ec-0F; Fri, 19 Jan 2007 13:55:54 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1H7yu1-0001EW-99 for urn-nid@apps.ietf.org; Fri, 19 Jan 2007 13:55:53 -0500
Received: from shu.cs.utk.edu ([160.36.56.39]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H7yu0-0002jq-2P for urn-nid@apps.ietf.org; Fri, 19 Jan 2007 13:55:53 -0500
Received: from localhost (localhost [127.0.0.1]) by shu.cs.utk.edu (Postfix) with ESMTP id 702155645D; Fri, 19 Jan 2007 13:55:51 -0500 (EST)
X-Virus-Scanned: by amavisd-new with ClamAV and SpamAssasin at cs.utk.edu
Received: from shu.cs.utk.edu ([127.0.0.1]) by localhost (shu.cs.utk.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7Bel9bv1Sbnp; Fri, 19 Jan 2007 13:55:42 -0500 (EST)
Received: from [192.168.0.4] (user-119b1dm.biz.mindspring.com [66.149.133.182]) by shu.cs.utk.edu (Postfix) with ESMTP id 0552756476; Fri, 19 Jan 2007 13:55:41 -0500 (EST)
Message-ID: <45B1142F.6070101@cs.utk.edu>
Date: Fri, 19 Jan 2007 13:55:43 -0500
From: Keith Moore <moore@cs.utk.edu>
User-Agent: Thunderbird 1.5.0.9 (Macintosh/20061207)
MIME-Version: 1.0
To: KSHam <ksham.nid@emgns.com>
References: <1166678183.15752.ksham.nid@emgns.com>
In-Reply-To: <1166678183.15752.ksham.nid@emgns.com>
Content-Type: text/plain; charset="EUC-KR"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Cc: urn-nid@apps.ietf.org
Subject: Re: Internet-draft for URN NID "name"
X-BeenThere: urn-nid@apps.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: discussion of new namespace identifiers for URNs <urn-nid.apps.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/urn-nid>, <mailto:urn-nid-request@apps.ietf.org?subject=unsubscribe>
List-Post: <mailto:urn-nid@apps.ietf.org>
List-Help: <mailto:urn-nid-request@apps.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/urn-nid>, <mailto:urn-nid-request@apps.ietf.org?subject=subscribe>
Errors-To: urn-nid-bounces@apps.ietf.org

this is a really bad idea in so many ways.

"name" is a confusing NID as it means nothing.  all URNs are names.

attempting to use human-readable strings as URNs makes naming conflicts
inevitable and invites disputes over ownership of those strings, both
within the resolution system and between those names and trademarks.  for
that reason alone it is very unlikely that the binding between a name: URN
and its resource will be able to be stable.

expecting clients to automatically insert disambiguating information such
as a country code will produce surprising and inconsistent results from one
user or client to another.  it hardly matters that the URN itself is
unambiguous
if the user interface is expected to create an inconsistency.  on the
Internet,
the notion of country is fairly arbitrary - is it the nationality of the
user (and
if he has multiple nationalities, which one?), the location of the user's
computer (shall it use GPS to determine this?), the location of the user's
PoP with his ISP, the nationality of the owner of the computer, what?

bottom line: this is exactly what URNs were not intended to be.  this
proposal should be denied with extreme prejudice.