[ https://issues.oasis-open.org/browse/MQTT-544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Simon Johnson updated MQTT-544:
-------------------------------
Proposal:
5.4.18 UNSUBACK
||Length||MsgType||MsgId||ReturnCode||
|(octet 0)|(1)|(2-3)|(4)
Table 21: UNSUBACK Message
An UNSUBACK message is sent by a GW to acknowledge the receipt and processing of an UNSUBSCRIBE message. Its format is illustrated in Table 21:
â Length and MsgType: see Section 5.2.
â MsgId: same value as the one contained in the corresponding UNSUBSCRIBE message.
â ReturnCode: "accepted", or rejection reason
was:
5.4.18 UNSUBACK
Length MsgType MsgId ReturnCode
(octet 0) (1) (2-3) (4)
Table 21: UNSUBACK Message
An UNSUBACK message is sent by a GW to acknowledge the receipt and processing of an UNSUBSCRIBE message. Its format is illustrated in Table 21:
â Length and MsgType: see Section 5.2.
â MsgId: same value as the one contained in the corresponding UNSUBSCRIBE message.
â ReturnCode: "accepted", or rejection reason
> Add return code to UNSUBACK
> ---------------------------
>
> Key: MQTT-544
> URL: https://issues.oasis-open.org/browse/MQTT-544
> 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 MQTT-SN SUBACK packet includes a return code. As in MQTT 3.1.1, the UNSUBACK packet does not. It would seem sensible to add a return code to every ack. I think the UNSUBACK is the only one without. This would mirror MQTT 5.0 too.
--
This message was sent by Atlassian Jira
(v8.3.3#803004)
