[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: NETCONF Notifications
On Sat, May 28, 2005 at 09:34:29AM -0700, Andy Bierman wrote:
> Let's start a thread to see if we agree on the problem we're trying to
> solve. First, let's remember where we left off.
I think it is important to not ignore what is going on in the syslog
WG. In particular, <draft-ietf-syslog-protocol-11.txt> seems to be
relevant.
The only strong reason I see for a netconf notification transport
would be the reuse of security associations. Perhaps a syslog mapping
over ssh would kind of solve the problem.
Bottom line: I am not really sure yet a notification channel within
netconf is essential. Even if it is, we should not be blind and ignore
that syslog is out there and that there is active work to build from
the original BSD design and which is not bound to BEEP.
/js
--
Juergen Schoenwaelder International University Bremen
<http://www.eecs.iu-bremen.de/> P.O. Box 750 561, 28725 Bremen, Germany
--
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/>