Re: [urn] TR: URN Registration for UIC

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

Hi all,

The UIC namespace has been added to the registry.

Full disclosure: I made a few editorial tweaks to the completed 
registration template before submitting it to IANA.

Peter

On 6/16/23 3:18 AM, Lars G. Svensson wrote:
> Dear David et al.,
> 
> I approve of your registration.
> 
> Some minor nits:
> * The "syntax" section says "The Namespace Specific String (NSS) of all URNs that use the "uic" NID has the following structure: urn:uic:{UICResource}:{ResourceSpecificString} [...]". This is not entirely correct, since the structure you quote is that of the complete URN. The structure of the NSS is "{UICResource}:{ResourceSpecificString}".
> * I also think it would be helpful if you added some examples and possibly a link to the catalogue of code lists [1]. As Dale has pointed out [2], there are some issues with that page that you might want to have a look at.
> 
> [1] https://osdm.io/spec/catalog-of-code-lists/
> [2] https://mailarchive.ietf.org/arch/msg/urn/kdIkbcj_tispCDB2jkDOi59NXCQ/
> 
> Best,
> 
> Lars
> 
> -----Ursprüngliche Nachricht-----
> Von: urn [mailto:[e-mail]] Im Auftrag von Peter Saint-Andre
> Gesendet: Donnerstag, 8. Juni 2023 00:59
> An: SARFATTI David <[e-mail]>
> Cc: [e-mail]; GANTERT Clemens <[e-mail]>
> Betreff: Re: [urn] TR: URN Registration for UIC
> 
> Hello David & all,
> 
> Because you are not submitting this registration request as an RFC, I would recommend moving some of the information from the "Introduction"
> section of the document into the "Purpose" section of the completed registration template.
> 
> In my opinion it would also be useful to include a few examples of UIC URNs, as well as a link to documentation (if any) on the uic.org website about assignment processes and procedures.
> 
> However, these suggestions are not blockers for me to voice approval for the registration request.
> 
> Lars and Stephanie, do you have feedback as well?
> 
> Peter
> 
> On 6/7/23 6:49 AM, SARFATTI David wrote:
>> Dear Juha, dear all,
>> Please find the form revised by Clemens according to your requirements below.
>> I stay at your disposal for any complementary information, Kind
>> regards, David
>>
>> David SARFATTI
>> Senior Advisor
>> Passenger Department
>> INTERNATIONAL UNION OF RAILWAYS
>> 16 rue Jean Rey - 75015 Paris - FRANCE Mob : [phone]
>>
>>
>> -----Message d'origine-----
>> De : Hakala, Juha E <[e-mail]> Envoyé : mercredi 7 juin
>> 2023 08:24 À : SARFATTI David <[e-mail]>; Peter Saint-Andre
>> <[e-mail]>; Dale R. Worley <[e-mail]>; John Levine
>> <[e-mail]> Cc : [e-mail]; GANTERT Clemens
>> <[e-mail]>
>> Objet : VS: [urn] TR: URN Registration for UIC
>>
>> Hello David; all,
>>
>> the latest version of the template is still based on RFC 3406 (Uniform Resource Namespace Definition Mechanisms). Unfortunately RFC 3406 itself is not marked as obsolete, although the procedure described in it has been replaced by the one outlined in RFC 8141 (which obsoletes both RFC 2141 and 3406).
>>
>> RFC Editor page of RFC 3406 (https://www.rfc-editor.org/info/rfc3406) and RFC 8141 (https://www.rfc-editor.org/rfc/rfc8141) do tell that RFC 3406 is obsolete and therefore it should not be used in namespace registration requests.
>>
>> Since RFC 3406 is obsolete, you should remove from the registration request the description of how formal namespaces are registered from the very beginning of the document. IESG review and publication as an RFC are no longer required for namespace registrations.
>>
>> You should also replace the copy of RFC 3406 Appendix A from the end of your request with Appendix A from RFC 8141. Although these two registration templates are quite similar, RFC 8141 template does require a Security and privacy section, which should "describe any potential issues related to security and privacy with regard to assignment, use, and resolution of names within the URN namespace". See clause 6.4.4 of RFC 8141 for more information.
>>
>> Usually URN namespace registrations are unproblematic from security & privacy point of view. DDI namespace registration (https://datatracker.ietf.org/doc/draft-urn-ddi/05/) may give you some ideas of what kind of information can be provided.
>>
>> Except for adding Security and privacy section, replacing RFC 3406 with RFC 8141 should not have a significant impact on the content of your registration.
>>
>> Best regards,
>>
>> Juha Hakala
>>      
>>
>> -----Alkuperäinen viesti-----
>> Lähettäjä: urn <[e-mail]> Puolesta SARFATTI David
>> Lähetetty: tiistai 6. kesäkuuta 2023 11.10
>> Vastaanottaja: Peter Saint-Andre <[e-mail]>; Dale R. Worley
>> <[e-mail]>; John Levine <[e-mail]>
>> Kopio: [e-mail]; GANTERT Clemens
>> <[e-mail]>
>> Aihe: Re: [urn] TR: URN Registration for UIC
>>
>> Dear Sir,
>> Please find attached the form revised and completed.
>>
>> Please find below answers from our IT expert Clemens Gantert.
>> I stay at your disposal for any complementary information and thank you very much for our UIC URN registration.
>> Best regards,
>> David
>>
>>
>> Should "CGI" be "UIC"?   --> Yes, this should be UIC.
>>
>> You might want to consider providing a "role address" here rather than an individual address as the address should remain valid over a period of many years.
>> --> [e-mail]
>>
>> RFC 2141 has been replaced by RFC 8141, so these references should be
>> updated.  (I don't think that significantly affects your
>> specification.)
>> --> this is a proposal to replace the last paragraph on page 1 (Declaration of structure:)  of the request as the form has changed:
>>
>> Old:
>>         The Namespace Specific String (NSS) of all URNs that use the "uic"
>>         NID has the following structure:
>>
>>         urn:uic:{UICResource}:{ResourceSpecificString}
>>
>>         where the "UICResource" is a US-ASCII string that conforms to the
>>         URN syntax requirements [RFC2141] and defines a specific class of
>>         resource type.  Each resource type has a specific labeling scheme
>>         that is covered by "ResourceSpecificString", which also conforms
>>         to the naming requirements of [RFC2141].
>>
>> RFC 2141 has been replaced by RFC 8141, so these references should be
>> updated.  (I don't think that significantly affects your
>> specification.)
>>
>> I think you want to clarify here that "UICResource" specifies the "resource type", and make clearer the requirements on ResourceSpecificString.  Perhaps:
>>
>> New:
>>         The Namespace Specific String (NSS) of all URNs that use the "uic"
>>         NID has the following structure:
>>
>>         where the "UICResource" is a US-ASCII string that specifies the
>>         resource class and "ResourceSpecificString" specifies the
>>         individual resource, such that the entire string conforms to the
>>         URN syntax requirements [RFC8141].  Each resource type has a
>>         specific labeling scheme for "ResourceSpecificString".
>>
>>
>> -----Message d'origine-----
>> De : Peter Saint-Andre <[e-mail]> Envoyé : samedi 27 mai
>> 2023 14:40 À : Dale R. Worley <[e-mail]>; SARFATTI David
>> <[e-mail]> Cc : [e-mail]; GANTERT Clemens
>> <[e-mail]>
>> Objet : Re: [urn] TR: URN Registration for UIC
>>
>> On 5/24/23 11:45 AM, Dale R. Worley wrote:
>>> SARFATTI David <[e-mail]> writes:
>>>> Please find attached our subscription form to obtain a Uniform
>>>> Resource Name (URN) Namespace for the International Union of
>>>> Railways (UIC).
>>>> I remain at your disposal for any complementary information,
>>>
>>> I approve of your registration,
>>
>> I too think it is reasonable to register this namespace and agree with Dale's comments. Here are additional suggestions...
>>
>> (1) The registration uses the template from RFC 2141. Please use the more modern template (see Appendix A of RFC 8141).
>>
>> (2) When you do so, please pay special attention to the privacy and security considerations.
>>
>> (3) Pointers to relevant documentation on the UIC website would also be helpful.
>>
>> Best Regards,
>>
>> Peter
>>
>>
> 
> _______________________________________________
> urn mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/urn
>