mqtt message

Subject: [OASIS Issue Tracker] Created: (MQTT-41) Inconsistency in the definition of the Remaining Length field for the different control packets

From: OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>
To: mqtt@lists.oasis-open.org
Date: Tue, 25 Jun 2013 04:09:43 -0400 (EDT)

Inconsistency in the definition of the Remaining Length field for the different control packets
-----------------------------------------------------------------------------------------------

                 Key: MQTT-41
                 URL: http://tools.oasis-open.org/issues/browse/MQTT-41
             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
          Issue Type: Improvement
          Components: edits
            Reporter: Julien Niset
            Priority: Minor


The Remaining Length field is sometimes defined as a "IS a multibyte field" (see e.g. CONNECT packet line 623 or PUBLISH packet line 988) and sometimes as a "CAN BE a multibyte field (see e.g. PUBACK packet line 1171 or SUBSCRIBE packet line 1381). 

I believe the wording should be more consistent and always define this field as a "Is a multibyte field".

I also noted that the Remaining Length field is not defined for the CONNACK packet, and incorrectly defined for the SUBSCRIBE packet (it should be "The length of the payload and the variable header.").

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