[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: sylsog in NETCONF notifications

Rainer Gerhards wrote:

Andy,


If you mean transformation of all ad-hoc syslog text content
to a standard and structured XML hierarchy -- no.  That is way out
of scope.  However, filter parameters to suppress notification delivery
are in scope.  (The non-normative appendices are supposed to be removed.)


I agree. But these filter parameters must not be SYSLOG specific - in
the same way as <get> is not specified for SYSLOG or any other
specific case. I'd like to see some standard properties for NETCONF. I
also think that specifying extensible filter mechanisms (as in section
6.) is useful and needed.


I agree.
I was referring to the "regexp" text filtering in Phil's draft.
I don't the best way to accomplish syslog content filtering,
but I doubt either subtree or Xpath filters would be it.

I don't think that if the netconf protocol had any particular
syslog content filters (for netconf delivery of syslog), the
syslog protocol (or WG) would be impacted in any way.





However, I do NOT think that specifying a "severity" filter for syslog
is appropriate (or any other SYSLOG reference). That I would expect to
see in a different document, and being announced as an optional
capability at the time of <hello>.

Putting any SYSLOG specifics into the core notification document
would, IMO,  remove its payload content-independence.


I agree.
We should not include non-normative appendices as a way
to avoid the actual standardization of that material either.
The final draft will be consistent with the architecture
and operations defined in the netconf-prot-12 draft.
We are not very close to a final draft yet.



Rainer




Andy


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