[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=82430#comment-82430 ] 

Davide Lenzarini commented on MQTT-596:
---------------------------------------

Thanks Simon!

This was not clear to me from the WD24.Â

I would suggest to add to chapter 2.1.25.4 the following sentence.

"At this point the keep alive becomes obsolete until the device issues a new CONNECT."Â

Does it make sense to you?

Davide

> 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)