| [OASIS Issue Tracker] Created: (MQTT-199) Inconsistent use of clean session |
1 |
2014-03-04 |
| [OASIS Issue Tracker] Updated: (MQTT-113) Handling of Session state mismatch between Client and Server |
2 |
2014-03-05 |
| =?UTF-8?B?R3JvdXBzIC0gT0FTSVNfTVFUVF9UQ19t?= =?UTF-8?B?aW51dGVzXzAyMjcyMDE0LnBkZiB1cGxv?= =?UTF-8?B?YWRlZA==?= |
1 |
2014-03-05 |
| [OASIS Issue Tracker] Commented: (MQTT-156) Vague treatment of "at most once" |
1 |
2014-03-05 |
| [OASIS Issue Tracker] Updated: (MQTT-156) Vague treatment of "at most once" |
3 |
2014-03-05 |
| [OASIS Issue Tracker] Updated: (MQTT-194) Status of chapter 6 Using WebSocket as a network transport. is unclear |
6 |
2014-03-06 |
| =?UTF-8?B?TVFUVCB2My4xLjEgd29ya2luZyBkcmFm?= =?UTF-8?B?dCAxOSBub3cgYXZhaWxhYmxlLg==?= |
1 |
2014-03-06 |
| RE: [mqtt] MQTT v3.1.1 working draft 19 now available. |
3 |
2014-03-06 |
| =?UTF-8?B?R3JvdXBzIC0gRXZlbnQgIk1RVFQgVEMg?= =?UTF-8?B?TWVldGluZyIgbW9kaWZpZWQ=?= |
4 |
2014-03-06 |
| [OASIS Issue Tracker] Updated: (MQTT-162) 2.1.2.1 Dup - setting of Dup flag |
2 |
2014-03-07 |
| [OASIS Issue Tracker] Created: (MQTT-200) Clarification on WD01 |
1 |
2014-03-07 |
| [OASIS Issue Tracker] Created: (MQTT-201) Remove unclear statement on Qos1 sender to Qos0 subscriber |
1 |
2014-03-10 |
| [OASIS Issue Tracker] Created: (MQTT-202) Inconsistent use of "Application Message" and "Publication" in WD19 |
1 |
2014-03-10 |
| =?UTF-8?B?UmVjZW50IGNsb2NrIGNoYW5nZXM=?= |
1 |
2014-03-10 |
| [OASIS Issue Tracker] Updated: (MQTT-151) Clarify "store data", and more generally make normative statements self-explanatory (as much as possible) |
4 |
2014-03-10 |
| [OASIS Issue Tracker] Updated: (MQTT-201) Remove unclear statement on Qos1 sender to Qos0 subscriber |
1 |
2014-03-11 |
| =?UTF-8?B?R3JvdXBzIC0gTVFUVF9UQ19UaW1lbGlu?= =?UTF-8?B?ZV8xMTAzMjAxNC5wZGYgdXBsb2FkZWQ=?= |
2 |
2014-03-12 |
| =?UTF-8?B?R3JvdXBzIC0gTSB1cGxvYWRlZA==?= |
1 |
2014-03-12 |
| [OASIS Issue Tracker] Updated: (MQTT-160) Weak definition.of Server |
1 |
2014-03-13 |
| =?UTF-8?B?R3JvdXBzIC0gT0FTSVNfTVFUVF9UQ19t?= =?UTF-8?B?aW51dGVzXzA2MDMyMDE0LnBkZiB1cGxv?= =?UTF-8?B?YWRlZA==?= |
1 |
2014-03-13 |
| =?UTF-8?B?TVFUVDMuMS4xIFdvcmtpbmcgZHJhZnQg?= =?UTF-8?B?MjAgbm93IGF2YWlsYWJsZS4=?= |
1 |
2014-03-13 |
| [OASIS Issue Tracker] Updated: (MQTT-168) Normative statement unrelated to conformance targets |
1 |
2014-03-13 |
| [OASIS Issue Tracker] Commented: (MQTT-168) Normative statement unrelated to conformance targets |
1 |
2014-03-13 |
| [OASIS Issue Tracker] Commented: (MQTT-160) Weak definition.of Server |
1 |
2014-03-13 |
| [OASIS Issue Tracker] Commented: (MQTT-151) Clarify "store data", and more generally make normative statements self-explanatory (as much as possible) |
1 |
2014-03-13 |
| [OASIS Issue Tracker] Commented: (MQTT-194) Status of chapter 6 Using WebSocket as a network transport. is unclear |
1 |
2014-03-13 |
| [OASIS Issue Tracker] (MQTT-203) MQTT URI Scheme |
6 |
2014-03-16 |
| [OASIS Issue Tracker] (MQTT-204) Make $ topic separation normative |
5 |
2014-03-17 |
| [OASIS Issue Tracker] (MQTT-205) Edits on WD20 chapters 1 and 2 |
1 |
2014-03-18 |
| =?UTF-8?B?R3JvdXBzIC0gT0FTSVNfTVFUVF9UQ19t?= =?UTF-8?B?aW51dGVzXzAzMTMyMDE0LnBkZiB1cGxv?= =?UTF-8?B?YWRlZA==?= |
1 |
2014-03-19 |
| =?UTF-8?B?R3JvdXBzIC0gbXF0dC12My4xLjEtd2Qy?= =?UTF-8?B?MS5kb2MgdXBsb2FkZWQ=?= |
1 |
2014-03-20 |
| =?UTF-8?B?R3JvdXBzIC0gbXF0dC12My4xLjEtd2Qy?= =?UTF-8?B?MS5wZGYgdXBsb2FkZWQ=?= |
1 |
2014-03-20 |
| [OASIS Issue Tracker] (MQTT-186) 1.2 Normative References, Unicode version 6.3.0 - or later? |
2 |
2014-03-20 |
| [OASIS Issue Tracker] (MQTT-145) MAY/may contain inconsistent usage - 1 known, others need researching |
3 |
2014-03-20 |
| [OASIS Issue Tracker] (MQTT-206) Summary of editorial issues Security SC WD04 |
1 |
2014-03-25 |
| [OASIS Issue Tracker] (MQTT-207) Update to abstract |
2 |
2014-03-25 |
| [OASIS Issue Tracker] (MQTT-208) confusing narrative around redelivery of control packets |
4 |
2014-03-26 |
| [OASIS Issue Tracker] (MQTT-193) CSD review comments (Martin Hurton) |
3 |
2014-03-27 |
| =?UTF-8?B?R3JvdXBzIC0gT0FTSVNfTVFUVF9UQ19t?= =?UTF-8?B?aW51dGVzXzIwMDMyMDE0LnBkZiB1cGxv?= =?UTF-8?B?YWRlZA==?= |
1 |
2014-03-27 |
| =?UTF-8?B?R3JvdXBzIC0gbXF0dC12My4xLjEtd2Qy?= =?UTF-8?B?Mi5wZGYgdXBsb2FkZWQ=?= |
1 |
2014-03-27 |
| =?UTF-8?B?R3JvdXBzIC0gbXF0dC12My4xLjEtd2Qy?= =?UTF-8?B?Mi5kb2MgdXBsb2FkZWQ=?= |
1 |
2014-03-27 |
| [OASIS Issue Tracker] (MQTT-143) Normative statement lack of precision |
2 |
2014-03-27 |
| [OASIS Issue Tracker] (MQTT-152) 4.3.3 QoS 2: Exactly once delivery diagram |
2 |
2014-03-27 |
| [OASIS Issue Tracker] (MQTT-209) QOS 2 delivery options must not be mixed |
1 |
2014-03-28 |
| [OASIS Issue Tracker] (MQTT-148) 7 conformance |
1 |
2014-03-31 |
| [OASIS Issue Tracker] (MQTT-210) Add clarity to keepAlive interval |
1 |
2014-03-31 |
