[urn] Moving ahead with draft-spinosa-urn-lex

worley@ariadne.com (Dale R. Worley) Tue, 01 May 2018 00:39 UTC

Return-Path: <worley@alum.mit.edu>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 7A30912DA21 for <urn@ietfa.amsl.com>; Mon, 30 Apr 2018 17:39:06 -0700 (PDT)
X-Quarantine-ID: <uAJQRZCvEbRe>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "To"
X-Spam-Flag: NO
X-Spam-Score: -1.684
X-Spam-Status: No, score=-1.684 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id uAJQRZCvEbRe for <urn@ietfa.amsl.com>; Mon, 30 Apr 2018 17:39:04 -0700 (PDT)
Received: from resqmta-ch2-12v.sys.comcast.net (resqmta-ch2-12v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:44]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BB11212DA18 for <urn@ietf.org>; Mon, 30 Apr 2018 17:39:04 -0700 (PDT)
Received: from resomta-ch2-19v.sys.comcast.net ([]) by resqmta-ch2-12v.sys.comcast.net with ESMTP id DJAEfV5gVwmrZDJJvfrTNE; Tue, 01 May 2018 00:39:03 +0000
Received: from hobgoblin.ariadne.com ([IPv6:2601:192:4603:9471:222:fbff:fe91:d396]) by resomta-ch2-19v.sys.comcast.net with ESMTPA id DJJpfMMHl3rorDJJpfNyKd; Tue, 01 May 2018 00:39:00 +0000
Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com []) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id w410ctfp029169; Mon, 30 Apr 2018 20:38:56 -0400
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id w410cqD9029152; Mon, 30 Apr 2018 20:38:52 -0400
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com (Dale R. Worley)
To: pierluigi.spinosa@gmail.com, enrico.francesconi@ittig.cnr.it, caterina.lupo@gmail.com
To: urn@ietf.org
Cc: Alexey Melnikov <aamelnikov@fastmail.fm>, Barry Leiba <barryleiba@computer.org>
Cc: Peter Saint-Andre <stpeter@stpeter.im>
Cc: john-ietf@jck.com, L.Svensson@dnb.de, juha.hakala@helsinki.fi
In-Reply-To: <72446a5a-ec31-cc7e-d00a-11029ed941b3@stpeter.im>
Sender: worley@ariadne.com (Dale R. Worley)
Date: Mon, 30 Apr 2018 20:38:52 -0400
Message-ID: <87a7tk6wgz.fsf@hobgoblin.ariadne.com>
X-CMAE-Envelope: MS4wfHlzIZLErR9CYme6LJXYgvmjYTQvNy2KEIJomV2q0nHuSKHGx8BEiZDyekiqYJSaxjrR2UBzkr21qrc1mES4pj8og17+R6YhDpxQxMc/Zbf4kof/mTHK g8cHipYKLFopne1wSQbBWEmH7ERrASYsluCHg4JCOY3fEqpGL0x2WdRrNuxbETs/44qAUZ1UbY1RgPs8w30P1fkj84csrnPAOJObd+oFUqrLKNF6cvnW5CBX Fxj/rkj63iAE3BDMW8Omb8EA8ou9GCWSLXoRfZeTon85bJcv4HHucAYrn5PW2CWWDTBKMnBBSu0xAM84D3a8iQEB+bt3fcBN+KyB8DOG3u2wmFz2mYF7pMQP h4Vwdjy0crWMZokHCoF7kYbRs4xB7auQ6NVij68d33fQ3/y8LvaCe1t4GysYrHnoHLMfxhdBK1RXZ0j37xbPmS445thXOd7d9Kdkk8Q2ntKQse7+/EQDP0vS oLlOa8q+iock4Br9O3Q0f12HMLZa1KKaPdPjKlnD09pLpXbyf2qeqOT2HtjR1nmMlHM74BUEKYDgN65Z
Archived-At: <https://mailarchive.ietf.org/arch/msg/urn/9duCwpF1DfNr6yjU3TyZBR8nIBE>
X-Mailman-Approved-At: Mon, 30 Apr 2018 19:24:58 -0700
Subject: [urn] Moving ahead with draft-spinosa-urn-lex
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Revisions to URN RFCs <urn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/urn>, <mailto:urn-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/urn/>
List-Post: <mailto:urn@ietf.org>
List-Help: <mailto:urn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/urn>, <mailto:urn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 May 2018 00:39:06 -0000

My apologies for not working on this earlier.

The current draft of "urn-lex" is draft-spinosa-urn-lex-12.  People have
criticized its proposed URN system in many ways, but it seems to me that
most of the criticisms are "bibliographic", they concern good ways to
create identifiers for written works.  As such, the IETF is not a good
forum for correcting most of those problems.

My proposal is that we implement "rough consensus and running code" --
obtain a usable registration of the "lex" URN namespace so that the
authors and ITTIG can put the "lex" URNs into practice.  The process of
using the URNs will educate the authors regarding the correct resolution
of the various problems, and will likely cause them to later submit a
revised registration.

That is, the registration we create at this time will be understood to
be experimental in nature.

In order to be suitable as an "experimental" registration, there are a
few problems that must be resolved:

1. The URN syntax must conform to the generic URN syntax.

2. The requirements of uniqueness and persistence must be met.  (That
is, any URN designates at most one resource, and the resource that it
designates must not change over time.  However, it is permissible to
have multiple URNs designate the same resource.)

3. The process or authority that assigns each URN must be well-defined.

Item 1 is taken care of, in that the syntax in -12 conforms (as far as I
can tell) to the URN syntax in RFC 8141.

Item 2 is the responsibility of the Jurisdictional Registrars, in the
same way that the naming authorities of many other URN namespaces are
responsible for uniqueness and persistence.

Item 3 requires that a registry of jurisdiction codes and Jurisdictional
Registrars be maintained.  Section 11.2 of the -12 draft proposes that
IANA maintain the registry.  Given the experimental nature of the URN
registration, it seems to me to be premature to involve IANA, especially
since the principles that the Designated Export must implement are
likely to change over time.  Instead, it seems to me that the best
choice for registrar is ITTIG-CNR, the proposer and developer of the URN

When the namespace definition is transitioned to a non-experimental
status (including fixing a good set of policies to assign jurisdiction
codes), the registry can be transferred to IANA to implement the proven

Following this path requires only small changes for -13, viz., updating
section 11.2.

Archived discussions:

16 Nov 2017
"urn:lex draft v. 12"

starting 20 Sep 2017
"Request for new URN namespace review: LEX"
Message-Id: <1505909590.1544977.1112321704.5FEB92F9@webmail.messagingengine.com>

starting 29 Apr 2014
"Publication request for draft-spinosa-urn-lex"
Message-Id: <CALaySJJk5YiCQZqt6WoWkqfAzi2A04HEAH=vG0pVAy8e45N5aQ@mail.gmail.com>

starting 27 Mar 2013
"Application for a formal URN NID"
Message-Id: <23A64284-6B03-4B24-B680-54A61E96BECA at ittig.cnr.it>

15 Oct 2009
"URN LEX Namespace submission"