[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Notification architecture



Hi,

This has probably been discussed before, and the answer might be
obvious, but I can't find anything in the archives.  I'd like to know
why a new notification framework is needed?  Is it simply that we need
to be able to send larger messages than what syslog can do?  Or is it
because the content of the notifications will be tightly coupled to the
ordinary netconf content, and therefore it's easier to use a new
scheme than trying to map the netconf model to syslog?  Or something
else?

I think the most important question then is the session model - if the
manager should set up the session and keep it open or if the agent
should establish the session when needed.  If the manager is supposed
to keep it open, how well does that scale?  1000 sessions?  10000?



/martin


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