[OASIS Issue Tracker] Created: (MQTT-23) Should Message Identifier be called as Packet Identifier

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

Should Message Identifier be called as Packet Identifier
--------------------------------------------------------

                 Key: MQTT-23
                 URL: http://tools.oasis-open.org/issues/browse/MQTT-23
             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
          Issue Type: Improvement
          Components: core
            Reporter: Rahul Gupta


As Part of issue MQTT-21, it was proposed and agreed to use term "MQTT Control Packet" consistently and not "MQTT Command Message" in the specification. 

However this change causes a problem in understanding of another term "message Identifier". Comments and discussion may be needed on the use of word Message Identifier and if it should be called as Packet Identifier.  I am opening this JIRA issue for further discussion in TC calls.

example - from WD-04, line 383 - 385

"A non zero  message identifier (MessageId) MUST be present in the variable header of the following MQTT command messages: PUBLISH(where Qos!=0), PUBACK, PUBREC, PUBREL, PUBCOMP, SUBSCRIBE, SUBACK, UNSUBSCRIBE, UNSUBACK "

In WD-05

"A non zero  message identifier (MessageId) MUST be present in the variable header of the following MQTT Control Packets: PUBLISH(where Qos!=0), PUBACK, PUBREC, PUBREL, PUBCOMP, SUBSCRIBE, SUBACK, UNSUBSCRIBE, UNSUBACK "

Should message Identifier be called as Packet Identifier ?


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