>The only tricky issue that remains is the NUL octet. The more I think
>about it, the more I think the CLR to disallow it is less evil than to
>make it stay...

I agree that having the CLR for NUL octet exclusion is OK.

Quick question, if someone is sending international data in UTF-8 format,
can there ever be a valid UTF-8 sequence that includes a NUL octet value? If
so, we need to allow NUL values in the MSG. 

Does anyone on the list know UTF-8 well enough to answer this?

Cheers

Andrew


_______________________________________________
Syslog mailing list
Syslog@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/syslog

Reply via email to