[core] YANG Packages for CoMI

[Andy Bierman <[e-mail]>]

Hi,

Michel raised some issues with the YANG library draft
http://datatracker.ietf.org/doc/draft-ietf-netconf-yang-library/

Maybe CoMI needs its own optimized module library.
I am concerned that data sizes of the YANG library will be
too big in some really constrained environments.

I wrote a draft that defines a way to specify the contents of the
YANG library in a single static document, called a YANG package.
http://datatracker.ietf.org/doc/draft-bierman-netmod-yang-package/

If there was a "shorthand" resource that listed YANG packages, instead
of YANG modules, then the CoMI client that supported YANG packages
could read that instead of the module library.

The YANG package message response can identify a single package
(e.g. match the firmware) so the size of the response will remain very
small, and not depend on the entire list of modules, features,
and deviations. The data savings could 1000X for 100 modules.

The client needs to retrieve the library first-time and anytime it changes.
The module-set-id values are per-server, not global. This could be a
significant bottleneck when a CoMI client starts or restarts, and
manages lots of servers.


Andy