Uploaded image for project: 'OASIS Message Queuing Telemetry Transport (MQTT) TC'
  1. OASIS Message Queuing Telemetry Transport (MQTT) TC
  2. MQTT-325

Use Disconnect RC 0x82 in place of Nack for incorrect Packet Id.

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 5, wd09
    • Fix Version/s: None
    • Component/s: edits
    • Labels:
      None
    • Proposal:
      Hide

      Use Disconnect RC 0x82 in place of ack return codes for invalid Packet Ids instead of return codes in PubRel 0x92, PubComp 0x92, and SubAck 0x91.

      Show
      Use Disconnect RC 0x82 in place of ack return codes for invalid Packet Ids instead of return codes in PubRel 0x92, PubComp 0x92, and SubAck 0x91.
    • Resolution:
      Hide

      Merge with MQTT 236 Consolidate handling of errors.

      Show
      Merge with MQTT 236 Consolidate handling of errors.

      Description

      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

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              Andrew_Banks Andrew Banks
            • Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: