[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (MQTT-325) Use Disconnect RC 0x82 in place of Nack for incorrect Packet Id.
Andrew Banks created MQTT-325: --------------------------------- Summary: Use Disconnect RC 0x82 in place of Nack for incorrect Packet Id. Key: MQTT-325 URL: https://issues.oasis-open.org/browse/MQTT-325 Project: OASIS Message Queuing Telemetry Transport (MQTT) TC Issue Type: Bug Components: core Affects Versions: 5, wd09 Reporter: Andrew Banks The following return codes amount to a protocol error: PubRel 0x92 PacketID not found PubComp 0x92 PacketID not found Suback 0x91 PacketID in use so we should send DISCONECT RC 0x82 Protocol error followed by network disconnect instead. Otherwise we risk corrupting data because either the client or server implementation is bad or their state has been corrupted. The same thing could happen on Publish / PubRec / PubAck , Unsunscribe/Unsuback as well. This is the same methodology as was adopted in Jira MQTT-311 -- This message was sent by Atlassian JIRA (v6.2.2#6258)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]