Details

    • Type: Improvement
    • Status: Applied
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: MQTT-SN-1.2
    • Fix Version/s: wd04
    • Component/s: MQTT-SN
    • Labels:
      None
    • Proposal:
      Hide

      Section should read;

      5.4.18 UNSUBACK

      Length MsgType MsgId ReturnCode
      (octet 0) (1) (2-3) (4)

      Table 21: UNSUBACK Message
      An UNSUBACK message is sent by a GW to acknowledge the receipt and processing of an UNSUBSCRIBE message. Its format is illustrated in Table 21:

      • Length and MsgType: see Section 5.2.
      • MsgId: same value as the one contained in the corresponding UNSUBSCRIBE message.
      • ReturnCode: “accepted”, or rejection reason. See section 5.3.10.
      Show
      Section should read; 5.4.18 UNSUBACK Length MsgType MsgId ReturnCode (octet 0) (1) (2-3) (4) Table 21: UNSUBACK Message An UNSUBACK message is sent by a GW to acknowledge the receipt and processing of an UNSUBSCRIBE message. Its format is illustrated in Table 21: Length and MsgType: see Section 5.2. MsgId: same value as the one contained in the corresponding UNSUBSCRIBE message. ReturnCode: “accepted”, or rejection reason. See section 5.3.10.

      Description

      The MQTT-SN SUBACK packet includes a return code. As in MQTT 3.1.1, the UNSUBACK packet does not. It would seem sensible to add a return code to every ack. I think the UNSUBACK is the only one without. This would mirror MQTT 5.0 too.

        Attachments

          Activity

            People

            • Assignee:
              simon.johnson Simon Johnson [X] (Inactive)
              Reporter:
              ian.craggs Ian Craggs
            • Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: