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 initiated ping

Ken Borgendale created MQTT-278:

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

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