[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Inconsistent reason code between SUBACK and UNSUBACK
Hi, According to 3.9.3 SUBACK Payload Table 3â8 - Subscribe Reason Codes https://docs.oasis-open.org/mqtt/mqtt/v5.0/os/mqtt-v5.0-os.html#_Toc3901178 SUBACK reason code has the following values: 158 Shared Subscriptions not supported 161 Subscription Identifiers not supported 162 Wildcard Subscriptions not supported On the contrary, UNSUBACK doesn't have them. 3.11.3 UNSUBACK Payload Table 3â9 - Unsubscribe Reason Codes https://docs.oasis-open.org/mqtt/mqtt/v5.0/os/mqtt-v5.0-os.html#_Toc3901194 It is reasonable that UNSUBACK doesn't have "Subscription Identifiers not supported" because UNSUBSCRIBE cannot have Subscription Identifier property. However, UNSUBSCRIBE could have $shhare/sharename, and wildcards. So UNSUBACK should have the following reason code: 158 Shared Subscriptions not supported 162 Wildcard Subscriptions not supported Any ideas? ---- Thanks, Takatoshi
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]