[OASIS Issue Tracker] (MQTT-400) Consistency: Remaining Length field

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

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

Ed Briggs commented on MQTT-400:
--------------------------------

I think these are incorrect, not just inconsistent.  The return code must be present in MQTT 5.0, PUBREC remaining length can't be two, same with PUBREL.  And since properties may extend the packet further, the remaining length can be other values as well.  

I spotted/corrected this in SUBACK last night (in WD11).  I think we need to visit all cases in which the return code length is 'hardwired' to a value in the specification.

> Consistency: Remaining Length field
> -----------------------------------
>
>                 Key: MQTT-400
>                 URL: https://issues.oasis-open.org/browse/MQTT-400
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: Bug
>          Components: edits
>    Affects Versions: 5, wd10
>            Reporter: Brian Raymor
>            Priority: Minor
>             Fix For: 5, wd11
>
>
> Three variations.
> 1. Specified - not specified
> 1938 ... For the PUBACK Packet this has the value 3 if a Return
> 1939 Code is specified and 2 if it a Return Code is not specified.
> 2. Not specified - specified
> 1987 ... For the PUBREC Packet this has the value 2
> 1988 if no Return Code is specified, and 3 if it a Return Code is specified.
> 3. Specified - otherwise
> 2045 ... For the PUBREL Packet this has the value 3 if the variable
> 2046 header contains a PUBREL Return Code, and 2 otherwise.



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