[urn] What is holding up the LEX URN namespace registration?

worley@ariadne.com Sun, 24 May 2020 15:53 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 BB0413A0AEE for <urn@ietfa.amsl.com>; Sun, 24 May 2020 08:53:53 -0700 (PDT)
X-Quarantine-ID: <FMoOEKjCQ5-j>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "Cc"
X-Spam-Flag: NO
X-Spam-Score: -1.639
X-Spam-Status: No, score=-1.639 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_HELO_NONE=0.001, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcastmailservice.net
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id FMoOEKjCQ5-j for <urn@ietfa.amsl.com>; Sun, 24 May 2020 08:53:52 -0700 (PDT)
Received: from resqmta-ch2-09v.sys.comcast.net (resqmta-ch2-09v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:41]) (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 1BE6E3A0AE5 for <urn@ietf.org>; Sun, 24 May 2020 08:53:51 -0700 (PDT)
Received: from resomta-ch2-04v.sys.comcast.net ([]) by resqmta-ch2-09v.sys.comcast.net with ESMTP id csjwjyiZTQzvbcswgjv7lM; Sun, 24 May 2020 15:53:50 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcastmailservice.net; s=20180828_2048; t=1590335630; bh=zBCl6nDoKvfx7V93nxrcMYrTbb0HHdm9rydUpxPFesI=; h=Received:Received:Received:Received:From:To:Subject:Date: Message-ID; b=AmkEJZV3amLvyjXWQob+WKA6e73Fozsp3c8o3B3UGi63bV14b/hB8E07hPcazMwlb Nb4PDMI18e915BGRTDMpstCF1eZr/YFHdcAP9XSO5cBL/kfrRv7Y/AOuqoTUank5E0 KmqcB/lw4G0BvGJd628+hEK4zzRbC1LZuEXUZOhUgjvva0B/tLyTUxZ7ZijEGDLwXH sT0jJaY/OSSbuY8PkvNQG5Co7bi8LT0u4e4njogWK+lapnJptAAaO5JJPuYv/iP4QC D5mQJZOgVfedq4Voxw7BMgekYJXTlULZNFBNoK2DFmN2dWRVPPZVBBB+2rcIlcQn0T /vqJeGVzFIZsQ==
Received: from hobgoblin.ariadne.com ([IPv6:2601:192:4a00:430:222:fbff:fe91:d396]) by resomta-ch2-04v.sys.comcast.net with ESMTPA id cswejiRsMHgVhcswfjieHK; Sun, 24 May 2020 15:53:50 +0000
X-Xfinity-VMeta: sc=0.00;st=legit
Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com []) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id 04OFrm2C003574; Sun, 24 May 2020 11:53:48 -0400
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id 04OFrldZ003569; Sun, 24 May 2020 11:53:47 -0400
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com
To: urn@ietf.org
Cc: barryleiba@computer.org, Murray Kucherawy <superuser@gmail.com>
Cc: aamelnikov@fastmail.fm
Sender: worley@ariadne.com
Date: Sun, 24 May 2020 11:53:47 -0400
Message-ID: <87k111l46s.fsf@hobgoblin.ariadne.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/urn/x6yC1pipFzVp73P5zY6tLxGJQAo>
Subject: [urn] What is holding up the LEX URN namespace registration?
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.29
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: Sun, 24 May 2020 15:53:54 -0000

