netconf-0----Page:20
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
|
13.12.3) Error handling for Need to clarify error handling and requirements for the lock operation Proposed consensus: Locking applies to all access mechanisms (e.g., SNMP, CLI, NETCONF, etc.) Implementations may choose to hide locking from CLI users, but the CLI sub-system must still use the locking mechanism The discard-changes parameter added to the lock operation should be removed (agent always discards changes to the candidate if they are abandoned by the session) The session-id zero will be used in an "lock failed" rpc-error to indicate that the lock is owned by a non-NETCONF entity |