On Fri, 13 Oct 2000, Chris Lonvick wrote:
> PROPOSED for ver01:
> The syslog message has traditionally contained ASCII alphanumerics
> and symbols. The code set most often used has been seven-bit
> ASCII in an eight-bit field. These are the ASCII codes as defined
> in "USA Standard Code for Information Interchange" [2] using codes
> 32 through 126. No indication of the code set used within the
> message is required, nor is it expected. Other codes and code
> sets MAY be used. The selection of a code set and codes used in
> a message should be made with thoughts of the intended receiver.
> A message containing characters in a code set that cannot be
> viewed by a receiver will yield no information of value to an
> operator or administrator looking at it.
What about reserving
FF FE - Unicode BOM (bigendian)
FE FF - Unicode BOM (little endian)
EF BF BE - Unicode BOM (BE) as UTF-8
EF BB BF - Unicode BOM (LE) as UTF-8
at the beginning of a message? There should be an escape sequence (like
"if there are only spaces before one of these sequences, one space is
meant to escape the sequence and must be deleted.").
We could also specify that said sequences form the start of a message in
said format, and receiving syslogds should at least know about this, or
even better handle such messages.
Simon
--
GPG public key available from http://phobos.fs.tum.de/pgp/Simon.Richter.asc
Fingerprint: A319 A60F 20F6 C8A4 3C86 54B4 99CD AC6E 79D1 B1E7
Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread!
