| [OASIS Issue Tracker] (MQTT-328) WD9: Inconsistencies/Overlaps in Return Codes |
1 |
2017-01-04 |
| =?UTF-8?B?R3JvdXBzIC0gbXF0dC12NS4wLXdkMTAu?= =?UTF-8?B?ZG9jeCB1cGxvYWRlZA==?= |
1 |
2017-01-05 |
| =?UTF-8?B?R3JvdXBzIC0gbXF0dC12NS4wLXdkMTAu?= =?UTF-8?B?cGRmIHVwbG9hZGVk?= |
1 |
2017-01-05 |
| [OASIS Issue Tracker] (MQTT-330) Bad bookmark: 'TLS [RFC5246]', line 1488 actually points to [RFC6455] |
2 |
2017-01-08 |
| =?UTF-8?B?R3JvdXBzIC0gTWludXRlcyBvZiBUQyBN?= =?UTF-8?B?ZWV0aW5nIDE1dGggRGVjZW1iZXIgMjAx?= =?UTF-8?B?NiBtb2RpZmllZA==?= |
1 |
2017-01-09 |
| =?UTF-8?B?R3JvdXBzIC0gTWludXRlcyBvZiBUQyBN?= =?UTF-8?B?ZWV0aW5nIDV0aCBKYW51YXJ5IDIwMTcg?= =?UTF-8?B?dXBsb2FkZWQ=?= |
1 |
2017-01-09 |
| [OASIS Issue Tracker] (MQTT-331) Clearing comments from the V5 specification. |
1 |
2017-01-09 |
| [OASIS Issue Tracker] (MQTT-332) Consistency: 8 bits or one byte? |
3 |
2017-01-10 |
| [OASIS Issue Tracker] (MQTT-333) Consistency: Zero, 0, and non-zero |
1 |
2017-01-10 |
| [OASIS Issue Tracker] (MQTT-334) refer section or refer to section |
1 |
2017-01-10 |
| [OASIS Issue Tracker] (MQTT-335) "using this version of MQTT" |
3 |
2017-01-10 |
| [OASIS Issue Tracker] (MQTT-336) Consistency: Retain As Published Subscription Option |
3 |
2017-01-10 |
| [OASIS Issue Tracker] (MQTT-337) UNSUBACK not UNSUBBACK |
2 |
2017-01-10 |
| [OASIS Issue Tracker] (MQTT-338) In [If] a non-zero Session Expiry is received by the Client |
2 |
2017-01-10 |
| [OASIS Issue Tracker] (MQTT-339) Unreasonable String |
3 |
2017-01-10 |
| [OASIS Issue Tracker] (MQTT-340) If this value is not 5 ... |
5 |
2017-01-10 |
| [OASIS Issue Tracker] (MQTT-341) Shared Subscription edits |
4 |
2017-01-10 |
| [OASIS Issue Tracker] (MQTT-342) value to be sent [set] to zero |
1 |
2017-01-10 |
| [OASIS Issue Tracker] (MQTT-343) Consistency: Topic Aliases and topic aliases |
3 |
2017-01-10 |
| [OASIS Issue Tracker] (MQTT-344) Wildcard subscriptions edits |
1 |
2017-01-10 |
| [OASIS Issue Tracker] (MQTT-345) re connection |
1 |
2017-01-10 |
| [OASIS Issue Tracker] (MQTT-346) Misplaced comma in Session Expiry Interval? |
2 |
2017-01-10 |
| [OASIS Issue Tracker] (MQTT-347) Comments and Questions about Will* |
3 |
2017-01-10 |
| [OASIS Issue Tracker] (MQTT-348) Consistency: Variations in Malformed Packet Return Code (with one error) |
1 |
2017-01-10 |
| [OASIS Issue Tracker] (MQTT-349) What is a "useful implementation"? |
1 |
2017-01-10 |
| [OASIS Issue Tracker] (MQTT-345) re connection and re transmission |
4 |
2017-01-10 |
| [OASIS Issue Tracker] (MQTT-350) UNSUBSCRIBE - Protocol Error or Protocol Violation? |
3 |
2017-01-10 |
| [OASIS Issue Tracker] (MQTT-351) "you" and your "loose" messages ... |
5 |
2017-01-11 |
| [OASIS Issue Tracker] (MQTT-352) Table 2.1 Control packet types - Description |
1 |
2017-01-11 |
| [OASIS Issue Tracker] (MQTT-353) Long discussion on Sessions in Session Expiry Interval |
1 |
2017-01-11 |
| [OASIS Issue Tracker] (MQTT-354) Special terms are not consistently capitalized |
1 |
2017-01-11 |
| [OASIS Issue Tracker] (MQTT-355) Receive Maximum - value less than 1 |
2 |
2017-01-11 |
| [OASIS Issue Tracker] (MQTT-356) Receive Maximum - PUBACK or PUBCOMP from the [Client]? |
2 |
2017-01-11 |
| [OASIS Issue Tracker] (MQTT-357) Receive Maximum - then the Client MUST NOT close the network connection |
3 |
2017-01-11 |
| [OASIS Issue Tracker] (MQTT-358) Receive Maximum - Not setting the Receive Maximum value |
5 |
2017-01-11 |
| [OASIS Issue Tracker] (MQTT-342) Maximum Packet Size - value to be sent [set] to zero and more |
9 |
2017-01-11 |
| [OASIS Issue Tracker] (MQTT-359) AuthMethod - enforcement |
1 |
2017-01-11 |
| [OASIS Issue Tracker] (MQTT-360) Figure 3.6 - Variable header non normative example - byte 8 |
1 |
2017-01-11 |
| [OASIS Issue Tracker] (MQTT-360) Figure 3.6 - Variable header non normative example - byte 8 and 12 |
3 |
2017-01-11 |
| [OASIS Issue Tracker] (MQTT-361) 3.1.3.1 Client Identifier (ClientID) comments |
2 |
2017-01-11 |
| [OASIS Issue Tracker] (MQTT-362) Consistency: "this" is the next field |
2 |
2017-01-11 |
| [OASIS Issue Tracker] (MQTT-363) byes of Binary Data |
1 |
2017-01-11 |
| [OASIS Issue Tracker] (MQTT-364) Repeating the Binary Data representation |
1 |
2017-01-11 |
| [OASIS Issue Tracker] (MQTT-365) Indentation issue on Line 1231 |
2 |
2017-01-11 |
| [OASIS Issue Tracker] (MQTT-366) Line 1243 : "the is new" and repeating the details of Will Message firing |
2 |
2017-01-11 |
| [OASIS Issue Tracker] (MQTT-367) The first packet sent from the Server to the Client ... it depends |
1 |
2017-01-11 |
| [OASIS Issue Tracker] (MQTT-368) Consistency: Session Expiry [Interval] |
3 |
2017-01-11 |
| [OASIS Issue Tracker] (MQTT-369) Will Topic *Is* Invalid |
2 |
2017-01-11 |
| [OASIS Issue Tracker] (MQTT-369) Table 3.1 - Connect Return Code values - comments |
3 |
2017-01-11 |
| =?UTF-8?B?TVFUVCBUQyBFZGl0b3IgUmV2aWV3?= |
2 |
2017-01-11 |
| [OASIS Issue Tracker] (MQTT-370) Consistency: Variable Byte integer |
1 |
2017-01-11 |
| =?UTF-8?B?Tm8gTVFUVCBUQyBjYWxsIHRvbW9ycm93?= |
1 |
2017-01-11 |
| [OASIS Issue Tracker] (MQTT-371) Missing QOS-NOT-SUPPORTED Return Code |
5 |
2017-01-11 |
| [OASIS Issue Tracker] (MQTT-372) 3.2.2.6 Maximum QoS - comments |
1 |
2017-01-11 |
| [OASIS Issue Tracker] (MQTT-373) 3.3.1.2 QoS - |
1 |
2017-01-11 |
| [OASIS Issue Tracker] (MQTT-373) 3.3.1.2 QoS - comments |
5 |
2017-01-11 |
| [OASIS Issue Tracker] (MQTT-374) 3.14.2.1 Disconnect Return Codes - question |
3 |
2017-01-11 |
| [OASIS Issue Tracker] (MQTT-375) Consistency: 4 Byte integer |
2 |
2017-01-11 |
| [OASIS Issue Tracker] (MQTT-376) Consistency: This is followed by ... |
2 |
2017-01-11 |
| [OASIS Issue Tracker] (MQTT-377) Consistency: Name or Name property? |
1 |
2017-01-11 |
| [OASIS Issue Tracker] (MQTT-378) Consistency: the send DISCONNECT and close variations |
1 |
2017-01-11 |
| [OASIS Issue Tracker] (MQTT-379) RETAIN-NOT-SUPPORTED is undefined |
2 |
2017-01-11 |
| [OASIS Issue Tracker] (MQTT-340) Continuing to process incorrect protocol names or protocol versions |
3 |
2017-01-12 |
| [OASIS Issue Tracker] (MQTT-380) Consistency: RETAIN flag - Retain Flag - Retain flag |
3 |
2017-01-12 |
| [OASIS Issue Tracker] (MQTT-381) 3.3.1.3 RETAIN - comments |
2 |
2017-01-12 |
| [OASIS Issue Tracker] (MQTT-382) Consistency: If QoS=0, QoS is 0, or QoS is set to 0 |
3 |
2017-01-12 |
| [OASIS Issue Tracker] (MQTT-383) Consistency: Payload Format - Payload Format Indicator |
3 |
2017-01-12 |
| [OASIS Issue Tracker] (MQTT-384) 3.3.2.4 Payload Format Indicator.- comments |
9 |
2017-01-12 |
| [OASIS Issue Tracker] (MQTT-385) Simple clients skipping properties |
8 |
2017-01-12 |
| [OASIS Issue Tracker] (MQTT-386) Question -Should Topic Alias be included in Terminology? |
5 |
2017-01-12 |
| [OASIS Issue Tracker] (MQTT-387) 3.3.2.6 Topic Alias. - comments |
5 |
2017-01-12 |
| [OASIS Issue Tracker] (MQTT-388) 3.3.2.7 Reply Topic - comments |
1 |
2017-01-12 |
| [OASIS Issue Tracker] (MQTT-389) 4.10 Request / Response - comments |
2 |
2017-01-12 |
| [OASIS Issue Tracker] (MQTT-390) 3.3.2.8 Correlation Data - comments |
2 |
2017-01-12 |
| [OASIS Issue Tracker] (MQTT-391) 3.3.2.11 Content Type - comments |
2 |
2017-01-12 |
| [OASIS Issue Tracker] (MQTT-392) 3.3.5 Actions - comments |
4 |
2017-01-12 |
| =?UTF-8?B?RWRpdG9yIHJldmlldyBjYWxsIHRoaXMg?= =?UTF-8?B?d2Vlaw==?= |
1 |
2017-01-18 |
| [OASIS Issue Tracker] (MQTT-393) Incorrect UNSUBACK Variable Length Header |
1 |
2017-01-18 |
| =?UTF-8?Q?[OASIS_Issue_Tracker]_(MQTT-394)_3.4_PUB?= =?UTF-8?Q?ACK_=E2=80=93_Publish_acknowledgement__-_comments?= |
6 |
2017-01-19 |
| [OASIS Issue Tracker] (MQTT-395) Consistency: Following fields ... |
1 |
2017-01-19 |
| [OASIS Issue Tracker] (MQTT-396) Consistency: Topic Name invalid or not valid |
1 |
2017-01-19 |
| [OASIS Issue Tracker] (MQTT-397) Return Code v |
4 |
2017-01-19 |
| [OASIS Issue Tracker] (MQTT-398) Consistency: Byte 3 in ... |
1 |
2017-01-19 |
| =?UTF-8?Q?[OASIS_Issue_Tracker]_(MQTT-399)_3.5?= =?UTF-8?Q?_PUBREC_=E2=80=93_Publish_received_-_comments?= |
4 |
2017-01-19 |
| [OASIS Issue Tracker] (MQTT-400) Consistency: Remaining Length field |
5 |
2017-01-19 |
| [OASIS Issue Tracker] (MQTT-401) Consistency: Property Length |
1 |
2017-01-19 |
| =?UTF-8?Q?[OASIS_Issue_Tracker]_(MQTT-402)_3.5?= =?UTF-8?Q?_PUBREC_=E2=80=93_Publish_received_-_comments?= |
3 |
2017-01-19 |
| [OASIS Issue Tracker] (MQTT-403) Change AUTH Flag Bit 0 to value 0 for consistency |
1 |
2017-01-19 |
| [OASIS Issue Tracker] (MQTT-404) Question - Reason String - representing the reason for the *connection* failure |
3 |
2017-01-19 |
| [OASIS Issue Tracker] (MQTT-405) an optional Return Code - but MUST use ... |
1 |
2017-01-20 |
| [OASIS Issue Tracker] (MQTT-406) 3.8 SUBSCRIBE |
2 |
2017-01-20 |
| =?UTF-8?Q?[OASIS_Issue_Tracker]_(MQTT-407)_WD11:_T?= =?UTF-8?Q?able_3.13_=E2=80=93_Disconnect_Return_Code_values?= |
2 |
2017-01-20 |
| =?UTF-8?B?TVFUVCBUQyBNZWV0aW5n?= |
2 |
2017-01-20 |
| [OASIS Issue Tracker] (MQTT-297) Packet Indentifier Leak on lost Subscription commands |
3 |
2017-01-21 |
| [OASIS Issue Tracker] (MQTT-408) Statement about packets with multiple errors |
2 |
2017-01-22 |
| [OASIS Issue Tracker] (MQTT-409) Publications which are undeliverable because the packet is too large. |
1 |
2017-01-23 |
| Call for agenda items: January 26 Thursday TC call |
1 |
2017-01-23 |
| [OASIS Issue Tracker] (MQTT-410) Payload Format Indicator text concerning V3.1.1 |
2 |
2017-01-24 |
| [OASIS Issue Tracker] (MQTT-411) Return code for Payload does not match Payload Format |
3 |
2017-01-24 |
| [OASIS Issue Tracker] (MQTT-412) Consolidated error handling. |
2 |
2017-01-25 |
| =?UTF-8?B?R3JvdXBzIC0gTWludXRlcyBvZiBUQyBN?= =?UTF-8?B?ZWV0aW5nIDV0aCBKYW51YXJ5IDIwMTcg?= =?UTF-8?B?bW9kaWZpZWQ=?= |
1 |
2017-01-31 |
| =?UTF-8?B?R3JvdXBzIC0gTWludXRlcyBvZiBUQyBN?= =?UTF-8?B?ZWV0aW5nIDI2dGggSmFudWFyeSAyMDE3?= =?UTF-8?B?IHVwbG9hZGVk?= |
1 |
2017-01-31 |
| Call for agenda items: Feb 2 Thursday TC call |
1 |
2017-01-31 |
