Re: another feature

[by way of "Chris M. Lonvick" <[EMAIL PROTECTED]>]

 >>>>> "Darren" == Darren Reed <[EMAIL PROTECTED]> writes:

Darren> This is somewhat related to the other IETF syslog effort.

Darren> See draft-abela-ulm-05.txt on your local IETF ftp server.

Darren> I think message content and the protocol used by syslog daemons to
Darren> exchange information are two different problems.

Unfortunately, I disagree. We have 3 options here:

- Leave _all_ message contents unspecified

This means we use regexps to dispatch data, or we throw it all in the same
place, as there is nothing of fixed format. This is a bit random for my
tastes.

- Specify _some_ message contents

This is what syslog does today. Facility and Severity are specified. The
rest is implementation specific. I would, at a minimum, add originating
system time to this list. I like this option the best, and we can have lots
of arguments about what is specified, what is mandatory, what is
optional... :)

- Specify _all_ message contents

This would combine the 2 efforts, and is, I beleive, too difficult to
accomplish.

-- 
Carson Gaspar -- [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED]
http://www.cs.columbia.edu/~carson/home.html
Queen Trapped in a Butch Body