Hi, 2 questions/ suggestions concerning the UTF-8 encoding in the syslog protocol:
1) Is the " " (white space) after the header to be encoded in ASCII or UTF-8? The spec seems currently open to that respect (although it would seem logical for it to be still in ASCII); should be clarified. 2) Concerning the UTF-8 encoding, depending on where you send syslog messages there are many scenarios in which it would be beneficial to have an option in which NOT to use UTF-8 encoding but to also allow for other encodings, in particular plain ASCII. Such an option would also allow for quicker adaptation of this specification, as it is eases the migration. To provide for that, it seems it would make sense to allow for a flag in the header part of the message - at the tail end (that is known to be still ASCII encoded), right before the structured data, that indicates which encoding is used - that is, whether UTF-8 is in effect, or if another encoding is used - ex. ASCII, or even proprietary. (Apologies in case this aspect was discussed in the past and I am beating on a dead horse; but this appears important enough to bring up.) --- Alex _______________________________________________ Syslog-sec mailing list Syslog-sec@www.employees.org http://www.employees.org/mailman/listinfo/syslog-sec
