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

Clarify "store data", and more generally make normative statements self-explanatory (as much as possible)

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 3.1.1
    • Fix Version/s: None
    • Component/s: core
    • Labels:
      None
    • Environment:

      Technical Content Quality

    • Proposal:
      Hide

      Replace words in Section 4.1 (Storing state) Prior to non-normative example.

      It is necessary for the Client and Server to store Session state in order to provide Quality of Service guarantees. The Client and Server MUST store Session state for the duration of the Session [MQTT-xyz]. A Session MUST last at least as long it has an active Network Connection [MQTT-xyz].

      Retained messages do not form part of the Session state in the Server. The Server SHOULD retain such messages until deleted by a Client.

      Non normative comment.
      The storage capabilities of Client and Server implementations will of course have limits in terms of capacity and may be subject to administrative policies such as the maximum time that Session state is stored between Network Connections. Stored Session state can be discarded as a result of an administrator action, including an automated response to defined conditions. This has the effect of terminating the Session. These actions might be prompted by resource constraints or for other operational reasons. It is prudent to evaluate the storage capabilities of the Client and Server to ensure that they are sufficient.

      Non normative comment.
      It is possible that hardware or software failures may result in loss or corruption of Session state stored by the Client or Server.

      >>> The non-normative example should stand <<<.

      Show
      Replace words in Section 4.1 (Storing state) Prior to non-normative example. It is necessary for the Client and Server to store Session state in order to provide Quality of Service guarantees. The Client and Server MUST store Session state for the duration of the Session [MQTT-xyz] . A Session MUST last at least as long it has an active Network Connection [MQTT-xyz] . Retained messages do not form part of the Session state in the Server. The Server SHOULD retain such messages until deleted by a Client. Non normative comment. The storage capabilities of Client and Server implementations will of course have limits in terms of capacity and may be subject to administrative policies such as the maximum time that Session state is stored between Network Connections. Stored Session state can be discarded as a result of an administrator action, including an automated response to defined conditions. This has the effect of terminating the Session. These actions might be prompted by resource constraints or for other operational reasons. It is prudent to evaluate the storage capabilities of the Client and Server to ensure that they are sufficient. Non normative comment. It is possible that hardware or software failures may result in loss or corruption of Session state stored by the Client or Server. >>> The non-normative example should stand <<<.
    • Resolution:
      Hide

      Fixed in WD21

      Show
      Fixed in WD21

      Description

      In 4.1:
      The Client and Server MUST store data for at least as long as the Network Connection lasts [MQTT-4.1.0-1].
      What kind of data are we talking about? Is it session state? Messages? both? need be more precise, especially within tagged normative statements that can be taken out of context, e.g. when referred by a test suite.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              patrick Patrick Durusau
            • Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: