| 00000 |
[OASIS Issue Tracker] Created: (MQTT-77) Should the Connect packet Useri Name and Password fields be binary rather than UTF-8 |
OASIS Issues Tracker
|
2013-09-03 09:26 |
| 00001 |
[OASIS Issue Tracker] Commented: (MQTT-77) Should the Connect packet Useri Name and Password fields be binary rather than UTF-8 |
OASIS Issues Tracker
|
2013-09-03 10:06 |
| 00002 |
[OASIS Issue Tracker] Commented: (MQTT-22) Specification is ambiguous with regards to dynamic topics |
OASIS Issues Tracker
|
2013-09-05 13:18 |
| 00003 |
[OASIS Issue Tracker] Updated: (MQTT-50) Handling of invalid CONNECT packets |
OASIS Issues Tracker
|
2013-09-05 13:34 |
| 00004 |
[OASIS Issue Tracker] Commented: (MQTT-22) Specification is ambiguous with regards to dynamic topics |
OASIS Issues Tracker
|
2013-09-05 13:38 |
| 00005 |
[OASIS Issue Tracker] Updated: (MQTT-54) How long should a client or server wait for, or expect to wait for, a response |
OASIS Issues Tracker
|
2013-09-05 13:40 |
| 00006 |
[OASIS Issue Tracker] Updated: (MQTT-22) Specification is ambiguous with regards to dynamic topics |
OASIS Issues Tracker
|
2013-09-05 14:04 |
| 00007 |
[OASIS Issue Tracker] Updated: (MQTT-68) Message delivery retry is not required where no network failure is detected |
OASIS Issues Tracker
|
2013-09-05 14:12 |
| 00008 |
[OASIS Issue Tracker] Created: (MQTT-78) Abstract references to the transport layer for MQTT |
OASIS Issues Tracker
|
2013-09-05 14:52 |
| 00009 |
[OASIS Issue Tracker] Commented: (MQTT-78) Abstract references to the transport layer for MQTT |
OASIS Issues Tracker
|
2013-09-05 15:10 |
| 00010 |
[OASIS Issue Tracker] Created: (MQTT-79) Allow deletion of QoS1/2 messages in rare circumstances |
OASIS Issues Tracker
|
2013-09-05 15:14 |
| 00011 |
[OASIS Issue Tracker] Created: (MQTT-80) Editorial issues following read through of WD10 |
OASIS Issues Tracker
|
2013-09-06 11:00 |
| 00012 |
MQTT Security Subcommittee - Security Content Proposal Submission |
Geoff Brown
|
2013-09-10 15:24 |
| 00013 |
Steps to CSD |
Mr. Richard Coppen
|
2013-09-10 20:59 |
| 00014 |
Groups - mqtt-v3.1.1-wd11.doc uploaded |
Rahul Gupta
|
2013-09-11 05:28 |
| 00015 |
Groups - mqtt-v3.1.1-wd11.pdf uploaded |
Rahul Gupta
|
2013-09-11 05:29 |
| 00016 |
[OASIS Issue Tracker] Commented: (MQTT-77) Should the Connect packet Useri Name and Password fields be binary rather than UTF-8 |
OASIS Issues Tracker
|
2013-09-11 17:03 |
| 00017 |
[OASIS Issue Tracker] Commented: (MQTT-78) Abstract references to the transport layer for MQTT |
OASIS Issues Tracker
|
2013-09-11 17:03 |
| 00018 |
Groups - Event "MQTT TC Meeting" modified |
Richard Coppen
|
2013-09-11 17:07 |
| 00019 |
[OASIS Issue Tracker] Commented: (MQTT-42) Clean session and random client ids |
OASIS Issues Tracker
|
2013-09-12 13:03 |
| 00020 |
[OASIS Issue Tracker] Updated: (MQTT-42) Clean session and random client ids |
OASIS Issues Tracker
|
2013-09-12 15:11 |
| 00021 |
Important: WEEKLY TC Calls |
Mr. Richard Coppen
|
2013-09-12 15:43 |
| 00022 |
Groups - OASIS_MQTT_TC_minutes_12092013.pdf uploaded |
Julien Niset
|
2013-09-13 15:29 |
| 00023 |
[OASIS Issue Tracker] Created: (MQTT-81) WD11 - typo in line 1161 |
OASIS Issues Tracker
|
2013-09-17 14:27 |
| 00024 |
[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-09-18 09:57 |
| 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-09-18 09:57 |
| 00026 |
[OASIS Issue Tracker] Created: (MQTT-82) Provide a way for clean-session=1 clients to specify no client identifier |
OASIS Issues Tracker
|
2013-09-18 10:19 |
| 00027 |
[OASIS Issue Tracker] Updated: (MQTT-16) Reserve $SYS topic name |
OASIS Issues Tracker
|
2013-09-18 10:19 |
| 00028 |
[OASIS Issue Tracker] Updated: (MQTT-10) Should Qos=0 retained messages be persisted in the server? |
OASIS Issues Tracker
|
2013-09-18 10:35 |
| 00029 |
[OASIS Issue Tracker] Commented: (MQTT-10) Should Qos=0 retained messages be persisted in the server? |
OASIS Issues Tracker
|
2013-09-18 10:35 |
| 00030 |
[OASIS Issue Tracker] Updated: (MQTT-8) Create a new CONNACK return code to indicate that the CONNECT packet was malformed. |
OASIS Issues Tracker
|
2013-09-18 10:45 |
| 00031 |
[OASIS Issue Tracker] Updated: (MQTT-1) Flowing MQTT V3.1.1 protocol over a WebSocket |
OASIS Issues Tracker
|
2013-09-18 10:51 |
| 00032 |
[OASIS Issue Tracker] Commented: (MQTT-79) Allow deletion of QoS1/2 messages in rare circumstances |
OASIS Issues Tracker
|
2013-09-18 13:05 |
| 00033 |
[OASIS Issue Tracker] Updated: (MQTT-14) Tighten up language in Quality of Service levels and flows |
OASIS Issues Tracker
|
2013-09-18 13:29 |
| 00034 |
[OASIS Issue Tracker] Updated: (MQTT-50) Handling of invalid CONNECT packets |
OASIS Issues Tracker
|
2013-09-18 13:49 |
| 00035 |
[OASIS Issue Tracker] Commented: (MQTT-50) Handling of invalid CONNECT packets |
OASIS Issues Tracker
|
2013-09-18 13:49 |
| 00036 |
[OASIS Issue Tracker] Updated: (MQTT-54) How long should a client or server wait for, or expect to wait for, a response |
OASIS Issues Tracker
|
2013-09-18 14:01 |
| 00037 |
[OASIS Issue Tracker] Commented: (MQTT-55) What should happen if a client issues multiple connect calls on the same TCP Connection |
OASIS Issues Tracker
|
2013-09-18 14:21 |
| 00038 |
[OASIS Issue Tracker] Commented: (MQTT-58) How many messages are received for overlapping subscriptions? |
OASIS Issues Tracker
|
2013-09-18 14:59 |
| 00039 |
[OASIS Issue Tracker] Updated: (MQTT-58) How many messages are received for overlapping subscriptions? |
OASIS Issues Tracker
|
2013-09-18 15:09 |
| 00040 |
[OASIS Issue Tracker] Updated: (MQTT-27) Handling of the Dup Flag (section 2.1.2.1) |
OASIS Issues Tracker
|
2013-09-18 15:11 |
| 00041 |
[OASIS Issue Tracker] Commented: (MQTT-58) How many messages are received for overlapping subscriptions? |
OASIS Issues Tracker
|
2013-09-18 15:13 |
| 00042 |
[OASIS Issue Tracker] Updated: (MQTT-27) Handling of the Dup Flag (section 2.1.2.1) |
OASIS Issues Tracker
|
2013-09-18 15:25 |
| 00043 |
[OASIS Issue Tracker] Commented: (MQTT-68) Message delivery retry is not required where no network failure is detected |
OASIS Issues Tracker
|
2013-09-18 15:51 |
| 00044 |
[OASIS Issue Tracker] Updated: (MQTT-68) Message delivery retry is not required where no network failure is detected |
OASIS Issues Tracker
|
2013-09-18 15:51 |
| 00045 |
[OASIS Issue Tracker] Commented: (MQTT-22) Specification is ambiguous with regards to dynamic topics |
OASIS Issues Tracker
|
2013-09-18 15:55 |
| 00046 |
[OASIS Issue Tracker] Commented: (MQTT-42) Clean session and random client ids |
OASIS Issues Tracker
|
2013-09-18 15:57 |
| 00047 |
[OASIS Issue Tracker] Updated: (MQTT-76) Should "+" be allowed at the beginning of the topic filter in a subscription? |
OASIS Issues Tracker
|
2013-09-18 16:05 |
| 00048 |
[OASIS Issue Tracker] Commented: (MQTT-76) Should "+" be allowed at the beginning of the topic filter in a subscription? |
OASIS Issues Tracker
|
2013-09-18 16:07 |
| 00049 |
[OASIS Issue Tracker] Updated: (MQTT-64) Edge case handling of unsubscribe |
OASIS Issues Tracker
|
2013-09-18 16:59 |
| 00050 |
Groups - Event "MQTT TC Meeting" modified |
Richard Coppen
|
2013-09-18 17:18 |
| 00051 |
[OASIS Issue Tracker] Created: (MQTT-83) Advice on clean session = 0 |
OASIS Issues Tracker
|
2013-09-18 22:33 |
| 00052 |
[OASIS Issue Tracker] Created: (MQTT-84) Typos in 3.1.2.3.1 |
OASIS Issues Tracker
|
2013-09-18 22:39 |
| 00053 |
[OASIS Issue Tracker] Commented: (MQTT-22) Specification is ambiguous with regards to dynamic topics |
OASIS Issues Tracker
|
2013-09-19 03:29 |
| 00054 |
[OASIS Issue Tracker] Commented: (MQTT-42) Clean session and random client ids |
OASIS Issues Tracker
|
2013-09-19 03:31 |
| 00055 |
[OASIS Issue Tracker] Commented: (MQTT-84) Typos in 3.1.2.3.1 |
OASIS Issues Tracker
|
2013-09-19 03:35 |
| 00056 |
[OASIS Issue Tracker] Created: (MQTT-85) Comments following read through of WD11 |
OASIS Issues Tracker
|
2013-09-19 07:48 |
| 00057 |
[OASIS Issue Tracker] Commented: (MQTT-58) How many messages are received for overlapping subscriptions? |
OASIS Issues Tracker
|
2013-09-19 08:21 |
| 00058 |
Groups - MQTT TC JIRA process update uploaded |
Richard Coppen
|
2013-09-19 13:04 |
| 00059 |
Groups - Event "MQTT TC Meeting" modified |
Richard Coppen
|
2013-09-19 13:08 |
| 00060 |
[OASIS Issue Tracker] Commented: (MQTT-79) Allow deletion of QoS1/2 messages in rare circumstances |
OASIS Issues Tracker
|
2013-09-19 14:49 |
| 00061 |
[OASIS Issue Tracker] Commented: (MQTT-82) Provide a way for clean-session=1 clients to specify no client identifier |
OASIS Issues Tracker
|
2013-09-19 14:49 |
| 00062 |
[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-09-19 14:57 |
| 00063 |
Jira issues not discussed today |
Mr. Richard Coppen
|
2013-09-19 15:47 |
| 00064 |
[OASIS Issue Tracker] Updated: (MQTT-16) Reserve $SYS topic name |
OASIS Issues Tracker
|
2013-09-19 15:53 |
| 00065 |
Groups - Event "MQTT Security Subcommittee call" added |
Richard Coppen
|
2013-09-20 15:35 |
| 00066 |
[OASIS Issue Tracker] Commented: (MQTT-75) Defintion for REASONABLE amount of time |
OASIS Issues Tracker
|
2013-09-25 08:35 |
| 00067 |
[OASIS Issue Tracker] Commented: (MQTT-85) Comments following read through of WD11 |
OASIS Issues Tracker
|
2013-09-25 09:45 |
| 00068 |
Working draft 12 now available |
Dr. Andrew Banks
|
2013-09-25 10:59 |
| 00069 |
Groups - OASIS_MQTT_TC_minutes_19092013.pdf uploaded |
Louis-P. Lamoureux
|
2013-09-25 13:28 |
| 00070 |
Groups - Event "MQTT TC Meeting" modified |
Richard Coppen
|
2013-09-26 10:57 |
| 00071 |
Jira issues to review on today's call |
Mr. Richard Coppen
|
2013-09-26 11:05 |
| 00072 |
Re: [mqtt] Jira issues to review on today's call |
Andrew Schofield
|
2013-09-26 11:52 |
| 00073 |
[OASIS Issue Tracker] Commented: (MQTT-68) Message delivery retry is not required where no network failure is detected |
OASIS Issues Tracker
|
2013-09-26 15:15 |
| 00074 |
[OASIS Issue Tracker] Updated: (MQTT-68) Message delivery retry is not required where no network failure is detected |
OASIS Issues Tracker
|
2013-09-26 15:20 |
| 00075 |
[OASIS Issue Tracker] Updated: (MQTT-54) How long should a client or server wait for, or expect to wait for, a response |
OASIS Issues Tracker
|
2013-09-26 17:47 |
| 00076 |
[OASIS Issue Tracker] Updated: (MQTT-77) Should the Connect packet User Name and Password fields be binary rather than UTF-8 |
OASIS Issues Tracker
|
2013-09-26 17:47 |
| 00077 |
[OASIS Issue Tracker] Commented: (MQTT-54) How long should a client or server wait for, or expect to wait for, a response |
OASIS Issues Tracker
|
2013-09-26 17:55 |
| 00078 |
[OASIS Issue Tracker] Updated: (MQTT-44) Specific details for UTF-8 Strings |
OASIS Issues Tracker
|
2013-09-27 13:10 |
| 00079 |
[OASIS Issue Tracker] Updated: (MQTT-73) Message ordering behaviour |
OASIS Issues Tracker
|
2013-09-27 13:39 |
| 00080 |
[OASIS Issue Tracker] Updated: (MQTT-71) Are messages order within Topic+Qos or within Qos |
OASIS Issues Tracker
|
2013-09-27 13:39 |
| 00081 |
[OASIS Issue Tracker] Updated: (MQTT-60) Are topic strings normalized at all? |
OASIS Issues Tracker
|
2013-09-27 13:41 |
| 00082 |
[OASIS Issue Tracker] Updated: (MQTT-75) Defintion for REASONABLE amount of time |
OASIS Issues Tracker
|
2013-09-27 13:44 |
| 00083 |
[OASIS Issue Tracker] Updated: (MQTT-78) Abstract references to the transport layer for MQTT |
OASIS Issues Tracker
|
2013-09-27 13:51 |
| 00084 |
Groups - OASIS_MQTT_TC_minutes_26092013.pdf uploaded |
Julien Niset
|
2013-09-30 14:29 |
