| =?UTF-8?B?R3JvdXBzIC0gT0FTSVNfTVFUVF9UQ19t?= =?UTF-8?B?aW51dGVzXzIzMDUyMDEzLnBkZiB1cGxv?= =?UTF-8?B?YWRlZA==?= |
1 |
2013-06-03 |
| [OASIS Issue Tracker] Commented: (MQTT-17) Terminology for MQTT command message. |
4 |
2013-06-04 |
| [OASIS Issue Tracker] Issue Comment Edited: (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. |
3 |
2013-06-04 |
| [OASIS Issue Tracker] Commented: (MQTT-15) Should the CONNECT packet Protocol Name and Protocol Version fields be changed? |
1 |
2013-06-04 |
| [OASIS Issue Tracker] Updated: (MQTT-15) Should the CONNECT packet Protocol Name and Protocol Version fields be changed? |
2 |
2013-06-04 |
| [OASIS Issue Tracker] Commented: (MQTT-4) Flowing MQTT messages before CONNACK is received in the client. |
3 |
2013-06-04 |
| [OASIS Issue Tracker] Updated: (MQTT-4) Flowing MQTT messages before CONNACK is received in the client. |
2 |
2013-06-04 |
| [OASIS Issue Tracker] Commented: (MQTT-13) Topic name has an upper length limit of 32,767 characters ? |
1 |
2013-06-05 |
| =?UTF-8?B?R3JvdXBzIC0gTVFUVF9UQ19UaW1lbGlu?= =?UTF-8?B?ZV8wNjA2MjAxMy5wZGYgdXBsb2FkZWQ=?= |
1 |
2013-06-05 |
| [OASIS Issue Tracker] Commented: (MQTT-2) UTF-8 for will messages |
2 |
2013-06-05 |
| =?UTF-8?B?R3JvdXBzIC0gRXZlbnQgIk1RVFQgVEMg?= =?UTF-8?B?TWVldGluZyIgbW9kaWZpZWQ=?= |
4 |
2013-06-05 |
| [OASIS Issue Tracker] Commented: (MQTT-21) Use of flag bits in general. |
1 |
2013-06-05 |
| [OASIS Issue Tracker] Commented: (MQTT-16) Reserve $SYS topic name |
3 |
2013-06-06 |
| [OASIS Issue Tracker] Commented: (MQTT-6) What should a server do if it receives a connect packet with and incorrect protocol name? |
1 |
2013-06-06 |
| Re: Can't call in - invalid access code |
1 |
2013-06-06 |
| [OASIS Issue Tracker] Updated: (MQTT-3) Keep alive interval grace period. |
2 |
2013-06-06 |
| [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-06-06 |
| [OASIS Issue Tracker] Created: (MQTT-22) Specification is ambiguous with regards to dynamic topics |
1 |
2013-06-10 |
| [OASIS Issue Tracker] Commented: (MQTT-22) Specification is ambiguous with regards to dynamic topics |
4 |
2013-06-10 |
| =?UTF-8?B?R3JvdXBzIC0gT0FTSVNfTVFUVF9UQ19t?= =?UTF-8?B?aW51dGVzXzA2MDYyMDEzLnBkZiB1cGxv?= =?UTF-8?B?YWRlZA==?= |
1 |
2013-06-13 |
| [OASIS Issue Tracker] Created: (MQTT-23) Should Message Identifier be called as Packet Identifier |
1 |
2013-06-15 |
| [OASIS Issue Tracker] Updated: (MQTT-23) Should Message Identifier be called as Packet Identifier |
3 |
2013-06-15 |
| [OASIS Issue Tracker] Created: (MQTT-24) Edits to Introduction section |
1 |
2013-06-16 |
| [OASIS Issue Tracker] Created: (MQTT-25) Placement of sentences on MSB/LSB byte order |
1 |
2013-06-16 |
| [OASIS Issue Tracker] Created: (MQTT-26) Typographical improvements to section 2.1.1 of WD04 |
1 |
2013-06-16 |
| [OASIS Issue Tracker] Created: (MQTT-27) Handling of the Dup Flag (section 2.1.2.1) |
1 |
2013-06-16 |
| [OASIS Issue Tracker] Commented: (MQTT-23) Should Message Identifier be called as Packet Identifier |
3 |
2013-06-17 |
| [OASIS Issue Tracker] Created: (MQTT-28) Typo comments on 2.1.2.2 and 2.1.2.3 in WD04 |
1 |
2013-06-17 |
| [OASIS Issue Tracker] Commented: (MQTT-27) Handling of the Dup Flag (section 2.1.2.1) |
1 |
2013-06-17 |
| [OASIS Issue Tracker] Commented: (MQTT-25) Placement of sentences on MSB/LSB byte order |
1 |
2013-06-17 |
| [OASIS Issue Tracker] Commented: (MQTT-24) Edits to Introduction section |
1 |
2013-06-17 |
| [OASIS Issue Tracker] Created: (MQTT-29) Editorial comments on 2.1.3 (Remaining Length) and 2.1.4 (Multibyte Length) |
1 |
2013-06-17 |
| [OASIS Issue Tracker] Created: (MQTT-30) Redundant paragraph in section 2.2 |
1 |
2013-06-17 |
| [OASIS Issue Tracker] Updated: (MQTT-28) Typo comments on 2.1.2.2 and 2.1.2.3 in WD04 |
1 |
2013-06-17 |
| [OASIS Issue Tracker] Created: (MQTT-31) Clarification of 2.2.1 (Message Identifiers) |
1 |
2013-06-17 |
| [OASIS Issue Tracker] Created: (MQTT-32) Editorial comments on 2.3 (UTF-8 encoded strings) |
1 |
2013-06-17 |
| [OASIS Issue Tracker] Created: (MQTT-33) Trivia relating to WD04 Connect |
1 |
2013-06-17 |
| [OASIS Issue Tracker] Created: (MQTT-34) Meaning of KeepAlive = 0 |
1 |
2013-06-17 |
| [OASIS Issue Tracker] Created: (MQTT-35) What is supposed to happen when the KeepAlive timeout expires? |
1 |
2013-06-18 |
| [OASIS Issue Tracker] Created: (MQTT-36) Editorial comments on Connect Payload |
1 |
2013-06-18 |
| [OASIS Issue Tracker] Updated: (MQTT-35) What is supposed to happen when the KeepAlive timeout expires? |
2 |
2013-06-18 |
| [OASIS Issue Tracker] Created: (MQTT-37) Editorial comments on 3.3 (Publish) |
1 |
2013-06-18 |
| [OASIS Issue Tracker] Updated: (MQTT-10) Should Qos=0 retained messages be persisted in the server? |
1 |
2013-06-18 |
| [OASIS Issue Tracker] Updated: (MQTT-31) Clarification of 2.2.1 (Message Identifiers) |
1 |
2013-06-18 |
| [OASIS Issue Tracker] Commented: (MQTT-33) Trivia relating to WD04 Connect |
2 |
2013-06-18 |
| [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-06-18 |
| [OASIS Issue Tracker] Commented: (MQTT-35) What is supposed to happen when the KeepAlive timeout expires? |
2 |
2013-06-18 |
| [OASIS Issue Tracker] Created: (MQTT-38) Malformed QoS for topics in SUBSCRIBE packet |
1 |
2013-06-19 |
| [OASIS Issue Tracker] Updated: (MQTT-12) CONNACK Topic name Compression response. |
2 |
2013-06-19 |
| [OASIS Issue Tracker] Commented: (MQTT-8) Create a new CONNACK return code to indicate that the CONNECT packet was malformed. |
1 |
2013-06-19 |
| [OASIS Issue Tracker] Created: (MQTT-39) CONNACK return code references are inconsistent |
1 |
2013-06-19 |
| Jira Issues |
1 |
2013-06-19 |
| [OASIS Issue Tracker] Updated: (MQTT-33) Trivia relating to WD04 Connect |
1 |
2013-06-20 |
| [OASIS Issue Tracker] Commented: (MQTT-36) Editorial comments on Connect Payload |
1 |
2013-06-20 |
| [OASIS Issue Tracker] Commented: (MQTT-28) Typo comments on 2.1.2.2 and 2.1.2.3 in WD04 |
1 |
2013-06-20 |
| =?UTF-8?B?R3JvdXBzIC0gTVFUVCBXRC0wNSBEcmFm?= =?UTF-8?B?dCB1cGxvYWRlZA==?= |
1 |
2013-06-20 |
| =?UTF-8?B?R3JvdXBzIC0gTVFUVCBXRC0wNSBEcmFm?= =?UTF-8?B?dCBwZGYgdXBsb2FkZWQ=?= |
1 |
2013-06-20 |
| =?UTF-8?B?R3JvdXBzIC0gTVFUVF9UQ19UaW1lbGlu?= =?UTF-8?B?ZV8yMDA2MjAxMy5wZGYgdXBsb2FkZWQ=?= |
1 |
2013-06-20 |
| [OASIS Issue Tracker] Created: (MQTT-40) Should MQTT Publisher and MQTT Subscriber be differentiated |
1 |
2013-06-20 |
| [OASIS Issue Tracker] Commented: (MQTT-40) Should MQTT Publisher and MQTT Subscriber be differentiated |
2 |
2013-06-20 |
| [OASIS Issue Tracker] Updated: (MQTT-40) Should MQTT Publisher and MQTT Subscriber be differentiated |
1 |
2013-06-20 |
| =?UTF-8?B?R3JvdXBzIC0gRXZlbnQgIk1RVFQgSklS?= =?UTF-8?B?QSBJc3N1ZSBzY3J1YiBjYWxsIiBhZGRl?= =?UTF-8?B?ZA==?= |
1 |
2013-06-20 |
| =?UTF-8?B?R3JvdXBzIC0gT0FTSVNfTVFUVF9UQ19t?= =?UTF-8?B?aW51dGVzXzIwMDYyMDEzLnBkZiB1cGxv?= =?UTF-8?B?YWRlZA==?= |
2 |
2013-06-20 |
| [OASIS Issue Tracker] Commented: (MQTT-30) Redundant paragraph in section 2.2 |
2 |
2013-06-22 |
| [OASIS Issue Tracker] Updated: (MQTT-20) Length of strings. |
1 |
2013-06-23 |
| [OASIS Issue Tracker] Created: (MQTT-41) Inconsistency in the definition of the Remaining Length field for the different control packets |
1 |
2013-06-25 |
| [OASIS Issue Tracker] Updated: (MQTT-18) Clarifying what MQTT means by storing data. |
1 |
2013-06-28 |
| [OASIS Issue Tracker] Updated: (MQTT-11) Length of client Identifier |
2 |
2013-06-28 |
| [OASIS Issue Tracker] Commented: (MQTT-14) Tighten up language in Quality of Service levels and flows |
1 |
2013-06-28 |
