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

From
OASIS Issues Tracker <>
Date
2017-01-11T14:39:11+00:00
ID
Thread
[OASIS Issue Tracker] (MQTT-357) Receive Maximum - then the Client MUST NOT close the network connection
[ https://issues.oasis-open.org/browse/MQTT-357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=64790#comment-64790 ] 

Ed Briggs commented on MQTT-357:
--------------------------------

FYI, there is a similar recommendation later with the endpoints swapped ( Server MUST NOT close the network connection...)



> 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)