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

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ https://issues.oasis-open.org/browse/MQTT-547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=76861#comment-76861 ] 

Allan Stockdill-Mander commented on MQTT-547:
---------------------------------------------

No appetite to change this from the current specification

> 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
>            Priority: Major
>
> 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)