Re: notification motivation and requirements

["David T. Perkins" <dperkins@dsperkins.com>]

HI,

Here are a couple to add to the list....

*) notifications to report unexpected consequences of
   a configuration change
*) notifications so that state changes can be followed
   due to configuration changes. (Background: some 
   configuration changes can result in destalization
   followed by transition through several states to
   the desired stable state. It is important to know
   the cause of a "service affecting event", and to
   know if the config change has resulted in a new
   stable and desired configuration. If not, then
   the config change, most likely, should be rolled
   back to the previous settings.) 

Regards,
/david t. perkins


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