| Congrats on a successful webinar yesterday |
1 |
2020-06-04 |
| =?UTF-8?B?TVFUVC1TTiB1cGRhdGUgYW5kIGNhbmRp?= =?UTF-8?B?ZGF0ZSBNUVRUIExvZ28gcmV2aWV3?= |
1 |
2020-06-05 |
| Re: [mqtt-comment] MQTT-SN update and candidate MQTT Logo review |
2 |
2020-06-12 |
| =?UTF-8?B?R3JvdXBzIC0gTWludXRlcyBvZiBUQyBN?= =?UTF-8?B?ZWV0aW5nIDEydGggRmViIDIwMjAgdXBs?= =?UTF-8?B?b2FkZWQ=?= |
1 |
2020-06-12 |
| =?UTF-8?B?TVFUVCBUQyBjYWxsIChDb25mZXJlbmNl?= =?UTF-8?B?IENhbGwp?= |
1 |
2020-06-12 |
| [OASIS Issue Tracker] (MQTT-567) Should ping in connected mode work the same as in sleep mode |
3 |
2020-06-17 |
| [OASIS Issue Tracker] (MQTT-556) Clarification of broker behaviour when REGISTER issued on a 2 byte topic name |
1 |
2020-06-17 |
| [OASIS Issue Tracker] (MQTT-539) TopicId in PUBACK is superfluous |
1 |
2020-06-17 |
| [OASIS Issue Tracker] (MQTT-557) Should REGACK be expanded to support multiple topicIdTypes |
1 |
2020-06-17 |
| [OASIS Issue Tracker] (MQTT-558) Short topic names allowed formats |
1 |
2020-06-17 |
| [OASIS Issue Tracker] (MQTT-552) Should a broker prohibit publish -1 messages from sleeping clients |
2 |
2020-06-17 |
| [OASIS Issue Tracker] (MQTT-559) DISCONNECT duration 16-bit field does not allow long enough to sleep |
1 |
2020-06-17 |
| [OASIS Issue Tracker] (MQTT-563) Client Id format |
1 |
2020-06-17 |
| [OASIS Issue Tracker] (MQTT-568) Authentication |
1 |
2020-06-17 |
| [OASIS Issue Tracker] (MQTT-560) Error codes need consideration, both quantity and location. |
1 |
2020-06-17 |
| [OASIS Issue Tracker] (MQTT-569) Firmware updates |
1 |
2020-06-17 |
| [OASIS Issue Tracker] (MQTT-565) Shared subscription delivery behaviour where QoS differs |
1 |
2020-06-22 |
| [OASIS Issue Tracker] (MQTT-564) MQTT 5.0 behaviour for Request Problem Information |
3 |
2020-06-23 |
| =?UTF-8?B?QmFsbG90IG5vdyBvcGVuIHRvIGFwcHJv?= =?UTF-8?B?dmUgTVFUVCBMb2dv?= |
1 |
2020-06-23 |
| =?UTF-8?B?R3JvdXBzIC0gTWludXRlcyBvZiBNUVRU?= =?UTF-8?B?LVNOIFNDIG1lZXRpbmcgMTh0aCBKdW5l?= =?UTF-8?B?IDIwMjAgdXBsb2FkZWQ=?= |
1 |
2020-06-27 |
