[OASIS Issue Tracker] (MQTT-572) Clarification of text advising number of inflight messages

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

Simon Johnson created MQTT-572:
----------------------------------

             Summary: Clarification of text advising number of inflight messages
                 Key: MQTT-572
                 URL: https://issues.oasis-open.org/browse/MQTT-572
             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
          Issue Type: Task
          Components: MQTT-SN
            Reporter: Simon Johnson


Presently, the specification section *6.6 Client Publish* reads;

_At any point in time a client may have only one QoS level 1 or 2 PUBLISH message outstanding, i.e. it has to wait for the termination of this PUBLISH message exchange before it could start a new level 1 or 2 transaction._

This is ambiguous and needs to state that the number of message inflight (and indeed message Ids) are PER NETWORK DIRECTION. For example, it is perfectly fine for a device to be sending a message whilst also receiving a message. QUESTION.. given that that message Ids are also per direction, this means that inflight message storage for acknowledgement cannot be shared between inbound and outbound messages, as a gateway could publish with ID 3 at the same time as the device PUBLISHs at ID 3. How is it suggested this is handled?



--
This message was sent by Atlassian Jira
(v8.3.3#803004)