Hello Jurgen,As we had many misunderstandings around the datastore parameter, and I am still not clear what you would like, could you propose a description text for the datastore parameter.
regards Balazs On 2018. 11. 23. 16:49, Juergen Schoenwaelder wrote:
On Fri, Nov 23, 2018 at 01:21:23PM +0000, Balázs Lengyel wrote:BALAZS: "Instance data associated with a datastore" may mean many things, that's why this relatively loose term is used. It may mean: * Data was read from that datastore * Data is intended to be fed into that datastore * Something else ??? This can be useful if data is read from a datastore, but in a number of cases it is not useful: * Preloading configuration data: datastore may be running or candidate. * Preloading mixed config and state data: We do have state data that is very stable and thus it is documented as instance data, and the instance data file is actually used to feed the state data into the SW. So datastore is: running, candidate + operational if NMDA is supported or state datastore (whatever that is) if NMDA is not supported regards BalazsI do not buy this story. Your software needs to decide somehow what instance data means. A config true leaf in candidate means something different than the same config true leaf in running and this yet again means something different than the same config true leaf in operational. /js
-- Balazs Lengyel Ericsson Hungary Ltd. Senior Specialist Mobile: +36-70-330-7909 email: balazs.leng...@ericsson.com
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ netmod mailing list netmod@ietf.org https://www.ietf.org/mailman/listinfo/netmod
