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

Peter Saint-Andre <stpeter@stpeter.im> Tue, 03 May 2022 15:30 UTC

Return-Path: <stpeter@stpeter.im>
X-Original-To: urn@ietfa.amsl.com
Delivered-To: urn@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2AC6BC1595FF for <urn@ietfa.amsl.com>; Tue, 3 May 2022 08:30:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.957
X-Spam-Level:
X-Spam-Status: No, score=-3.957 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-1.857, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=stpeter.im header.b=oJ0Y4FmS; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=tPG5xsd0
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GxnugdRcDNgA for <urn@ietfa.amsl.com>; Tue, 3 May 2022 08:30:03 -0700 (PDT)
Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com [64.147.123.25]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 409B5C1595FB for <urn@ietf.org>; Tue, 3 May 2022 08:30:03 -0700 (PDT)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id E7C5332002E2; Tue, 3 May 2022 11:29:59 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Tue, 03 May 2022 11:30:00 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=stpeter.im; h=cc :cc:content-transfer-encoding:content-type:date:date:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to; s=fm2; t=1651591799; x= 1651678199; bh=VQ0/6C5Pv942c3To6APSCp8HpGwdyse/qgyXxwKmSmA=; b=o J0Y4FmSunIad416mfSlPKliNIRcoo/LP8XzmmrIe7Gnmld+JLdVgpLe+gqkD9sDV 4rSDnMIu1tjPr+bmm/2ferzvV4+EHtP3SzJYoey5sbOu90RcMvrHYg/HDsaxKgbb 5O6MuDKNaakQG4ueWCzKKCTraparcU9ul00ORtfHz5Ni4j6mDVyQrGydyN9xbygV RRlaoho3JCZczWhuPMBsP49X1ecH8omck4BqywZewjOFhJezCXn9neMFIcmxH+fy wK9msEJc2adCfiIyiuzUhfH5FQk+u4YCsvidxVYDl5T/oLhUBfbp3DzKpzSK4Exo R1SL064crn7/W+g0ow4Tw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:date:date:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; t=1651591799; x=1651678199; bh=VQ0/6C5Pv942c 3To6APSCp8HpGwdyse/qgyXxwKmSmA=; b=tPG5xsd0PjlsICP/maBPXo9hxRr1N 2OTTydFY7TJvLk5cBwAXRaTL2ui4bFksXCdnaNgjxrrs8aS/5Id30ViCypH6m1Jo ts1cOkjXyLrtWQLfHEzoMQKi7Ci2FOjHOuH8vSmRBPgYBRhg9PAq9Qha7NuDXWrO JE2B4Ft22sWMaTCfD5mOnXfI6dREisniArEKGfb2FFMCmi0aZd+ZA4mbJMO29Aye 0YULGGSm/RP0BjhbVC8zupv4EL0dZFmlSKvqGJHrwCpfeWFjj3gLRURf256wPiNv 1ycNlgpHOs6PsEsU4HKDtUq45z0R3uFVOPh2heKmDj/GXF9dHosE347VQ==
X-ME-Sender: <xms:dkpxYnYQBrhUIap0GLmyaNqYPpD8Pu9tnOmA3XlAqlbxsytFxKJ8eQ> <xme:dkpxYmYiHZZJxlZStjTUNTJLWJ1aldynYar12ZqpDEIPON7trrj7uKmHAXUBQJaMc t0PBV197YLTFuywlQ>
X-ME-Received: <xmr:dkpxYp-htzjUcfu_YuoqoYZvoe67lC6bfRIgKnQ3qoz3ocUcZRFRij5YFhHv>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedrvdejgdeltdcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefkffggfgfvvehfhffujggtgfesthejredttdefjeenucfhrhhomheprfgvthgv rhcuufgrihhnthdqtehnughrvgcuoehsthhpvghtvghrsehsthhpvghtvghrrdhimheqne cuggftrfgrthhtvghrnhepiefgudekfeekffethffhuddvffetvedvheehkeevjefhfeej ffdtkeehgfeludeunecuffhomhgrihhnpehivghtfhdrohhrghenucevlhhushhtvghruf hiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehsthhpvghtvghrsehsthhpvght vghrrdhimh
X-ME-Proxy: <xmx:dkpxYtoW3EYAlX5tlkqsq1U6Obbzj57ANpK5LUvCigacNvzS67JRlw> <xmx:dkpxYipbeUG8cFqv2lY-T7glexL_vjpn9gwvFSMt0qkZPApU9AHwgA> <xmx:dkpxYjQpMuAqc2PJY81dFXRuzwwkcZNQUrV2tQcvsjOQurPjJoGWIg> <xmx:d0pxYp3jINDoUSNBELFdMN1JI4BXrouYl_UmdQAizMr-FWUebqd3zw>
Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue, 3 May 2022 11:29:58 -0400 (EDT)
Message-ID: <9c4012cb-f17b-b3aa-1d48-d8cdf90d509f@stpeter.im>
Date: Tue, 03 May 2022 09:29:57 -0600
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.8.1
Content-Language: en-US
To: "Dale R. Worley" <worley@ariadne.com>, urn@ietf.org
Cc: Enrico Francesconi <francesconi@ittig.cnr.it>
References: <87k111l46s.fsf@hobgoblin.ariadne.com>
From: Peter Saint-Andre <stpeter@stpeter.im>
In-Reply-To: <87k111l46s.fsf@hobgoblin.ariadne.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/urn/CAvuIjYzc-pl0TLOjzhlQ0YDtKM>
Subject: Re: [urn] What is holding up the LEX URN namespace registration?
X-BeenThere: urn@ietf.org
X-Mailman-Version: 2.1.34
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, 03 May 2022 15:30:08 -0000

[ Old thread alert! ]

Please accept my apologies - I thought we had already processed this 
request.

I will move forward on this with IANA.

Separately, I understand that the authors of draft-spinosa-urn-lex-15 
would like to publish it as an RFC through the Independent Submissions 
stream, so I will follow up on that, too.

Peter

On 5/24/20 9:53 AM, Dale R. Worley wrote:
> "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
> 2018:
> 
>      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,
>              barryleiba@computer.org
> 
>      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
>      IANA?
> 
> 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
>      Director.
>      [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:
> <https://mailarchive.ietf.org/arch/msg/urn/g8eC8QR6Lv1jmtgDT-yCApCvUIQ>
> <https://mailarchive.ietf.org/arch/msg/urn/6_hLnPj9pXjM3cV-qSPGY_xkCy4>
> 
> 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
> 
>      Alexey,
> 
>      Can you get us (urn@ietf.org) an update on the processing of
>      draft-spinosa-urn-lex?
> 
>      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?
> 
> Dale
> 
> _______________________________________________
> urn mailing list
> urn@ietf.org
> https://www.ietf.org/mailman/listinfo/urn