[OASIS Issue Tracker] (MQTT-558) Short topic names allowed formats

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

     [ https://issues.oasis-open.org/browse/MQTT-558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Simon Johnson updated MQTT-558:
-------------------------------
    Proposal: 
Add a new implementation section;

7.5 Integer Formats
Two Byte Integer data values are 16-bit unsigned integers in big-endian order: the high order byte precedes the lower order byte. This means that a 16-bit word is presented on the network as Most Significant Byte (MSB), followed by Least Significant Byte (LSB).

  was:
A âshortâ topic name is a topic represented with a Two Byte Integer that does not require registration before use.
Two Byte Integer data values are 16-bit unsigned integers in big-endian order: the high order byte precedes the lower order byte. This means that a 16-bit word is presented on the network as Most Significant Byte (MSB), followed by Least Significant Byte (LSB).


> Short topic names allowed formats
> ---------------------------------
>
>                 Key: MQTT-558
>                 URL: https://issues.oasis-open.org/browse/MQTT-558
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: Improvement
>          Components: MQTT-SN
>    Affects Versions: MQTT-SN-1.2
>            Reporter: Simon Johnson
>            Assignee: Simon Johnson
>            Priority: Minor
>
> The format allows 2 octets for short topic names. The same 2 octets that are encoded as 16 bit topicIds in BE.
> When in short topic name mode, should the topicId be decoded or read as string data. Further should single char short topic names be allowed, and if so I assume they should be zero padded. 



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