Re: [NGO] external module properties

On Tue, Apr 29, 2008 at 12:56:23PM -0400, David Harrington wrote:

> I think that's a problem.

Why do we not work on the YANG specification? It says:

   Standard module names will be assigned by IANA.  The names of all
   standard modules MUST be unique (but different revisions of the same
   module should have the same name).

   Private module names will be assigned by the organization owning the
   module without a central registry.  It is 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.

This is more or less what we do with the SMI. It is not perfect
(reverse DNS names a la Java surely are better but also much more
verbose), but it also seems SMI module name clashes have not been a
serious problem in practice. (Correct me if I am wrong.)

/js

-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: +49 421 200 3587         Campus Ring 1, 28759 Bremen, Germany
Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>
_______________________________________________
NGO mailing list
NGO@ietf.org
https://www.ietf.org/mailman/listinfo/ngo