Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Review / TEST spec chapter 1 #25

Open
3 tasks
anyflow opened this issue May 6, 2016 · 0 comments
Open
3 tasks

Review / TEST spec chapter 1 #25

anyflow opened this issue May 6, 2016 · 0 comments

Comments

@anyflow
Copy link
Owner

anyflow commented May 6, 2016

  • [MQTT-1.5.3-1]
    The character data in a UTF-8 encoded string MUST be well-formed UTF-8 as defined by the Unicode specification [Unicode] and restated in RFC 3629 [RFC3629]. In particular this data MUST NOT include encodings of code points between U+D800 and U+DFFF. If a Server or Client receives a Control Packet containing ill-formed UTF-8 it MUST close the Network Connection.
  • [MQTT-1.5.3-2]
    A UTF-8 encoded string MUST NOT include an encoding of the null character U+0000. If a receiver (Server or Client) receives a Control Packet containing U+0000 it MUST close the Network Connection.
  • [MQTT-1.5.3-3]
    A UTF-8 encoded sequence 0xEF 0xBB 0xBF is always to be interpreted to mean U+FEFF ("ZERO WIDTH NO-BREAK SPACE") wherever it appears in a string and MUST NOT be skipped over or stripped off by a packet receiver.
@anyflow anyflow self-assigned this May 6, 2016
@anyflow anyflow added this to the version 0.9.9 milestone Oct 5, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

1 participant