Should the unused DUP, QoS, and RETAIN flags be zero in the CONNECT message?

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Major
    • 3.1.1
    • Affects Version/s: None
    • Component/s: core
    • None
    • Hide

      The client MUST set DUP, QoS, and RETAIN flags be zero in the Connect message but the server is not required to check that they are zero.

      Show
      The client MUST set DUP, QoS, and RETAIN flags be zero in the Connect message but the server is not required to check that they are zero.
    • Hide

      i) Flag bits in the Connect header must be zero .
      ii) Server MUST check that they are zero.
      iii) All of these bits are reserved for future use.

      Show
      i) Flag bits in the Connect header must be zero . ii) Server MUST check that they are zero. iii) All of these bits are reserved for future use.

      Should the unused DUP, QoS, and RETAIN flags be zero in the MQTT Connect message? The current mqtt.org specification leaves this open. By
      specifying that they must be zero we make it possible to put them to some use in the future.
      See Draft 04.

            Assignee:
            Andrew Banks (Inactive)
            Reporter:
            Andrew Banks (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: