Re: [Netconf] New draft-ietf-netconf-partial-lock-08.txt goes to AD andIETF Last Call
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Netconf] New draft-ietf-netconf-partial-lock-08.txt goes to AD andIETF Last Call
Hi,
> If one believes that access decisions are made during "commit" then
> all these horrible things *will* happen, and it's broken, just as
> Balazs argues.
>
> If access decisions are *not* made during "commit" then the problem
> goes away.
I am afraid access decision during commit or not is not the key
reason to the problem. even access decision during config-edit
can cause the problem. The point is, we only edit a portion of
candidate, when we try to commit the whole candidate, we
have no idea if other parts have been modified by other people.
washam
> The problem, if I recall an off-line discussion correctly, is the
> language in an
> example in the netconf spec that indicates that access decisions are
> made
> during the commit. Other than that, I see no reason for access
> decisions to
> be made during commit time in a single-candidate view of how things should
> work.
>
> Randy
>
> _______________________________________________
> Netconf mailing list
> Netconf at ietf.org
> https://www.ietf.org/mailman/listinfo/netconf
>
Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.