mqtt message

Subject: [OASIS Issue Tracker] (MQTT-547) Consider whether current length encoding is acceptable

From: OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>
To: mqtt@lists.oasis-open.org
Date: Mon, 27 Apr 2020 15:33:00 +0000 (UTC)

Ian Craggs created MQTT-547:
-------------------------------

             Summary: Consider whether current length encoding is acceptable
                 Key: MQTT-547
                 URL: https://issues.oasis-open.org/browse/MQTT-547
             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
          Issue Type: Improvement
          Components: MQTT-SN
    Affects Versions: MQTT-SN-1.2
            Reporter: Ian Craggs


From 'suggestions for 1.3' comments.

The length encoding was extended for version 1.2 to support packets > 255 octets in length, in a backward compatible way.Â For packets of length > 255, the length field is 3 octets rather than optimally 2.

Some options:

1) Always use 2 octets for the length

2)Â Length field is 1 or 2 octets long.Â 0 to 6 in the first octet means there is a second octet. The length can be up to 6*256 + 255 (=1791).

3) the MQTT algorithm, perhaps restricted to fewer octets.



--
This message was sent by Atlassian Jira
(v8.3.3#803004)