[OASIS Issue Tracker] (MQTT-357) Receive Maximum - then the Client MUST NOT close the network connection

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

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

Ken Borgendale commented on MQTT-357:
-------------------------------------

This imperative is unenforceable.  Either the client or server (or indeed the network between them) may close the connection at any time.  Thus to say that it MUST NOT close the connection for this reason means that it only need to do it for any other reason, or indeed for no reason at all.

Perhaps it would be best to just say the default value of Receive Maximum is 65535 (in both CONNECT and CONNACK).

> Receive Maximum - then the Client MUST NOT close the network connection
> -----------------------------------------------------------------------
>
>                 Key: MQTT-357
>                 URL: https://issues.oasis-open.org/browse/MQTT-357
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: Bug
>          Components: edits
>    Affects Versions: 5, wd10
>            Reporter: Brian Raymor
>            Assignee: Rahul Gupta
>            Priority: Minor
>             Fix For: 5, wd10
>
>
> What is the value of this requirement? Can it be deleted?
> 1072 If the Receive Maximum value is absent, then the Client MUST NOT close the network connection
> 1073 because it has received too many unacknowledged PUBLISH packets.
> It could be a recommendation (SHOULD NOT) - but how would an implementation know that the client was closing the connection for this reason? 



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