[MQTT-571] New structure of the CONNACK packet - OASIS Technical Committees Issue Tracker

XML

Word

Printable

Type: Bug
Status: Applied
Priority: Major
Resolution: Fixed
Affects Version/s: MQTT-SN-1.2
Fix Version/s: wd04
Component/s: MQTT-SN
Labels:
None
Environment:

Hide

Based on accepting #~~MQTT-542~~ we need to specify the new structure of the CONNACK to allow for the returned client id

Show
Based on accepting # MQTT-542 we need to specify the new structure of the CONNACK to allow for the returned client id

Proposal:

Hide

Section should read;

Section 5.4.5 CONNACK

Length MsgType ReturnCode ClientIdentifier

(octet 0) (1) (2) (3:n)

Table 10: CONNACK Message

The CONNACK message is sent by the server in response to a connection request from a client. Its format is shown in Table 10:
• Length and MsgType: see Section 5.2.
• ReturnCode: “accepted”, or rejection reason. See section 5.3.10.
• ClientIdentifier: The ClientIdentifier assigned by the gateway when the associated CONNECT message contained no ClientIdentifier.

For more details of the connection procedure, refer to section 6.2.

Show
Section should read; Section 5.4.5 CONNACK Length MsgType ReturnCode ClientIdentifier (octet 0) (1) (2) (3:n) Table 10: CONNACK Message The CONNACK message is sent by the server in response to a connection request from a client. Its format is shown in Table 10: • Length and MsgType: see Section 5.2. • ReturnCode: “accepted”, or rejection reason. See section 5.3.10. • ClientIdentifier: The ClientIdentifier assigned by the gateway when the associated CONNECT message contained no ClientIdentifier. For more details of the connection procedure, refer to section 6.2.

Related to

MQTT-542 Allow 0-length client id