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

[Allan Stockdill-Mander <asm@uk.ibm.com>]

I have opened this issue to start a discussion
on what the TC thinks should be done regarding changes to the CONNECT packet,
specifically regarding the Protocol Name and Protocol Version fields. If
we are anticipating behavioural, or other changes that would break interoperability
between current clients/servers and those that are conformant to the spec
we release, or for auditability and firewall discrimination reasons such
as Raph suggested on the last call, it would seem appropriate to look at
changing these values. The proposal included should be treated as the starting
point for this discussion rather than necessarily a complete solution.

Thanks,

Allan Stockdill-Mander, GCFA
Websphere MQ
Phone: +44 1962 815415 (37245415 Internal)



From:      
 OASIS Issues Tracker
<workgroup_mailer@lists.oasis-open.org>
To:      
 mqtt@lists.oasis-open.org,

Date:      
 22/05/2013 13:16
Subject:    
   [mqtt] [OASIS
Issue Tracker] Created: (MQTT-15) Should the CONNECT packet Protocol Name
and Protocol Version fields be changed?
Sent by:    
   <mqtt@lists.oasis-open.org>

---

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

        

---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that 
generates this mail.  Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php



Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number
741598. 
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6
3AU