OASIS Message Queuing Telemetry Transport (MQTT) TCIcon indicating the project type

OASIS Message Queuing Telemetry Transport (MQTT) TC

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

Normative statement unrelated to conformance targets

    Details

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

      conformance

    • Proposal:
      Hide

      1. Remove the numbered conformance clause that appears at the start of 4.2 and replace with the following:

      The MQTT protocol requires an underlying transport that provides an ordered, lossless, stream of bytes from the Client to Server and Server to Client.

      2. Add the following sentence to section 7.1.1 (Server conformance target)

      A conformant Server MUST support the use of one or more underlying transport protocols that provide an ordered, lossless, stream of bytes from the Client to Server and Server to Client [MQTT-7.0.0.x]. However conformance does not depend on it supporting any specific transport protocols. A Server MAY support any of the transport protocols listed in Section 4.2, or any other transport protocol that meets the requirements of [MQTT-7.0.0.x]

      3. 2. Add the following sentence to section 7.12 (Client conformance target)

      A conformant Client MUST support the use of one or more underlying transport protocols that provide an ordered, lossless, stream of bytes from the Client to Server and Server to Client [MQTT-7.0.0.x]. However conformance does not depend on it supporting any specific transport protocols. A Client MAY support any of the transport protocols listed in Section 4.2, or any other transport protocol that meets the requirements of [MQTT-7.0.0.x]

      4. Move the reference to RFC 793 (TCP/IP) from section 1.2 (Normative references) to section 1.3 (Non-normative references)

      Show
      1. Remove the numbered conformance clause that appears at the start of 4.2 and replace with the following: The MQTT protocol requires an underlying transport that provides an ordered, lossless, stream of bytes from the Client to Server and Server to Client. 2. Add the following sentence to section 7.1.1 (Server conformance target) A conformant Server MUST support the use of one or more underlying transport protocols that provide an ordered, lossless, stream of bytes from the Client to Server and Server to Client [MQTT-7.0.0.x] . However conformance does not depend on it supporting any specific transport protocols. A Server MAY support any of the transport protocols listed in Section 4.2, or any other transport protocol that meets the requirements of [MQTT-7.0.0.x] 3. 2. Add the following sentence to section 7.12 (Client conformance target) A conformant Client MUST support the use of one or more underlying transport protocols that provide an ordered, lossless, stream of bytes from the Client to Server and Server to Client [MQTT-7.0.0.x] . However conformance does not depend on it supporting any specific transport protocols. A Client MAY support any of the transport protocols listed in Section 4.2, or any other transport protocol that meets the requirements of [MQTT-7.0.0.x] 4. Move the reference to RFC 793 (TCP/IP) from section 1.2 (Normative references) to section 1.3 (Non-normative references)
    • Resolution:
      Hide

      Resolved in WD21

      Show
      Resolved in WD21

      Description

      in 4.2:
      "The Network Connection used to transport the MQTT protocol MUST be an ordered, lossless, stream of bytes from the Client to Server and Server to Client [MQTT-4.2.0-1]."
      Which conformance target is responsible for this? If failing this requirement does not affect the conformance of any implementation (i.e. of any conformance target per conformance clauses) I suggest to make this a SHOULD.

        Attachments

          Activity

          Ascending order - Click to sort in descending order
          Hide
          Permalink
          peterniblett Peter Niblett (Inactive) added a comment -

          I have provided a proposal that makes both the Client and Server the targets of the requirement, and also makes it clear that they aren't required to support any specific protocol. Since it is such a global conformance point, I though it best to put the text in Chapter 7 rather than Chapter 4

          Show
          peterniblett Peter Niblett (Inactive) added a comment - I have provided a proposal that makes both the Client and Server the targets of the requirement, and also makes it clear that they aren't required to support any specific protocol. Since it is such a global conformance point, I though it best to put the text in Chapter 7 rather than Chapter 4
          Hide
          Permalink
          coppen Richard Coppen (Inactive) added a comment -

          TC accept proposal TC call 13.03.2014

          Show
          coppen Richard Coppen (Inactive) added a comment - TC accept proposal TC call 13.03.2014

            People

            • Assignee:
              peterniblett Peter Niblett (Inactive)
              Reporter:
              patrick Patrick Durusau
            • Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: