Re: [core] YANG Packages for CoMI

On Sun, Jul 26, 2015 at 11:26 PM, peter van der Stok <stokcons@xs4all.nl>
wrote:

> HI Andy,
>
> Is the proposal to make YANG packages compulsory over yang-library in Comi
> servers and clients?
>
>
No, it would be optional.
Another solution approach would be to make the module-set-id values
global instead of per-server. That might be less work perhaps.

Peter
>

Andy

>
> Andy Bierman schreef op 2015-07-26 19:44:
>
>> 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
>>
>>
>> _______________________________________________
>> core mailing list
>> core@ietf.org
>> https://www.ietf.org/mailman/listinfo/core
>>
>