Re: sylsog in NETCONF notifications

[Balazs Lengyel <balazs.lengyel@ericsson.com>]

Hello,
There are some NEW implementations for Netconf as well. These don't always need a 
transition plan. Also if you look at Jurgens requirement page a good number of 
requirements are not refering to syslog.
Generally I would like to avoid being forced to use syslog in order to have a standard 
notification mechanism with filtering.
Balazs

> IMO, syslog is important enough that it is worthwhile to have
> filtering mechanisms that actually work for syslog.
> Generalized filters sound great, but if they are impossible
> to use for the most common application (syslog/RAW), then
> they are mostly irrelevant.  Telling all the vendors "Hey, I have a
> really cool XML tool, so if you could re-design and re-code
> 15,000 or so syslog messages to output an XML subtree instead of text,
> well, that would be great."
>
>
> I suggest coming up with a transition plan, because it will
> be about a decade before you get to use your fancy XML tools on
> notification content.

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