[OASIS Issue Tracker] Updated: (MQTT-54) How long should a client or server wait for, or expect to wait for, a response

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

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

Richard Coppen updated MQTT-54:
-------------------------------

    Proposal: 
The client and server should respond 'as soon as is practical' to drive the protocol for the reliable delivery of messages. They should not 'misuse' the protocol ACK flow by delaying an ACK for other reasons, such as attempts to pace traffic.

However, CONNACK is a special case. The Server MAY delay a non-zero CONNACK to defend DoS attacks.

Add draft proposal to promote discussion 

> How long should a client or server wait for, or expect to wait for, a response
> ------------------------------------------------------------------------------
>
>                 Key: MQTT-54
>                 URL: http://tools.oasis-open.org/issues/browse/MQTT-54
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: Improvement
>          Components: core
>    Affects Versions: 3.1.1
>            Reporter: Richard Coppen
>             Fix For: 3.1.1
>
>
> How long should a client or server wait for, or expect to wait for, an ACKNOWLEDGEMENT
> If the server is allowed to wait for a long time before sending an ACK, then the client must be able to handle this.
> PINGRESP is a special case, should the server be expected to respond as promptly as it can?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira