[OASIS Issue Tracker] (MQTT-571) New structure of the CONNACK packet

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

     [ https://issues.oasis-open.org/browse/MQTT-571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Simon Johnson updated MQTT-571:
-------------------------------
    Proposal: 
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: encoded according to Table 5.
â ClientIdentifier: _optional _ The ClientIdentifier assigned by the gateway when the CONNECT contained no ClientIdentifier




  was:
New CONNACK message format to support gateway assigned client ids;

||Length||MsgType||ReturnCode||ClientIdentifier||
|(octet 0)|(1)|(2)|(3:n)



> New structure of the CONNACK packet
> -----------------------------------
>
>                 Key: MQTT-571
>                 URL: https://issues.oasis-open.org/browse/MQTT-571
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: Bug
>          Components: MQTT-SN
>    Affects Versions: MQTT-SN-1.2
>         Environment: Based on accepting #MQTT-542 we need to specify the new structure of the CONNACK to allow for the returned client id
>            Reporter: Allan Stockdill-Mander
>            Assignee: Simon Johnson
>            Priority: Major
>




--
This message was sent by Atlassian Jira
(v8.3.3#803004)