OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

mqtt message

[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:all-tabpanel ]

Simon Johnson updated MQTT-542:
-------------------------------
    Proposal: 
Section 6.2 should now read;

6.2 Clientâs Connection Setup
As with MQTT, a MQTT-SN client needs to setup a connection to a GW before it can exchange information with that GW. The procedure for setting up a connection with a GW is illustrated in Fig. 3, in which it is assumed that the client requests the gateway to prompt for the transfer of Will topic and Will message. This request is indicated by setting the Will flag of the CONNECT message. The client then sends these two pieces of information to the GW upon receiving the corresponding request messages WILLTOPICREQ and WILLMSGREQ. The procedure is terminated with the CONNACK message sent by the GW.
If Will flag is not set then the GW answers directly with a CONNACK message.

- CONNECT PROCEDURE SEQUENCE DIAGRAM - 
 Figure 3: Connect procedure

In case the GW could not accept the connection request (e.g. because of congestion or it does not support a feature indicated in the CONNECT message), the GW returns a CONNACK message with the rejection reason.

_In the case where the client provides a zero length client identifier, the Server MUST respond with a CONNACK containing an Assigned Client Identifier. The Assigned Client Identifier MUST be a new Client Identifier not used by any other Session currently in the Server._

  was:
Section 6.2 should now read;

6.2 Clientâs Connection Setup
As with MQTT, a MQTT-SN client needs to setup a connection to a GW before it can exchange information with that GW. The procedure for setting up a connection with a GW is illustrated in Fig. 3, in which it is assumed that the client requests the gateway to prompt for the transfer of Will topic and Will message. This request is indicated by setting the Will flag of the CONNECT message. The client then sends these two pieces of information to the GW upon receiving the corresponding request messages WILLTOPICREQ and WILLMSGREQ. The procedure is terminated with the CONNACK message sent by the GW.
If Will flag is not set then the GW answers directly with a CONNACK message.
âc Copyright IBM Corporation 1999, 2013. All rights reserved. 20
 Figure 3: Connect procedure
In case the GW could not accept the connection request (e.g. because of congestion or it does not support a feature indicated in the CONNECT message), the GW returns a CONNACK message with the rejection reason.

_In the case where the client provides a zero length client identifier, the Server MUST respond with a CONNACK containing an Assigned Client Identifier. The Assigned Client Identifier MUST be a new Client Identifier not used by any other Session currently in the Server._


> 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)


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]