mqtt

← back

39 messages · 24 threads

Thread Messages Started
[OASIS Issue Tracker] (MQTT-539) TopicId in PUBACK is superfluous 2 2020-04-27
[OASIS Issue Tracker] (MQTT-540) Messages shorter than 256 octets may use the 1-octet format 3 2020-04-27
[OASIS Issue Tracker] (MQTT-541) Cleansession should act like MQTT 5.0 not 3.1.1 2 2020-04-27
[OASIS Issue Tracker] (MQTT-542) Allow 0-length client id 2 2020-04-27
[OASIS Issue Tracker] (MQTT-543) Allow long topic names for publish of all QoS 2 2020-04-27
[OASIS Issue Tracker] (MQTT-544) Add return code to UNSUBACK 2 2020-04-27
[OASIS Issue Tracker] (MQTT-545) Remove retained messages by sending QoS 0 0 length publish 1 2020-04-27
[OASIS Issue Tracker] (MQTT-546) Improve description of sleeping clients message flows 3 2020-04-27
[OASIS Issue Tracker] (MQTT-547) Consider whether current length encoding is acceptable 1 2020-04-27
[OASIS Issue Tracker] (MQTT-548) Clarify when sessions are cleaned up for sleeping clients 1 2020-04-27
[OASIS Issue Tracker] (MQTT-549) Remove the discovery procedure 3 2020-04-27
[OASIS Issue Tracker] (MQTT-550) Mandate the use of separate id spaces for device normal topic alias's 4 2020-04-28
[OASIS Issue Tracker] (MQTT-551) Discussion about predefined topicId values being allowed to match normal topicId values 1 2020-04-28
[OASIS Issue Tracker] (MQTT-552) Should a broker prohibit publish -1 messages from sleeping clients 1 2020-04-28
[OASIS Issue Tracker] (MQTT-553) Clarify whether clients should maintain normal topicIds during sleep state 1 2020-04-28
[OASIS Issue Tracker] (MQTT-554) Should QoS 0 messages be held on a message queue during sleep cycle 1 2020-04-28
[OASIS Issue Tracker] (MQTT-555) Clarification of broker behaviour when client REGISTERs a PREDEFINED topic 1 2020-04-28
[OASIS Issue Tracker] (MQTT-556) Clarification of broker behaviour when REGISTER issued on a 2 byte topic name 2 2020-04-28
[OASIS Issue Tracker] (MQTT-551) Clarification as to whether predefined topicId values are allowed to match normal topicId values 1 2020-04-28
[OASIS Issue Tracker] (MQTT-557) Should REGACK be expanded to support multiple topicIdTypes 1 2020-04-28
[OASIS Issue Tracker] (MQTT-558) Short topic names allowed formats 1 2020-04-28
[OASIS Issue Tracker] (MQTT-559) DISCONNECT duration 16-bit field does not allow long enough to sleep 1 2020-04-28
[OASIS Issue Tracker] (MQTT-560) Error codes need consideration, both quantity and location. 1 2020-04-28
[OASIS Issue Tracker] (MQTT-561) Introduce a broker Timer to monitor sleeping ping flush 1 2020-04-28