[Netconf] RFC6241 - Confirmed Commit Capability, <close-session> and <kill-session>

["Jonathan Hansford" <[e-mail]>]

Hi,

RFC6241, Section 7.9 <kill-session> states "If a NETCONF server receives 
a <kill-session> request while processing a confirmed commit (Section 
8.4), it MUST restore the configuration to its state before the 
confirmed commit was issued."

Is it correct to assume that only applies if the session being killed is 
the one for which a confirmed commit is being processed?

Section 8.4.1 states "If the session issuing the confirmed commit is 
terminated for any reason before the confirm timeout expires, the server 
MUST restore the configuration to its state before the confirmed commit 
was issued, unless the confirmed commit also included a <persist> 
element."

Is it correct to assume if a <kill-session> is received for a session 
for which the confirmed commit included a <persist> element, the 
behaviour is still to restore the configuration to its state before the 
confirmed commit was issued since the client owning the session is no 
longer in control and the session is having to be killed using a 
different client?

Section 7.8 <close-session> makes no mention of confirmed commits.

Is it correct to assume the client would be expected to cancel a 
confirmed commit before closing its session unless the client wished to 
continue on a new session (e.g. after a device reboot) in which case the 
confirmed commit would have included a <persist> element?

Thanks,

Jonathan

---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus