[OASIS Issue Tracker] (MQTT-358) Receive Maximum - Not setting the Receive Maximum value

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

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

Brian Raymor commented on MQTT-358:
-----------------------------------

Also this could be compressed to:

It is a Protocol Error to include the Receive Maximum value more than once or to have the value 0.

1347 Receive Maximum value. It is a Protocol Error to include the Receive Maximum value more than once. It
1348 is a Protocol Error for the Receive Maximum to have the value 0.

> Receive Maximum - Not setting the Receive Maximum value 
> --------------------------------------------------------
>
>                 Key: MQTT-358
>                 URL: https://issues.oasis-open.org/browse/MQTT-358
>             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
>
>
> I'm not sure why this text below is separated out in a comment. It seems important to document the "default" value of Receive Maximum.
> 1083 Non normative comment
> 1084 Not setting the Receive Maximum value has the same effect as setting it to 65535.
> It's also awkwardly phrased. Why not include a reference in the main text:
> If Receive Maximum is absent, then its value defaults to 65535.



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