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-278) Server keepalive


     [ https://issues.oasis-open.org/browse/MQTT-278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ken Borgendale updated MQTT-278:
--------------------------------

    Proposal: 
Add a CONNACK Optional value for "Server Keepalive" of type Int2.

If the server sets the optional value Server Keepalive in the CONNACK packet, the Client SHOULD use this value instead of the Keepalive value it set on the CONNECT.  In the absence of this optional value, the server agrees to the Keepalive value set by the client.  

Non normative:
The primary use of this is for the server to inform the client that the server will disconnect the client for inactivity sooner than the keepalive specified by the client.

If the client requests a zero keepalive and the server returns a non-zero keepalive, then the client must either send a packet within the keepalive time indicated by the server, or be prepared for the session to be disconnected.

  was:
CONNACK flows max keep alive value
If the client requests 0 then the server says anything else then the server wins.
add non-normative comment to explain how to handle this


> Server keepalive
> ----------------
>
>                 Key: MQTT-278
>                 URL: https://issues.oasis-open.org/browse/MQTT-278
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: Improvement
>          Components: futures
>            Reporter: Ken Borgendale
>
> While we are at this, we should clarify the expected behavior of either side if they receive a PINGRESP without having send a PINGREQ. My suggestion is that it should be ignored but there is currently no text (normative or not) to indicate what should be done 



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


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