RE: on <close-session>

[<jayaprakash.kulkarni@wipro.com>]

Eliot Lear wrote:

>  - an agent MUST cease processing <RPC>s if it determines that it has
>    lost communications with the manager, and release all state
>    associated with the session, including locks.

Is this para concerned with a normal termination using close-session
command?

If yes, is it a expected behaviour that manager will terminate a session
immediately on sending a close-session OR should it wait until it
recieves a <ok> reply from the manager?

IMO, manager should not terminate a session immediately at the end of a
close-session command and should wait until it recieves a <ok> reply.

For example: If the user wants to run the following script on a daily
basis:
<get-config>
<edit-config>
<commit>
<close-session>

All the commands should be pipelined, so the close-session would get
executed only at the end of the commit operation.

Regards
Jayaprakash



--
to unsubscribe send a message to netconf-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/netconf/>