[OASIS Issue Tracker] (MQTT-249) Add expiry capabilities to MQTT.

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

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

Brian Raymor commented on MQTT-249:
-----------------------------------

Since MQTT-249 has not been closed, I'm adding feedback related to WD4 here.

The CONNECT example at line 976 references "Session State Expiry interval" but Section 3.1.2.12 at line 851 references "Session Expiry interval". In addition, the example shows byte 12 is repeated and the value as "10" but the bits as "0"?

Byte 12 Session State Expiry Identifier (17) 0 0 0 1 0 0 0 1
byte 12 Session State Expiry (10) 0 0 0 0 0 0 0 0

In the DISCONNECT related text, there are references to both "Session Expiry interval" and "Session State Expiry interval" in Section 3.14.2.2 starting at line 1827. 

> Add expiry capabilities to MQTT.
> --------------------------------
>
>                 Key: MQTT-249
>                 URL: https://issues.oasis-open.org/browse/MQTT-249
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: Improvement
>          Components: futures
>    Affects Versions: 5
>            Reporter: Andrew Banks
>            Assignee: Andrew Banks
>             Fix For: 5
>
>
> MQTT has the ability to purge all of the session state on demand by using the clean session flag. This proposal is for a time based and more granular capability to clear up state.  
> Add capabilities to MQTT to allow for expiry of.
> 1) Messages.
> 2) Subscriptions.
> 3) All session state, for example if the client is disconnected for a time period then treat it as if it had connected with clean session true.  This is sometimes referred to as offline keep alive.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)