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

Do we need packet id in DISCONNECT and AUTH packets?

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: MQTT-SN
    • Labels:
      None

      Description

      Packet id has been added to nearly all packets as a resolution to isse 619: https://issues.oasis-open.org/browse/MQTT-619. The only (unicast) packets that do not now have a packet id are DISCONNECT and AUTH.

      When DISCONNECT is sent by a client, it expects DISCONNECT as an acknowledgement to signal the Virtual Connection has ended. AUTH packets may be sent by the server as a response to the CONNECT or AUTH packets. So both of these can be responses to another packet, which according to the logic in issue 619, I believe means they need a packet id.

        Attachments

          Activity

            People

            • Assignee:
              ian.craggs Ian Craggs
              Reporter:
              ian.craggs Ian Craggs
            • Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: