[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Updated: (MQTT-15) Should the CONNECT packet Protocol Name and Protocol Version fields be changed?
[ http://tools.oasis-open.org/issues/browse/MQTT-15?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Allan Stockdill-Mander updated MQTT-15:
----------------------------------------
Proposal:
The Protocol Name field will be referred to as an immutable string, following the standard convention of two prefix bytes indicating length followed by the content 'MQTT'.
The Protocol Version field will be renamed Protocol Level, specified as an unsigned 8bit integer, and for this release of the specification set as the value 4.
was:Following from the TC decision that the formal protocol name should be 'MQTT' I propose that the Protocol Name string should be fixed as 4 bytes in length with no size prefix and contain only the characters 'MQTT', and additionally that the Protocol Version field be renamed to Protocol Level (to decouple it from the version number on the specification) and specified as an unsigned 8bit integer and be incremented to 4 (anticipating that potential future revisions would also increment this number).
> 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
> Affects Versions: 3.1.1
> Reporter: Allan Stockdill-Mander
> Assignee: Andrew Banks
> Fix For: 3.1.1
>
>
> 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
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]