> -----Original Message----- > From: netmod [mailto:netmod-boun...@ietf.org] On Behalf Of Ladislav > Lhotka > Sent: 14 December 2016 14:25 > To: Andy Bierman <a...@yumaworks.com>; Mehmet Ersue > <mer...@gmail.com> > Cc: NetMod WG Chairs <netmod-cha...@ietf.org>; NetConf WG Chairs > <netconf-cha...@ietf.org>; NetMod WG <netmod@ietf.org>; Netconf > <netc...@ietf.org> > Subject: Re: [netmod] [Netconf] WG adoption poll draft-nmdsdt-netmod- > revised-datastores-00 > : > As for candidate, it is optional and we all know that it is quite problematic if > concurrent access of multiple clients is possible. Therefore, it would IMO be a > good riddance.
For someone who is yet to see NETCONF and YANG used in anger, can you explain why judicious use of candidate and lock is problematic with concurrent access and why, as a consequence, it should be got rid of? One of the features of NETCONF that attracted us to it is its support for transactioning, a feature which it would appear came from previous experience with JUNOS. Is it current guidance that transactioning should not be used? Jonathan > > Lada _______________________________________________ netmod mailing list netmod@ietf.org https://www.ietf.org/mailman/listinfo/netmod
