Re: [urn] Formal request for URN for ITU

[Scott Mansfield <[e-mail]>]

Please see inline (marked with <scott></scott>)

Thanks,
-scott.

-----Original Message-----
From: Dale R. Worley <[e-mail]> 
Sent: Monday, July 02, 2018 11:09 PM
To: Scott Mansfield <[e-mail]>
Cc: [e-mail]
Subject: Re: [urn] Formal request for URN for ITU

Scott Mansfield <[e-mail]> writes:
> This is a request from International Telecommunication Union (ITU) for 
> a namespace.
>
> Please review and provide comments/revisions to ensure clarity and 
> focus of the request.  The format of the request is in ID format 
> capturing the information requested from Appendix A of RFC 8141.

The registration looks generally good to me.  Some questions are:

   Abstract

   This document describes the Namespace Identifier (NID) 'itu' for
   Uniform Resource Names (URNs) used to identify resources published by
   the ITU (International Telecommunication Union).

The word "published" is used in the Abstract but nowhere else.  All of the example URNs seem to name either publications or abstract resources described in publications.  But some thought should be given to whether "published" is more restrictive that you want to commit to, and if you want to keep the word, it would probably be better to incorporate it into section 2.5 ("Purpose").

<scott>
I'm not sure I understand how 'published' is overly restrictive.  I want what the itu puts under the itu NID to be limited to resources published by the itu (not by other groups).
</scott>

Section 2.5 describes the purpose of this namespace entirely in terms of Yang module names.  But it seems likely to me that other purposes will be found for ITU URNs, and it would be wise to allow the ITU to define URNs for other types of resources.

<scott>
Section 2.5 says "including those used in YANG modules", that indicates that identifiers can be used for other things.  YANG is the example here because that will be the first use of this namespace.
</scott>

This document is referenced four times:

   [4]        ITU, "ITU URN Management", 2017, <http://www.itu.int/en/
              ITU-T/Documents/ITU-URN-Management.pdf>.

This document is an Informative Reference, so the namespace registration supersedes it, but it would be wise to edit "ITU URN Management" and the registration to be compatible.  In particular:

(1) The registration states:

       The ITU process is found in the ITU URN Management [4] document.

Although [4] describes the syntax and semantics of URNs, it doesn't seem to describe any organizational processes.

(2) The document contains two syntax specifications that omit colons between components that seem to be intended:

    urn:itu:t:rec:{ITU-T-RecommendationNumber}{ITU-T-RecommendationSpecificString}

    {ITU-T-RecommendationType}{ITU-T-RecommendationTypeIdentifier}

<scott>
This is good feedback.  I will get the ITU to fix the syntax errors and also add a paragraph about how the ITU General Secretariat has given the ITU-T TSB the role of coordinating with the rest of ITU to manage the assignments.
</scott>

Dale