kill-session: editorial mistake

[Lei Zhang <lzhang@juniper.net>]

In draft 10:

7.9.  <kill-session>

  Description:

     Force the termination of a NETCONF session.

     When a NETCONF entity receives a <kill-session> request for an
     open session, it will abort any operations currently in process,
     release any locks and resources associated with the session and
     close any associated connections.

     ... ...

     Otherwise, the <kill-session> operation does not roll back
     configuration or other device state modifications made by the
     entity holding the lock.

And:

8.3.5.1.  <lock> and <unlock>

  ... ... To facilitate easy
  recovery, any outstanding changes are discarded when the lock is
  released, whether explicitly with the <unlock> operation or
  implicitly from session failure.


The two sections conflict with each other. The 'otherwise' paragraph of 
<kill-session>
seems to be misplaced right?

Thanks,
Lei


--
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/>