[OASIS Issue Tracker] (MQTT-596) CONNECT keep alive max is 18h 12m and 15s!

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

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

Simon Johnson commented on MQTT-596:
------------------------------------

Hi Davide,Â

Â

During the ASLEEPing state the GW will be using the session expiry interval sent during the DISCONNECT message as the monitor of the SLEEP. At this point the keep alive becomes obsolete until the device issues a new CONNECT. I believe therefore, this would not be an issue, since 4 bytes allows about 136 years of sleep time before the DW will consider the device lost.

Best,

Si

> CONNECT keep alive max is 18h 12m and 15s!
> ------------------------------------------
>
>                 Key: MQTT-596
>                 URL: https://issues.oasis-open.org/browse/MQTT-596
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: Improvement
>          Components: MQTT-SN
>            Reporter: Davide Lenzarini
>            Priority: Major
>
> Having a keep alive max of only 18h 12m and 15s can be a real limit for constrained IoT device that for instance needs to send a single message per day. A possible solution is to create a new CONNECT flags byte (anyway required to support security). So the current flag on bit 7 instead of reserved should be:
>  * 0=no additional flags
>  * 1= another byte of flags with the following structure
>  ** Reserved (7)
>  ** Reserved (6)
>  ** Reserved (5)
>  ** Reserved (4)
>  ** Reserved (3)
>  ** Reserved (2)
>  ** Reserved (1)
>  ** KeepAliveUOM
>  *** 0 = seconds
>  *** 1 = minutes



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