[OASIS Issue Tracker] (MQTT-546) Improve description of sleeping clients message flows

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

    [ https://issues.oasis-open.org/browse/MQTT-546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=77328#comment-77328 ] 

Simon Johnson commented on MQTT-546:
------------------------------------

The sentence in the implementation notes should be updated;

The identified client is then in the awake state. If the server/gateway has buffered messages for the client, it will sends these messages to the client. *For each message the gateway sends to the client, the messages' quality of service shall be honoured and a full message interaction shall take place, including any associated retransmission logic.*

> Improve description of sleeping clients message flows
> -----------------------------------------------------
>
>                 Key: MQTT-546
>                 URL: https://issues.oasis-open.org/browse/MQTT-546
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: Improvement
>          Components: MQTT-SN
>    Affects Versions: MQTT-SN-1.2
>            Reporter: Ian Craggs
>            Assignee: Simon Johnson
>            Priority: Minor
>         Attachments: Sleeping Client Sequence Diagram-2.png
>
>
> From an old set of comments about possible improvements for version '1.3'.
> When a client awakens by sending a PINGREQ, the server responds by sending queued up messages before sending the PINGRESP. If queued-up messages are of QoS 1 or 2, the PINGRESP is sent after the entire message exchanges are completed, that is, on receipt of all PUBACKs or PUBCOMPs.



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