[OASIS Issue Tracker] Created: (MQTT-44) Specific details for UTF-8 Strings

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

Specific details for UTF-8 Strings
----------------------------------

                 Key: MQTT-44
                 URL: http://tools.oasis-open.org/issues/browse/MQTT-44
             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
          Issue Type: Improvement
          Components: core
            Reporter: Rahul Gupta


This issues is based on comments in MQTT-24, and is opened  a Core issue to discuss in MQTT TC Call, I had a discussion with my co-editor Andy and he suggested to open a core issue for TC discussion.

from MQTT-24
-------------------

> We should also make a simple statement that UTF-8 encodings MUST NOT have a three character initial BOM.

> A clarification that the encoding MUST NOT be Java's Modified UTF-8, and can contain ASCII NULL

> At the same time, it's probably worth nothing too that certain unicode combinations are invalid in UTF- 8 - the use of surrogate pairs from UTF-16 re-encoded and certain non-transmissable characters (eg U+FFFE from memory) - these normally delimit the last 2 characters in a multi-lingual plain. These restrictions are only a minor burden fro java implementations using the naive methods in string / character. These restrictions serve to stop propagation of bad data through a network of nodes.

> Implementations MAY decide to not support the use of ASCII NUL and C0 / C1 control codes / MAY decide to place additional restrictions on supported characters


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira