RE: [Syslog] draft-ietf-syslog-protocol-21.txt: section 3containsnewtext to address ietf last call comments (fwd)

["Rainer Gerhards" <rgerhards at hq.adiscon.com>]

I have been a bit brief. MSG is passed in via the POSIX API. So the
actual generator of MSG is not syslogd. However, and you are right on
this, from the "on the wire" IETF point of view, both are generated by
the same entity, that being syslogd.

Rainer

> -----Original Message-----
> From: Rainer Gerhards [mailto:rgerhards at hq.adiscon.com]
> Sent: Monday, June 25, 2007 9:59 AM
> To: Glenn M. Keeni; syslog at ietf.org
> Subject: RE: [Syslog] draft-ietf-syslog-protocol-21.txt: section
> 3containsnewtext to address ietf last call comments (fwd)
> 
> > I agree that it is a point of view. I do not see the necessity of
> > the two layers for MSG and SYSLOG-MSG as a part of operations and
> > management.
> > The reason being that it will generally be the same entity
> > ("application", "module" call it whatever) that will generate MSG
and
> > SYSLOG-MSG.
> 
> Unix *nix, these are always two different entities.
> 
> Rainer
> 
> _______________________________________________
> Syslog mailing list
> Syslog at lists.ietf.org
> https://www1.ietf.org/mailman/listinfo/syslog

_______________________________________________
Syslog mailing list
Syslog at lists.ietf.org
https://www1.ietf.org/mailman/listinfo/syslog