| 00000 |
[OASIS Issue Tracker] (MQTT-539) TopicId in PUBACK is superfluous |
OASIS Issues Tracker
|
2020-04-27 13:40 |
| 00001 |
[OASIS Issue Tracker] (MQTT-539) TopicId in PUBACK is superfluous |
OASIS Issues Tracker
|
2020-04-27 13:42 |
| 00002 |
[OASIS Issue Tracker] (MQTT-540) Messages shorter than 256 octets may use the 1-octet format |
OASIS Issues Tracker
|
2020-04-27 14:02 |
| 00003 |
[OASIS Issue Tracker] (MQTT-540) Messages shorter than 256 octets may use the 1-octet format |
OASIS Issues Tracker
|
2020-04-27 14:03 |
| 00004 |
[OASIS Issue Tracker] (MQTT-541) Cleansession should act like MQTT 5.0 not 3.1.1 |
OASIS Issues Tracker
|
2020-04-27 14:18 |
| 00005 |
[OASIS Issue Tracker] (MQTT-542) Allow 0-length client id |
OASIS Issues Tracker
|
2020-04-27 14:20 |
| 00006 |
[OASIS Issue Tracker] (MQTT-543) Allow long topic names for publish of all QoS |
OASIS Issues Tracker
|
2020-04-27 14:23 |
| 00007 |
[OASIS Issue Tracker] (MQTT-544) Add return code to UNSUBACK |
OASIS Issues Tracker
|
2020-04-27 14:24 |
| 00008 |
[OASIS Issue Tracker] (MQTT-545) Remove retained messages by sending QoS 0 0 length publish |
OASIS Issues Tracker
|
2020-04-27 15:08 |
| 00009 |
[OASIS Issue Tracker] (MQTT-546) Improve description of sleeping clients message flows |
OASIS Issues Tracker
|
2020-04-27 15:23 |
| 00010 |
[OASIS Issue Tracker] (MQTT-547) Consider whether current length encoding is acceptable |
OASIS Issues Tracker
|
2020-04-27 15:33 |
| 00011 |
[OASIS Issue Tracker] (MQTT-548) Clarify when sessions are cleaned up for sleeping clients |
OASIS Issues Tracker
|
2020-04-27 15:37 |
| 00012 |
[OASIS Issue Tracker] (MQTT-549) Remove the discovery procedure |
OASIS Issues Tracker
|
2020-04-27 15:40 |
| 00013 |
[OASIS Issue Tracker] (MQTT-549) Remove the discovery procedure |
OASIS Issues Tracker
|
2020-04-27 15:44 |
| 00014 |
[OASIS Issue Tracker] (MQTT-549) Remove the discovery procedure |
OASIS Issues Tracker
|
2020-04-27 15:44 |
| 00015 |
[OASIS Issue Tracker] (MQTT-546) Improve description of sleeping clients message flows |
OASIS Issues Tracker
|
2020-04-28 13:25 |
| 00016 |
[OASIS Issue Tracker] (MQTT-546) Improve description of sleeping clients message flows |
OASIS Issues Tracker
|
2020-04-28 13:47 |
| 00017 |
[OASIS Issue Tracker] (MQTT-550) Mandate the use of separate id spaces for device normal topic alias's |
OASIS Issues Tracker
|
2020-04-28 14:19 |
| 00018 |
[OASIS Issue Tracker] (MQTT-550) Mandate the use of separate id spaces for device normal topic alias's |
OASIS Issues Tracker
|
2020-04-28 14:19 |
| 00019 |
[OASIS Issue Tracker] (MQTT-550) Mandate the use of separate id spaces for device normal topic alias's |
OASIS Issues Tracker
|
2020-04-28 14:20 |
| 00020 |
[OASIS Issue Tracker] (MQTT-551) Discussion about predefined topicId values being allowed to match normal topicId values |
OASIS Issues Tracker
|
2020-04-28 14:30 |
| 00021 |
[OASIS Issue Tracker] (MQTT-552) Should a broker prohibit publish -1 messages from sleeping clients |
OASIS Issues Tracker
|
2020-04-28 14:34 |
| 00022 |
[OASIS Issue Tracker] (MQTT-550) Mandate the use of separate id spaces for device normal topic alias's |
OASIS Issues Tracker
|
2020-04-28 14:45 |
| 00023 |
[OASIS Issue Tracker] (MQTT-553) Clarify whether clients should maintain normal topicIds during sleep state |
OASIS Issues Tracker
|
2020-04-28 14:50 |
| 00024 |
[OASIS Issue Tracker] (MQTT-554) Should QoS 0 messages be held on a message queue during sleep cycle |
OASIS Issues Tracker
|
2020-04-28 14:54 |
| 00025 |
[OASIS Issue Tracker] (MQTT-555) Clarification of broker behaviour when client REGISTERs a PREDEFINED topic |
OASIS Issues Tracker
|
2020-04-28 15:07 |
| 00026 |
[OASIS Issue Tracker] (MQTT-556) Clarification of broker behaviour when REGISTER issued on a 2 byte topic name |
OASIS Issues Tracker
|
2020-04-28 15:15 |
| 00027 |
[OASIS Issue Tracker] (MQTT-556) Clarification of broker behaviour when REGISTER issued on a 2 byte topic name |
OASIS Issues Tracker
|
2020-04-28 15:17 |
| 00028 |
[OASIS Issue Tracker] (MQTT-551) Clarification as to whether predefined topicId values are allowed to match normal topicId values |
OASIS Issues Tracker
|
2020-04-28 15:20 |
| 00029 |
[OASIS Issue Tracker] (MQTT-557) Should REGACK be expanded to support multiple topicIdTypes |
OASIS Issues Tracker
|
2020-04-28 15:23 |
| 00030 |
[OASIS Issue Tracker] (MQTT-558) Short topic names allowed formats |
OASIS Issues Tracker
|
2020-04-28 15:30 |
| 00031 |
[OASIS Issue Tracker] (MQTT-559) DISCONNECT duration 16-bit field does not allow long enough to sleep |
OASIS Issues Tracker
|
2020-04-28 15:34 |
| 00032 |
[OASIS Issue Tracker] (MQTT-560) Error codes need consideration, both quantity and location. |
OASIS Issues Tracker
|
2020-04-28 15:37 |
| 00033 |
[OASIS Issue Tracker] (MQTT-561) Introduce a broker Timer to monitor sleeping ping flush |
OASIS Issues Tracker
|
2020-04-28 15:43 |
| 00034 |
[OASIS Issue Tracker] (MQTT-540) Messages shorter than 256 octets may use the 1-octet format |
OASIS Issues Tracker
|
2020-04-28 15:50 |
| 00035 |
[OASIS Issue Tracker] (MQTT-541) Cleansession should act like MQTT 5.0 not 3.1.1 |
OASIS Issues Tracker
|
2020-04-28 16:03 |
| 00036 |
[OASIS Issue Tracker] (MQTT-542) Allow 0-length client id |
OASIS Issues Tracker
|
2020-04-28 16:04 |
| 00037 |
[OASIS Issue Tracker] (MQTT-543) Allow long topic names for publish of all QoS |
OASIS Issues Tracker
|
2020-04-28 16:21 |
| 00038 |
[OASIS Issue Tracker] (MQTT-544) Add return code to UNSUBACK |
OASIS Issues Tracker
|
2020-04-28 16:22 |
