[Syslog] Message format

WG, Sorry for joining in the discussion late. I've only just found some time to reply. My thoughts below... The new format looks great. PRIVERSION TIMESTAMP HOSTNAME APP-NAME PROCID MSGID [SD-ID]s MSG Replace all received null characters with either 00 or /0. My preference is 00. Keep MSGID

RE: [Syslog] #5 - character encoding (was: Consensus?)

Hi Rainer, Why don't we look at it from the other direction? We could state that any encoding is acceptable - for ease-of-use/migration with existing syslog implementations. It is RECOMMENDED that UTF-8 be used. When it is used, an SD-ID element will be REQUIRED. e.g. - [enc=utf-8

RE: [Syslog] #3 NUL octets, #4 binary data, #8 octet-counting

We are still ok with always having UTF-8 in SD values, right? We need this for foreign usernames. We have discussed this before. Yes, this would work for me. We need to ensure that the SD-IDs are always going to be encoded in a known format. UTF-8 is a good choice. Cheers Andrew

RE: [Syslog] #3 NUL octets, #4 binary data, #8 octet-counting

binary data, #8 octet-counting I think for TCP mapping a transport header with message size would be more appropriate framing than termination character. Thanks, Anton. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Andrew Ross Sent: Wednesday

RE: [Syslog] TIMESTAMP and leap seconds

Hi Rainer, Happy new year! Your idea of ignoring the leap seconds sounds very sensible to me. Cheers Andrew -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rainer Gerhards Sent: Monday, 2 January 2006 11:42 p.m. To: [EMAIL PROTECTED] Subject:

[Syslog] Syslog TLS and the Huawei IPR claim

Chris, After reading the IPR document, my vote is for A. A. The WG SHOULD proceed with draft-ietf-syslog-transport-tls as a Working Group document. Regards Andrew Kiwi Enterprises Chris Lonvick wrote: Hi Folks, Please continue to send in your opinion on this. I'll determine

RE: [Syslog] delineated datagrams

Rainer, I'm in favour of using the LF delimiter as a starting point. This way we can get something that works with Cisco PIX, Netscreen, Monitorware, Kiwi, Syslog-ng etc. Then it becomes an easy task to just wrap the session with TLS. How do you suggest we escape the LF? Regards Andrew Kiwi

RE: [Syslog] timeline

Just to clarify, Kiwi Syslog V8 currently sends CRLF as the TCP delimiter, but will accept LF, CR, CRLF, LFCR and NULL as valid delimiters on the incoming stream. We will be changing our sending delimiter to LF in the near future to make it more compatible with syslog-ng etc. Cheers Andrew