[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
sylsog in NETCONF notifications
- To: netconf@ops.ietf.org
- Subject: sylsog in NETCONF notifications
- From: "Rainer Gerhards" <rgerhards@gmail.com>
- Date: Thu, 6 Jul 2006 17:43:42 +0200
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=SGT8dXfqeEegkrrtmZnPBAFQHxeZo3mn+v/DdCpI1bZOewg472JC2fC452LO0BFsNDqa9UVnGYrlc4MFDI2MfgOtNmsNAxwFpY/daG+FOdOiaWreHsP02LuSTU81v94FMgAnmoGYfOiVMjqdC0R/4zYoouBqjGUdbcMY+d2FbUg=
WG,
I suggest that the mapping of syslog to netconf notifications as well
as the "syslogTunnel" event type be left out of the netconf
notifications I-D. The reason is that I think the syslog community
should provide a data model for syslog notifications as well as a
mapping. The same should probably be done for SMTP traps.
Having syslog mappings in a basic netconf document forces the netconf
document to be changed/obsoleted whenever there is change on the
syslog side. I think this dependency should be avoided.
There is some growing interest in the syslog community to define event
data models. This effort could play nicely together with netconf.
Rainer
--
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/>