Packet format vs Implementation behavior

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major
    • None
    • Affects Version/s: 3.1.1
    • Component/s: edits
    • None
    • Environment:

      structure

    • Hide

      Move the description of DUP, Qos, RETAIN from chapter 2 to PUBLISH in section 3. This makes the content of chapter 2 a generic description of control packets. I left the title of Chapters 2,3 unchanged as some statements in 3 have already been moved into 4 where we consolidated the description of the QoS flows..

      Show
      Move the description of DUP, Qos, RETAIN from chapter 2 to PUBLISH in section 3. This makes the content of chapter 2 a generic description of control packets. I left the title of Chapters 2,3 unchanged as some statements in 3 have already been moved into 4 where we consolidated the description of the QoS flows..
    • Hide

      Fixed in WD23

      Show
      Fixed in WD23

      In Section 2 (supposed to be about MQTT Control Packet Format ) there are many requirements like MQTT-2.1.2-6 (in 2.1.2.3) that are more about Client/Server behavior and seem to belong more to "Operational" section 4. Unless they are moved under 4, I'd suggest to broaden the title of Section 2 to: "MQTT Control Packet Format and Semantics" or the like. Same for Section 3: add "... and Semantics" to title, or explain more clearly the difference between behavioral requirements found in Section 4 compared with section 2 & 3.

            Assignee:
            Unassigned
            Reporter:
            Patrick Durusau
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: