Re: [urn] LEI namespace registration request

Peter Saint-Andre <stpeter@mozilla.com> Fri, 17 December 2021 20:47 UTC

Return-Path: <stpeter@mozilla.com>
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 A39323A043E for <urn@ietfa.amsl.com>; Fri, 17 Dec 2021 12:47:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.951
X-Spam-Level:
X-Spam-Status: No, score=-3.951 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.852, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=mozilla.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L-xCJrlRrG_f for <urn@ietfa.amsl.com>; Fri, 17 Dec 2021 12:47:47 -0800 (PST)
Received: from mail-io1-xd36.google.com (mail-io1-xd36.google.com [IPv6:2607:f8b0:4864:20::d36]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A48313A0773 for <urn@ietf.org>; Fri, 17 Dec 2021 12:47:45 -0800 (PST)
Received: by mail-io1-xd36.google.com with SMTP id b187so4681074iof.11 for <urn@ietf.org>; Fri, 17 Dec 2021 12:47:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mozilla.com; s=google; h=message-id:date:mime-version:user-agent:subject:content-language:to :cc:references:from:in-reply-to:content-transfer-encoding; bh=rmJLzImlytrPExt8eht6kx0GzflY/IuVvs41abKBgpM=; b=Rsp3POklUKF7Ve6NwWzDKdl6Fl8VSLXtFGqog//Eb0WNU29hJi2MJFGWEiagNCzut0 8Aa44+ttkmr7NDgVpbj0OA+IXG8pWIHbNdcEKWnyqI85k1ELJzAF3fC7v/caIKY8hTU7 WnB3TyFABmc1k6YHsnyaPkRXwi0w+GlaFsin4=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent:subject :content-language:to:cc:references:from:in-reply-to :content-transfer-encoding; bh=rmJLzImlytrPExt8eht6kx0GzflY/IuVvs41abKBgpM=; b=zpPZeSh4HSSJoweEbXefSTIFVWx0xHqNHEUVEvzG+BCmOhpRCN0W2UP7KIiErmMZG6 Y7DrJNtW85+/WviguBD82xhkn3IDRiHsfSx/rn6XOqhcNJqBxt6/oh5mMa2m4lXFuBrB vusc565G1IyOkUuISC1Hx0Jnm/OT4oApuwngQiCnMLhkvsMrYPJY+YCpSLDRqFl7lBXO v21RhDwhGZKMTwZNerlSA8q4QudKPn5PAjxH3gABziY78CqZ57HJlwCkRcRaOCBi7kZg phW+t3qcvr3cOOPWnIW1wFtFCBRnE5KW+3o5iWPrjJTsMyKV7ywwNJnb6KMQuZ8Lun40 qgjQ==
X-Gm-Message-State: AOAM5327kvbB+sn8lrgz4CVKlqBBGA/H5wM7FWJuZrV33tAmjU2yDpOb A1KrkDSRpRcb64kj31OY6Nckvw==
X-Google-Smtp-Source: ABdhPJwu5r/OhcRdYeJdbYDrZDKLRG75mob9fWF7q+N1avOpO9a70xiiqiRSh1EYB287DAMz8a2JFg==
X-Received: by 2002:a5e:c807:: with SMTP id y7mr2625179iol.9.1639774063339; Fri, 17 Dec 2021 12:47:43 -0800 (PST)
Received: from [192.168.1.13] (c-76-25-154-156.hsd1.co.comcast.net. [76.25.154.156]) by smtp.gmail.com with ESMTPSA id f10sm4893345iob.7.2021.12.17.12.47.42 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 17 Dec 2021 12:47:42 -0800 (PST)
Message-ID: <791297b2-9b25-b52e-bbc9-20947aba125b@mozilla.com>
Date: Fri, 17 Dec 2021 13:47:41 -0700
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.4.0
Content-Language: en-US
To: Ivan Marin <Ivan.Marin@Gleif.org>, "urn@ietf.org" <urn@ietf.org>
Cc: Christoph Schneider <Christoph.Schneider@Gleif.org>, Karla Mckenna <Karla.Mckenna@Gleif.org>, Clare Rowley <Clare.Rowley@Gleif.org>, "Dale R. Worley" <worley@ariadne.com>
References: <522D804F-BC40-4BC2-8CAD-A7A96B1C86B3@gleif.org> <87h7er7th4.fsf@hobgoblin.ariadne.com> <31CD9E68-CF53-46AD-85A0-16367069EB89@gleif.org> <D68EE112-CCE1-4297-9B18-4D753260DED4@gleif.org>
From: Peter Saint-Andre <stpeter@mozilla.com>
In-Reply-To: <D68EE112-CCE1-4297-9B18-4D753260DED4@gleif.org>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/urn/CjXAcNfXdY40IbboMtAJ2aQRxNg>
Subject: Re: [urn] LEI namespace registration request
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: Fri, 17 Dec 2021 20:47:53 -0000

Hi Ivan,

Thanks for your work on this and your patience with the review team.

Here are a few small suggestions regarding your request.

"Namespace Identifier:  Requested of IANA (formal)"

Presumably this should be:

"Namespace Identifier:  LEI"

We can probably shorten the "Purpose" section but it's fine as is 
(although let's remove the questions/guidance copied over from the 
template itself).

With regard to the syntax and equivalence, urn:LEI:foo should be 
equivalent to urn:lei:foo and in general we have not specified that the 
Namespace Identifier is uppercase (e.g., "LEI") with past registrations:

https://www.iana.org/assignments/urn-namespaces/urn-namespaces.xhtml

Everything else looks fine to me and I can work with IANA to add this 
NID to the registry.

Peter

On 9/21/21 2:21 AM, Ivan Marin wrote:
> Hi,
> 
> we have generated a new version attached adding some more information of 
> the existing LEI system (which we are asking the namespace registration 
> for) that is mature and providing already service world wide.
> 
> Let us know please if you need further information and what else is 
> needed from our side to get the namespace released.
> 
> Thanks,
> 
> *Ivan Marin*
> GLEIF Business Development
> . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . .
> Global Legal Entity IdentifierFoundation (GLEIF)
> Bleichstrasse 59, 60313, Frankfurtam Main, Germany
> Work Phone: +49 69 9074999-22
> Cell phone: +34 670 246 255
> Email: Ivan.Marin@gleif.org <mailto:Ivan.Marin@gleif.org>
> Web: www.gleif.org <http://www.gleif.org>
> 
> 
> . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . .
> Global Legal Entity IdentifierFoundation (GLEIF)
> St. Alban-Vorstadt 5, PO Box,4002 Basel, Switzerland
> Chairman of the Board: StevenJoachim
> CEO: Stephan Wolf
> Commercial-Register-No.: CHE-200.595.965
> LEI: 506700GE1G29325QX363
> 
> This message may containconfidential and/or privilegedinformation. If 
> you are not theintended recipient or if you havereceived this message in 
> error,please notify the sender anddelete this message. Anyunauthorised 
> copying, disclosureor distribution of this message is strictly forbidden.
> 
>> On 13 Sep 2021, at 10:01, Ivan Marin <Ivan.Marin@Gleif.org 
>> <mailto:Ivan.Marin@Gleif.org>> wrote:
>>
>> Thanks for your feedback Mr. Worley.
>>
>> Besides the document shared, you can also find all the information 
>> regarding LEI here: 
>> https://www.gleif.org/en/about-lei/introducing-the-legal-entity-identifier-lei 
>> <https://www.gleif.org/en/about-lei/introducing-the-legal-entity-identifier-lei>
>>
>> Indeed as you have stated the LEI system is already well-developed and 
>> standardized and all the LEI namespace registration provides is a 
>> systematic way of mapping existing LEIs into URNs.
>>
>> We are willing to read your revised version. Let us know any question 
>> you may have.
>>
>> Regards,
>> Ivan Marin
>> GLEIF Business Development
>>
>>
>>
>> On 11/9/21, 04:10, "Dale R. Worley" <worley@ariadne.com 
>> <mailto:worley@ariadne.com>> wrote:
>>
>>    Please consider revising your descriptions to emphasize certain points
>>    which I only fully grasped as I had nearly finished reading the
>>    document.
>>
>>    When I started reading the document, I was unaware of the system of 
>> LEIs
>>    that already exists, and so without thinking I assumed that all of what
>>    you describe is a proposed system.  Instead, the LEI system is already
>>    well-developed and standardized and all the LEI namespace registration
>>    provides is a systematic way of mapping existing LEIs into URNs.
>>
>>    I suspect that this misunderstanding is due to minor matters of 
>> wording,
>>    combined with the fact that I was reading the registration quite
>>    quickly.  But as you prepare a revised version please consider my
>>    mistake.
>>
>>    Dale
>>
>>
> 
> 
> _______________________________________________
> urn mailing list
> urn@ietf.org
> https://www.ietf.org/mailman/listinfo/urn