MQTT-S rename to MQTT-SN

[Ian Craggs]

As part of the job of applying the same or similar license terms to the MQTT-S specification as those on the MQTT specification, we are proposing a small name change.  The new name would be MQTT-SN, standing for exactly the same long name, MQTT for Sensor Networks.  Some people had assumed that the S in MQTT-S stood for secure, so we hope this change will avoid that confusion.

Please feel free to comment or ask questions.

Ian Craggs

[Andy Piper]

I think this makes sense, and should reduce the confusion around the assumption that any -S suffix denotes "secure".

Another point worth making on this list is that as part of the OASIS standardisation efforts, MQTT now just stands for "MQTT", rather than the former (and somewhat inaccurate) "Message Queueing Telemetry Transport". You'll find that change in the description of this Google Group, in the MQTT.org website, and in the name of the Google+ page, for example. So, having MQTT-SN fully expand to MQTT for Sensor Networks makes perfect sense :-)

Thanks for the update, Ian!

--
--
To learn more about MQTT please visit http://mqtt.org
 
To post to this group, send email to mq...@googlegroups.com
To unsubscribe from this group, send email to
mqtt+uns...@googlegroups.com
 
For more options, visit this group at
http://groups.google.com/group/mqtt
 
---
You received this message because you are subscribed to the Google Groups "MQ Telemetry Transport" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mqtt+uns...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
Andy Piper | Farnborough, Hampshire (UK)
blog: http://andypiper.co.uk   |   skype: andypiperuk
twitter: @andypiper  |  images: http://www.flickr.com/photos/andypiper

[Paul Fremantle]

I think it's a good change. Is mqtt-sn going to be donated to oasis?

Paul

[andyg (@geekscape)]

hi Ian,

On Monday, 8 July 2013 20:23:29 UTC+10, Ian Craggs wrote:

As part of the job of applying the same or similar license terms to the MQTT-S specification as those on the MQTT specification, we are proposing a small name change.  The new name would be MQTT-SN, standing for exactly the same long name, MQTT for Sensor Networks.  Some people had assumed that the S in MQTT-S stood for secure, so we hope this change will avoid that confusion.

Since both MQTT and MQTT-SN are both intended for Sensor Networks ... couldn't this lead to another confusing result.  Newcomers may think MQTT-SN is for sensors network, but good old MQTT must have some other purpose (not related to Sensor Networks).

Why not just spell it out and rename MQTT-S to become MQTT-Serial ?  Or, for a little more brevity you might like MQTT-SLP for "Serial Line Protocol" (which is remeniscent of SLIP).

cheers andyg (@geekscape)

[Paul Fremantle]

I think I prefer the other suggestion of MQTT-Light. Or we could go with drinks branding and call it MQTT-Zero.

Paul

--
--
To learn more about MQTT please visit http://mqtt.org
 
To post to this group, send email to mq...@googlegroups.com
To unsubscribe from this group, send email to
mqtt+uns...@googlegroups.com
 
For more options, visit this group at
http://groups.google.com/group/mqtt
 
---
You received this message because you are subscribed to the Google Groups "MQ Telemetry Transport" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mqtt+uns...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
Paul Fremantle
CTO and Co-Founder, WSO2
OASIS WS-RX TC Co-chair, VP, Apache Synapse

UK: +44 207 096 0336
US: +1 646 595 7614

blog: http://pzf.fremantle.org
twitter.com/pzfreo
pa...@wso2.com

wso2.com Lean Enterprise Middleware

Disclaimer: This communication may contain privileged or other confidential information and is intended exclusively for the addressee/s. If you are not the intended recipient/s, or believe that you may have received this communication in error, please reply to the sender indicating that fact and delete the copy you received and in addition, you should not print, copy, retransmit, disseminate, or otherwise use the information contained in this communication. Internet communications cannot be guaranteed to be timely, secure, error or virus-free. The sender does not accept liability for any errors or omissions.

[Tomoaki Yamaguchi]

How about MQTT-LowPAN?

2013/7/9 Paul Fremantle <pa...@wso2.com>

--

         

               Tomoaki  YAMAGUCHI

[Nicholas Humfrey]

Great news that MQTT-S is going to be available under the same terms as MQTT :)

Not sure I have any better naming suggestions but more letters is better - just having a -S did make naming in code confusing.

When I first implemented MQTT-S, I was also surprised at how different the protocol was (not reflected in the difference in name). Some of the differences felt like evolution and improvement of the protocol - will any of that be back-ported to the new OASIS MQTT standard?

Sent from my phone

[Dave Locke]

the charter for the first version of the OASIS MQTT standard does not allow much deviation from the current MQTT v3.1 spec - the main aim is to provide clarify areas that are ambiguous or unclear meaning there should be little or not change for existing implementations.   Once that is complete I would hope the next version of the standard can take on board many of the ideas that have been discussed and even implemented in the likes of MQTT-S.


All the best
Dave Locke

Senior Inventor, Pervasive and Advanced Messaging Technologies

lo...@uk.ibm.com Dave Locke/UK/IBM@ibmgb 7-246165 (int) +44 1962816165 (ext) 37274133 (mobex) +44 7764132584 (ext)

Fringe Bluepages with fuel injection My Cattail: Share files in IBM and save your in-box

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

[Paul Fremantle]

Dave

I agree. I think it is important to publish MQTT tidied up but as-is under OASIS. This will get MQTT as an international standard. Then we can look at improving. 

Paul

[Andy Piper]

Both Serial and LowPan imply binding connections to other specific protocols or connection methods, so I would avoid them. 

We could go with MQTT-L for Lightweight, that makes sense. As previously stated, I'm happy with -SN as well.

[Roger Light]

On Tue, Jul 9, 2013 at 11:58 AM, Andy Piper <andyp...@gmail.com> wrote:

> We could go with MQTT-L for Lightweight, that makes sense. As previously
> stated, I'm happy with -SN as well.

I think that -L makes the most sense and I like all things with Light
in the name. -SN would be fine as well.

Cheers,

Roger

[Ian Craggs]

Thanks for the input.  I prefer a name which emphasizes the motivation for MQTT-S, that is being lighter and not relying on TCP.  We did think about some options like this.  MQTT-SN does have the advantage of being a minimal change, which might be good for getting this done reasonably quickly, as lawyers are involved.  I'll pass on the suggestions, and see what response I get.

Ian

[Andy Piper]

This discussion is now reflected on mqtt.org - http://mqtt.org/2013/12/mqtt-for-sensor-networks-mqtt-sn - and the protocol specification has been re-issued (thanks Ian) with the new naming, at the existing version 1.2.

[Nicholas Humfrey]

Glad this has been sorted out. Let the grand renaming/string substitution begin!

Sent from my phone

--