| =?UTF-8?B?R3JvdXBzIC0gT0FTSVNfTVFUVF9UQ19t?= =?UTF-8?B?aW51dGVzXzI1MDQyMDEzLnBkZiB1cGxv?= =?UTF-8?B?YWRlZA==?= |
2 |
2013-05-01 |
| =?UTF-8?B?R3JvdXBzIC0gRXZlbnQgIk1RVFQgVEMg?= =?UTF-8?B?TWVldGluZyAoQ29uZmVyZW5jZSBDYWxs?= =?UTF-8?B?KSIgYWRkZWQ=?= |
2 |
2013-05-01 |
| [OASIS Issue Tracker] Created: (MQTT-1) Flowing MQTT V3.1.1 protocol over a WebSocket |
1 |
2013-05-01 |
| [OASIS Issue Tracker] Commented: (MQTT-1) Flowing MQTT V3.1.1 protocol over a WebSocket |
5 |
2013-05-01 |
| [OASIS Issue Tracker] Created: (MQTT-2) UTF-8 for will messages |
1 |
2013-05-02 |
| [OASIS Issue Tracker] Commented: (MQTT-2) UTF-8 for will messages |
3 |
2013-05-02 |
| =?UTF-8?B?R3JvdXBzIC0gRXZlbnQgIkFuIGludHJv?= =?UTF-8?B?ZHVjdGlvbiB0byBNUVRUOiBvdmVydmll?= =?UTF-8?B?dyBhbmQgcmVmcmVzaGVyIiBhZGRlZA==?= |
1 |
2013-05-02 |
| [OASIS Issue Tracker] Created: (MQTT-3) Keep alive interval grace period. |
1 |
2013-05-02 |
| [OASIS Issue Tracker] Created: (MQTT-4) Flowing MQTT messages before CONNACK is received in the client. |
1 |
2013-05-07 |
| [OASIS Issue Tracker] Created: (MQTT-5) Should the unused DUP, QoS, and RETAIN flags be zero in the CONNECT message? |
1 |
2013-05-07 |
| [OASIS Issue Tracker] Commented: (MQTT-5) Should the unused DUP, QoS, and RETAIN flags be zero in the CONNECT message? |
3 |
2013-05-07 |
| [OASIS Issue Tracker] Commented: (MQTT-4) Flowing MQTT messages before CONNACK is received in the client. |
2 |
2013-05-07 |
| [OASIS Issue Tracker] Created: (MQTT-6) What should a server do if it receives a connect packet with and incorrect protocol name? |
1 |
2013-05-07 |
| [OASIS Issue Tracker] Created: (MQTT-7) Can the client and server store QoS=0 messages after a client using CleanSession=0 has disconnected? |
1 |
2013-05-07 |
| [OASIS Issue Tracker] Commented: (MQTT-6) What should a server do if it receives a connect packet with and incorrect protocol name? |
1 |
2013-05-07 |
| [OASIS Issue Tracker] Created: (MQTT-8) Create a new CONNACK return code to indicate that the CONNECT packet was malformed. |
1 |
2013-05-08 |
| [OASIS Issue Tracker] Created: (MQTT-9) If the Connect flags indicate that he user name exists but none is present in the payload treat this as a malformed CONNECT packet. |
1 |
2013-05-08 |
| Second working draft |
1 |
2013-05-08 |
| [OASIS Issue Tracker] Commented: (MQTT-7) Can the client and server store QoS=0 messages after a client using CleanSession=0 has disconnected? |
1 |
2013-05-08 |
| =?UTF-8?B?R3JvdXBzIC0gTVFUVCBUQyBKSVJBIE92?= =?UTF-8?B?ZXJ2aWV3IHVwbG9hZGVk?= |
1 |
2013-05-08 |
| =?UTF-8?B?R3JvdXBzIC0gRXZlbnQgIk1RVFQgVEMg?= =?UTF-8?B?TWVldGluZyAoQ29uZmVyZW5jZSBDYWxs?= =?UTF-8?B?KSIgbW9kaWZpZWQ=?= |
3 |
2013-05-08 |
| [OASIS Issue Tracker] Created: (MQTT-10) Should Qos=0 retained messages be persisted in the server? |
1 |
2013-05-12 |
| [OASIS Issue Tracker] Commented: (MQTT-10) Should Qos=0 retained messages be persisted in the server? |
1 |
2013-05-13 |
| [OASIS Issue Tracker] Updated: (MQTT-3) Keep alive interval grace period. |
1 |
2013-05-13 |
| [OASIS Issue Tracker] Updated: (MQTT-9) If the Connect flags indicate that he user name exists but none is present in the payload treat this as a malformed CONNECT packet. |
1 |
2013-05-13 |
| [OASIS Issue Tracker] Updated: (MQTT-2) UTF-8 for will messages |
1 |
2013-05-13 |
| [OASIS Issue Tracker] Updated: (MQTT-4) Flowing MQTT messages before CONNACK is received in the client. |
1 |
2013-05-13 |
| [OASIS Issue Tracker] Updated: (MQTT-6) What should a server do if it receives a connect packet with and incorrect protocol name? |
1 |
2013-05-13 |
| [OASIS Issue Tracker] Updated: (MQTT-5) Should the unused DUP, QoS, and RETAIN flags be zero in the CONNECT message? |
2 |
2013-05-13 |
| [OASIS Issue Tracker] Updated: (MQTT-8) Create a new CONNACK return code to indicate that the CONNECT packet was malformed. |
1 |
2013-05-13 |
| [OASIS Issue Tracker] Updated: (MQTT-7) Can the client and server store QoS=0 messages after a client using CleanSession=0 has disconnected? |
1 |
2013-05-13 |
| [OASIS Issue Tracker] Updated: (MQTT-1) Flowing MQTT V3.1.1 protocol over a WebSocket |
1 |
2013-05-13 |
| [OASIS Issue Tracker] Created: (MQTT-11) Length of client Identifier |
1 |
2013-05-13 |
| [OASIS Issue Tracker] Commented: (MQTT-11) Length of client Identifier |
5 |
2013-05-13 |
| [OASIS Issue Tracker] Created: (MQTT-12) CONNACK Topic name Compression response. |
1 |
2013-05-13 |
| =?UTF-8?B?R3JvdXBzIC0gRXZlbnQgIkFuIGludHJv?= =?UTF-8?B?ZHVjdGlvbiB0byBNUVRUOiBvdmVydmll?= =?UTF-8?B?dyBhbmQgcmVmcmVzaGVyIiBtb2RpZmll?= =?UTF-8?B?ZA==?= |
2 |
2013-05-15 |
| =?UTF-8?B?R3JvdXBzIC0gSW50cm9kdWN0aW9uIHRv?= =?UTF-8?B?IE1RVFQgdXBsb2FkZWQ=?= |
1 |
2013-05-16 |
| [OASIS Issue Tracker] Issue Comment Edited: (MQTT-11) Length of client Identifier |
2 |
2013-05-17 |
| [OASIS Issue Tracker] Created: (MQTT-13) Topic name has an upper length limit of 32,767 characters ? |
1 |
2013-05-20 |
| [OASIS Issue Tracker] Commented: (MQTT-13) Topic name has an upper length limit of 32,767 characters ? |
3 |
2013-05-20 |
| [OASIS Issue Tracker] Created: (MQTT-14) Tighten up language in Quality of Service levels and flows |
1 |
2013-05-20 |
| [OASIS Issue Tracker] Updated: (MQTT-13) Topic name has an upper length limit of 32,767 characters ? |
2 |
2013-05-20 |
| [OASIS Issue Tracker] Commented: (MQTT-14) Tighten up language in Quality of Service levels and flows |
1 |
2013-05-21 |
| [OASIS Issue Tracker] Updated: (MQTT-14) Tighten up language in Quality of Service levels and flows |
1 |
2013-05-21 |
| =?UTF-8?B?R3JvdXBzIC0gT0FTSVNfTVFUVF9UQ19t?= =?UTF-8?B?aW51dGVzXzA5MDUyMDEzLnBkZiB1cGxv?= =?UTF-8?B?YWRlZA==?= |
1 |
2013-05-21 |
| =?UTF-8?B?Q2FsbCBmb3IgQWdlbmRhIGl0ZW1z?= |
1 |
2013-05-21 |
| [OASIS Issue Tracker] Created: (MQTT-15) Should the CONNECT packet Protocol Name and Protocol Version fields be changed? |
2 |
2013-05-22 |
| [OASIS Issue Tracker] Commented: (MQTT-15) Should the CONNECT packet Protocol Name and Protocol Version fields be changed? |
1 |
2013-05-22 |
| [OASIS Issue Tracker] Created: (MQTT-16) Reserve $SYS topic name |
1 |
2013-05-22 |
| [OASIS Issue Tracker] Updated: (MQTT-16) Reserve $SYS topic name |
1 |
2013-05-23 |
| [OASIS Issue Tracker] Commented: (MQTT-16) Reserve $SYS topic name |
4 |
2013-05-23 |
| =?UTF-8?B?R3JvdXBzIC0gRXZlbnQgIk1RVFQgVEMg?= =?UTF-8?B?TWVldGluZyIgbW9kaWZpZWQ=?= |
1 |
2013-05-23 |
| [OASIS Issue Tracker] Issue Comment Edited: (MQTT-16) Reserve $SYS topic name |
1 |
2013-05-23 |
| [OASIS Issue Tracker] Commented: (MQTT-8) Create a new CONNACK return code to indicate that the CONNECT packet was malformed. |
2 |
2013-05-23 |
| [OASIS Issue Tracker] Commented: (MQTT-9) If the Connect flags indicate that he user name exists but none is present in the payload treat this as a malformed CONNECT packet. |
1 |
2013-05-23 |
| [OASIS Issue Tracker] Created: (MQTT-17) Terminology for MQTT command message. |
1 |
2013-05-23 |
| [OASIS Issue Tracker] Created: (MQTT-18) Clarifying what MQTT means by storing data. |
1 |
2013-05-28 |
| [OASIS Issue Tracker] Created: (MQTT-19) How Retained publications are deleted. |
1 |
2013-05-28 |
| [OASIS Issue Tracker] Updated: (MQTT-18) Clarifying what MQTT means by storing data. |
1 |
2013-05-28 |
| [OASIS Issue Tracker] Created: (MQTT-20) Length of strings. |
1 |
2013-05-28 |
| [OASIS Issue Tracker] Updated: (MQTT-20) Length of strings. |
1 |
2013-05-28 |
| [OASIS Issue Tracker] Created: (MQTT-21) Use of flag bits in general. |
1 |
2013-05-28 |
| [OASIS Issue Tracker] Commented: (MQTT-19) How Retained publications are deleted. |
6 |
2013-05-28 |
| =?UTF-8?B?R3JvdXBzIC0gRXZlbnQgIk1RVFQgVEMg?= =?UTF-8?B?TWVldGluZyIgYWRkZWQ=?= |
1 |
2013-05-31 |
| =?UTF-8?B?R3JvdXBzIC0gT0FTSVNfTVFUVF9UQ19t?= =?UTF-8?B?aW51dGVzXzIzMDUyMDEzLnBkZiB1cGxv?= =?UTF-8?B?YWRlZA==?= |
1 |
2013-05-31 |
