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

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

     [ https://issues.oasis-open.org/browse/MQTT-572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Simon Johnson updated MQTT-572:
-------------------------------
    Proposal: 
Section should read;

6.6 Clientâs Publish Procedure
After having registered successfully a topic name with the gateway, the client can start publishing data relating to the registered topic name by sending PUBLISH messages to the gateway. The PUBLISH messages contain the assigned topic id.

All three QoS levels and their corresponding message flows are supported as defined in MQTT. The only difference is the use of topic ids instead of topic names in the PUBLISH messages.
Regardless of the requested QoS level the client may receive in response to its PUBLISH a PUBACK message which contains either;

â the ReturnCode= âRejection: invalid topic Idâ: in this case the client needs to register the topic name again before it can publish data related to that topic name; or
â the ReturnCode= âRejection: congestionâ: in this the client shall stop publishing toward the gateway for at least the time TW AIT .

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




  was:
Section should read;

6.6 Clientâs Publish Procedure
After having registered successfully a topic name with the gateway, the client can start publishing data relating to the registered topic name by sending PUBLISH messages to the gateway. The PUBLISH messages contain the assigned topic id.

All three QoS levels and their corresponding message flows are supported as defined in MQTT. The only difference is the use of topic ids instead of topic names in the PUBLISH messages.
Regardless of the requested QoS level the client may receive in response to its PUBLISH a PUBACK message which contains either;
â the ReturnCode= âRejection: invalid topic Idâ: in this case the client needs to register the topic name again before it can publish data related to that topic name; or
â the ReturnCode= âRejection: congestionâ: in this the client shall stop publishing toward the gateway for at least the time TW AIT .
_At any point in time a client may have only one QoS level 1 or 2 PUBLISH message outstanding in each direction, i.e. it has to wait for the termination of each PUBLISH message exchange before it could start a new level 1 or 2 transaction._





> 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
>            Assignee: Simon Johnson
>            Priority: Major
>
> 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. 



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