Re: [NGO] external module properties

Phil Shafer <phil@juniper.net> wrote:
> The other option is the one java took: use reversed domain name
> hierarchies to ensure that there are no conflicts.  No one but sun
> can make a com.sun.java.swing module, given you instant
> self-organizing uniqueness.  If you own the domain, you own the
> namespace under that domain.  Pro: simple; con: verbose.

If we want something verbose, we already have the namespace uri, which
also is supposed to be globally unique.  It could be used to identify
the module.

I have limited experience of using SNMP MIBs in larger NMS systems;
but is the current module name scheme of SMI a problem?  If it is, we
should do something better.  If it isn't, we shouldn't try to solve
it.

/martin
_______________________________________________
NGO mailing list
NGO@ietf.org
https://www.ietf.org/mailman/listinfo/ngo