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-596) CONNECT keep alive max is 18h 12m and 15s!


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

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

Hi Davide,

Â

We discussed the situation of 18hr 12m and 15s for sleep being too restrictive and increased this to 4 bytes per session expiry interval. It was a felt during this discussions that in the case of keep alive - using seconds was adequate since the device should be pinging to keep the session alive and informing the GW that it is there and able to receive messages (or implied that it is healthy on the network); if in fact they are not alive (and thus not able to receive messages) they should be utilising the asleep state. Devices that simply want to publish daily could just CONNECT clean false, PUBLISH, DISCONNECT. I feel moving the ACTIVE presence to weeks and months is a contradiction in terms?Â

Â

Thoughts?

Â

Â

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


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