Details

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

      A new content type descriptor identifier should be added to providing a content type property, which would be a UTF-8 string containing a MIME content type label as shown in RFC 2184 and RFC-2231.

      Show
      A new content type descriptor identifier should be added to providing a content type property, which would be a UTF-8 string containing a MIME content type label as shown in RFC 2184 and RFC-2231.

      Description

      MQTT 5.0 needs the ability to describe the payload content with a property that is not part of the payload for those systems which may not be able to reliably infer the content type from the payload field or topic alone. Such a need arises in larger system in which payloads may be encrypted or otherwise indecipherable to applications which may need to perform special processing on certain payload types. This may also occur if multiple applications are consolidated into a single system.

        Attachments

          Activity

          Hide
          edbriggs Ed Briggs [X] (Inactive) added a comment -

          Hi Ken,

          I'm not clear on your proposed change. Are you saying we should change the existing scheme (e.g. 0x01,

          {0x00, 0x01, 0x02}

          with a different scheme, or only in the case of the newly proposed content-type. (I have no problem with removing the term MIME and simply using ContentType).

          Show
          edbriggs Ed Briggs [X] (Inactive) added a comment - Hi Ken, I'm not clear on your proposed change. Are you saying we should change the existing scheme (e.g. 0x01, {0x00, 0x01, 0x02} with a different scheme, or only in the case of the newly proposed content-type. (I have no problem with removing the term MIME and simply using ContentType).
          Hide
          edbriggs Ed Briggs [X] (Inactive) added a comment -

          Ed Briggs to Bring this back to the next TC meeting for a vote. We ran out of time in the call.

          Show
          edbriggs Ed Briggs [X] (Inactive) added a comment - Ed Briggs to Bring this back to the next TC meeting for a vote. We ran out of time in the call.
          Hide
          brianraymor Brian Raymor [X] (Inactive) added a comment -

          Opened per discussion on 12/1 TC call.

          Show
          brianraymor Brian Raymor [X] (Inactive) added a comment - Opened per discussion on 12/1 TC call.
          Hide
          brianraymor Brian Raymor [X] (Inactive) added a comment -

          Resolved to editor per agreement on 12/1 TC call. Noting from the soaphub:

          MQTT-322, change proposal to include two properties: content-type and payload format. In addition, the server checking will be limited to checking if it's a valid UTF-8 string

          Show
          brianraymor Brian Raymor [X] (Inactive) added a comment - Resolved to editor per agreement on 12/1 TC call. Noting from the soaphub: MQTT-322 , change proposal to include two properties: content-type and payload format. In addition, the server checking will be limited to checking if it's a valid UTF-8 string
          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:
              edbriggs Ed Briggs [X] (Inactive)
              Reporter:
              edbriggs Ed Briggs [X] (Inactive)
            • Watchers:
              3 Start watching this issue

              Dates

              • Due:
                Created:
                Updated:
                Resolved: