[OASIS Issue Tracker] (MQTT-270) SN Feature: server initiated disconnects

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

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

Ken Borgendale updated MQTT-270:
--------------------------------

    Proposal:   (was: 
2.Request that the Server responds to confirm that it is alive.
3.Exercise the network to indicate that the Network Connection is active.
 section 3.12 (PING request)
4. Request that the Client responds to confirm that it is alive

In Section 3.13 (PING response)
A PINGRESP Packet is sent by the Server to the Client or by the Client to the Server in response to a PINGREQ Packet. It indicates that the sender is alive.

If a PINGREQ is received without having sent a PINGREQ, not action should be taken.)

> SN Feature: server initiated disconnects
> ----------------------------------------
>
>                 Key: MQTT-270
>                 URL: https://issues.oasis-open.org/browse/MQTT-270
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: Improvement
>          Components: futures
>    Affects Versions: 3.1.1
>            Reporter: Ian Craggs
>
> MQTT-SN allows the server to send a disconnect packet to a client. This is much nicer behaviour, for example in the case that a server is shutting down. A reason could also be transmitted with the disconnect packet, so that the client had some idea of when to attempt to reconnect. 



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