MQTT v3.1 specification available

August 20th, 2010 - admin

A protocol isn’t much use without a specification that allows others to understand how it works and how they can implement it. This has been a missing piece to the MQTT story for a while. The specification was originally made available as a part of the WebSphere Message Broker InfoCenter. This was done to get the protocol ‘out there’ with the intent that others could adopt it, but it came with the InfoCenter license that didn’t allow for others to implement it. With MQTT support moving from Message Broker to MQ, the protocol needed a new home.

One week ahead of the planned availability date of MQTT support in MQ, the MQTT v3.1 specification has been published on IBM developerWorks. This has been done with a royalty free license so anyone is free to create their own implementations.

You may notice the version has bumped to v3.1. There are some updates to the spec that adds support for security and clarifies the use of UTF-8 versus US-ASCII. The spec has also had a rewrite to make it a clearer and more complete document.

MQTT for Internet-of-Things :

[…] MQTT specs 3.1 are out and I am very surprised. This is probably because I did not bother looking at them before and I was sincerely expecting that, being associated to OASIS, it would consist of 10KB of xml tags with a lonely number or message code in the middle. I still remember the first time I experimented with Web-Services: converting Celsius to Fahrenheit. I would send a number (Celsius) and the server would return the conversion. When looking at raw code, it was a sea of tags with a tiny number in the middle. The response would be even worse. MQTT surprised me because it is not like this. It is beautiful. It even looks like an old RFC where you’d understand the protocol in 5 min and the rest are details and message codes. MQTT even has (some sort of) QoS. All beautifully packaged and with a lot of implementations and brokers in all flavours and sizes. To be perfect, they only have to find a better name as Internet-of-Things is not exactly only about Telemetry anymore. And make it run on top of UDP. That was a bit disappointing regarding my home project MQTT-S is just not exactly the same. I can understand using TCP for Pub/Sub. But then I do not and the need to have a live connection for topic notification is not completely valid. What creates the “connection” is MQTT itself, not TCP. May 6, 2013  –  Uncategorized Leave a Comment Name: Required […]

add a comment