[core] draft-bierman-core-yid-00.txt questions

[David Reid <[e-mail]>]

I read draft-bierman-core-yid-00.txt and have a few questions.

Will all IETF standard yang modules be included in the YANG identifier 
registry or just ones that might be used on constrained devices? 

In order to assign numbers, is it correct that I need the first revision of 
the module or else the current revision and the registry assignments for the 
previous revision?

What is the benefit of assigning values using hashing over sequentially 
assigning values? 

When there is a hash collision, would it be possible to rehash the value
to get a unique number so that we never have to manually assign numbers and
thus never need to register the numbers in the registry?

Why does module-id need to be added to the YANG module names registry since
it is also in the YANG identifier registry? 

Would it make sense to put the module-id inside the yang module with a yid 
extension so that I would not have to go lookup that information from a 
registry? 

Would it be possible to assign the module-id based on information in the 
module, for example a hash of the namespace and maybe the revision date. 
That way, a module-id would not have to be assigned and maintained in a 
registry.

If I want to handle private modules, do I have to create my own registry?
It seems important that private modules be supported. Could we re-use the
SMI enterprise number assignments for creating module-ids for private modules?

Who will assign the local-id numbers? Is that done by the working group that 
defines the YANG module?

-David Reid