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

Enrico Francesconi <> Mon, 04 June 2018 20:46 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id E3D05130DC0 for <>; Mon, 4 Jun 2018 13:46:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.102
X-Spam-Status: No, score=-2.102 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.248, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-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 VsHcDjJusNDE for <>; Mon, 4 Jun 2018 13:46:41 -0700 (PDT)
Received: from ( [IPv6:2a00:1450:400c:c09::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 14E46130DE2 for <>; Mon, 4 Jun 2018 13:46:41 -0700 (PDT)
Received: by with SMTP id v131-v6so871355wma.1 for <>; Mon, 04 Jun 2018 13:46:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=sender:mime-version:subject:from:in-reply-to:date:cc:message-id :references:to; bh=A9S3dPdPYY7iePONzhmAe/W/2qi26Jtlv4L9c6KkOj8=; b=QhtICdv6axYjI0CS1RwiKxo3y3/O/btDE9Ep0vASihD8uHmA9H4lyYmI80LXez2Llg mMbht2J2qb7xMKOQBg5pIgLyd22yxUwM0wTte7qYpiO827JCAUtqKa/VRYPmlsFc/xjX 1P17TZSHBWM6RB4bRF6grG+SQR0H5q6DGK3SC+M0hUP2SotwN4u9HnQ8DkLxDSiBDTeW vmys4RnShxBFNky5x2ra6WcwYzL9mRXu3nG8FPc2Pq1/lt+g+B+AvR0X+oif8jGd2IGD Aw9abi44RxHk73oNlBSS0iV+VT81By3q+afaLGJIFszbVbb8HoJr/mqwi0M7RYOdWLNg +4Vw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:sender:mime-version:subject:from:in-reply-to :date:cc:message-id:references:to; bh=A9S3dPdPYY7iePONzhmAe/W/2qi26Jtlv4L9c6KkOj8=; b=bn7PERqBSVkHkUuTW8L8YLRehIeH7/+aJMM4n011KLgUtllpdPCtVxqCxhG5C3Gpw9 AzxfseplQpBMiF1wAjcJWVgBNwBodI05G8GOIqbRgE8yTUSm7LEhyHTzShiA93jePdcN CFnoynwJguCZSqzXh8HHgcE8wDgJu//1whJYlmtYMCX38wsOOTbyY4QDzgaiHk1oJRL3 MoEHeAuDnBLDMdegyFfRWi9V1P3q2jj1kS/mJDM1kgq1GR8VI0wEFjClRdJZ3GebIT9i SAxA/4HTJeigEjzsdgZlddann3f0MKd7sgDnPe9I20WsMWmSN6ggtIzTrYDVNOdLai7S zCgw==
X-Gm-Message-State: ALKqPwdriLNdgIVq97dzKT1TZhLdNM4VpXrxDqPcuOOSagdPL2XOveC/ mlHwJv6pOhNDm/OSs9DexOw=
X-Google-Smtp-Source: ADUXVKLHAzL3+vLjs1Zv5WDLgzHnw2zfRyV3kOTvSdlVRRqFzE4SIti+y4nQNeWvT8f2Q8o6i2Y2uw==
X-Received: by 2002:a50:9176:: with SMTP id f51-v6mr25834797eda.29.1528145199412; Mon, 04 Jun 2018 13:46:39 -0700 (PDT)
Received: from ( []) by with ESMTPSA id q22-v6sm424694edd.69.2018. (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Mon, 04 Jun 2018 13:46:38 -0700 (PDT)
Sender: Enrico Francesconi <>
Content-Type: multipart/alternative; boundary="Apple-Mail=_D54EB501-EDF6-4FEB-AB16-ED37D3A57F0C"
Mime-Version: 1.0 (Mac OS X Mail 9.0 \(3094\))
From: Enrico Francesconi <>
In-Reply-To: <>
Date: Mon, 4 Jun 2018 22:46:35 +0200
Cc: Pierluigi Spinosa <>, LUPO Caterina <>,, Alexey Melnikov <>, Barry Leiba <>, Peter Saint-Andre <>,,, "Hakala, Juha E" <>
Message-Id: <>
References: <>
To: "Dale R. Worley" <>
X-Mailer: Apple Mail (2.3094)
Archived-At: <>
X-Mailman-Approved-At: Mon, 04 Jun 2018 14:23:21 -0700
Subject: Re: [urn] Moving ahead with draft-spinosa-urn-lex
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: Revisions to URN RFCs <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 04 Jun 2018 20:46:45 -0000

Dear Dale,
   thanks for your message and to the colleagues who approved your proposal to move ahead with urn-lex registration. 

As for the issue you raised about the maintenance of the registry of jurisdiction codes, we agree at this stage to be ITTIG-CNR the
Registrar. In this respect we propose the following changes:

Section 3.1

"However, a special register for the <jurisdiction-code>, maintained
by IANA, is required, the rules of which are defined in section 11.2."
"However, a special register for the <jurisdiction-code> is required,
the rules of which are defined in section 11.2."


Section 11.2

"IANA is requested to create a new registry for <jurisdiction-code>,
with the following format:"
"It is requested to create a new registry for <jurisdiction-code>,
with the following format:"


" <>"; "United Nations"; "DPI, United Nations, <address>, <contact>"; [reference]
" <>"; "United Nations"; "DPI, United Nations, <address>, <contact>"; [reference]
In the current experimental LEX registration phase, ITTIG-CNR will take care to create and maintain the registry for <jurisdiction-code>.
As the criteria of the LEX names assignment will be consolidated, after the experimental phase such registry will be maintained by
The adopted registration policy is compliant with the "Expert Review" as specified in [RFC8126].
Designated Expert(s) will assign jurisdiction codes based on the following principles: "

If you think that such changes are sufficient, we are going to produce
the draft v. 13 and upload it in the ietf versioning service.

Best regards
   Pierluigi and Enrico

Enrico Francesconi
Institute of Legal Information Theory and Techniques
Italian National Research Council

Via de' Barucci 20
50127 Florence

Tel: +39-055-4399-665
Fax: +39-055-4399-605

> On 01 mag 2018, at 02:38, Dale R. Worley <> wrote:
> 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
> namespace.
> 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
> policies.
> Following this path requires only small changes for -13, viz., updating
> section 11.2.
> Dale
> ----------------------------------------------------------------------
> Archived discussions:
> 16 Nov 2017
> "urn:lex draft v. 12"
> starting 20 Sep 2017
> "Request for new URN namespace review: LEX"
> Message-Id: <>
> starting 29 Apr 2014
> "Publication request for draft-spinosa-urn-lex"
> Message-Id: <>
> starting 27 Mar 2013
> "Application for a formal URN NID"
> Message-Id: <23A64284-6B03-4B24-B680-54A61E96BECA at>
> 15 Oct 2009
> "URN LEX Namespace submission"