[OASIS Issue Tracker] Commented: (MQTT-11) Length of client Identifier

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

    [ http://tools.oasis-open.org/issues/browse/MQTT-11?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=33472#action_33472 ] 

Raphael Cohen commented on MQTT-11:
-----------------------------------

Adding Comment from Roger Light from mqtt-comments list:-

"The client ID length limit is one of the points that has come up
frequently when people have been talking to me about MQTT.

There is no intrinsic reason within the protocol to limit it to 23
characters. I would be keen on increasing the limit.

I've carried out a survey of existing MQTT implementations

Servers:

mosquitto, activemq, rabbitmq, apollo, rsmb, mqtt.js

Client libraries:

libmosquitto, python-mosquitto, paho c, paho java, paho javascript, paho lua.

Of these, only rabbitmq on the server side and paho java and
javascript implement the 23 character client id limit.

Even a minor increase in length to 32 bytes would be very helpful."


> Length of client Identifier
> ---------------------------
>
>                 Key: MQTT-11
>                 URL: http://tools.oasis-open.org/issues/browse/MQTT-11
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: Improvement
>          Components: core
>            Reporter: Andrew Banks
>
> The current specification says that the client Identifier must be 1 - 23 characters in length.
> Should this mean 
> 1-23 bytes when transformed to UTF-8
> 1-23 Unicode characters, counting surrogate pairs as single characters
> 1-23 Unicode characters, counting surrogate pairs as two 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