Re: [YANG] Questions about submodule

On Fri, Jan 18, 2008 at 11:15:05AM +0100, Martin Bjorklund wrote:

> In larger projects, this might actually be useful.  Instead of having
> one big centralized module, we allow people to split the task into
> submodules.  If the submodule becomes big enough, it might be useful
> to split it into other submodules.  Even though I cannot see that 100
> levels are ever used, I don't think we should add a rule which says
> that you cannot nest more than 99 levels.

I am not a big fan of introducing such arbitrary limits. A yang
compiler is not something that you need at NETCONF run time so memory
constraints etc. are not a big deal. We also have no limits for the
number of identifiers a module may define, the max. nesting of
containers and many other things. And I think this is goodness and we
should stick to this.

If people really want limits (I hope not), we should define minimums
that must be supported to be compliant, but leave the maximum open.
(Note that libsmi allocates everything dynamically so the limits are
 actually the available memory at run time; I would not like to move to
 a different implementation model just to be compliant to some rather
 arbitrarily choosen limits.)

/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/>

_______________________________________________
YANG mailing list
YANG@ietf.org
https://www1.ietf.org/mailman/listinfo/yang