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

Expectations of timing accuracy in MQTT implementations

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Minor
    • Resolution: No Action
    • Affects Version/s: 5
    • Fix Version/s: None
    • Component/s: core
    • Labels:
      None
    • Proposal:
      Hide

      Non-normative.

      In this specification time intervals in seconds are used to indicate when some future event should occur, such as the Keep Alive time.
      These intervals specify the minimum time before the event will occur, with no assurance of the exact time interval. It is likely that
      for relatively short time intervals, the margin of error will be greater than that for relatively large values.

      Show
      Non-normative. In this specification time intervals in seconds are used to indicate when some future event should occur, such as the Keep Alive time. These intervals specify the minimum time before the event will occur, with no assurance of the exact time interval. It is likely that for relatively short time intervals, the margin of error will be greater than that for relatively large values.

      Description

      There are a number of aspects of MQTT which involve timings, starting with the keepalive interval, and some new features introduced in MQTT 5 such as message expiration.

      These timers are denoted in seconds (I don't think we have any exceptions to that), but the implementation of those timers in both servers and clients may not actually be at the resolution of small numbers of seconds. I suggest that we include some wording to limit the expectation of accuracy when a small number of seconds is used on such a timer, where "small" is to be defined, but could be less than 10 for instance.

        Attachments

          Activity

            People

            • Assignee:
              icraggs Ian Craggs (Inactive)
              Reporter:
              icraggs Ian Craggs (Inactive)
            • Watchers:
              4 Start watching this issue

              Dates

              • Due:
                Created:
                Updated:
                Resolved: