| 00000 |
Groups - OASIS_MQTT_TC_minutes_23052013.pdf uploaded |
Richard Coppen
|
2013-06-03 09:19 |
| 00001 |
[OASIS Issue Tracker] Commented: (MQTT-17) Terminology for MQTT command message. |
OASIS Issues Tracker
|
2013-06-04 12:51 |
| 00002 |
Re: [mqtt] [OASIS Issue Tracker] Commented: (MQTT-17) Terminology for MQTT command message. |
Pavan Reddy (pareddy)
|
2013-06-04 13:07 |
| 00003 |
[OASIS Issue Tracker] Commented: (MQTT-17) Terminology for MQTT command message. |
OASIS Issues Tracker
|
2013-06-04 14:47 |
| 00004 |
[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. |
OASIS Issues Tracker
|
2013-06-04 15:05 |
| 00005 |
[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. |
OASIS Issues Tracker
|
2013-06-04 15:13 |
| 00006 |
[OASIS Issue Tracker] Commented: (MQTT-15) Should the CONNECT packet Protocol Name and Protocol Version fields be changed? |
OASIS Issues Tracker
|
2013-06-04 16:33 |
| 00007 |
[OASIS Issue Tracker] Updated: (MQTT-15) Should the CONNECT packet Protocol Name and Protocol Version fields be changed? |
OASIS Issues Tracker
|
2013-06-04 16:34 |
| 00008 |
[OASIS Issue Tracker] Commented: (MQTT-4) Flowing MQTT messages before CONNACK is received in the client. |
OASIS Issues Tracker
|
2013-06-04 16:41 |
| 00009 |
[OASIS Issue Tracker] Updated: (MQTT-4) Flowing MQTT messages before CONNACK is received in the client. |
OASIS Issues Tracker
|
2013-06-04 16:43 |
| 00010 |
[OASIS Issue Tracker] Commented: (MQTT-4) Flowing MQTT messages before CONNACK is received in the client. |
OASIS Issues Tracker
|
2013-06-04 16:59 |
| 00011 |
[OASIS Issue Tracker] Commented: (MQTT-13) Topic name has an upper length limit of 32,767 characters ? |
OASIS Issues Tracker
|
2013-06-05 02:20 |
| 00012 |
Groups - MQTT_TC_Timeline_06062013.pdf uploaded |
Richard Coppen
|
2013-06-05 15:43 |
| 00013 |
[OASIS Issue Tracker] Commented: (MQTT-2) UTF-8 for will messages |
OASIS Issues Tracker
|
2013-06-05 16:04 |
| 00014 |
Groups - Event "MQTT TC Meeting" modified |
Richard Coppen
|
2013-06-05 16:33 |
| 00015 |
[OASIS Issue Tracker] Commented: (MQTT-21) Use of flag bits in general. |
OASIS Issues Tracker
|
2013-06-05 20:33 |
| 00016 |
[OASIS Issue Tracker] Commented: (MQTT-16) Reserve $SYS topic name |
OASIS Issues Tracker
|
2013-06-06 09:00 |
| 00017 |
[OASIS Issue Tracker] Commented: (MQTT-16) Reserve $SYS topic name |
OASIS Issues Tracker
|
2013-06-06 10:15 |
| 00018 |
[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. |
OASIS Issues Tracker
|
2013-06-06 10:37 |
| 00019 |
[OASIS Issue Tracker] Commented: (MQTT-6) What should a server do if it receives a connect packet with and incorrect protocol name? |
OASIS Issues Tracker
|
2013-06-06 10:59 |
| 00020 |
Groups - Event "MQTT TC Meeting" modified |
Richard Coppen
|
2013-06-06 13:01 |
| 00021 |
Re: Can't call in - invalid access code |
Richard J Coppen
|
2013-06-06 14:19 |
| 00022 |
[OASIS Issue Tracker] Updated: (MQTT-3) Keep alive interval grace period. |
OASIS Issues Tracker
|
2013-06-06 14:27 |
| 00023 |
[OASIS Issue Tracker] Commented: (MQTT-16) Reserve $SYS topic name |
OASIS Issues Tracker
|
2013-06-06 15:45 |
| 00024 |
[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. |
OASIS Issues Tracker
|
2013-06-06 16:05 |
| 00025 |
[OASIS Issue Tracker] Created: (MQTT-22) Specification is ambiguous with regards to dynamic topics |
OASIS Issues Tracker
|
2013-06-10 14:03 |
| 00026 |
[OASIS Issue Tracker] Commented: (MQTT-22) Specification is ambiguous with regards to dynamic topics |
OASIS Issues Tracker
|
2013-06-10 14:43 |
| 00027 |
[OASIS Issue Tracker] Commented: (MQTT-22) Specification is ambiguous with regards to dynamic topics |
OASIS Issues Tracker
|
2013-06-10 14:55 |
| 00028 |
Groups - OASIS_MQTT_TC_minutes_06062013.pdf uploaded |
Louis-P. Lamoureux
|
2013-06-13 15:46 |
| 00029 |
[OASIS Issue Tracker] Created: (MQTT-23) Should Message Identifier be called as Packet Identifier |
OASIS Issues Tracker
|
2013-06-15 17:39 |
| 00030 |
[OASIS Issue Tracker] Updated: (MQTT-23) Should Message Identifier be called as Packet Identifier |
OASIS Issues Tracker
|
2013-06-15 17:40 |
| 00031 |
[OASIS Issue Tracker] Updated: (MQTT-23) Should Message Identifier be called as Packet Identifier |
OASIS Issues Tracker
|
2013-06-15 17:45 |
| 00032 |
[OASIS Issue Tracker] Created: (MQTT-24) Edits to Introduction section |
OASIS Issues Tracker
|
2013-06-16 18:17 |
| 00033 |
[OASIS Issue Tracker] Created: (MQTT-25) Placement of sentences on MSB/LSB byte order |
OASIS Issues Tracker
|
2013-06-16 18:23 |
| 00034 |
[OASIS Issue Tracker] Created: (MQTT-26) Typographical improvements to section 2.1.1 of WD04 |
OASIS Issues Tracker
|
2013-06-16 18:29 |
| 00035 |
[OASIS Issue Tracker] Created: (MQTT-27) Handling of the Dup Flag (section 2.1.2.1) |
OASIS Issues Tracker
|
2013-06-16 23:23 |
| 00036 |
[OASIS Issue Tracker] Commented: (MQTT-23) Should Message Identifier be called as Packet Identifier |
OASIS Issues Tracker
|
2013-06-17 10:03 |
| 00037 |
[OASIS Issue Tracker] Created: (MQTT-28) Typo comments on 2.1.2.2 and 2.1.2.3 in WD04 |
OASIS Issues Tracker
|
2013-06-17 10:11 |
| 00038 |
[OASIS Issue Tracker] Commented: (MQTT-23) Should Message Identifier be called as Packet Identifier |
OASIS Issues Tracker
|
2013-06-17 12:11 |
| 00039 |
[OASIS Issue Tracker] Commented: (MQTT-27) Handling of the Dup Flag (section 2.1.2.1) |
OASIS Issues Tracker
|
2013-06-17 12:25 |
| 00040 |
[OASIS Issue Tracker] Commented: (MQTT-25) Placement of sentences on MSB/LSB byte order |
OASIS Issues Tracker
|
2013-06-17 12:27 |
| 00041 |
[OASIS Issue Tracker] Commented: (MQTT-24) Edits to Introduction section |
OASIS Issues Tracker
|
2013-06-17 12:39 |
| 00042 |
[OASIS Issue Tracker] Created: (MQTT-29) Editorial comments on 2.1.3 (Remaining Length) and 2.1.4 (Multibyte Length) |
OASIS Issues Tracker
|
2013-06-17 12:40 |
| 00043 |
[OASIS Issue Tracker] Created: (MQTT-30) Redundant paragraph in section 2.2 |
OASIS Issues Tracker
|
2013-06-17 12:42 |
| 00044 |
[OASIS Issue Tracker] Updated: (MQTT-28) Typo comments on 2.1.2.2 and 2.1.2.3 in WD04 |
OASIS Issues Tracker
|
2013-06-17 14:23 |
| 00045 |
[OASIS Issue Tracker] Created: (MQTT-31) Clarification of 2.2.1 (Message Identifiers) |
OASIS Issues Tracker
|
2013-06-17 15:06 |
| 00046 |
[OASIS Issue Tracker] Created: (MQTT-32) Editorial comments on 2.3 (UTF-8 encoded strings) |
OASIS Issues Tracker
|
2013-06-17 16:11 |
| 00047 |
[OASIS Issue Tracker] Created: (MQTT-33) Trivia relating to WD04 Connect |
OASIS Issues Tracker
|
2013-06-17 16:59 |
| 00048 |
[OASIS Issue Tracker] Created: (MQTT-34) Meaning of KeepAlive = 0 |
OASIS Issues Tracker
|
2013-06-17 17:20 |
| 00049 |
[OASIS Issue Tracker] Created: (MQTT-35) What is supposed to happen when the KeepAlive timeout expires? |
OASIS Issues Tracker
|
2013-06-18 09:17 |
| 00050 |
[OASIS Issue Tracker] Created: (MQTT-36) Editorial comments on Connect Payload |
OASIS Issues Tracker
|
2013-06-18 09:37 |
| 00051 |
[OASIS Issue Tracker] Updated: (MQTT-35) What is supposed to happen when the KeepAlive timeout expires? |
OASIS Issues Tracker
|
2013-06-18 09:41 |
| 00052 |
[OASIS Issue Tracker] Created: (MQTT-37) Editorial comments on 3.3 (Publish) |
OASIS Issues Tracker
|
2013-06-18 10:59 |
| 00053 |
[OASIS Issue Tracker] Updated: (MQTT-10) Should Qos=0 retained messages be persisted in the server? |
OASIS Issues Tracker
|
2013-06-18 12:03 |
| 00054 |
[OASIS Issue Tracker] Updated: (MQTT-31) Clarification of 2.2.1 (Message Identifiers) |
OASIS Issues Tracker
|
2013-06-18 13:23 |
| 00055 |
[OASIS Issue Tracker] Commented: (MQTT-33) Trivia relating to WD04 Connect |
OASIS Issues Tracker
|
2013-06-18 13:40 |
| 00056 |
[OASIS Issue Tracker] Updated: (MQTT-7) Can the client and server store QoS=0 messages after a client using CleanSession=0 has disconnected? |
OASIS Issues Tracker
|
2013-06-18 14:35 |
| 00057 |
[OASIS Issue Tracker] Commented: (MQTT-4) Flowing MQTT messages before CONNACK is received in the client. |
OASIS Issues Tracker
|
2013-06-18 15:29 |
| 00058 |
[OASIS Issue Tracker] Commented: (MQTT-22) Specification is ambiguous with regards to dynamic topics |
OASIS Issues Tracker
|
2013-06-18 16:53 |
| 00059 |
[OASIS Issue Tracker] Commented: (MQTT-35) What is supposed to happen when the KeepAlive timeout expires? |
OASIS Issues Tracker
|
2013-06-18 17:05 |
| 00060 |
[OASIS Issue Tracker] Created: (MQTT-38) Malformed QoS for topics in SUBSCRIBE packet |
OASIS Issues Tracker
|
2013-06-19 02:21 |
| 00061 |
[OASIS Issue Tracker] Commented: (MQTT-2) UTF-8 for will messages |
OASIS Issues Tracker
|
2013-06-19 07:13 |
| 00062 |
[OASIS Issue Tracker] Commented: (MQTT-17) Terminology for MQTT command message. |
OASIS Issues Tracker
|
2013-06-19 07:15 |
| 00063 |
[OASIS Issue Tracker] Updated: (MQTT-23) Should Message Identifier be called as Packet Identifier |
OASIS Issues Tracker
|
2013-06-19 09:57 |
| 00064 |
[OASIS Issue Tracker] Updated: (MQTT-12) CONNACK Topic name Compression response. |
OASIS Issues Tracker
|
2013-06-19 14:05 |
| 00065 |
[OASIS Issue Tracker] Commented: (MQTT-8) Create a new CONNACK return code to indicate that the CONNECT packet was malformed. |
OASIS Issues Tracker
|
2013-06-19 14:35 |
| 00066 |
[OASIS Issue Tracker] Created: (MQTT-39) CONNACK return code references are inconsistent |
OASIS Issues Tracker
|
2013-06-19 17:09 |
| 00067 |
Jira Issues |
Richard J Coppen
|
2013-06-19 19:49 |
| 00068 |
[OASIS Issue Tracker] Commented: (MQTT-33) Trivia relating to WD04 Connect |
OASIS Issues Tracker
|
2013-06-20 03:53 |
| 00069 |
[OASIS Issue Tracker] Updated: (MQTT-33) Trivia relating to WD04 Connect |
OASIS Issues Tracker
|
2013-06-20 03:54 |
| 00070 |
[OASIS Issue Tracker] Commented: (MQTT-36) Editorial comments on Connect Payload |
OASIS Issues Tracker
|
2013-06-20 04:25 |
| 00071 |
[OASIS Issue Tracker] Commented: (MQTT-28) Typo comments on 2.1.2.2 and 2.1.2.3 in WD04 |
OASIS Issues Tracker
|
2013-06-20 04:42 |
| 00072 |
Groups - MQTT WD-05 Draft uploaded |
Rahul Gupta
|
2013-06-20 04:56 |
| 00073 |
Groups - MQTT WD-05 Draft pdf uploaded |
Rahul Gupta
|
2013-06-20 04:57 |
| 00074 |
Groups - MQTT_TC_Timeline_20062013.pdf uploaded |
Richard Coppen
|
2013-06-20 10:36 |
| 00075 |
Groups - Event "MQTT TC Meeting" modified |
Richard Coppen
|
2013-06-20 11:44 |
| 00076 |
[OASIS Issue Tracker] Commented: (MQTT-23) Should Message Identifier be called as Packet Identifier |
OASIS Issues Tracker
|
2013-06-20 13:13 |
| 00077 |
[OASIS Issue Tracker] Created: (MQTT-40) Should MQTT Publisher and MQTT Subscriber be differentiated |
OASIS Issues Tracker
|
2013-06-20 13:35 |
| 00078 |
[OASIS Issue Tracker] Commented: (MQTT-35) What is supposed to happen when the KeepAlive timeout expires? |
OASIS Issues Tracker
|
2013-06-20 14:06 |
| 00079 |
[OASIS Issue Tracker] Commented: (MQTT-40) Should MQTT Publisher and MQTT Subscriber be differentiated |
OASIS Issues Tracker
|
2013-06-20 14:09 |
| 00080 |
[OASIS Issue Tracker] Updated: (MQTT-40) Should MQTT Publisher and MQTT Subscriber be differentiated |
OASIS Issues Tracker
|
2013-06-20 14:15 |
| 00081 |
[OASIS Issue Tracker] Commented: (MQTT-40) Should MQTT Publisher and MQTT Subscriber be differentiated |
OASIS Issues Tracker
|
2013-06-20 14:21 |
| 00082 |
Groups - Event "MQTT TC Meeting" modified |
Richard Coppen
|
2013-06-20 16:22 |
| 00083 |
Groups - Event "MQTT JIRA Issue scrub call" added |
Richard Coppen
|
2013-06-20 16:27 |
| 00084 |
Groups - OASIS_MQTT_TC_minutes_20062013.pdf uploaded |
Julien Niset
|
2013-06-20 17:22 |
| 00085 |
[OASIS Issue Tracker] Updated: (MQTT-12) CONNACK Topic name Compression response. |
OASIS Issues Tracker
|
2013-06-20 17:29 |
| 00086 |
Groups - OASIS_MQTT_TC_minutes_20062013.pdf uploaded |
Julien Niset
|
2013-06-20 19:09 |
| 00087 |
[OASIS Issue Tracker] Updated: (MQTT-15) Should the CONNECT packet Protocol Name and Protocol Version fields be changed? |
OASIS Issues Tracker
|
2013-06-21 11:07 |
| 00088 |
[OASIS Issue Tracker] Updated: (MQTT-3) Keep alive interval grace period. |
OASIS Issues Tracker
|
2013-06-21 11:09 |
| 00089 |
[OASIS Issue Tracker] Commented: (MQTT-30) Redundant paragraph in section 2.2 |
OASIS Issues Tracker
|
2013-06-22 13:45 |
| 00090 |
[OASIS Issue Tracker] Updated: (MQTT-20) Length of strings. |
OASIS Issues Tracker
|
2013-06-23 13:37 |
| 00091 |
[OASIS Issue Tracker] Updated: (MQTT-35) What is supposed to happen when the KeepAlive timeout expires? |
OASIS Issues Tracker
|
2013-06-23 13:51 |
| 00092 |
[OASIS Issue Tracker] Commented: (MQTT-30) Redundant paragraph in section 2.2 |
OASIS Issues Tracker
|
2013-06-24 09:41 |
| 00093 |
[OASIS Issue Tracker] Created: (MQTT-41) Inconsistency in the definition of the Remaining Length field for the different control packets |
OASIS Issues Tracker
|
2013-06-25 08:09 |
| 00094 |
[OASIS Issue Tracker] Updated: (MQTT-18) Clarifying what MQTT means by storing data. |
OASIS Issues Tracker
|
2013-06-28 08:37 |
| 00095 |
[OASIS Issue Tracker] Updated: (MQTT-11) Length of client Identifier |
OASIS Issues Tracker
|
2013-06-28 08:47 |
| 00096 |
[OASIS Issue Tracker] Commented: (MQTT-22) Specification is ambiguous with regards to dynamic topics |
OASIS Issues Tracker
|
2013-06-28 08:59 |
| 00097 |
[OASIS Issue Tracker] Updated: (MQTT-11) Length of client Identifier |
OASIS Issues Tracker
|
2013-06-28 09:01 |
| 00098 |
[OASIS Issue Tracker] Updated: (MQTT-4) Flowing MQTT messages before CONNACK is received in the client. |
OASIS Issues Tracker
|
2013-06-28 09:09 |
| 00099 |
[OASIS Issue Tracker] Commented: (MQTT-14) Tighten up language in Quality of Service levels and flows |
OASIS Issues Tracker
|
2013-06-28 13:13 |
