[MQTT-611] Utilise the REASON CODE in SUBACK to communicate Granted QoS - OASIS Technical Committees Issue Tracker

XML

Word

Printable

Type: New Feature
Status: Closed
Priority: Major
Resolution: Fixed
Affects Version/s: None
Fix Version/s: wd29
Component/s: MQTT-SN
Labels:
None
Environment:

Hide

Presently, Granted QoS is communicated in the SUBACK in the flags field (Bits 5 & 6). TT uses Granted QoS Reason Codes. Since there is also a reason code field available in the SUBACK, we should look to standardise this and remove the Granted QoS from the Flags into the Reason code inline with TT.

Show
Presently, Granted QoS is communicated in the SUBACK in the flags field (Bits 5 & 6). TT uses Granted QoS Reason Codes. Since there is also a reason code field available in the SUBACK, we should look to standardise this and remove the Granted QoS from the Flags into the Reason code inline with TT.

Proposal:

Hide

The QoS flags in the SUBACK packet are now reserved.

The reason codes for SUBACK include granted QoS 0, 1 and 2 as in MQTT 5.0.

Show
The QoS flags in the SUBACK packet are now reserved. The reason codes for SUBACK include granted QoS 0, 1 and 2 as in MQTT 5.0.
Resolution:

Hide

The QoS flags in the SUBACK packet are now reserved.

The reason codes for SUBACK include granted QoS 0, 1 and 2 as in MQTT 5.0.

Show
The QoS flags in the SUBACK packet are now reserved. The reason codes for SUBACK include granted QoS 0, 1 and 2 as in MQTT 5.0.