On Mon, Dec 19, 2016 at 11:37:57AM +0100, Ladislav Lhotka wrote: > > I am not proposing to ban candidate or something but IMO it needn't be part > of the base NETCONF (or whatever protocol) spec. >
Lets recall that candidate is a _capability_. Nobody is required to implement it. > A typical problem of candidate combined with NACM is that user A edits item X > and B edits Y in candidate. If B doesn't have write access to X and A to Y, > then none of them is able to make a commit. > The problem is caused by allowing users with inconsistent access rights to both use candidate. So you get what you asked for. But I assume you can still do <discard-changes> and recover. /js -- Juergen Schoenwaelder Jacobs University Bremen gGmbH Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany Fax: +49 421 200 3103 <http://www.jacobs-university.de/> _______________________________________________ netmod mailing list [email protected] https://www.ietf.org/mailman/listinfo/netmod
