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

Improvements of the description of Disconnect Reason Code values

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Trivial
    • Resolution: Fixed
    • Affects Version/s: 5, wd14
    • Fix Version/s: 5, wd15
    • Component/s: edits
    • Labels:
      None
    • Proposal:
      Hide

      RC 137: accepted
      RC 142: The new connection already exists so the words are corrrect
      RC 150: Change to "The received data rate is too high". We do not actually otherwise define this RC, and thus we do not define the basis on which the receiver determines that the rate is too high.
      RC 159: The present perfect (is closed) is correct in this case. Although the receive of the DISCONNECT and the closing of the connection are asynchronous events, it is likely that the close is done before the DISCONNECT is received. In any case, the present perfect indicates that they are closely coincident in time.

      I would prefer not to renumber reason codes at this time. We have stated there is no meaning to the codes. There were mostly assigned with similar RCs together, but often that means blocks of server only RCs together.

      Show
      RC 137: accepted RC 142: The new connection already exists so the words are corrrect RC 150: Change to "The received data rate is too high". We do not actually otherwise define this RC, and thus we do not define the basis on which the receiver determines that the rate is too high. RC 159: The present perfect (is closed) is correct in this case. Although the receive of the DISCONNECT and the closing of the connection are asynchronous events, it is likely that the close is done before the DISCONNECT is received. In any case, the present perfect indicates that they are closely coincident in time. I would prefer not to renumber reason codes at this time. We have stated there is no meaning to the codes. There were mostly assigned with similar RCs together, but often that means blocks of server only RCs together.

      Description

      Line 2772: Table 3-13 – Disconnect Reason Code values

      Description of code 137: cannot continue processing this Client. --> cannot continue processing requests from this Client.
      Description of code 142: has connected --> is being established
      Description of code 150: "The rate of publish": does it mean "publish" specifically or is it better to say "The rate of messages"
      Description of code 159: connection is closed --> connection is being closed

      Is it possible to rearrange the codes, so that 158, 161 and 162 are next to each other, and 159 is next to 150 and 151?

      These issues were originally reported in MQTT-417, but they don't seem to be applied in WD14.

        Attachments

          Activity

            People

            • Assignee:
              ken.borgendale Ken Borgendale (Inactive)
              Reporter:
              kdot Konstantin Dotchkoff [X] (Inactive)
            • Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: