[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Notification Message Processing Model
Steve Berl wrote:
The main use that I see for notifications is for "configuration change
notifications". A netconf based client would like to know if someone else is
changing the configuration, and just what it is that has been changed. The
notification needs to include information about who made the change, when
they made the change, and exactly what they changed. Just a dumb
notification that "something changed" is not good enough. We need to send a
potentially large message describing the actual changes made. This data is
typically too large to send over a standard syslog message or SNMP trap.
This makes sense.
So far I see a compelling need for 2 standard notification types:
<syslog-event> and <config-change-event>
to unsubscribe send a message to firstname.lastname@example.org with
the word 'unsubscribe' in a single line as the message text body.