Re: [urn] URN expert review of 'etsi' NID

[Mahesh Jethanandani <[e-mail]>]

Hi Peter,

> On Jun 7, 2018, at 1:22 PM, Peter Saint-Andre <[e-mail]> wrote:
> 
> Upon review, I noticed a few things:
> 
> 1. The registration request uses the old template from RFC 3406, not the
> new template from RFC 8141. IANA requires new registrations to use the
> new template.

I will update the draft with the template information that is new in RFC 8141.

> 
> 2. Can you provide a slightly more detailed description of the kinds of
> resources these URNs will identify?

I have added a Purpose section to the draft that reads as:

Purpose:
The URN requested in this document will be used by ETSI for allocation of namespaces to be used by YANG modules, to begin with, that are developed by the organization. These namespaces are globally unique. The URN will be used in public networks by devices used to configure and manage resources in the network. It is these devices that will enforce the  uniqueness of the namespaces by using the namespace and the XPath associated with the managed node in the network, when accessing a resource.

Does this answer your question?

> 
> 3. Can you provide a slightly more detailed description of the syntax
> within the NSS?

Let me work with my co-author to provide you a more detailed description of the syntax of NSS. It is currently under a password protected web site, but the idea is to make it public once we have finalized the syntax.

Thanks.

> 
> Other reviewers might notice additional issues...
> 
> Peter
> 
> On 6/7/18 10:58 AM, Peter Saint-Andre wrote:
>> Hello Expert Reviewers & others,
>> 
>> I just noticed that draft-mahesh-etsi-urn requests a URN NID for 'etsi'
>> to identify resources published by European Telecommunications Standards
>> Institute:
>> 
>> https://datatracker.ietf.org/doc/draft-mahesh-etsi-urn/
>> 
>> Although it's not clear which IESG telechat this is on (the responsible
>> AD, Ignas Bagdonas, can tell us), let's make sure to review it in a
>> timely fashion.
>> 
>> Thanks!
>> 
>> Peter
>> 
> 

Mahesh Jethanandani
[e-mail]