[OASIS Issue Tracker] (MQTT-278) Server initiated ping

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

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

Richard Coppen commented on MQTT-278:
-------------------------------------

Discussion notes from April face-to-face:

Is it possible to solve this, at least in part, by flowing a min keep alive on the CONNACK.
If it's not bound to keepalive then we need to be able to articulate when and why the server should flow this. It doesn't seem to be a 'routine' operation.
Radical thoughts - can the server just disconnect e.g., server initiated disconnect or a authentication challenge.

Can it be a non-normative comment e.g., under these circumstances disconnect or send a challenge ?

> Server initiated ping
> ---------------------
>
>                 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
>
> The MQTT 3.1.1 spec allows the client to send a PINGREQ to the server which has the dual affect of telling the server that the client is still up, and telling the client that the server is still up. 
> Change to also allow the server to also send a PINGREQ to the client. 
> While a server is often informed when a client connection is terminated, it has no method to check this if it is not informed. 
> Also change PINGRESP to be allowed from client to server. 
> 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)