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

Vague treatment of "at most once"

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Won't Fix
    • Affects Version/s: 3.1.1
    • Fix Version/s: 3.1.1
    • Component/s: core
    • Labels:
      None
    • Environment:

      Technical

    • Proposal:
      Hide

      Modify normative statement [MQTT-3.8.4-6] to make 'at most once' to mean 'at most once' under Section 3.8.4

      Remove >>The server is permitted to send duplicate copies of a message to a subscriber in the case where the original message was published with QoS 1 and the maximum QoS granted was QoS 0.[MQTT-3.8.4-6] <<

      Replace with:

      To avoid the risk of duplicate messages being published to QoS 0 subscribers, the Server MUST NOT forward a message to a QoS 0 subscriber if the message arrived with QoS 1 and the duplicate flag was set to 1. [MQTT-3.8.4-6]

      Remove the following sentence in the non-normative comments (line 1213 in CSD):

      "A QoS 1 Message published to the same topic might either get lost or duplicated on its transmission to that Client."

      Show
      Modify normative statement [MQTT-3.8.4-6] to make 'at most once' to mean 'at most once' under Section 3.8.4 Remove >>The server is permitted to send duplicate copies of a message to a subscriber in the case where the original message was published with QoS 1 and the maximum QoS granted was QoS 0. [MQTT-3.8.4-6] << Replace with: To avoid the risk of duplicate messages being published to QoS 0 subscribers, the Server MUST NOT forward a message to a QoS 0 subscriber if the message arrived with QoS 1 and the duplicate flag was set to 1. [MQTT-3.8.4-6] Remove the following sentence in the non-normative comments (line 1213 in CSD): "A QoS 1 Message published to the same topic might either get lost or duplicated on its transmission to that Client."
    • Resolution:
      Hide

      No Action TC meeting 06.03.2014

      Dup of MQTT-102 previous discussed by TC, the spec is clear that in one edge case duplicates might be delivered to QoS 0 subscribers.

      Show
      No Action TC meeting 06.03.2014 Dup of MQTT-102 previous discussed by TC, the spec is clear that in one edge case duplicates might be delivered to QoS 0 subscribers.

      Description

      In 4.3.1 4.3.1 QoS 0: At most once delivery:
      "The message arrives at the receiver either once or not at all."
      At most once delivery raises expectations about making sure no message is delivered twice.
      It is unclear how duplicates of a messages are prevented from "arriving". What mechanism allows for that QoS aspect? (i.e. duplicate elimination). If there is no explicit provision for eliminating duplicates, aren't we rather talking of more simply "Best effort" semantics?

        Attachments

          Activity

            People

            • Assignee:
              coppen Richard Coppen (Inactive)
              Reporter:
              patrick Patrick Durusau
            • Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: