[ https://issues.oasis-open.org/browse/MQTT-542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Simon Johnson updated MQTT-542:
-------------------------------
Assignee: Simon Johnson (was: Allan Stockdill-Mander)
> Allow 0-length client id
> ------------------------
>
> Key: MQTT-542
> URL: https://issues.oasis-open.org/browse/MQTT-542
> Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
> Issue Type: Improvement
> Components: MQTT-SN
> Affects Versions: MQTT-SN-1.2
> Reporter: Ian Craggs
> Assignee: Simon Johnson
> Priority: Major
>
> The *clientid variable length field* is allowed to be 0-length in both MQTT 3.1.1 and 5.0, indicating that the server should assign a clientid itself. If we do allow this behaviour in MQTT-SN I think itâs important that that clientid is returned to the client, as it is in MQTT 5.0. This could be done by including the server assigned clientid in the MQTT-SN CONNACK packet, which currently has no variable length field.
--
This message was sent by Atlassian Jira
(v8.3.3#803004)
