Hello
Nobody
Logout
Sign In
or
Sign Up
(
Why?
)
Home
39 messages
org.oasis-open.lists.mqtt [
All Lists
]
2020 April [
All Months
]
Page 1 (Messages 1 to 25):
1
2
[mqtt] [OASIS Issue Tracker] (MQTT-539) TopicId in PUBACK is superfluous
-
OASIS Issues Tracker
[mqtt] [OASIS Issue Tracker] (MQTT-539) TopicId in PUBACK is superfluous
-
OASIS Issues Tracker
[mqtt] [OASIS Issue Tracker] (MQTT-540) Messages shorter than 256 octets may use the 1-octet format
-
OASIS Issues Tracker
[mqtt] [OASIS Issue Tracker] (MQTT-540) Messages shorter than 256 octets may use the 1-octet format
-
OASIS Issues Tracker
[mqtt] [OASIS Issue Tracker] (MQTT-544) Add return code to UNSUBACK
-
OASIS Issues Tracker
[mqtt] [OASIS Issue Tracker] (MQTT-548) Clarify when sessions are cleaned up for sleeping clients
-
OASIS Issues Tracker
[mqtt] [OASIS Issue Tracker] (MQTT-549) Remove the discovery procedure
-
OASIS Issues Tracker
[mqtt] [OASIS Issue Tracker] (MQTT-549) Remove the discovery procedure
-
OASIS Issues Tracker
[mqtt] [OASIS Issue Tracker] (MQTT-546) Improve description of sleeping clients message flows
-
OASIS Issues Tracker
[mqtt] [OASIS Issue Tracker] (MQTT-546) Improve description of sleeping clients message flows
-
OASIS Issues Tracker
[mqtt] [OASIS Issue Tracker] (MQTT-550) Mandate the use of separate id spaces for device normal topic alias's
-
OASIS Issues Tracker
[mqtt] [OASIS Issue Tracker] (MQTT-550) Mandate the use of separate id spaces for device normal topic alias's
-
OASIS Issues Tracker
[mqtt] [OASIS Issue Tracker] (MQTT-550) Mandate the use of separate id spaces for device normal topic alias's
-
OASIS Issues Tracker
[mqtt] [OASIS Issue Tracker] (MQTT-551) Discussion about predefined topicId values being allowed to match normal topicId values
-
OASIS Issues Tracker
[mqtt] [OASIS Issue Tracker] (MQTT-550) Mandate the use of separate id spaces for device normal topic alias's
-
OASIS Issues Tracker
[mqtt] [OASIS Issue Tracker] (MQTT-556) Clarification of broker behaviour when REGISTER issued on a 2 byte topic name
-
OASIS Issues Tracker
[mqtt] [OASIS Issue Tracker] (MQTT-556) Clarification of broker behaviour when REGISTER issued on a 2 byte topic name
-
OASIS Issues Tracker
[mqtt] [OASIS Issue Tracker] (MQTT-557) Should REGACK be expanded to support multiple topicIdTypes
-
OASIS Issues Tracker
[mqtt] [OASIS Issue Tracker] (MQTT-558) Short topic names allowed formats
-
OASIS Issues Tracker
[mqtt] [OASIS Issue Tracker] (MQTT-560) Error codes need consideration, both quantity and location.
-
OASIS Issues Tracker
[mqtt] [OASIS Issue Tracker] (MQTT-561) Introduce a broker Timer to monitor sleeping ping flush
-
OASIS Issues Tracker
[mqtt] [OASIS Issue Tracker] (MQTT-540) Messages shorter than 256 octets may use the 1-octet format
-
OASIS Issues Tracker
[mqtt] [OASIS Issue Tracker] (MQTT-541) Cleansession should act like MQTT 5.0 not 3.1.1
-
OASIS Issues Tracker
[mqtt] [OASIS Issue Tracker] (MQTT-543) Allow long topic names for publish of all QoS
-
OASIS Issues Tracker
[mqtt] [OASIS Issue Tracker] (MQTT-544) Add return code to UNSUBACK
-
OASIS Issues Tracker
Page 1 (Messages 1 to 25):
1
2