| [OASIS Issue Tracker] Created: (MQTT-77) Should the Connect packet Useri Name and Password fields be binary rather than UTF-8 |
1 |
2013-09-03 |
| [OASIS Issue Tracker] Commented: (MQTT-77) Should the Connect packet Useri Name and Password fields be binary rather than UTF-8 |
2 |
2013-09-03 |
| [OASIS Issue Tracker] Commented: (MQTT-22) Specification is ambiguous with regards to dynamic topics |
4 |
2013-09-05 |
| [OASIS Issue Tracker] Updated: (MQTT-50) Handling of invalid CONNECT packets |
2 |
2013-09-05 |
| [OASIS Issue Tracker] Updated: (MQTT-54) How long should a client or server wait for, or expect to wait for, a response |
3 |
2013-09-05 |
| [OASIS Issue Tracker] Updated: (MQTT-22) Specification is ambiguous with regards to dynamic topics |
1 |
2013-09-05 |
| [OASIS Issue Tracker] Updated: (MQTT-68) Message delivery retry is not required where no network failure is detected |
3 |
2013-09-05 |
| [OASIS Issue Tracker] Created: (MQTT-78) Abstract references to the transport layer for MQTT |
1 |
2013-09-05 |
| [OASIS Issue Tracker] Commented: (MQTT-78) Abstract references to the transport layer for MQTT |
2 |
2013-09-05 |
| [OASIS Issue Tracker] Created: (MQTT-79) Allow deletion of QoS1/2 messages in rare circumstances |
1 |
2013-09-05 |
| [OASIS Issue Tracker] Created: (MQTT-80) Editorial issues following read through of WD10 |
1 |
2013-09-06 |
| MQTT Security Subcommittee - Security Content Proposal Submission |
1 |
2013-09-10 |
| =?UTF-8?B?U3RlcHMgdG8gQ1NE?= |
1 |
2013-09-10 |
| =?UTF-8?B?R3JvdXBzIC0gbXF0dC12My4xLjEtd2Qx?= =?UTF-8?B?MS5kb2MgdXBsb2FkZWQ=?= |
1 |
2013-09-11 |
| =?UTF-8?B?R3JvdXBzIC0gbXF0dC12My4xLjEtd2Qx?= =?UTF-8?B?MS5wZGYgdXBsb2FkZWQ=?= |
1 |
2013-09-11 |
| =?UTF-8?B?R3JvdXBzIC0gRXZlbnQgIk1RVFQgVEMg?= =?UTF-8?B?TWVldGluZyIgbW9kaWZpZWQ=?= |
4 |
2013-09-11 |
| [OASIS Issue Tracker] Commented: (MQTT-42) Clean session and random client ids |
3 |
2013-09-12 |
| [OASIS Issue Tracker] Updated: (MQTT-42) Clean session and random client ids |
1 |
2013-09-12 |
| =?UTF-8?B?SW1wb3J0YW50OiBXRUVLTFkgVEMgQ2Fs?= =?UTF-8?B?bHM=?= |
1 |
2013-09-12 |
| =?UTF-8?B?R3JvdXBzIC0gT0FTSVNfTVFUVF9UQ19t?= =?UTF-8?B?aW51dGVzXzEyMDkyMDEzLnBkZiB1cGxv?= =?UTF-8?B?YWRlZA==?= |
1 |
2013-09-13 |
| [OASIS Issue Tracker] Created: (MQTT-81) WD11 - typo in line 1161 |
1 |
2013-09-17 |
| [OASIS Issue Tracker] Updated: (MQTT-7) Can the client and server store QoS=0 messages after a client using CleanSession=0 has disconnected? |
2 |
2013-09-18 |
| [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-09-18 |
| [OASIS Issue Tracker] Created: (MQTT-82) Provide a way for clean-session=1 clients to specify no client identifier |
1 |
2013-09-18 |
| [OASIS Issue Tracker] Updated: (MQTT-16) Reserve $SYS topic name |
2 |
2013-09-18 |
| [OASIS Issue Tracker] Updated: (MQTT-10) Should Qos=0 retained messages be persisted in the server? |
1 |
2013-09-18 |
| [OASIS Issue Tracker] Commented: (MQTT-10) Should Qos=0 retained messages be persisted in the server? |
1 |
2013-09-18 |
| [OASIS Issue Tracker] Updated: (MQTT-8) Create a new CONNACK return code to indicate that the CONNECT packet was malformed. |
1 |
2013-09-18 |
| [OASIS Issue Tracker] Updated: (MQTT-1) Flowing MQTT V3.1.1 protocol over a WebSocket |
1 |
2013-09-18 |
| [OASIS Issue Tracker] Commented: (MQTT-79) Allow deletion of QoS1/2 messages in rare circumstances |
2 |
2013-09-18 |
| [OASIS Issue Tracker] Updated: (MQTT-14) Tighten up language in Quality of Service levels and flows |
1 |
2013-09-18 |
| [OASIS Issue Tracker] Commented: (MQTT-50) Handling of invalid CONNECT packets |
1 |
2013-09-18 |
| [OASIS Issue Tracker] Commented: (MQTT-55) What should happen if a client issues multiple connect calls on the same TCP Connection |
1 |
2013-09-18 |
| [OASIS Issue Tracker] Commented: (MQTT-58) How many messages are received for overlapping subscriptions? |
3 |
2013-09-18 |
| [OASIS Issue Tracker] Updated: (MQTT-58) How many messages are received for overlapping subscriptions? |
1 |
2013-09-18 |
| [OASIS Issue Tracker] Updated: (MQTT-27) Handling of the Dup Flag (section 2.1.2.1) |
2 |
2013-09-18 |
| [OASIS Issue Tracker] Commented: (MQTT-68) Message delivery retry is not required where no network failure is detected |
2 |
2013-09-18 |
| [OASIS Issue Tracker] Updated: (MQTT-76) Should "+" be allowed at the beginning of the topic filter in a subscription? |
1 |
2013-09-18 |
| [OASIS Issue Tracker] Commented: (MQTT-76) Should "+" be allowed at the beginning of the topic filter in a subscription? |
1 |
2013-09-18 |
| [OASIS Issue Tracker] Updated: (MQTT-64) Edge case handling of unsubscribe |
1 |
2013-09-18 |
| [OASIS Issue Tracker] Created: (MQTT-83) Advice on clean session = 0 |
1 |
2013-09-18 |
| [OASIS Issue Tracker] Created: (MQTT-84) Typos in 3.1.2.3.1 |
1 |
2013-09-18 |
| [OASIS Issue Tracker] Commented: (MQTT-84) Typos in 3.1.2.3.1 |
1 |
2013-09-19 |
| [OASIS Issue Tracker] Created: (MQTT-85) Comments following read through of WD11 |
1 |
2013-09-19 |
| =?UTF-8?B?R3JvdXBzIC0gTVFUVCBUQyBKSVJBIHBy?= =?UTF-8?B?b2Nlc3MgdXBkYXRlIHVwbG9hZGVk?= |
1 |
2013-09-19 |
| [OASIS Issue Tracker] Commented: (MQTT-82) Provide a way for clean-session=1 clients to specify no client identifier |
1 |
2013-09-19 |
| =?UTF-8?B?SmlyYSBpc3N1ZXMgbm90IGRpc2N1c3Nl?= =?UTF-8?B?ZCB0b2RheQ==?= |
1 |
2013-09-19 |
| =?UTF-8?B?R3JvdXBzIC0gRXZlbnQgIk1RVFQgU2Vj?= =?UTF-8?B?dXJpdHkgU3ViY29tbWl0dGVlIGNhbGwi?= =?UTF-8?B?IGFkZGVk?= |
1 |
2013-09-20 |
| [OASIS Issue Tracker] Commented: (MQTT-75) Defintion for REASONABLE amount of time |
1 |
2013-09-25 |
| [OASIS Issue Tracker] Commented: (MQTT-85) Comments following read through of WD11 |
1 |
2013-09-25 |
| =?UTF-8?B?V29ya2luZyBkcmFmdCAxMiBub3cgYXZh?= =?UTF-8?B?aWxhYmxl?= |
1 |
2013-09-25 |
| =?UTF-8?B?R3JvdXBzIC0gT0FTSVNfTVFUVF9UQ19t?= =?UTF-8?B?aW51dGVzXzE5MDkyMDEzLnBkZiB1cGxv?= =?UTF-8?B?YWRlZA==?= |
1 |
2013-09-25 |
| =?UTF-8?B?SmlyYSBpc3N1ZXMgdG8gcmV2aWV3IG9u?= =?UTF-8?B?IHRvZGF5J3MgY2FsbA==?= |
1 |
2013-09-26 |
| Re: [mqtt] Jira issues to review on today's call |
1 |
2013-09-26 |
| [OASIS Issue Tracker] Updated: (MQTT-77) Should the Connect packet User Name and Password fields be binary rather than UTF-8 |
1 |
2013-09-26 |
| [OASIS Issue Tracker] Commented: (MQTT-54) How long should a client or server wait for, or expect to wait for, a response |
1 |
2013-09-26 |
| [OASIS Issue Tracker] Updated: (MQTT-44) Specific details for UTF-8 Strings |
1 |
2013-09-27 |
| [OASIS Issue Tracker] Updated: (MQTT-73) Message ordering behaviour |
1 |
2013-09-27 |
| [OASIS Issue Tracker] Updated: (MQTT-71) Are messages order within Topic+Qos or within Qos |
1 |
2013-09-27 |
| [OASIS Issue Tracker] Updated: (MQTT-60) Are topic strings normalized at all? |
1 |
2013-09-27 |
| [OASIS Issue Tracker] Updated: (MQTT-75) Defintion for REASONABLE amount of time |
1 |
2013-09-27 |
| [OASIS Issue Tracker] Updated: (MQTT-78) Abstract references to the transport layer for MQTT |
1 |
2013-09-27 |
| =?UTF-8?B?R3JvdXBzIC0gT0FTSVNfTVFUVF9UQ19t?= =?UTF-8?B?aW51dGVzXzI2MDkyMDEzLnBkZiB1cGxv?= =?UTF-8?B?YWRlZA==?= |
1 |
2013-09-30 |
