OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

mqtt message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [OASIS Issue Tracker] (MQTT-600) A Gateway should buffer Q0S 0 messages for ASLEEP clients


Davide Lenzarini created MQTT-600:
-------------------------------------

             Summary: A Gateway should buffer Q0S 0 messages for ASLEEP clients
                 Key: MQTT-600
                 URL: https://issues.oasis-open.org/browse/MQTT-600
             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
          Issue Type: Improvement
            Reporter: Davide Lenzarini


Chapter 3.19 (Sleeping clients) of WD24

_During the asleep state, packets that need to be sent to the client are buffered at the server/gateway. The gateway MUST buffer application messages of quality-of-service 1 & 2._

_Non-normative comment_
_The gateway may choose to buffer messages of all quality-of-service 0, whilst the client is sleeping and is within it's session expiry interval._

Â

I propose to modify the above in

_During the asleep state, packets that need to be sent to the client are buffered at the server/gateway. The gateway MUST buffer application messages of quality-of-service 1 & 2 *{color:#FF0000}& 0{color}*._

-_Non-normative comment_-
-_The gateway may choose to buffer messages of all quality-of-service 0, whilst the client is sleeping and is within it's session expiry interval._-

Â

With this modification the following scenario is possible:ÂÂ
 # A client CONNECT to a gateway (client enrollment) with a very long session expiry interval
 # The client subscribe to a certain topic to receive pending messages as soon as it sends a publish-1 message to a certain (also different) topic
 # The client DISCONNECTÂwith a very long session expiry interval
 # After some time the client send a PUBLISH-1 message and would like to receive (like with the PINGREQ when in ASLEEP state) all pending messages on the topic it has subscribed to, also with QoS 0 (the most efficient as they don't require any acknowledge)



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


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]