Re: [Netconf] restconf and namespaces and unique module names.

[Xiang Li <[e-mail]>]

Hi
On 9/22/2015 2:03 PM, Juergen Schoenwaelder wrote:
> On Tue, Sep 22, 2015 at 05:25:04PM +0000, Kent Watsen wrote:
>>> RFC 6020:
>>>
>>>    The names of all standard modules and submodules MUST be unique.
>>>    Developers of enterprise modules are RECOMMENDED to choose names for
>>>    their modules that will have a low probability of colliding with
>>>    standard or other enterprise modules, e.g., by using the enterprise
>>>    or organization name as a prefix for the module name.
>>>
>>> Apparently, both module names in the example violate this. Note that
>>> module names are used to resolve imports and hence they better are
>>> unique. For the IETF, we can manage that via the IANA registry. For
>>> the other modules, there is a clear recommendation.
>>
>> OK, that's fair, but it doesn't seem to be a followed often outside of the
>> IETF.
>>
>> For instance,
>>
>>    - ETSI NFV-MANO has module names like "nsd", "vnfd" and "vld"
>>    - Open Config has module names beginning with "bgp-" and "mpls-"
>>    - IEEE has module names like "ethernet"
>>    - ODL has some module names like "config" and "flow-errors"
> Because people often do not read specifications and if tools do not
> complain they assume everything is fine. The YANG spec has clear
> words, there is text in the guidelines. We can write more text and it
> will likely not help. Perhaps tutorials need to stress these points.

I agree for standard modules it "MUST" have unique names since it is 
enforceable.

To ensure maximum interoperability, a private module designer better 
follow the
recommendation and carefully choose a name that is unlikely conflicting 
with
others.  We see many private MIBs use a name with company name prefixed, and
for some MIB designers, I believe that is a learned lesson.


--Xiang Li