RE: NETCONF Notifications: Consensus Points

["Sharon Chisholm" <schishol@nortel.com>]

<Andy>
Notification Info Model/Payload

  There is WG consensus to reuse syslog classification, although
  the ability to transfer additional user data (similar to the OBJECTS
  clause in an SNMP notification) is also required.  The option
  of asking the SYSLOG WG for enhancements to RFC 3195 is also
  possible, and some WG members prefer this approach if syslog
  is going to be enhanced in any meaningful way.
</Andy>

This one I think requires more discussion before we can declare some
consensus. I think there is a general sense that there is something from
the land of syslog that we want to take advantage of and learn from, but
I have not seen strong consensus as to what that is. And which version
of syslog are people looking to leverage? 

I think being able to tunnel syslog content into netconf is good for
transitioning and our internet draft discusses this a bit in one of the
appendices. What is more interesting though, is some of the SD-Params we
have developed in syslog. I think bringing these in, not using SD-Param
grammar, but as properly tagged XML would be very very useful.

Sharon

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