MQTT 5.0 behaviour for Request Problem Information

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Major
    • None
    • Affects Version/s: 5
    • Component/s: core, edits
    • None

      Question from Takatoshi on MQTT Comments list

       

      I have a comment about the following part of MQTT Version 5.0 document:

      https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.oasis-2Dopen.org_mqtt_mqtt_v5.0_os_mqtt-2Dv5.0-2Dos.html-23-5FToc3901053&d=DwIFaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=HFOYf-FWdPMlPq2g5pc8M7HUYiSp2sC9P2hDoZdjdRo&m=jvexqqlWqfyLENYV-w-vdlZeZVUY9XTEHIAJKvZXxwo&s=GaNM7rm25khF8RtMPACWSQWGDvA7Mw4xE1MTuoQ28Xo&e=

       If the value of Request Problem Information is 0, the Server MAY return a Reason String or User Properties on a CONNACK or DISCONNECT packet, but MUST NOT send a Reason String or User Properties on any packet other than PUBLISH, CONNACK, or DISCONNECT [MQTT-3.1.2-29]. If the value is 0 and the Client receives a Reason String or User Properties in a packet other than PUBLISH, CONNACK, or DISCONNECT, it uses a DISCONNECT packet with Reason Code 0x82 (Protocol Error) as described in section 4.13 Handling errors.

      At first, the spec refer to CONNACK and DISCONNECT. But from the middle, PUBLISH is mixed.

      Which MQTT control packets can use Reason String and/or User
      Properties if Request Problem Information is 0 ?

      Thanks,
      Takatoshi

            Assignee:
            Unassigned
            Reporter:
            Richard Coppen (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: