[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:
--------------------------------

        Summary: SN Feature: server initiated disconnects  (was: Server initiated PING)
       Reporter: Ian Craggs  (was: Ken Borgendale)
    Description: 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.   (was: 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 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 havnig 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.)
       Proposal: 

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.

  was:
InThe PINGREQ Packet is sent from a Client to the Server or from the Client to the Sever. It can be used to: 
1.Indicate to the Server that the Client is alive in the absence of any other Control Packets being sent from the Client to the Server.
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)