I also think that the instance data header needs to have a way of
indicating which modules (and versions/revisions) the instance data
applies to.
It can be optional, so producers that know it is not required can leave
it out. But I think that it is required, at least for situations where
being able to programmatically consume the instance data in a robust way
is important.
Thanks,
Rob
On 30/11/2018 17:48, Andy Bierman wrote:
Hi,
I don't see much standards value in this draft so far.
It seems the parser of the file needs to know the YANG library information
for the instance file data in some out-of-scope non-standard manner.
This is what we already have today just by naming the file in a
specific way.
Is the intent that the instance-data-set leafs will be used to determine
the module revisions, features, and deviations used in the children
or the 'data' node?
Andy
_______________________________________________
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod
_______________________________________________
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod
