Re: Notification Message Processing Model

[Phil Shafer <phil@juniper.net>]

Andy Bierman writes:
>3) lack of an <abort> command.
>   The manager cannot shut up the agent if it is spewing a reply
>   or a notification, except by closing the connection.
>   We took this command out of the protocol when we took out
>   channels.  We took out channels because of unwarranted inherent
>   complexity.

Any chance of getting <abort/> back in?

Thanks,
 Phil

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