"Hakala, Juha E" <juha.hakala@helsinki.fi> writes:
> The status of urn:lex request is unclear to me as well. Version 13 was
> published ages ago
> (https://datatracker.ietf.org/doc/draft-spinosa-urn-lex/) but I don't
> know if it addressed the concerns Dale brought up in an email sent
> April 30 2018. It seemed at that point that we were very close to
> approving the request, so it is unfortunate that the process was
> stalled. We should contact Enrico Francesconi and tell him what he
> needs to do to finish the work. He did ask us the status of the
> process last October, but I don't know if he got an answer.

My latest opinion regarding the urn:lex proposal was approval on 5 June

    From: worley@ariadne.com (Dale R. Worley)
    To: Enrico Francesconi <francesconi@ittig.cnr.it>
    Date: Tue, 05 Jun 2018 22:28:24 -0400
    Archived-At: <https://mailarchive.ietf.org/arch/msg/urn/VpshWLYPcRfqy__xqsH5wz_BO-A>
    Subject: Re: [urn] Moving ahead with draft-spinosa-urn-lex
    Cc: barryleiba@computer.org, aamelnikov@fastmail.fm,
            pierluigi.spinosa@gmail.com, L.Svensson@dnb.de,
            caterina.lupo@gmail.com, urn@ietf.org

    Enrico Francesconi <francesconi@ittig.cnr.it> writes:
    > 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:

    The changes you propose seem satisfactory to me.

I posted this comment on 11 Dec 2018:

    From: worley@ariadne.com (Dale R. Worley)
    To: Enrico Francesconi <francesconi@ittig.cnr.it>
    Date: Tue, 11 Dec 2018 22:13:13 -0500
    Archived-At: <https://mailarchive.ietf.org/arch/msg/urn/71un9dFHWjatiVVsLND0HRKiC8s>
    Subject: Re: [urn] Moving ahead with draft-spinosa-urn-lex
    Cc: urn@ietf.org, pierluigi.spinosa@gmail.com, aamelnikov@fastmail.fm,
            L.Svensson@dnb.de, caterina.lupo@gmail.com, stpeter@stpeter.im,

    Enrico Francesconi <francesconi@ittig.cnr.it> writes:
    > being quite a long time since the last communication (June 2018), we
    > were wondering whether any action from our side is needed before to
    > proceed with the so called "experimental" registration of the URN:LEX
    > namespace.

    Sorry, we've dropped the ball here.  As far as I can tell from reviewing
    the discussion at
    https://www.ietf.org/mail-archive/web/urn/current/maillist.html, we have
    consensus to register the namespace based on draft-spinosa-urn-lex-13,
    but we haven't actually notified IANA of that.  Who is it that notifies

Then there was this message on 12 Dec 2018:

    Subject: Re: [urn] Moving ahead with draft-spinosa-urn-lex
    To: Enrico Francesconi <francesconi@ittig.cnr.it>,
            "Dale R. Worley" <worley@ariadne.com>
    Cc: Alexey Melnikov <aamelnikov@fastmail.fm>,
            Barry Leiba <barryleiba@computer.org>, pierluigi.spinosa@gmail.com,
            L.Svensson@dnb.de, caterina.lupo@gmail.com, urn@ietf.org
    From: Peter Saint-Andre <stpeter@stpeter.im>
    Date: Wed, 12 Dec 2018 07:39:20 -0700

    In my role as URN review team lead, I will contact the IANA.
    [quoted material deleted - DRW]

Followed up by this on the same day:

    To: Enrico Francesconi <francesconi@ittig.cnr.it>,
            "Dale R. Worley" <worley@ariadne.com>
    From: Peter Saint-Andre <stpeter@mozilla.com>
    Date: Wed, 12 Dec 2018 10:30:25 -0700
    Archived-At: <https://mailarchive.ietf.org/arch/msg/urn/z6sx-t9fCVZ5dfCKOEbIrHe6jis>
    Subject: Re: [urn] Moving ahead with draft-spinosa-urn-lex
    Cc: Barry Leiba <barryleiba@computer.org>,
            Alexey Melnikov <aamelnikov@fastmail.fm>, pierluigi.spinosa@gmail.com,
            L.Svensson@dnb.de, caterina.lupo@gmail.com, urn@ietf.org

    Actually, I'll coordinate with Alexey, since he's the sponsoring Area
    [quoted material deleted - DRW]

And then this on 4 Mar 2019:

    To: Enrico Francesconi <francesconi@ittig.cnr.it>
    From: Peter Saint-Andre <stpeter@mozilla.com>
    Date: Mon, 4 Mar 2019 18:41:42 -0700
    Archived-At: <https://mailarchive.ietf.org/arch/msg/urn/2ZNAplit_W8dwQmALHh-8zLR4dk>
    Subject: Re: [urn] Moving ahead with draft-spinosa-urn-lex
    Cc: urn@ietf.org, Alexey Melnikov <aamelnikov@fastmail.fm>,
            LUPO Caterina <caterina.lupo@gmail.com>,
            Pierluigi Spinosa <pierluigi.spinosa@gmail.com>

    As far as I know, this Internet-Draft is intended to be published as an
    informational RFC, in which case the IANA registration would happen
    through normal processes before publication. However, the datatracker
    page indicates that Alexey needs to follow up (specifically it appears
    that he needs to create the writeup for balloting by the IESG).

    Alexey, please let us know if we're mistaken about the next steps for
    this registration.
    [quoted material deleted - DRW]

Then I have record of a few similar messages between the review group
and our AD:

On 17 Oct 2019, I sent this inquiry to our AD:

    From: worley@ariadne.com (Dale R. Worley)
    To: aamelnikov@fastmail.fm
    Date: Thu, 17 Oct 2019 22:00:33 -0400
    Archived-At: <https://mailarchive.ietf.org/arch/msg/urn/AtoVfxYg_b7Ho-RaRGcft0CVWxg>
    Subject: Re: [urn] Moving ahead with draft-spinosa-urn-lex
    Cc: Enrico Francesconi <enrico.francesconi@gmail.com>,
            pierluigi.spinosa@gmail.com, caterina.lupo@gmail.com,
            stpeter@mozilla.com, urn@ietf.org


    Can you get us (urn@ietf.org) an update on the processing of

    As far as I can tell, the URN group has been satisfied with this
    registration/I-D since last December, but its processing has been
    stalled for reasons that are obscure.

    I understand that you are the supervising Area Director of this
    activity, so on behalf of the URN group, I am requesting guidance from
    you as to the next step for completing this work.

After that date, I can find no record of e-mail from our AD, either to
me personally or the URN mailing list.

However, checking with https://datatracker.ietf.org/wg/, I see that
Alexey is no longer an ART AD, which may account for why things have
gone awry.

Who is responsible for the next step?