Re: [urn] Registration request for urn:eris: namespace Fri, 29 September 2023 02:28 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 6C46DC1516E1 for <>; Thu, 28 Sep 2023 19:28:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -5.993
X-Spam-Status: No, score=-5.993 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_SOFTFAIL=0.665, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id pUROq79CjqKy for <>; Thu, 28 Sep 2023 19:28:41 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 9F058C15155F for <>; Thu, 28 Sep 2023 19:28:41 -0700 (PDT)
Received: from ([]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 256/256 bits) (Client did not present a certificate) by with ESMTP id m2hRqnKCeNFoGm3DEqR0Jr; Fri, 29 Sep 2023 02:26:40 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20211018a; t=1695954400; bh=vR0nNgmyU650VoPV4hUd7frkeRcCVfDVtqSXH88Hypk=; h=Received:Received:Received:Received:From:To:Subject:Date: Message-ID:Xfinity-Spam-Result; b=tSpTRSAC8PQPXt0dtbf5BwvyUYrqMHTysTGcQ1iE4X2kGs63PqhmNV6RpDAoGC0tC ZGsPXz42JOCE71IZalePFTUTKhmGAtzc/WN+3wQxaPlTGBZRLIYICa6qX8sBs+wop4 WvL1Btvm6l8zx8BzEVoTa/r4tddPNsYK8sFRMdfB5rwv+QgGDYmgki+jANxeLkVnzp th0vlQgk22CAR9IsG1kwngId9pwYqLV22lJ399lVNMS46RwVDJF58HHS9wPuXt7w9D 5Hq+FXKiy7qcujkdbHuge7ARDKnFji9LVdxmMNn1cvcFOvx8iMHNqH54ZwduNkxq3O ExnIKM4/MONCw==
Received: from ([IPv6:2601:192:4a00:430::a771]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 256/256 bits) (Client did not present a certificate) by with ESMTPA id m3Cpqyybxj5nMm3CqqPDeu; Fri, 29 Sep 2023 02:26:18 +0000
Received: from (localhost []) by (8.16.1/8.16.1) with ESMTPS id 38T2QEcO2067088 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NOT); Thu, 28 Sep 2023 22:26:14 -0400
Received: (from worley@localhost) by (8.16.1/8.16.1/Submit) id 38T2QEww2067085; Thu, 28 Sep 2023 22:26:14 -0400
X-Authentication-Warning: worley set sender to using -f
To: Endo Renberg <>
In-Reply-To: <1695889031.zxsvg3ofky.astroid@garbage.none> (
Date: Thu, 28 Sep 2023 22:26:14 -0400
Message-ID: <>
Archived-At: <>
Subject: Re: [urn] Registration request for urn:eris: namespace
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Revisions to URN RFCs <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 29 Sep 2023 02:28:45 -0000

My problem is that I have a continuing unease about the proposed
namespace.  Probably the best summary I can make is that the proposed
identifiers don't qualify as *names*.

Due to the large amount of entropy in the NSSs, an identifier that was
created for one unit of information can never be mistakenly used to
identify another unit of information even in another system.  But once
you are outside of a particular Eris system they are not only unusable,
but an individual identifier carries no discernible information.  About
all you can tell is that the local Eris system does not contain any
resource with that identifier, either because the identifier is from
another Eris system or because the local resource it identifies was
deleted.  This lack of any global significance strikes me as a
fundamental contradiction with the concept of a global namespace.

A concrete consequence of this is that you'd never expect to see a
urn:eris in a location where any other type of URI might appear, and
vice-versa.  Their only use is as input to processes which can only
handle Eris identifiers because they only have meaning within contexts
that are Eris universes.

One solution to this is to add some sort of "Eris system" identification
field to the URN.  E.g., instead of this (which is my interpretation of
the example in 2.7.1)



where is a DNS name that somehow identifies the Eris
universe involved.  That approach allows straightforward differentiation
of references to the local Eris universe vs. references to other Eris
universes.  If some sort of protocol is assumed, it even becomes a URL.