[OASIS Issue Tracker] Commented: (MQTT-15) Should the CONNECT packet Protocol Name and Protocol Version fields be changed?

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

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

Allan Stockdill-Mander  commented on MQTT-15:
---------------------------------------------

I have no issue with removing the first two bytes that indicate the size of the Protocol Name string, and agree its size should be constant between versions.
I would however want there to be a notional difference between the Protocol Name and the Protocol Level, the latter remaining a single integer rather than a character representation of the version number. It would be simpler to programatically determine whether a client Protocol Level is a supported one.

> Should the CONNECT packet Protocol Name and Protocol Version fields be changed?
> -------------------------------------------------------------------------------
>
>                 Key: MQTT-15
>                 URL: http://tools.oasis-open.org/issues/browse/MQTT-15
>             Project: OASIS Message Queuing Telemetry Transport (MQTT) TC
>          Issue Type: Improvement
>          Components: core
>            Reporter: Allan Stockdill-Mander 
>
> The draft specification states that the Bytes 1 to 9 of the variable header section of the CONNECT packet are currently a spec encoded string (2 prefix bytes indicating the string length followed by the string data) containing the letters 'MQIsdp' followed by the number 3. Changing these fields would be an easy way to differentiate between old and OASIS spec compliant clients.
> Reasons for wanting to differentiate between clients include using discrimination of access to MQTT servers and understanding/implementing behavioural differences.

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