| 00000 |
Groups - OASIS_MQTT_TC_minutes_25042013.pdf uploaded |
Richard Coppen
|
2013-05-01 13:17 |
| 00001 |
Groups - OASIS_MQTT_TC_minutes_25042013.pdf uploaded |
Richard Coppen
|
2013-05-01 13:21 |
| 00002 |
Groups - Event "MQTT TC Meeting (Conference Call)" added |
Richard Coppen
|
2013-05-01 13:33 |
| 00003 |
[OASIS Issue Tracker] Created: (MQTT-1) Flowing MQTT V3.1.1 protocol over a WebSocket |
OASIS Issues Tracker
|
2013-05-01 13:49 |
| 00004 |
[OASIS Issue Tracker] Commented: (MQTT-1) Flowing MQTT V3.1.1 protocol over a WebSocket |
OASIS Issues Tracker
|
2013-05-01 14:06 |
| 00005 |
[OASIS Issue Tracker] Commented: (MQTT-1) Flowing MQTT V3.1.1 protocol over a WebSocket |
OASIS Issues Tracker
|
2013-05-01 15:13 |
| 00006 |
[OASIS Issue Tracker] Created: (MQTT-2) UTF-8 for will messages |
OASIS Issues Tracker
|
2013-05-02 07:59 |
| 00007 |
[OASIS Issue Tracker] Commented: (MQTT-2) UTF-8 for will messages |
OASIS Issues Tracker
|
2013-05-02 08:29 |
| 00008 |
Groups - Event "An introduction to MQTT: overview and refresher" added |
Richard Coppen
|
2013-05-02 11:10 |
| 00009 |
[OASIS Issue Tracker] Created: (MQTT-3) Keep alive interval grace period. |
OASIS Issues Tracker
|
2013-05-02 14:01 |
| 00010 |
[OASIS Issue Tracker] Commented: (MQTT-1) Flowing MQTT V3.1.1 protocol over a WebSocket |
OASIS Issues Tracker
|
2013-05-02 14:11 |
| 00011 |
[OASIS Issue Tracker] Commented: (MQTT-1) Flowing MQTT V3.1.1 protocol over a WebSocket |
OASIS Issues Tracker
|
2013-05-02 14:34 |
| 00012 |
[OASIS Issue Tracker] Commented: (MQTT-1) Flowing MQTT V3.1.1 protocol over a WebSocket |
OASIS Issues Tracker
|
2013-05-02 14:43 |
| 00013 |
[OASIS Issue Tracker] Created: (MQTT-4) Flowing MQTT messages before CONNACK is received in the client. |
OASIS Issues Tracker
|
2013-05-07 14:02 |
| 00014 |
[OASIS Issue Tracker] Created: (MQTT-5) Should the unused DUP, QoS, and RETAIN flags be zero in the CONNECT message? |
OASIS Issues Tracker
|
2013-05-07 14:09 |
| 00015 |
[OASIS Issue Tracker] Commented: (MQTT-5) Should the unused DUP, QoS, and RETAIN flags be zero in the CONNECT message? |
OASIS Issues Tracker
|
2013-05-07 14:25 |
| 00016 |
[OASIS Issue Tracker] Commented: (MQTT-4) Flowing MQTT messages before CONNACK is received in the client. |
OASIS Issues Tracker
|
2013-05-07 14:26 |
| 00017 |
[OASIS Issue Tracker] Commented: (MQTT-4) Flowing MQTT messages before CONNACK is received in the client. |
OASIS Issues Tracker
|
2013-05-07 15:47 |
| 00018 |
[OASIS Issue Tracker] Created: (MQTT-6) What should a server do if it receives a connect packet with and incorrect protocol name? |
OASIS Issues Tracker
|
2013-05-07 16:58 |
| 00019 |
[OASIS Issue Tracker] Created: (MQTT-7) Can the client and server store QoS=0 messages after a client using CleanSession=0 has disconnected? |
OASIS Issues Tracker
|
2013-05-07 17:16 |
| 00020 |
[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-05-07 22:21 |
| 00021 |
[OASIS Issue Tracker] Commented: (MQTT-5) Should the unused DUP, QoS, and RETAIN flags be zero in the CONNECT message? |
OASIS Issues Tracker
|
2013-05-08 10:48 |
| 00022 |
[OASIS Issue Tracker] Created: (MQTT-8) Create a new CONNACK return code to indicate that the CONNECT packet was malformed. |
OASIS Issues Tracker
|
2013-05-08 11:16 |
| 00023 |
[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. |
OASIS Issues Tracker
|
2013-05-08 11:29 |
| 00024 |
Second working draft |
Richard J Coppen
|
2013-05-08 15:51 |
| 00025 |
[OASIS Issue Tracker] Commented: (MQTT-7) Can the client and server store QoS=0 messages after a client using CleanSession=0 has disconnected? |
OASIS Issues Tracker
|
2013-05-08 16:19 |
| 00026 |
Groups - MQTT TC JIRA Overview uploaded |
Richard Coppen
|
2013-05-08 21:13 |
| 00027 |
Groups - Event "MQTT TC Meeting (Conference Call)" modified |
Richard Coppen
|
2013-05-08 21:26 |
| 00028 |
Groups - Event "MQTT TC Meeting (Conference Call)" modified |
Richard Coppen
|
2013-05-09 11:09 |
| 00029 |
Groups - Event "MQTT TC Meeting (Conference Call)" modified |
Richard Coppen
|
2013-05-09 13:56 |
| 00030 |
[OASIS Issue Tracker] Created: (MQTT-10) Should Qos=0 retained messages be persisted in the server? |
OASIS Issues Tracker
|
2013-05-12 14:55 |
| 00031 |
[OASIS Issue Tracker] Commented: (MQTT-10) Should Qos=0 retained messages be persisted in the server? |
OASIS Issues Tracker
|
2013-05-13 07:56 |
| 00032 |
[OASIS Issue Tracker] Updated: (MQTT-3) Keep alive interval grace period. |
OASIS Issues Tracker
|
2013-05-13 13:55 |
| 00033 |
[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. |
OASIS Issues Tracker
|
2013-05-13 13:59 |
| 00034 |
[OASIS Issue Tracker] Updated: (MQTT-2) UTF-8 for will messages |
OASIS Issues Tracker
|
2013-05-13 14:00 |
| 00035 |
[OASIS Issue Tracker] Updated: (MQTT-4) Flowing MQTT messages before CONNACK is received in the client. |
OASIS Issues Tracker
|
2013-05-13 14:01 |
| 00036 |
[OASIS Issue Tracker] Updated: (MQTT-6) What should a server do if it receives a connect packet with and incorrect protocol name? |
OASIS Issues Tracker
|
2013-05-13 14:02 |
| 00037 |
[OASIS Issue Tracker] Updated: (MQTT-5) Should the unused DUP, QoS, and RETAIN flags be zero in the CONNECT message? |
OASIS Issues Tracker
|
2013-05-13 14:02 |
| 00038 |
[OASIS Issue Tracker] Updated: (MQTT-8) Create a new CONNACK return code to indicate that the CONNECT packet was malformed. |
OASIS Issues Tracker
|
2013-05-13 14:02 |
| 00039 |
[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-05-13 14:02 |
| 00040 |
[OASIS Issue Tracker] Updated: (MQTT-1) Flowing MQTT V3.1.1 protocol over a WebSocket |
OASIS Issues Tracker
|
2013-05-13 14:02 |
| 00041 |
[OASIS Issue Tracker] Created: (MQTT-11) Length of client Identifier |
OASIS Issues Tracker
|
2013-05-13 14:12 |
| 00042 |
[OASIS Issue Tracker] Commented: (MQTT-11) Length of client Identifier |
OASIS Issues Tracker
|
2013-05-13 14:29 |
| 00043 |
[OASIS Issue Tracker] Created: (MQTT-12) CONNACK Topic name Compression response. |
OASIS Issues Tracker
|
2013-05-13 14:51 |
| 00044 |
Groups - Event "An introduction to MQTT: overview and refresher" modified |
Richard Coppen
|
2013-05-15 08:54 |
| 00045 |
Groups - Event "MQTT TC Meeting (Conference Call)" added |
Richard Coppen
|
2013-05-16 08:41 |
| 00046 |
Groups - Introduction to MQTT uploaded |
David Locke
|
2013-05-16 10:13 |
| 00047 |
Groups - Event "An introduction to MQTT: overview and refresher" modified |
Richard Coppen
|
2013-05-16 12:53 |
| 00048 |
[OASIS Issue Tracker] Commented: (MQTT-11) Length of client Identifier |
OASIS Issues Tracker
|
2013-05-17 10:20 |
| 00049 |
[OASIS Issue Tracker] Commented: (MQTT-11) Length of client Identifier |
OASIS Issues Tracker
|
2013-05-17 10:28 |
| 00050 |
[OASIS Issue Tracker] Issue Comment Edited: (MQTT-11) Length of client Identifier |
OASIS Issues Tracker
|
2013-05-17 10:29 |
| 00051 |
[OASIS Issue Tracker] Commented: (MQTT-11) Length of client Identifier |
OASIS Issues Tracker
|
2013-05-17 10:45 |
| 00052 |
[OASIS Issue Tracker] Commented: (MQTT-11) Length of client Identifier |
OASIS Issues Tracker
|
2013-05-17 13:06 |
| 00053 |
[OASIS Issue Tracker] Issue Comment Edited: (MQTT-11) Length of client Identifier |
OASIS Issues Tracker
|
2013-05-17 13:14 |
| 00054 |
[OASIS Issue Tracker] Created: (MQTT-13) Topic name has an upper length limit of 32,767 characters ? |
OASIS Issues Tracker
|
2013-05-20 07:57 |
| 00055 |
[OASIS Issue Tracker] Commented: (MQTT-13) Topic name has an upper length limit of 32,767 characters ? |
OASIS Issues Tracker
|
2013-05-20 11:02 |
| 00056 |
[OASIS Issue Tracker] Commented: (MQTT-13) Topic name has an upper length limit of 32,767 characters ? |
OASIS Issues Tracker
|
2013-05-20 12:24 |
| 00057 |
[OASIS Issue Tracker] Created: (MQTT-14) Tighten up language in Quality of Service levels and flows |
OASIS Issues Tracker
|
2013-05-20 22:52 |
| 00058 |
[OASIS Issue Tracker] Updated: (MQTT-13) Topic name has an upper length limit of 32,767 characters ? |
OASIS Issues Tracker
|
2013-05-20 22:54 |
| 00059 |
[OASIS Issue Tracker] Commented: (MQTT-14) Tighten up language in Quality of Service levels and flows |
OASIS Issues Tracker
|
2013-05-21 13:57 |
| 00060 |
[OASIS Issue Tracker] Updated: (MQTT-14) Tighten up language in Quality of Service levels and flows |
OASIS Issues Tracker
|
2013-05-21 14:12 |
| 00061 |
Groups - OASIS_MQTT_TC_minutes_09052013.pdf uploaded |
Richard Coppen
|
2013-05-21 14:18 |
| 00062 |
Call for Agenda items |
Mr. Richard Coppen
|
2013-05-21 14:39 |
| 00063 |
[OASIS Issue Tracker] Created: (MQTT-15) Should the CONNECT packet Protocol Name and Protocol Version fields be changed? |
OASIS Issues Tracker
|
2013-05-22 12:16 |
| 00064 |
Re: [mqtt] [OASIS Issue Tracker] Created: (MQTT-15) Should the CONNECT packet Protocol Name and Protocol Version fields be changed? |
Allan Stockdill-Mander
|
2013-05-22 12:26 |
| 00065 |
[OASIS Issue Tracker] Commented: (MQTT-15) Should the CONNECT packet Protocol Name and Protocol Version fields be changed? |
OASIS Issues Tracker
|
2013-05-22 12:38 |
| 00066 |
[OASIS Issue Tracker] Created: (MQTT-16) Reserve $SYS topic name |
OASIS Issues Tracker
|
2013-05-22 13:12 |
| 00067 |
[OASIS Issue Tracker] Updated: (MQTT-16) Reserve $SYS topic name |
OASIS Issues Tracker
|
2013-05-23 08:28 |
| 00068 |
[OASIS Issue Tracker] Commented: (MQTT-16) Reserve $SYS topic name |
OASIS Issues Tracker
|
2013-05-23 08:40 |
| 00069 |
[OASIS Issue Tracker] Commented: (MQTT-16) Reserve $SYS topic name |
OASIS Issues Tracker
|
2013-05-23 09:58 |
| 00070 |
Groups - Event "MQTT TC Meeting" modified |
Richard Coppen
|
2013-05-23 12:35 |
| 00071 |
[OASIS Issue Tracker] Commented: (MQTT-2) UTF-8 for will messages |
OASIS Issues Tracker
|
2013-05-23 14:12 |
| 00072 |
[OASIS Issue Tracker] Commented: (MQTT-2) UTF-8 for will messages |
OASIS Issues Tracker
|
2013-05-23 14:22 |
| 00073 |
[OASIS Issue Tracker] Commented: (MQTT-13) Topic name has an upper length limit of 32,767 characters ? |
OASIS Issues Tracker
|
2013-05-23 14:26 |
| 00074 |
[OASIS Issue Tracker] Commented: (MQTT-16) Reserve $SYS topic name |
OASIS Issues Tracker
|
2013-05-23 14:32 |
| 00075 |
[OASIS Issue Tracker] Commented: (MQTT-16) Reserve $SYS topic name |
OASIS Issues Tracker
|
2013-05-23 14:38 |
| 00076 |
[OASIS Issue Tracker] Issue Comment Edited: (MQTT-16) Reserve $SYS topic name |
OASIS Issues Tracker
|
2013-05-23 14:39 |
| 00077 |
[OASIS Issue Tracker] Commented: (MQTT-5) Should the unused DUP, QoS, and RETAIN flags be zero in the CONNECT message? |
OASIS Issues Tracker
|
2013-05-23 15:06 |
| 00078 |
[OASIS Issue Tracker] Commented: (MQTT-8) Create a new CONNACK return code to indicate that the CONNECT packet was malformed. |
OASIS Issues Tracker
|
2013-05-23 15:24 |
| 00079 |
[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-05-23 15:25 |
| 00080 |
[OASIS Issue Tracker] Created: (MQTT-17) Terminology for MQTT command message. |
OASIS Issues Tracker
|
2013-05-23 16:48 |
| 00081 |
[OASIS Issue Tracker] Commented: (MQTT-8) Create a new CONNACK return code to indicate that the CONNECT packet was malformed. |
OASIS Issues Tracker
|
2013-05-23 16:49 |
| 00082 |
[OASIS Issue Tracker] Created: (MQTT-18) Clarifying what MQTT means by storing data. |
OASIS Issues Tracker
|
2013-05-28 10:43 |
| 00083 |
[OASIS Issue Tracker] Created: (MQTT-19) How Retained publications are deleted. |
OASIS Issues Tracker
|
2013-05-28 14:08 |
| 00084 |
[OASIS Issue Tracker] Updated: (MQTT-13) Topic name has an upper length limit of 32,767 characters ? |
OASIS Issues Tracker
|
2013-05-28 14:37 |
| 00085 |
[OASIS Issue Tracker] Updated: (MQTT-18) Clarifying what MQTT means by storing data. |
OASIS Issues Tracker
|
2013-05-28 15:07 |
| 00086 |
[OASIS Issue Tracker] Created: (MQTT-20) Length of strings. |
OASIS Issues Tracker
|
2013-05-28 15:10 |
| 00087 |
[OASIS Issue Tracker] Updated: (MQTT-20) Length of strings. |
OASIS Issues Tracker
|
2013-05-28 15:11 |
| 00088 |
[OASIS Issue Tracker] Updated: (MQTT-5) Should the unused DUP, QoS, and RETAIN flags be zero in the CONNECT message? |
OASIS Issues Tracker
|
2013-05-28 15:26 |
| 00089 |
[OASIS Issue Tracker] Created: (MQTT-21) Use of flag bits in general. |
OASIS Issues Tracker
|
2013-05-28 15:35 |
| 00090 |
[OASIS Issue Tracker] Commented: (MQTT-19) How Retained publications are deleted. |
OASIS Issues Tracker
|
2013-05-28 15:49 |
| 00091 |
[OASIS Issue Tracker] Commented: (MQTT-19) How Retained publications are deleted. |
OASIS Issues Tracker
|
2013-05-28 16:10 |
| 00092 |
[OASIS Issue Tracker] Commented: (MQTT-19) How Retained publications are deleted. |
OASIS Issues Tracker
|
2013-05-28 17:40 |
| 00093 |
[OASIS Issue Tracker] Commented: (MQTT-19) How Retained publications are deleted. |
OASIS Issues Tracker
|
2013-05-29 09:08 |
| 00094 |
[OASIS Issue Tracker] Commented: (MQTT-19) How Retained publications are deleted. |
OASIS Issues Tracker
|
2013-05-29 09:34 |
| 00095 |
[OASIS Issue Tracker] Commented: (MQTT-19) How Retained publications are deleted. |
OASIS Issues Tracker
|
2013-05-29 09:36 |
| 00096 |
Groups - Event "MQTT TC Meeting" added |
Richard Coppen
|
2013-05-31 10:38 |
| 00097 |
Groups - OASIS_MQTT_TC_minutes_23052013.pdf uploaded |
Richard Coppen
|
2013-05-31 16:21 |
