[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (MQTT-542) Allow 0-length client id
[ https://issues.oasis-open.org/browse/MQTT-542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=76803#comment-76803 ] Simon Johnson commented on MQTT-542: ------------------------------------ I believe it is important that the clients are aware of their IDs. CONNACK would seem like a sensible mechanism to do this where it is broker assigned. > 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 > 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)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]