Details

    • Type: New Feature
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: wd04, 5
    • Fix Version/s: 5, wd10
    • Component/s: core
    • Labels:
    • Proposal:
      Hide

      Section 3.14.1 add
      "A Client or Server send a DISCONNECT indicating a malformed packet rc=0x81 in response to a malformed DISCONNECT packet.

      Show
      Section 3.14.1 add "A Client or Server send a DISCONNECT indicating a malformed packet rc=0x81 in response to a malformed DISCONNECT packet.
    • Resolution:
      Hide

      Updated WD10

      Show
      Updated WD10

      Description

      Proposed textual addition to WD04 following review of MQTT-270 (Server Initiated Disconnect) which has been closed.

      WD04 Section 3.14.1 describes the DISCONNECT command packet fixed header. Line 1798 says
      "The Client or Server MUST validate that the reserved bits are set to zero and close the Network Connection if they are not zero."

      As a precaution I propose we should add
      "A Client or Server MUST NOT send a DISCONNECT in response to a malformed DISCONNECT."

      Rationale: The DISCONNECT error table in table 3.13 includes values for MALFORMED CONTROL PACKET and PROTOCOL ERROR. Sending a DISCONNECT in response to a malformed DISCONNECT introduces the possibility of an endless cycle. (i.e. the two session partners disagree on the format of the disconnect and reject each others disconnects.)

        Attachments

          Activity

          Hide
          ken.borgendale Ken Borgendale (Inactive) added a comment -

          I do not understand the requirement for this. After sending a DISCONNECT the sender is required to close the connection. We certainly could in any case have DISCONNECT packets are flowing in both directions, but this does not cause any problems.

          I suggest we reject this JIRA

          Show
          ken.borgendale Ken Borgendale (Inactive) added a comment - I do not understand the requirement for this. After sending a DISCONNECT the sender is required to close the connection. We certainly could in any case have DISCONNECT packets are flowing in both directions, but this does not cause any problems. I suggest we reject this JIRA
          Hide
          ken.borgendale Ken Borgendale (Inactive) added a comment -

          Issue included in MQTTv5.0 CS01 December 25, 2017

          Show
          ken.borgendale Ken Borgendale (Inactive) added a comment - Issue included in MQTTv5.0 CS01 December 25, 2017

            People

            • Assignee:
              andrew_banks Andrew Banks (Inactive)
              Reporter:
              edbriggs Ed Briggs [X] (Inactive)
            • Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: