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

Should Message Identifier be called as Packet Identifier

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 3.1.1
    • Fix Version/s: 3.1.1
    • Component/s: core
    • Labels:
      None
    • Proposal:
      Hide

      Replace the terms such as "Message Identifier" with "Packet Identifier" in all cases

      Show
      Replace the terms such as "Message Identifier" with "Packet Identifier" in all cases

      Description

      As Part of issue MQTT-17, it was proposed and agreed to use term "MQTT Control Packet" consistently and not "MQTT Command Message" in the specification.

      However this change causes a problem in understanding of another term "message Identifier". Comments and discussion may be needed on the use of word Message Identifier and if it should be called as Packet Identifier. I am opening this JIRA issue for further discussion in TC calls.

      example - from WD-04, line 383 - 385

      "A non zero message identifier (MessageId) MUST be present in the variable header of the following MQTT command messages: PUBLISH(where Qos!=0), PUBACK, PUBREC, PUBREL, PUBCOMP, SUBSCRIBE, SUBACK, UNSUBSCRIBE, UNSUBACK "

      In WD-05

      "A non zero message identifier (MessageId) MUST be present in the variable header of the following MQTT Control Packets: PUBLISH(where Qos!=0), PUBACK, PUBREC, PUBREL, PUBCOMP, SUBSCRIBE, SUBACK, UNSUBSCRIBE, UNSUBACK "

      Should message Identifier be called as Packet Identifier ?

        Attachments

          Activity

            People

            • Assignee:
              andrew_banks Andrew Banks (Inactive)
              Reporter:
              ragupta2 Rahul Gupta
            • Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: