Re: [urn] LEI namespace registration request

[Peter Saint-Andre <[e-mail]>]

Thanks, I can work with this and will proceed with IANA today.

On 12/21/21 12:27 AM, Ivan Marin wrote:
> Hi Peter,
> Find attached a text version as requested.
> 
> Let as you if this is enough for moving it forward in the process, please.
> 
> Thanks again for your support.
> 
> 
> *Ivan Marin*
> GLEIF Business Development
> . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . .
> Global Legal Entity IdentifierFoundation (GLEIF)
> Bleichstrasse 59, 60313, Frankfurtam Main, Germany
> Work Phone: [phone]
> Cell phone: [phone]
> Email: [e-mail] <mailto:[e-mail]>
> 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 20 Dec 2021, at 19:54, Peter Saint-Andre <[e-mail] 
>> <mailto:[e-mail]>> wrote:
>>
>> On 12/20/21 2:01 AM, Ivan Marin wrote:
>>> Thanks Peter for your comments.
>>> I have added suggested modifications:
>>> - amended the title to: "Namespace Identifier:  LEI"
>>> - urn:LEI:foo is equivalent to urn:lei:foo ... as the "LEI" name is 
>>> not case sensitive.
>>> - As is correct, I keep the template titles for easier reference in 
>>> further reviews.
>>> Find version 7 attached.
>>> Following your statement: "Everything else looks fine to me and I can 
>>> work with IANA to add this NID to the registry."
>>> We understand that you push it through the IANA registration process.
>>
>> Yes, this is my responsibility because I am the team lead for the 
>> expert reviewers.
>>
>>> Which dates can we expect for its final release or publication?
>>
>> Although I'm not sure about the end-of-year schedule at IANA, I would 
>> say we can update the registry in the next few weeks (perhaps sooner).
>>
>>> Let us know please if further actions are needed on our side at this 
>>> stage to make it happen.
>>
>> If you could send me a plaintext (non-PDF) version that would be 
>> great, because this is the format that we post at the registry (click 
>> on any of the "template" links):
>>
>> https://www.iana.org/assignments/urn-namespaces/urn-namespaces.xhtml 
>> <https://www.iana.org/assignments/urn-namespaces/urn-namespaces.xhtml>
>>
>> Thanks!
>>
>> Peter
>>
>>> Thanks for your support.
>>> Regards,
>>> Ivan Marin
>>> GLEIF Business Development
>>>    On 17/12/21, 21:47, "Peter Saint-Andre" <[e-mail] 
>>> <mailto:[e-mail]>> wrote:
>>>     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 
>>> <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: [phone]
>>>     > Cell phone: [phone]
>>>     > Email: [e-mail] <mailto:[e-mail]> 
>>> <mailto:[e-mail] <mailto:[e-mail]>>
>>>     > Web: www.gleif.org <http://www.gleif.org> <http://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 <[e-mail] 
>>> <mailto:[e-mail]>
>>>     >> <mailto:[e-mail] <mailto:[e-mail]>>> 
>>> 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>
>>>     >> 
>>> <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" <[e-mail] 
>>> <mailto:[e-mail]>
>>>     >> <mailto:[e-mail] <mailto:[e-mail]>>> 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
>>>     >[e-mail] <mailto:[e-mail]>
>>>     >https://www.ietf.org/mailman/listinfo/urn 
>>> <https://www.ietf.org/mailman/listinfo/urn>
>