40 messages

org.oasis-open.lists.mqtt [All Lists]

2023 January [All Months]

Page 2 (Messages 26 to 40): 1 2

[mqtt] [OASIS Issue Tracker] (MQTT-597) The Gateway may need a way to identify the sender - OASIS Issues Tracker
[mqtt] [OASIS Issue Tracker] (MQTT-598) The SUBSCRIBE flag QoS should allow the QoS-1 value - OASIS Issues Tracker
[mqtt] [OASIS Issue Tracker] (MQTT-599) In ASLEEP state also a PUBLISH-1 should trigger the sending of the pending messages on the subscribed topics - OASIS Issues Tracker
[mqtt] [OASIS Issue Tracker] (MQTT-598) The SUBSCRIBE flag QoS should allow the QoS-1 value - OASIS Issues Tracker
[mqtt] [OASIS Issue Tracker] (MQTT-598) The SUBSCRIBE flag QoS should allow the QoS-1 value - OASIS Issues Tracker
[mqtt] [OASIS Issue Tracker] (MQTT-596) CONNECT keep alive max is 18h 12m and 15s! - OASIS Issues Tracker
[mqtt] [OASIS Issue Tracker] (MQTT-597) The Gateway may need a way to identify the sender - OASIS Issues Tracker
[mqtt] [OASIS Issue Tracker] (MQTT-596) CONNECT keep alive max is 18h 12m and 15s! - OASIS Issues Tracker
[mqtt] [OASIS Issue Tracker] (MQTT-600) A Gateway should buffer Q0S 0 messages for ASLEEP clients - OASIS Issues Tracker
[mqtt] [OASIS Issue Tracker] (MQTT-599) In ASLEEP state also a PUBLISH-1 should trigger the sending of the pending messages on the subscribed topics - OASIS Issues Tracker
[mqtt] [OASIS Issue Tracker] (MQTT-596) CONNECT keep alive max is 18h 12m and 15s! - OASIS Issues Tracker
[mqtt] [OASIS Issue Tracker] (MQTT-601) Transition from AWAKE to LOST status unclear - OASIS Issues Tracker
[mqtt] [OASIS Issue Tracker] (MQTT-595) Publish QoS -1 has no protocol version indication - OASIS Issues Tracker
[mqtt] [OASIS Issue Tracker] (MQTT-595) Publish QoS -1 has no protocol version indication - OASIS Issues Tracker
[mqtt] [OASIS Issue Tracker] (MQTT-599) In ASLEEP state also a PUBLISH-1 should trigger the sending of the pending messages on the subscribed topics - OASIS Issues Tracker

Page 2 (Messages 26 to 40): 1 2