Re: [Syslog-sec] Syslog message versioning

I don't recall seeing it but I think that this is feature creep we should avoid. Primarily this is a protocol for the transport of event messages, not a standard for the contents of event messages, although we go some way down that road (well far enough for me). If the generators of messages

RE: [Syslog-sec] Syslog protocol - UTF-8 encoding

Robert, the good news is that syslog-protcol requires the header to be pure USASCII (NOT UTF-8). The reason is that all fields in the header should be properly encodable in ASCII, no need for any local encodings there. If someone sees a need, please send a note to the list, as this obviously is

[Syslog-sec] Syslog protocol - version 12, sec 6.2.4 TRUNCATE value

Hi,   These are the current assigned values for TRUNCATE: 0 = no truncate 1 = all or some SD-ELEMENTS were truncated 2 = all or part of MSG was truncated    4 = truncation occurred at the initial sender   I like to point out that the current reserved numbers do not seem sufficient to cover