little problem with <close-session>

[Eliot Lear <lear@cisco.com>]

The manager is meant to issue a <close-session> element to initiate a 
close.  For BEEP this is a bad idea, and it's probably a bad idea for 
everyone else as well.  The problem is that either side should be able 
to initiate a close.  This is particularly necessary for orderly 
shutdown of the device running the agent.

This argues *strongly* for the removal of <close-session> and returning 
this function to the application mappings.  If we need to add some 
meta-thing into SSH, so be it, but the agent needs to initiate the close 
- somehow.

Eliot


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