Re: [mqtt-comment] MQTT Version 5.0 - Public Review - Property Length in UNSUBACK cannot be zero or missing

From
Christoph Krey <>
Date
2017-09-03T12:00:01+00:00
ID
Thread
Re: [mqtt-comment] MQTT Version 5.0 - Public Review - Property Length in UNSUBACK cannot be zero or missing
Same situation for SUBACK

---
3.9.2.1 SUBACK Properties3.9.2.1.1 Property Length
The length of Properties in the SUBACK packet Variable Header encoded as a Variable Byte Integer. If the Remaining Length is less than 3, there is no Properties.

 

Am 03.09.2017 um 13:19 schrieb Christoph Krey <>:

In MQTT V5, the UNSUBACK Payload will be always at least 1 byte long to contain the reason code(s).

Keeping this in mind the Remaining length will always be at least 4 bytes long and the property length variable byte can never be left out.

Please remove the sentence "If the Remaining Length is less than 3 there is no Properties."

--- 
3.11.2.1 UNSUBACK Properties3.11.2.1.1 Property Length
The length of the Properties in the UNSUBACK packet Variable Header encoded as a Variable Byte Integer. If the Remaining Length is less than 3 there is no Properties.

…

3.11.3 UNSUBACK Payload
The Payload contains a list of Reason Codes. Each Reason Code corresponds to a Topic Filter in the UNSUBSCRIBE packet being acknowledged. The order of Reason Codes in the UNSUBACK packet MUST match the order of Topic Filters in the UNSUBSCRIBE packet [MQTT-3.11.3-1].

Christoph Krey

<> 7582 9188 8D6C E945 15BA  4CD9 900D FB34 2AB0 38D7Breite Strasse 79, 41460 Neuss, Germany+49 1511 874 4526

Attachment:
signature.asc

Description: Message signed with OpenPGP