| 1 |
MQTT TC Meeting |
63 |
Dec 2014 |
| 2 |
Groups - Event "MQTT TC Meeting" modified |
53 |
Apr 2013 |
| 3 |
[OASIS Issue Tracker] (MQTT-257) Flow Control |
36 |
Mar 2015 |
| 4 |
Modified: MQTT TC Meeting |
34 |
Nov 2014 |
| 5 |
[OASIS Issue Tracker] (MQTT-260) Add a CONNACK code of 'Try Another Server' |
30 |
Mar 2015 |
| 6 |
[OASIS Issue Tracker] (MQTT-197) Support request/reply as a new MEP |
29 |
Mar 2015 |
| 7 |
[OASIS Issue Tracker] (MQTT-256) Message Format indication and message metadata in general. |
26 |
Dec 2015 |
| 8 |
[OASIS Issue Tracker] (MQTT-235) NoLocal Subscription for MQTT Subscribers |
25 |
Jul 2014 |
| 9 |
[OASIS Issue Tracker] (MQTT-236) Consolidate Acks, enable negative acknowledgements. |
25 |
Aug 2014 |
| 10 |
[OASIS Issue Tracker] (MQTT-234) Shared Subscriptions |
23 |
Jul 2014 |
| 11 |
[OASIS Issue Tracker] (MQTT-253) Subscription identification |
20 |
Mar 2015 |
| 12 |
[OASIS Issue Tracker] (MQTT-203) MQTT URI Scheme |
19 |
Mar 2014 |
| 13 |
[OASIS Issue Tracker] (MQTT-276) MQTT enhancements for large scale distributed systems |
18 |
Aug 2015 |
| 14 |
[OASIS Issue Tracker] (MQTT-263) Simplified State Management |
17 |
Mar 2015 |
| 15 |
[OASIS Issue Tracker] (MQTT-498) No way to set properties on will message |
16 |
Sep 2017 |
| 16 |
[OASIS Issue Tracker] (MQTT-542) Allow 0-length client id |
16 |
Apr 2020 |
| 17 |
[OASIS Issue Tracker] (MQTT-251) Return server assigned client id to client |
15 |
Mar 2015 |
| 18 |
[OASIS Issue Tracker] (MQTT-324) Consolidate list of optional server capabilities and review how they are signaled to the client |
15 |
Nov 2016 |
| 19 |
[OASIS Issue Tracker] (MQTT-541) Cleansession should act like MQTT 5.0 not 3.1.1 |
15 |
Apr 2020 |
| 20 |
[OASIS Issue Tracker] (MQTT-249) Add expiry capabilities to MQTT. |
14 |
Mar 2015 |
| 21 |
[OASIS Issue Tracker] (MQTT-269) MQTT-SN Feature: Topic Registration |
14 |
Jul 2015 |
| 22 |
[OASIS Issue Tracker] (MQTT-320) Expectations of timing accuracy in MQTT implementations |
14 |
Nov 2016 |
| 23 |
[OASIS Issue Tracker] (MQTT-440) Names in Appendix a should be in normal format |
14 |
Jun 2017 |
| 24 |
[OASIS Issue Tracker] (MQTT-574) Add reason code/string to the disconnect packet |
14 |
Nov 2020 |
| 25 |
[OASIS Issue Tracker] (MQTT-262) Clarify will messages if server disconnects |
13 |
Mar 2015 |
| 26 |
[OASIS Issue Tracker] (MQTT-286) Make Qos 2 Delivery Method 'B' Normative |
13 |
Jun 2016 |
| 27 |
[OASIS Issue Tracker] (MQTT-321) Add User Defined Property to ACKs |
13 |
Nov 2016 |
| 28 |
[OASIS Issue Tracker] (MQTT-217) Deliver implementation guidance around overlapping subscriptions |
12 |
May 2014 |
| 29 |
[OASIS Issue Tracker] (MQTT-255) Alternate authentication mechanisms |
12 |
Mar 2015 |
| 30 |
[OASIS Issue Tracker] (MQTT-546) Improve description of sleeping clients message flows |
12 |
Apr 2020 |
| 31 |
[OASIS Issue Tracker] (MQTT-550) Mandate the use of separate id spaces for device normal topic alias's |
12 |
Apr 2020 |
| 32 |
[OASIS Issue Tracker] (MQTT-571) New structure of the CONNACK packet |
12 |
Jul 2020 |
| 33 |
[OASIS Issue Tracker] (MQTT-252) Support for large message transmission |
11 |
Feb 2015 |
| 34 |
[OASIS Issue Tracker] (MQTT-270) SN Feature: server initiated disconnects |
11 |
Sep 2015 |
| 35 |
[OASIS Issue Tracker] (MQTT-278) Server keepalive |
11 |
Apr 2016 |
| 36 |
[OASIS Issue Tracker] (MQTT-421) WD11 Review comments by Stefan (restored from MQTT-417) |
11 |
Mar 2017 |
| 37 |
[OASIS Issue Tracker] (MQTT-464) Add reason code 150 to PUBACK packet |
11 |
Jun 2017 |
| 38 |
[OASIS Issue Tracker] (MQTT-555) Clarification of broker behaviour when client REGISTERs a PREDEFINED topic |
11 |
Apr 2020 |
| 39 |
Groups - Event "MQTT TC Meeting" added |
10 |
Apr 2013 |
| 40 |
Re: [mqtt] Groups - Event "MQTT TC Meeting" modified |
10 |
Jul 2013 |
| 41 |
Cancelled: MQTT TC Meeting |
10 |
Nov 2014 |
| 42 |
[OASIS Issue Tracker] (MQTT-327) Words like Malformed Control Packet and Protocol Errors are used randomly |
10 |
Dec 2016 |
| 43 |
[OASIS Issue Tracker] (MQTT-342) Maximum Packet Size - value to be sent [set] to zero and more |
10 |
Jan 2017 |
| 44 |
[OASIS Issue Tracker] (MQTT-559) DISCONNECT duration 16-bit field does not allow long enough to sleep |
10 |
Apr 2020 |
| 45 |
[OASIS Issue Tracker] Commented: (MQTT-16) Reserve $SYS topic name |
9 |
May 2013 |
| 46 |
[OASIS Issue Tracker] Commented: (MQTT-58) How many messages are received for overlapping subscriptions? |
9 |
Jul 2013 |
| 47 |
[OASIS Issue Tracker] (MQTT-271) Describing small device limitations, aka "the Arduino problem" |
9 |
Jul 2015 |
| 48 |
Recharter: Shared subscriptions and $share |
9 |
Apr 2016 |
| 49 |
[OASIS Issue Tracker] (MQTT-384) 3.3.2.4 Payload Format Indicator.- comments |
9 |
Jan 2017 |
| 50 |
[OASIS Issue Tracker] (MQTT-385) Simple clients skipping properties |
9 |
Jan 2017 |
| 51 |
[OASIS Issue Tracker] (MQTT-465) Change description of User Property |
9 |
Jun 2017 |
| 52 |
[OASIS Issue Tracker] (MQTT-466) Add reason code 150 to PUBREC packet |
9 |
Jun 2017 |
| 53 |
[OASIS Issue Tracker] (MQTT-543) Allow long topic names for publish of all QoS |
9 |
Apr 2020 |
| 54 |
[OASIS Issue Tracker] (MQTT-553) Clarify whether clients should maintain normal topicIds during sleep state |
9 |
Apr 2020 |
| 55 |
[OASIS Issue Tracker] (MQTT-568) Authentication |
9 |
Jun 2020 |
| 56 |
[OASIS Issue Tracker] Commented: (MQTT-22) Specification is ambiguous with regards to dynamic topics |
8 |
Jun 2013 |
| 57 |
[OASIS Issue Tracker] Commented: (MQTT-42) Clean session and random client ids |
8 |
Jul 2013 |
| 58 |
[OASIS Issue Tracker] Updated: (MQTT-194) Status of chapter 6 Using WebSocket as a network transport. is unclear |
8 |
Feb 2014 |
| 59 |
[OASIS Issue Tracker] (MQTT-256) Message Format indication |
8 |
Mar 2015 |
| 60 |
[OASIS Issue Tracker] (MQTT-285) Subscribe options for retained messages |
8 |
Apr 2016 |
| 61 |
[OASIS Issue Tracker] (MQTT-300) Metadata: CONNACK Maximum QoS |
8 |
Sep 2016 |
| 62 |
[OASIS Issue Tracker] (MQTT-293) Recommendations for securing an MQTT server |
8 |
Sep 2016 |
| 63 |
[OASIS Issue Tracker] (MQTT-417) WD11 Review comments by Konstantin |
8 |
Mar 2017 |
| 64 |
[OASIS Issue Tracker] (MQTT-545) Remove retained messages by sending QoS 0 0 length publish |
8 |
Apr 2020 |
| 65 |
[OASIS Issue Tracker] (MQTT-554) Should QoS 0 messages be held on a message queue during sleep cycle |
8 |
Apr 2020 |
| 66 |
Groups - Event "MQTT TC Kickoff" modified |
7 |
Mar 2013 |
| 67 |
[OASIS Issue Tracker] Commented: (MQTT-60) Are topic strings normalized at all? |
7 |
Jul 2013 |
| 68 |
[OASIS Issue Tracker] (MQTT-261) Add a CONNACK return code for 'Upgrade to TLS' |
7 |
Mar 2015 |
| 69 |
MQTT TC Meeting (Conference Call) |
7 |
Jul 2015 |
| 70 |
[OASIS Issue Tracker] (MQTT-274) Request-Response needs clarity on what is supportable in MQTT 3.1.1 |
7 |
Aug 2015 |
| 71 |
[OASIS Issue Tracker] (MQTT-290) Session Expiry Will message. |
7 |
Jul 2016 |
| 72 |
[OASIS Issue Tracker] (MQTT-299) Metadata: CONNECT and CONNACK Maximum Message Length |
7 |
Sep 2016 |
| 73 |
[OASIS Issue Tracker] (MQTT-306) Clarify Handling of Malformed DISCONNECT command in WD04 |
7 |
Sep 2016 |
| 74 |
[OASIS Issue Tracker] (MQTT-322) Add ContentType property to PUBLISH messages |
7 |
Nov 2016 |
| 75 |
[OASIS Issue Tracker] (MQTT-326) Consolidate Handling for NAKs, Protocol Errors and |
7 |
Nov 2016 |
| 76 |
[OASIS Issue Tracker] (MQTT-468) Single UNSUBACK Reason Code for SUBSCRIBE |
7 |
Jun 2017 |
| 77 |
[OASIS Issue Tracker] (MQTT-540) Messages shorter than 256 octets may use the 1-octet format |
7 |
Apr 2020 |
| 78 |
[OASIS Issue Tracker] (MQTT-544) Add return code to UNSUBACK |
7 |
Apr 2020 |
| 79 |
[OASIS Issue Tracker] (MQTT-558) Short topic names allowed formats |
7 |
Apr 2020 |
| 80 |
[OASIS Issue Tracker] (MQTT-564) MQTT 5.0 behaviour for Request Problem Information |
7 |
May 2020 |
| 81 |
[OASIS Issue Tracker] (MQTT-567) Should ping in connected mode work the same as in sleep mode |
7 |
Jun 2020 |
| 82 |
[OASIS Issue Tracker] (MQTT-572) Clarification of text advising number of inflight messages |
7 |
Aug 2020 |
| 83 |
Motion to request a TC GitHub repository at https://github.com/oasis-tcs/mqtt |
7 |
Dec 2023 |
| 84 |
[OASIS Issue Tracker] Commented: (MQTT-19) How Retained publications are deleted. |
6 |
May 2013 |
| 85 |
[OASIS Issue Tracker] Updated: (MQTT-45) summary of editorial issues from read through of WD07 |
6 |
Jul 2013 |
| 86 |
Re: [TC Admin] Liaison letter from ISO/IEC JTC 1/SWG 5 |
6 |
Jul 2013 |
| 87 |
[OASIS Issue Tracker] Updated: (MQTT-70) Assumptions for QoS levels 1 and 2 replaced by new Storing State section |
6 |
Nov 2013 |
| 88 |
[OASIS Issue Tracker] Updated: (MQTT-151) Clarify "store data", and more generally make normative statements self-explanatory (as much as possible) |
6 |
Feb 2014 |
| 89 |
[OASIS Issue Tracker] Updated: (MQTT-192) Will Message clarification (CSD review comment) |
6 |
Feb 2014 |
| 90 |
[OASIS Issue Tracker] (MQTT-216) Explore the downgrade of MUST level requirements to check UTF-8 encodings |
6 |
May 2014 |
| 91 |
Modified MQTT TC Meeting |
6 |
Aug 2014 |
| 92 |
[OASIS Issue Tracker] (MQTT-250) Merge the MQTT 3.1.1 and MQTT-SN 1.2 specifications |
6 |
Mar 2015 |
| 93 |
[OASIS Issue Tracker] (MQTT-259) Describe using DNS SRV records to scale MQTT as a committee note |
6 |
Mar 2015 |
| 94 |
[OASIS Issue Tracker] (MQTT-272) Recommend adding time to live to requests. |
6 |
Jul 2015 |
| 95 |
[OASIS Issue Tracker] (MQTT-273) Comments on request / reply TC note |
6 |
Aug 2015 |
| 96 |
[OASIS Issue Tracker] (MQTT-301) Metadata: CONNACK Retained messages supported |
6 |
Sep 2016 |
| 97 |
[OASIS Issue Tracker] (MQTT-307) Clarify Handling of DISCONNECT Expiry interval error in WD04 |
6 |
Sep 2016 |
| 98 |
[OASIS Issue Tracker] (MQTT-394) 3.4 PUBACK – Publish acknowledgement - comments |
6 |
Jan 2017 |
| 99 |
[OASIS Issue Tracker] (MQTT-417) Feedback comments on WD 11 by Stefan |
6 |
Mar 2017 |
| 100 |
[OASIS Issue Tracker] (MQTT-436) Feedback from Ken Borgendale on WD14 |
6 |
May 2017 |
| 101 |
[OASIS Issue Tracker] (MQTT-492) Validating the payload format |
6 |
Jul 2017 |
| 102 |
[OASIS Issue Tracker] (MQTT-505) Denial of Service Attacks possible |
6 |
Sep 2017 |
| 103 |
[OASIS Issue Tracker] (MQTT-522) Clarification of the behaviour of properties for retained messages |
6 |
Sep 2017 |
| 104 |
[OASIS Issue Tracker] (MQTT-539) TopicId in PUBACK is superfluous |
6 |
Apr 2020 |
| 105 |
[OASIS Issue Tracker] (MQTT-549) Remove the discovery procedure |
6 |
Apr 2020 |
| 106 |
[OASIS Issue Tracker] (MQTT-566) Capabilities packet |
6 |
May 2020 |
| 107 |
[OASIS Issue Tracker] Commented: (MQTT-1) Flowing MQTT V3.1.1 protocol over a WebSocket |
5 |
May 2013 |
| 108 |
[OASIS Issue Tracker] Commented: (MQTT-2) UTF-8 for will messages |
5 |
May 2013 |
| 109 |
[OASIS Issue Tracker] Commented: (MQTT-4) Flowing MQTT messages before CONNACK is received in the client. |
5 |
May 2013 |
| 110 |
[OASIS Issue Tracker] Commented: (MQTT-11) Length of client Identifier |
5 |
May 2013 |
| 111 |
[OASIS Issue Tracker] Updated: (MQTT-18) Clarifying what MQTT means by storing data. |
5 |
May 2013 |
| 112 |
[OASIS Issue Tracker] Commented: (MQTT-55) What should happen if a client issues multiple connect calls on the same TCP Connection |
5 |
Jul 2013 |
| 113 |
Groups - Event "MQTT Security weekly call" modified |
5 |
Aug 2013 |
| 114 |
[OASIS Issue Tracker] Updated: (MQTT-102) What does QoS 0 mean? Should it be called "At Most Once"? |
5 |
Nov 2013 |
| 115 |
[OASIS Issue Tracker] Commented: (MQTT-102) What does QoS 0 mean? Should it be called "At Most Once"? |
5 |
Nov 2013 |
| 116 |
[OASIS Issue Tracker] Updated: (MQTT-156) Vague treatment of "at most once" |
5 |
Feb 2014 |
| 117 |
[OASIS Issue Tracker] (MQTT-204) Make $ topic separation normative |
5 |
Mar 2014 |
| 118 |
[OASIS Issue Tracker] (MQTT-233) Modify Language around use of $ topics |
5 |
May 2014 |
| 119 |
Leave of Absence |
5 |
Aug 2014 |
| 120 |
[OASIS Issue Tracker] (MQTT-247) Incorrect hyperlink to RFC2119 |
5 |
Sep 2014 |
| 121 |
[OASIS Issue Tracker] (MQTT-280) MQTT 3.1.1 Session Take Over and Will Message Delivery |
5 |
Mar 2016 |
| 122 |
Groups - Jira input list for April face-to-face session uploaded |
5 |
Apr 2016 |
| 123 |
[OASIS Issue Tracker] (MQTT-284) Enhanced problem determination |
5 |
Apr 2016 |
| 124 |
[OASIS Issue Tracker] (MQTT-291) Collect Version Compatibility and Upgrade Issues |
5 |
Jul 2016 |
| 125 |
[OASIS Issue Tracker] (MQTT-292) Modify statements about message ordering |
5 |
Aug 2016 |
| 126 |
[OASIS Issue Tracker] (MQTT-293) Review Section 3.1.4 CONNECT Response behaviour and Section 5 Security |
5 |
Aug 2016 |
| 127 |
[OASIS Issue Tracker] (MQTT-295) Eliminate Retransmission during a Transport Connection in MQTT 5.0 |
5 |
Aug 2016 |
| 128 |
[OASIS Issue Tracker] (MQTT-308) Further Ack return codes. |
5 |
Sep 2016 |
| 129 |
[OASIS Issue Tracker] (MQTT-323) Comments from reading MQTT Version 5.0 WD08 |
5 |
Nov 2016 |
| 130 |
[OASIS Issue Tracker] (MQTT-325) Use Disconnect RC 0x82 in place of Nack for incorrect Packet Id. |
5 |
Nov 2016 |
| 131 |
[OASIS Issue Tracker] (MQTT-329) Remove the ID/Value Pair length field |
5 |
Dec 2016 |
| 132 |
[OASIS Issue Tracker] (MQTT-340) If this value is not 5 ... |
5 |
Jan 2017 |
| 133 |
[OASIS Issue Tracker] (MQTT-351) "you" and your "loose" messages ... |
5 |
Jan 2017 |
| 134 |
[OASIS Issue Tracker] (MQTT-358) Receive Maximum - Not setting the Receive Maximum value |
5 |
Jan 2017 |
| 135 |
[OASIS Issue Tracker] (MQTT-371) Missing QOS-NOT-SUPPORTED Return Code |
5 |
Jan 2017 |
| 136 |
[OASIS Issue Tracker] (MQTT-373) 3.3.1.2 QoS - comments |
5 |
Jan 2017 |
| 137 |
[OASIS Issue Tracker] (MQTT-386) Question -Should Topic Alias be included in Terminology? |
5 |
Jan 2017 |
| 138 |
[OASIS Issue Tracker] (MQTT-387) 3.3.2.6 Topic Alias. - comments |
5 |
Jan 2017 |
| 139 |
[OASIS Issue Tracker] (MQTT-400) Consistency: Remaining Length field |
5 |
Jan 2017 |
| 140 |
[OASIS Issue Tracker] (MQTT-402) 3.5 PUBREC – Publish received - comments |
5 |
Jan 2017 |
| 141 |
[OASIS Issue Tracker] (MQTT-431) Review Re-authentication mechanism |
5 |
May 2017 |
| 142 |
[OASIS Issue Tracker] (MQTT-467) Single SUBACK Reason Code for SUBSCRIBE |
5 |
Jun 2017 |
| 143 |
[OASIS Issue Tracker] (MQTT-481) Clarify/define WIll Message behavior for Server intiated disconnect |
5 |
Jun 2017 |
| 144 |
[OASIS Issue Tracker] (MQTT-486) RFC 2119 scan for MAYs |
5 |
Jun 2017 |
| 145 |
[OASIS Issue Tracker] (MQTT-536) Revocation of authority to publish and subscribe |
5 |
May 2019 |
| 146 |
[OASIS Issue Tracker] (MQTT-563) Client Id format |
5 |
May 2020 |
| 147 |
[OASIS Issue Tracker] Updated: (MQTT-4) Flowing MQTT messages before CONNACK is received in the client. |
4 |
May 2013 |
| 148 |
[OASIS Issue Tracker] Updated: (MQTT-7) Can the client and server store QoS=0 messages after a client using CleanSession=0 has disconnected? |
4 |
May 2013 |
| 149 |
[OASIS Issue Tracker] Commented: (MQTT-13) Topic name has an upper length limit of 32,767 characters ? |
4 |
May 2013 |
| 150 |
[OASIS Issue Tracker] Commented: (MQTT-17) Terminology for MQTT command message. |
4 |
Jun 2013 |
| 151 |
[OASIS Issue Tracker] Updated: (MQTT-10) Should Qos=0 retained messages be persisted in the server? |
4 |
Jun 2013 |
| 152 |
[OASIS Issue Tracker] Commented: (MQTT-36) Editorial comments on Connect Payload |
4 |
Jun 2013 |
| 153 |
Leave of Absence Notification |
4 |
Jul 2013 |
| 154 |
[OASIS Issue Tracker] Updated: (MQTT-54) How long should a client or server wait for, or expect to wait for, a response |
4 |
Jul 2013 |
| 155 |
Groups - Event "MQTT TC Meeting" cancelled |
4 |
Oct 2013 |
| 156 |
[OASIS Issue Tracker] Commented: (MQTT-103) Normative meaning of Keep Alive = 0 |
4 |
Nov 2013 |
| 157 |
[OASIS Issue Tracker] Updated: (MQTT-106) Behaviour when Will Flag = 0 |
4 |
Nov 2013 |
| 158 |
[OASIS Issue Tracker] (MQTT-208) confusing narrative around redelivery of control packets |
4 |
Mar 2014 |
| 159 |
[OASIS Issue Tracker] (MQTT-245) Remove trailing slashes from topic strings (review comment from Nicholas Humfrey) |
4 |
Aug 2014 |
| 160 |
Groups - MQTT Candidate OASIS Standard 02 uploaded |
4 |
Sep 2014 |
| 161 |
MQTT Version 3.1.1 becomes an OASIS Standard |
4 |
Oct 2014 |
| 162 |
[OASIS Issue Tracker] (MQTT-278) Server initiated ping |
4 |
Sep 2015 |
| 163 |
[OASIS Issue Tracker] (MQTT-282) Consider refactoring existing packets to express existing fields as metadata |
4 |
Apr 2016 |
| 164 |
Template for recontribution message |
4 |
Jun 2016 |
| 165 |
[OASIS Issue Tracker] (MQTT-287) Clarify text to insure unified packet identifier space |
4 |
Jun 2016 |
| 166 |
Starter Document for MQTT Version 5.0 |
4 |
Jul 2016 |
| 167 |
[OASIS Issue Tracker] (MQTT-294) Incorrect version number in section 3.1.2.2 Protocol Level |
4 |
Aug 2016 |
| 168 |
[OASIS Issue Tracker] (MQTT-296) Variable Byte Integer decode does not check for shortest encoding |
4 |
Sep 2016 |
| 169 |
[OASIS Issue Tracker] (MQTT-297) Packet Indentifier Leak on lost Subscription commands |
4 |
Sep 2016 |
| 170 |
[OASIS Issue Tracker] (MQTT-341) Shared Subscription edits |
4 |
Jan 2017 |
| 171 |
[OASIS Issue Tracker] (MQTT-345) re connection and re transmission |
4 |
Jan 2017 |
| 172 |
[OASIS Issue Tracker] (MQTT-392) 3.3.5 Actions - comments |
4 |
Jan 2017 |
| 173 |
[OASIS Issue Tracker] (MQTT-397) Return Code v |
4 |
Jan 2017 |
| 174 |
[OASIS Issue Tracker] (MQTT-399) 3.5 PUBREC – Publish received - comments |
4 |
Jan 2017 |
| 175 |
[OASIS Issue Tracker] (MQTT-411) Return code for Payload does not match Payload Format |
4 |
Jan 2017 |
| 176 |
[OASIS Issue Tracker] (MQTT-412) Consolidated error handling. |
4 |
Jan 2017 |
| 177 |
[OASIS Issue Tracker] (MQTT-415) Is there any order to Server References? |
4 |
Mar 2017 |
| 178 |
[OASIS Issue Tracker] (MQTT-419) Ambiguity over Session Expiry |
4 |
Mar 2017 |
| 179 |
[OASIS Issue Tracker] (MQTT-422) WD11 - Section 3.2.2.2 Session Present has to be reworked |
4 |
Mar 2017 |
| 180 |
MQTT 3.1.1 partial connect packets over TCP |
4 |
May 2017 |
| 181 |
[OASIS Issue Tracker] (MQTT-432) Consider adding return code of "Authentication failed" |
4 |
May 2017 |
| 182 |
[OASIS Issue Tracker] (MQTT-429) WD12 Review comments by David Horton |
4 |
May 2017 |
| 183 |
[OASIS Issue Tracker] (MQTT-469) Non-normative comment on optional CONNACK |
4 |
Jun 2017 |
| 184 |
[OASIS Issue Tracker] (MQTT-479) Subscription Identifier optional |
4 |
Jun 2017 |
| 185 |
[OASIS Issue Tracker] (MQTT-480) Subscription Options when Retain is optional |
4 |
Jun 2017 |
| 186 |
[OASIS Issue Tracker] (MQTT-491) Wording of 3.3.1.3 RETAIN |
4 |
Jul 2017 |
| 187 |
[OASIS Issue Tracker] (MQTT-501) Change type of Maximum Packet Size to Variable Byte Integer |
4 |
Aug 2017 |
| 188 |
[OASIS Issue Tracker] (MQTT-504) No way to tell when a retained message was set |
4 |
Sep 2017 |
| 189 |
[OASIS Issue Tracker] (MQTT-506) Session Expiry in CONNACK |
4 |
Sep 2017 |
| 190 |
[OASIS Issue Tracker] (MQTT-507) Allow Server-sent AUTH packets |
4 |
Sep 2017 |
| 191 |
[OASIS Issue Tracker] (MQTT-508) The default for session expiry should be 0, not never |
4 |
Sep 2017 |
| 192 |
[OASIS Issue Tracker] (MQTT-509) exercise reuse in Conformance Clauses |
4 |
Sep 2017 |
| 193 |
[OASIS Issue Tracker] (MQTT-510) Improper self reference from Conformance Clause section |
4 |
Sep 2017 |
| 194 |
[OASIS Issue Tracker] (MQTT-532) style: Section 5 heading differs from 3.1.1 |
4 |
Apr 2018 |
| 195 |
[OASIS Issue Tracker] (MQTT-552) Should a broker prohibit publish -1 messages from sleeping clients |
4 |
Apr 2020 |
| 196 |
[OASIS Issue Tracker] (MQTT-556) Clarification of broker behaviour when REGISTER issued on a 2 byte topic name |
4 |
Apr 2020 |
| 197 |
[OASIS Issue Tracker] (MQTT-560) Error codes need consideration, both quantity and location. |
4 |
Apr 2020 |
| 198 |
[OASIS Issue Tracker] (MQTT-561) Introduce a broker Timer to monitor sleeping ping flush |
4 |
Apr 2020 |
| 199 |
[OASIS Issue Tracker] (MQTT-569) Firmware updates |
4 |
Jun 2020 |
| 200 |
[OASIS Issue Tracker] (MQTT-566) Capabilities |
4 |
Oct 2020 |
