[OASIS Issue Tracker] (MQTT-594) Keep Alive and Session Expiry Interval controls - (session leak)

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

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

Simon Johnson commented on MQTT-594:
------------------------------------

It was agreed on the committee call that Keep Alive 0 was dangerous and could in affect lead to devices that would be in an ACTIVE state forever using gateway resources. Therefore Keep Alive 0 should be removed.

Â

Session Expiry Interval can be set and overridden by there gateway and as such this is safe to leave as is.

> Keep Alive and Session Expiry Interval controls - (session leak)
> ----------------------------------------------------------------
>
>                 Key: MQTT-594
>                 URL: https://issues.oasis-open.org/browse/MQTT-594
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: Improvement
>          Components: MQTT-SN
>            Reporter: Simon Johnson [X]
>            Assignee: Simon Johnson [X]
>            Priority: Major
>
> The "Keep Alive" and "Session Expiry Interval" behaviour defined in MQTT 5 applied "as-is" in MQTT-SN would be dangerous. Since the "Network Connection" cannot be used as a control vector to start session expiry clocks, this is a session memory leak.



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