Re: configuration: writable MIB modules versus NETCONF/YANG modules

On Fri, Feb 14, 2014 at 06:39:00AM +0000, Dave Thaler wrote:

> As a chair of WGs outside the OPS area, I'd still like to see
> additional guidance around notification/logging mechanisms as well
> (IPFIX vs Syslog vs SNMP traps/informs, etc.)

This is much harder. Here is how I see things:

IPFIX works well for large amounts of notification/logging data that
has a common structure, i.e. you get things reported with a few IPFIX
templates. SYSLOG works well with semi-structured data - traditionally
there was very little common structure and the value was in the
free-form text field. SNMP again works with structured data that is
defined in data models (which is different from many IPFIX templates
that IPFIX data processors are expected to discover at runtime,
although I am aware of I-Ds trying to nail down IPFIX templates).

Both, SYSLOG and SNMP notifications have seen many years of wide
spread deployment, IPFIX for notification/logging is more a new kid on
the block. IPFIX may have nice performance characteristics but most
management systems I have seen support SNMP notifications and/or
SYSLOG messages to extract notification/logging data but not IPFIX. I
believe what is widely deployed today (and feel free to prove me
wrong) is largely SYSLOG and SNMP for notification/logging data.

What I am saying here is that the situation is less clear cut compared
to SNMP for persistent configuration.

/js

-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: +49 421 200 3587         Campus Ring 1, 28759 Bremen, Germany
Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>