• Type: Bug
    • Resolution: Fixed
    • Priority: Minor
    • None
    • Affects Version/s: 3.1.1
    • Component/s: edits
    • None
    • Environment:

      Technical Content Quality

    • Hide

      An MQTT implementation MAY conform as both an MQTT Client and MQTT Server implementation. A Server that both accepts inbound connections and establishes outbound connections to other Servers MUST conform as both an MQTT Client and MQTT Server. [MQTT-7.0.0-1]

      1. The format of all Control Packets that the Server sends matches the format described in Chapters 2 and 3.

      1. The format of all Control Packets that the Client sends matches the format described in chapters 2 and 3

      Show
      An MQTT implementation MAY conform as both an MQTT Client and MQTT Server implementation. A Server that both accepts inbound connections and establishes outbound connections to other Servers MUST conform as both an MQTT Client and MQTT Server. [MQTT-7.0.0-1] 1. The format of all Control Packets that the Server sends matches the format described in Chapters 2 and 3. 1. The format of all Control Packets that the Client sends matches the format described in chapters 2 and 3
    • Hide

      Resolved in WD18

      Show
      Resolved in WD18

      At several places in Conformance clause, the terminology is vague:

      • "A single entity MAY conform ..." What is an entity? never used before.Rather an "implementation"?
      • "The syntax of all Control Packets that it sends matches the syntax d..."
        this is the first time "syntax" is used in this specification. Isn't that rather the "Format"? Instead of "matches the syntax " --> "conforms to the format"?

            Assignee:
            Unassigned
            Reporter:
            Jacques Durand (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: