[OASIS Issue Tracker] Commented: (MQTT-25) Placement of sentences on MSB/LSB byte order

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

    [ http://tools.oasis-open.org/issues/browse/MQTT-25?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=34150#action_34150 ] 

Rahul Gupta commented on MQTT-25:
---------------------------------

Section 1 of WD-08
------------------

Bits in a byte are labeled 7 through 0. Bit number 7 is the most significant bit, the least significant bit is assigned bit number 0.

All 16-bit word presented in this specification is in big-endian order: higher order bytes precede lower order bytes over the wire. A 16-bit word is presented on the wire as Most Significant Byte (MSB), followed by Least Significant Byte (LSB). This is based on IETF RFC 1700.

Normative Reference

[RFC 1700]
Joyce K. Reynolds, Internet standard STD 2, IETF RFC 1700, October 1994
http://tools.ietf.org/html/rfc1700



Section 2.1(fixed header)

----------

Removed reference of Big endian from fixed header section as 16-bit word is not used here



Section 2.2.1(Packet identifier)
----------

Removed   ---- "The ordering of the two bytes of the Packet Identifier is MSB, then LSB (big-endian)."

fixed     ----  "SUBSCRIBE, UNSUBSCRIBE, and PUBLISH (in cases where QoS > 0) MUST contain a non-zero 16-bit word PacketId."



Section 3.1.2.4(KeepAlive Interval)
---------

Removed  -----  "The ordering of the 2 bytes of the Keep Alive Timer is MSB, then LSB (big-endian)."

fixed    -----  "The Keep Alive interval field is a 16-bit word, measured in seconds; It is the maximum time interval that is permitted to elapse between messages sent by a client. "

fixed    -----   The Keep Alive timer is a 16-bit word that represents the number of seconds for the time period. The actual value is application-specific, but a typical value is a few minutes. 




> Placement of sentences on MSB/LSB byte order
> --------------------------------------------
>
>                 Key: MQTT-25
>                 URL: http://tools.oasis-open.org/issues/browse/MQTT-25
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: Improvement
>          Components: edits
>            Reporter: Peter Niblett
>            Assignee: Rahul Gupta
>
> WD04 lines 259-261 describe the way that 16-bit data values are presented. The text is correct, however  it appears in section 2.1 which is about the Fixed Header, and that header does not contain any 16-bit words. Also I think I am right in saying that each place in the spec where a 16-bit value does occur, there are words that state the byte order.  So these words aren't needed in 2.1 and should be removed. You could consider putting them in Section 1, and saying that they apply to all 16-bit integer quantities anywhere in the spec (in which case you could argue that there's no need to repeat them each time the spec mentions a 16-bit quantity)

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