* Feedback from review of Continua Sequence Diagrams as input to API work.

+

* Starting API Work.

−

* Discussion of MQTT related topics raised by Axeda but not covered last week.

+

* MqGnatt contribution

−

**Lua: We are very interested in the Paho MQTT Lua client, however, as of October 2012 it was missing a significant number of features which according to the Paho roadmap are supposed to be fixed or implemented in Q1-2013…

+

−

**Best Practices: It would be great if there was a list of “best practices” and “things to know” when using MQTT; for example, should hierarchies be very deep or flat.

+

<br>

<br>

<br>

+

= Feb 12, 2013=

+

* There is general consensus that the Continua sequence diagrams can serve as starting point for REST mapping and API work. We will look for means to get that work going in one or more of the projects, on the next call. Axeda's work on the scenarios will factor into this as well.

+

* Arlen is still intending to contribute McGnatt. It could as a "best practices implementation" in combination with some new documentation.

+

* Possible Webinars

+

** It was proposed that a whitepaper and/or webinar on Device Management/Provisioning with respect to the Eclipse work, would be of value. Mats will look further into this.

+

** A security webinar to outline and discuss security solutions in end-to-end M2M application development

+

* An introduction to the Lua MQTT client, and the platforms and applications it is being used on.

<br>

<br>

<br>

<br>

+

+

= Feb 5, 2013=

+

== Attendees ==

+

*Mats Samuelsson, Axeda

+

*Patrick Dempsey, Band XI

+

*Hilary Tomasson, Eurotech

+

*Scott de Deugd, IBM

+

==Continuation: discussion of MQTT related topics raised by Axeda==

+

* Scott gave update on OASIS TC. Last date to join the TC is March 18th.

+

* There was some feedback from review of Continua Sequence Diagrams that it looks like useful input to the API work. No next steps were agreed to but we will revisit this again after Phil and Mats have the opportunity to update the Scenarios and Problems.

+

* Discussion of MQTT related topics raised by Axeda but not covered last week.

+

**Lua: Axeda would like to contribute to Lua Client. Scott suggested their project lead call into the bi-weekly Paho calls for an introduction to Andy Gelme.

+

**Best Practices: There still are no volunteers for such a document but Mats said Axeda is interested in taking a lead to get this moving. There was some discussion of integration this with the pending MqGnatt contribution from Cirrus Link so we will discuss again when Arlen can make the cal.

+

* Ian pointed out a potential new contributions from m2m.io (https://twitter.com/kylemroche/status/297462594699157505). It looks that discussion has moved to the MQTT Google Group.

+

<br>

+

= Jan 29, 2013 =

= Jan 29, 2013 =

== Attendees ==

== Attendees ==

Line 41:

Line 64:

<br>

<br>

----------------------------------------

----------------------------------------

−

<br>

−

−

= Dec 11, 2012 =

−

== Attendees ==

−

*Mats Samuelsson, Axeda

−

*Patrick Dempsey, Band XI

−

*Hilary Tomasson, Eurotech

−

*Arlen Nipper, Paho

−

*Benjamin Cabé, Sierra Wireless

−

*Scott de Deugd, IBM

−

−

−

== M2M-IWG related feedback from LeWeb Paris ==

−

*There is not any significant awareness of the Eclipse projects and the M2M-IWG

−

*There seems to be continuing expectations that devices/things should be directly reachable via the internet.

−

* This group should look into ways to be more aggressive in promotion and awareness

−

**Articulate business value of open source and standards for M2M and IoT

−

** Get out story and experience on why abstraction of actual device and address is important to scalable solutions and open industry growth.

−

**Tie in a case study based on Continua obstacles, inhibitors and changes

−

**Tie in technical strategy being pursued at Eclipse

−

== Goal, Plans, Objectives for 2013 (continuation) ==

−

*We started into the 2013 goals, plans and objectives compiled so far:

−

**Exposing REST APIs: These is general consensus that this is an important technical priority and is a logical next step in the strategy/architecture role of the IWG. Arlen suggested that this could tie into "getting out the story" needs and could be initially focused by defining how application would "get to the topics". That would lead to mapping to URIs, and then lead into mapping fo payloads. To get started, Arlen will walk us through the Continua sequence diagrams which are going down this same path.

−

** While the API work is a key piece, the overall focus should be on how an application developer, solution builder and/or integrator ties all of the pieces together into solutions. As the strategy and priority of the Eclipse projects develops out of this M2M IWG work, it will do no good to get the message out unless Eclipse can offer and enable integration with, "industrial strength" code. For example starting with an Eclipse-based solutions platform, developers could combine Eclipse code and "plug-in" real scalable products to deploy.

−

** Both QEST and EIT/ICT Labs provide valuable collaboration opportunities so the IWG should focus on concrete projects with them in 2013.

−

** It is important to get a decision on Mosquitto and pursue a server story in 2013.

−

−

== Deferred for Future Calls ==

−

*Goal, Plans, Objectives for 2013 (continuation)

−

**Expose REST APIs

−

**Focus on tangible results and deliverables from the Working Group

−

**Pickup the previous work on architecture and key interface design

−

**Find ways to affect related Eclipse projects from technical, community and market perspective

−

**Put a priority back on an MQTT server project supporting M2M messaging

−

**The projects prove various APIS are needed but their needs to be a focus on a ready to use infrastructure for developers. Something where Eclipse can provide a "start from scratch" approach for developers building M2M applications.

−

**Expanded runtime platform support

−

**Continue looking in to collaboration with Continua, not just as an industry, but also as a template for finding ways the Eclipse projects can enable M2M industry solutions. Are there other industries we could discuss collaboration with?

−

**Market need/opportunity in expanding Mihini and Koneki tooling to Java

−

**To increase adoption and reducing bar to entry, there is a need ot "wrap" the MQTT clients to handle the basic housekeeping and configuration

−

**Commit MqGnatt as example and template

−

**Identify other means to abstract complexity

−

**Work with QEST developer to incorporate into IWG and/or projects. This could lead to "bridging" of various M2M networks. Identify and translate this to to concrete actions and next steps.

−

**Relationship with Continua, OASIS, OneM2M

−

**Consider expanding scope

−

**Security needs to be addressed overall and in context of related Eclipse projects

−

**Device level protocol from both standards and open source project perspective

−

<br>

−

<br>

−

−

= Nov 27, 2012 =

−

== Attendees ==

−

*Ian Skerrett, Eclipse

−

*Mats Samuelsson, Axeda

−

*Hilary Tomasson, Eurotech

−

*Marco Carrer, Eurotech

−

*Arlen Nipper, Paho

−

*Gaétan Morice, Sierra Wireless

−

*Benjamin Cabé, Sierra Wireless

−

*Scott de Deugd, IBM

−

*Patrick Dempsey, Band XI

−

−

== EIT ICT Labs ==

−

Petri Liuha of Nokia provided an overview of [http://www.eitictlabs.eu/ EIT ICT Labs]. There was a discussion around to potential ways that the EIT/ICT projects and Eclipse M2M projects could benefit from a collaboration between the organizations.

−

<br>

−

<br>

−

−

= November 6, 2012 =

−

−

== Attendees ==

−

*Ian Skerrett, Eclipse

−

*Mats Samuelsson, Axeda

−

*Hilary Tomasson, Eurotech

−

*Arlen Nipper, Paho

−

*Gaétan Morice, Sierra Wireless

−

*Benjamin Cabé, Sierra Wireless

−

*Scott de Deugd, IBM

−

*Patrick Dempsey, Band XI

−

−

==Goal, Plans, Objectives for 2013==

−

The following is a running summary of an open discussion looking back on the first year and toward goals, plans, and objectives for the Working Group in 2013

−

*Focus on tangible results and deliverables from the Working Group

−

*Pickup the previous work on architecture and key interface design

−

*Find ways to affect related Eclipse projects from technical, community and market perspective

−

*Put a priority back on an MQTT server project supporting M2M messaging

−

*The projects prove various pies needed but their needs to be a focus on a ready to infrastructure for developers. Something where Eclipse can provide a "start from scratch" approach for developers building M2M applications.

−

*Expanded runtime platform support

−

*Continue looking in to collaboration with Continua, not just as an industry, but also as a template for finding ways the Eclipse projects can enable M2M industry solutions. Are there other industries we could discuss collaboration with?

−

*Market need/opportunity in expanding Mihini and Koneki tooling to Java

−

*To increase adoption and reducing bar to entry, there is a need ot "wrap" the MQTT clients to handle the basic housekeeping and configuration

−

**Expose REST APIs

−

**Commit MqGnatt as example and template

−

**Identify other means to abstract complexity

−

*Work with QEST developer to incorporate into IWG and/or projects. This could lead to "bridging" of various M2M networks. Identify and translate this to to concrete actions and next steps.

−

*Relationship with Continua, OASIS, OneM2M

−

*Consider expanding scope

−

**Security needs to be addressed overall and in context of related Eclipse projects

−

**Device level protocol from both standards and open source project perspective

−

−

==EclipseCon 2013==

−

*Call for paper deadline is November 19th

−

*A hands-on workshop perhaps expanding on successful MicroDoc tutorial would be valuable to the community

−

−

−

<br>

−

−

= October 16, 2012 =

−

−

== Attendees ==

−

*Mats Samuelsson, Axeda

−

*Hilary Tomasson, Eurotech

−

*Arlen Nipper, Paho

−

*Gaétan Morice, Sierra Wireless

−

*Benjamin Cabé, Sierra Wireless

−

*Scott de Deugd, IBM

−

*James Branigan, Band XI

−

−

== QEST Followup ==

−

−

The call was spent discussing the QEST proposal presented on October 9th. The QEST work appears to share common ground some important areas the IWG will be looking at: REST APIs, Security and Payload, which together seem to warrant a parallel discussion thread. These have the potential of affecting M2M related projects in Eclipse and has overlap with the Continua work presented previously to the IWG.

−

−

It was suggested that a subgroup could be set up to work on this. We will discuss in more detail in a future call and followup with Matteo for his thoughts and interest in participating.

−

−

The remaining agenda items were postponed for the next call.

−

<br>

−

−

= October 9, 2012 =

−

−

== Attendees ==

−

*Matteo Collina (University of Bologna, presenter)

−

*Mats Samuelsson, Axeda

−

*Hilary Tomasson, Eurotech

−

*Arlen Nipper, Paho

−

*Andy Piper, VMware

−

*Benjamin Cabé, Sierra Wireless

−

*Julian, Sierra WIreless

−

*Scott de Deugd, IBM

−

*Patrick Dempsey, Band XI

−

*Peter Niblett, IBM

−

*Ian Skerrett, Eclipse

−

−

== QEST ==

−

Matteo Collina presented his work on a model for interfacing smart objects with those that have evolved in the Web to interface with people. QEST is new pattern for a broker that can address the Internet of Things, bridging the gap between MQTT and web protocols.

−

−

QEST address some important technology and adoption issues. Matteo will provide links here to his paper and the presentations. The M2M IWG will schedule some time to discuss this in more detail.

−

−

<br>

−

<br>

−

−

= October 2, 2012 =

−

−

== Attendees ==

−

*Mats Samuelsson, Axeda

−

*Hilary Tomasson, Eurotech

−

*Marco Carrer, Eurotech

−

*Benjamin Cabé, Sierra Wireless

−

*Scott de Deugd, IBM

−

*Patrick Dempsey, Band XI

−

*Peter Niblett, IBM

−

== Eclipse Project Updates ==

−

Scott and Benjamin gave brief updates on Paho, Koneki and Mihini. Paho project plan has been submitted based on 4Q12 build,a 1Q13 release and an 0.9 release in 2Q13 for Kepler. Benjamin gave a brief report on his attendance at the [http://summit.oshwa.org/ Open Hardware Summit] which led to a discussion summarized below.

−

−

== Open Hardware Summit ==

−

Benjamin noted form his attendance at Open Hardware Summit that the may be some common interests between M2M IWG and the Open Source Hardware Association that sponsors the conference. There was discussion of this on the call resulting in suggestion s for future followup:

−

*Promote the Eclipse M2M IWG at the next conference.

−

*There may be value to both the open source hardware community and the open source software M2M community in readily available software platforms. A version of Mihini for contained devices like the Raspberry Pi and an Arduino that would leverage M2M gateways and servers, was given as an example.

−

*Start with demonstrations using recommended configurations of Eclipse project code for M2M for open soruce hardware. Include a constrained framework in Eclipse.

−

*Contact some of the Open Source Hardware Association companies supporting and using open source hardware for a discussion around open hardware and software collaboration via Eclipse.

−

*This is an annual conference. Add this discussion to future call agendas to gauge further interest.

−

== Related standards ==

−

Ian was not on the call but Scott reported that Ian was in contact with OneM2M and looking into ways that the M2M IWG could participate. Final approval of the MQTT specification is proceeding at Continua. Scott will have more to report in future calls about moving the MQTT specification to OASIS.

−

−

== Other Business ==

−

*Scott observed that the M2M interface work based on the Scenarios, has a high degree of overlap with a new work effort forming at Continua to define a services layer using MQTT. He is recommending we the M2M IWG collaborate there and will report in with more details alter. It was recommended that we pull the proposal James made, out of the minutes and onto a separate section in the Wiki.

−

*General agreement that compiling an agenda for this call in advance on the wiki is best.

−

−

−

<br>

−

<br>

−

= September 19, 2012 =

−

−

== Attendees ==

−

*Mats Samuelsson, Axeda

−

*Andy Piper, Paho

−

*Ian Skerrett, Eclipse Foundation

−

*Hilary Tomasson, Eurotech

−

*Marco Carrer, Eurotech

−

*Benjamin Cabé, Sierra Wireless

−

*Scott de Deugd, IBM

−

*Patrick Dempsey, Band XI

−

*James Branigan, Band XI

−

== Eclipse Project Updates ==

−

Scott and Benjamin gave brief updates on Paho, Koneki and Mihini.

−

−

There have been no updates since the last meeting on options for MQTT broker support in Paho. The consensus then was that moving Mosquitto over to Eclipse and Paho subproject would be the best path. Scott agreed to follow up with Roger Light and Arlen Nipper to see where the the decision process is.

−

−

Andy Piper will send a list of related HTTP - MQTT bridges out to the mailing list.

−

== Webinars ==

−

The webinars remain on track on track for September. Webinar information can be [http://eclipse.org/community/m2m-webinars/ found here].

−

Ian again requests that request that all members who can, promote these within their company.

−

−

== M2M Portal and M2M Eclipse Package ==

−

The [http://m2m.eclipse.org/Eclipse M2M portal] is now live. The design, content and purposing of the portal received very positive feedback and compliments.

−

−

Benjamin is looking for input from Paho project on the Eclipse M2M Package Proposal. Paho is now building a plan to be part of the Kepler release and has milestones that will allow for integration with the EPP. Scott will encourage input on this from the Paho community.

−

== Event Coverage: LeWeb conference, EclipseCon Europe ==

−

We discussed the [http://paris.leweb.co/ 2012 LeWeb conference] in Paris Dec 4-6. The theme of the conference is Internet of Things. Ian asked all members to let him know their interest in an Eclipse M2M Booth. Ian also reminded us about [http://www.eclipsecon.org/europe2012/ EclipseCon Europe].

−

−

== Standards discussion ==

−

Scott gave an update on the ongoing work with Continua Alliance to incorporate MQTT into their specifications, and there he is now seeing strong interest and support in moving the MQTT protocol specification over to OASIS.

−

−

Following up on a previous conversation here, Mats proposed we explore a relationship with OneM2M. There was consensus on this so Ian will look into the options available.

−

<br>

−

<br>

−

−

= September 4, 2012 =

−

−

== Attendees ==

−

−

*Mats Samuelsson, Axeda

−

*Peter Niblett, IBM

−

*Benjamin Cabé, Sierra Wireless

−

*Scott de Deugd, IBM

−

*Patrick Dempsey, Band XI

−

*James Branigan, Band XI

−

*Gaétan Morice, Sierra Wireless

−

*Ian Skerrett, Eclipse Foundation

−

−

== Moving from Scenarios to Architecture ==

−

−

There was a discussion on the proposal James sent around (included below). Everyone was in agreement on this design point for the interfaces into MQTT for for programming models like SOAP or REST that run over HTTP.

−

−

----

−

−

''Eclipse M2M IWG Topic Space Design Thoughts''

−

−

''Within an MQTT design space, there are issues related to topic space design. &nbsp;This is not a unique concern for MQTT, in fact HTTP has already been through many of these issues with URL design. &nbsp;One way to think about MQTT and HTTP is as follows: The difference between MQTT and HTTP is directional: MQTT is to HTTP as PUSH is to PULL. &nbsp;SOAP and REST both use very different design styles on top of HTTP. &nbsp;Both styles are also possible in MQTT topic space design. &nbsp;The following topic space is more aligned with a REST style design. &nbsp;It has relatively few verbs and is organized around resources, which provide representations for the sensors, actuators and devices.''

''<br> A request for all meta-data for zone 2 of refrigeration unit 2 at store 456.''

−

−

''/META/store/456/refrigeration-unit/2/zone-2''

−

−

''<br> A request for all sensor and actuator ids for a refrigeration unit 2 at store 456.''

−

−

''/LIST/store/456/refrigeration-unit/2''

−

−

''One of the first things you notice is that I've added the VERB in all caps as the first segment. &nbsp;This is by convention only. &nbsp;Next I have a multi-segment path that provides addressibility to the device in question. &nbsp;In these examples that is a refrigeration unit. &nbsp;Finally, I have multi-segment path that provides addressibility to the unique sensor and actuator in question. &nbsp;Multiple paths to the same device is a more advanced topic and not shown here. &nbsp;By limiting the verbs in use and defining tight semantics, it is possible to construct processes that bridge brokers and provide additional services(proxy servers, data historian, etc).&nbsp;''

−

−

''<br> Payload Format''

−

−

''The payloads are not shown, although I highly recommend something programming language neutral. &nbsp;Please do not directly serialize Java or C# objects, you will regret it later. &nbsp;XML can be very heavy-weight for embedded devices to process. &nbsp;I often use CSV or JSON for payloads when dealing with embedded systems. &nbsp;A translation client can be used to rebroadcast after turning XML into CSV/JSON and CSV/JSON back into XML if necessary for enterprise integration. &nbsp;''

−

−

''<br> Advanced Topic Space Design''

−

−

''There are many other best practices for multi-reads, multi-write, meta-data update, dynamic sensor and actuator installation/removal, id claiming, admin features(log retrieval, firmware flashing, etc.). &nbsp;These are explicitly left out of this note in order to avoid distracting from the most simple operations.''

−

−

----

−

−

== Webinars ==

−

−

The webinars are are on track for September with dry runs coming up. Ian be scheudling these a week or two in advance. Webinar information can be [http://wiki.eclipse.org/Machine-to-Machine/M2MIWG/Marketing-Programs found here]. Ian is requesting that anyone who can promote these within their company to please contact him.

−

−

== oneM2M ==

−

−

Mats gave a brief overview of oneM2M which lead into a discussion about the M2M IWG participation with OneM2M. There was general agreement that and it could be a key relationship and we should discuss this in future calls. <br> <br>

−

−

= August 14, 2012 =

−

−

== Attendees ==

−

−

*Arlen Nipper, Paho

−

*Benjamin Cabé, Sierra Wireless

−

*Scott de Deugd, IBM

−

*James Branigan, Band XI

−

*Hilary Tomasson, Eurotech

−

*Ian Skerrett, Eclipse Foundation

−

−

== Webinars ==

−

−

The webinars are confirmed. Ian will update the webpage and make it public. They will run 1 hour and Ian recommend leaving 15 minutes for questions and answers. We should all look for introductions and other points to tie these together but it is important that each webinar can standalone. Ian will schedule a dry-run of these.

−

−

Ian asked everyone to look for ways to promote this within their company's related PR oe marketing activities.

−

−

== Moving from Scenarios to Architecture ==

−

−

There was a discussion on how to get from the scenarios, to the architecture, design and implementation of key open interface points for gateways, servers and the applications. REST is an API that is recurring requirement and topic for M2M. It is a proposed element of the Mihini proposal and and as is it use for application integration with MQTT.

−

−

The timing to do this is good as it was pointed out that both the Mihini proposal and the work Scott and Arlen are doing with Continua have very similar requirements for a RESTful interface. The M2M IWG has considerable combined experience in building M2M systems, and we expect further participate as the community grows. James suggested that the place to start is mapping topic spaces to devices and device data interfacing techniques that have been used before, today and may be used in the future. James will try and take a first pass at this. <br>

−

−

= July 24, 2012 =

−

−

== Attendees ==

−

−

*Ian Skerrett, Eclipse Foundation

−

*Arlen Nipper, Paho

−

*Scott de Deugd, IBM

−

*Patrick Dempsey, Band XI

−

*Hilary Tomasson, Eurotech

−

*Benjamin Cabé, Sierra Wireless

−

−

== Project update ==

−

−

The Lua framework proposal has been submitted to Eclipse: [http://www.eclipse.org/proposals/technology.mihini/ (Mihini). Everyone is requested to review the plan and to look for intersection and /or overlap with Paho compoents and plans.

−

−

From the Paho project, Scott said he will be responding to concerns that the project is not responding quickly enough to the community. He asked Ian about the contributor/committer process for the new Lua client being added to Paho. Ian suggested that the contributor -&gt; committer path may indeed not be the correct one for a major new contribution and agreed to work this off line with Scott to speed things up.

−

−

== MQTT Server Support ==

−

−

This topic has moved over to the Paho lists but it was pointed out that there is some confusion and we need to make clear that the proposal right now is only for C language. There is interest in Java support but no concrete proposal yet.

−

−

== Scenarios ==

−

−

The group agreed on the scenarios although it was noted that we may need to go back and extend them for device management. There was a brief discussion on how to move forward, turning these into a high level architecture and requirements for existing and new projects. Arlen suggested we need to be sure we are addressing real customer problems today while looking out to where M2M and IoT will be in the near future. He said the we neeed to address the IT architects as a key audience that needs means to be able to mask much of the unnecessary complexities they are dealing with today to integrate physical world systems. Benjamin asked how we could also use this to bring the existing project closer together. The timing is good for this with the MQTT server support kicked off and the Mihini proposal that will be looking at APIs including REST. This will be a continuing topic for the IWG. &lt;br&lt;

−

−

= July 17, 2012 =

−

−

== Attendees ==

−

−

*Arlen Nipper, Paho

−

*Scott de Deugd, IBM

−

*James Branigan, Band XI

−

*Patrick Dempsey, Band XI

−

*Benjamin Cabé, Sierra Wireless

−

−

== Project Updates ==

−

−

Benjamin gave an update on the Lua framework proposal. He is submitting this to Eclipse as a new project . Goal for end of year are REST APIs. Benjamin also is planning to have a preview of the Developer Portal sometime in August.

−

−

The group agreed on the fist of the two logos that Benjamin had previously sent around. (note: Bnejamin can you provide a link here to the logo?)

−

−

== oneM2M ==

−

−

Arlen gave the group an overview of oneM2M, a recently announced Standards consortium for M2M standards. The organization is closely aligned with ETSI and will work to consolidate various worldwide standards that affect M2M. Arlen thought the first oneM2M face-to-face meeting will be in September. As it appears we may have common goals for the M2M market, it was suggested that there may be ways in which Eclipse and oneM2M could cooperate. Scott and Arlen review this with Mike and Ian and see if introductions can be arranged.

−

−

== Scenarios ==

−

−

Scott suggested that it is time to close the scenario work as they do focus on key interface areas (device &lt;-&gt; M2M Gateway &lt;-&gt; M2M Server/Enterprise Server), and they map well to the current projects and to the proposed framework project. We will take this on in the following call.

−

−

There was general agreement that we may soon have enough even with the limited scenarios to get started on this work.

−

−

<br>

−

−

<br> <br>

−

−

= July 10, 2012 =

−

−

== Attendees ==

−

−

*Ian Skerrett, Eclipse Foundation

−

*Arlen Nipper, Paho

−

*Scott de Deugd, IBM

−

*James Branigan, Band XI

−

*Patrick Dempsey, Band XI

−

*Hilary Tomasson, Eurotech

−

*Benjamin Cabé, Sierra Wireless

−

−

== Project Updates ==

−

−

Benjamin gave a brief overview of an Lua framework for embedded applications being considered for Koneki. It was suggested we discuss this further when Marco from Eurotech was on as they were proposing a similar framework contribution at one time.

−

−

Benjamin will narrow down two logos for the M2M developer portal, and send them out for decision on the next call.

−

−

A new technical "Redbook" on MQTT and its application is available from IBM. Scott will send out a [http://www.redbooks.ibm.com/redpieces/abstracts/sg248054.html link] and include it on the Paho project website.

−

−

== Scenarios ==

−

−

Arlen has added to the scenarios and problems. He will be doing more work to see if this can fit as an extension of the refrigeration scenario.

−

−

There was some discussion if these basic scenarios now provide enough to get the architecture work started. This may be possible, given the initial scope of the work to focus on interface between M2M gateway, and Enterprise or Web servers.

−

−

James suggested that we need to develop a useful vocabulary to describe the architectural approaches which may come down to "push vs pull". For example compare MQTT to HTTP and one could looking at how how topics would map to URIs. Similarly, with SOAP vs REST. We may be able to identify needed patterns.

−

−

There was general agreement that we may soon have enough even with the limited scenarios to get started on this work.

−

−

== Status on Proposal for Open Source Messaging Server ==

−

−

Arlen reported that both IBM and Roger Light are now both interested in creating a proposal around Eclipse open source server support for the MQTT protocol. As IBM may be looking at RSMB, and Roger already has Mosquitto out in open source, the next step is to start a technical discussion about these code bases as potential starting points. This discussion will be now moved over to the Paho mailing list.

−

−

== Webinars ==

−

−

A proposal for two seminars was made. On would be an overall session on the M2M markets, technologies and opportunity. Arlen and Benjamin are interested in this. James proposed another piece to this that could bridge the overall view into the architectural and technical points that the IWG feels are important to address. So this webinar may end up having two parts. The second would be on MQTT, publish/subscribe and the applicability of those types of messaging patterns.

−

−

== EclipseCon Europe ==

−

−

This will be at the end of October. Ian will reserve a space for an F2F meeting.

−

−

<br> <br>

−

−

= June 5, 2012 =

−

−

== Attendees ==

−

−

*Ian Skerrett, Eclipse Foundation

−

*Arlen Nipper, Paho

−

*Scott de Deugd, IBM

−

*James Branigan, Band XI

−

*Patrick Dempsey, Band XI

−

*Hilary Tomasson, Eurotech

−

*Benjamin Cabé, Sierra Wireless

−

−

== Status on Proposal for Open Source Messaging Server ==

−

−

No updates to report but Arlen said he will be able to report back on the June 19th call.

−

−

== Review and Approval of Marchitecture ==

−

−

The Marchitecture presentation was approved by consensus [http://dev.eclipse.org/mhonarc/lists/m2m-iwg/pptFBTEk7K421.ppt and can be found here].

−

−

== Scenario/Problem Discussion ==

−

−

Arlen is introducing a scenario that can lead to requirements for less direct coupling between M2M/IoT applications and the protocols used by devices and controllers. He distributed a new Problem Description: “One-to-One Data Model for SCADA/Telemetry Information". A number of points were brought up in the discussion:

−

−

*Designs and implementations for M2M systems, standards, or integration often focus too much on a question like "well what about this protocol?". This is because often the device protocol interface is the application's means to access device data. This leads to unnecessarily tight coupling between the applications and the specific protocol used, which in turn can lead to "brittle" system design. Arlen gave some examples of this from SCADA application domains. The M2M IWG should look into this so that the M2M and IoT application and solutions markets can move forward more rapidly, being somewhat independent of device protocols and promote support of multiple protocols.

−

*While M2M system developers sometimes design frameworks, abstraction layers, models and generators in order to quickly adapt to multiple protocols, a better solution is needed.

−

*There will always be multiple protocols and standards - that is inherent to the space. Supporting/Integrating existing and new protocols is important and always will be . The IWG scenario work should result in identifying problems and solutions and a level of decoupling that reflects this, while encouraging rapid open application development and integration.

−

*From an application developer perspective, the IWG architecture work should include where and how protocol conversion should be supported - e.g. in tools, frameworks and/or abstraction layers. This needs to address devices, edge controllers/gateways, and servers.

−

−

Arlen said he would factor this Problem description into an appropriate scenario and post these on the Wiki. Although the currently documented refrigeration scenario is not specifically SCADA-related, Arlen said he may be able to extend it to be representative of a larger class of M2M problems including the SCADA ones he has experience with.

−

−

== Feedback on Eclipse Damos Proposal ==

−

−

There was a discussion about a new proposal, [http://www.eclipse.org/proposals/tools.damos/ Damos], recently published on Eclipse. Damos proposes a data flow oriented model to generate embedded system applications and simulations. It uses data models. Damos appears focused on creating the logic/algorithms for these embedded applications rather than their integration with servers and other applications. Given that this is model driven and proposed to run in Eclipse, the data models, the target embedded devices themselves and/or applications running on them may be of interest from an M2M perspective. For example, the sensor values should be compatible with what the M2M projects do with the proposed data model. Benjamin also noted that Damos appears to be based on Itemis technology and that he would followup with them.

−

−

== Eclipse based MQTT Client ==

−

−

Hilary reported that work is proceeding on the Client to run inside Eclipse, Chad has sorted out his Committer credentials, and has started the code commit process.

−

−

== PR ==

−

−

Ian has decided that given the timing, it is not practical to participate in Connected World's Hackathon or have an Eclipse booth. He will be attending and promoting the Eclipse M2M IWG and projects. He will report back in two weeks and we can discuss participation and possibly supporting the Hackathon next year. <br> <br>

−

−

= May 22, 2012 =

−

−

== Attendees ==

−

−

*Ian Skerrett, Eclipse Foundation

−

*Marco Carrer, Eurotech

−

*Arlen Nipper, Paho

−

*Scott de Deugd, IBM

−

*James Branigan, Band XI

−

*Peter Niblett, IBM

−

*Hilary Tomasson, Eurotech

−

*Benjamin Cabé, Sierra Wireless

−

−

== Marchitecture and PR Update ==

−

−

An update of the presentation was sent out on the Mailing List and [http://dev.eclipse.org/mhonarc/lists/m2m-iwg/pptFBTEk7K421.ppt can be found here]. We will review this on the next call a try to approve for posting. We ran out of time for Ian to update us on PR but he later posted this status:

−

−

*The momentum press release to go out Thursday morning 5/24. It will be posted on the eclipse.org web site and the [http://www.prweb.com/releases/2012/5/prweb9524538.htm PRWeb newswire].

−

*Based on feedback and conversations, we will not have an Eclipse booth at Connected World. Ian will attend the conference and evangelize the IWG objectives.

−

−

== Scenario Walk-through and Discussion ==

−

−

Scott summarized the goals of the scenario work:

−

−

*Document key needs obstacles, and inhibitors, both technical and market based, that the Eclipse M2M community can address with architecture and project deliverables.

−

*Document requirements to be addressed by follow-on architecture and open source project deliverables

−

−

Call today is to walk through the the first scenarios provided by Band XI to see if the format and level match our goals:

*Arlen suggested we identify what we want to accomplish and try to scope which scenarios we go after first. He suggested an immediate goal to help developers an integrators see how to "put together M2M applications" and, how the resulting code could feed into the concept of an "app store".

−

*Peter added that we need to also raise and focus on what are expected to be the main architectural issues. James suggested that we keep that in mind but that the problems should leads to architecture and corresponding frameworks.

−

*James noted that these initial scenario/problems imply a hardwired connection to the internet. Because wireless device connections are driving the M2M space, Arlen agreed to look over these scenarios from a wireless requirements perspective and to add additional scenarios representative of the wireless issues and opportunity.

−

*Peter noted that while this level of Scenarios are good, what we are identifying as "Problems" in the wiki will be what end up driving the technical work. Peter feels we need a Scenario and related Problems that are indicative of a "producer/consumer" architecture. He will try to add these.

−

*Ian reminded the group that while we may specific goals to get to an architecture and project deliverables, this level of Problems/Scenarios will also prove very educational for people trying to understand this space better.

−

*James indicated they would continue working scenarios when possible.

−

−

<br>

−

−

<br> <br>

−

−

= May 8, 2012 =

−

−

== Attendees ==

−

−

*Ian Skerrett, Eclipse Foundation

−

*Marco Carrer, Eurotech

−

*Arlen Nipper, Paho

−

*Scott de Deugd, IBM

−

*Patrick Dempsey, Band XI

−

*Peter Niblett, IBM

−

−

== PR Update ==

−

−

Ian sent out a draft press release.

−

−

He needs edits back from Eurotech, IBM, and Sierra Wireless on May 17th

−

−

Press release will go out on May 24th.

−

−

== Update and Discussion on Marchitecture ==

−

−

A new version incorporating edits/comments from last calls, is not yet available.

−

−

Scott asked that the last list of technical challenges be included as a bridge from the problem statement to the goals and objectives of the IWG. He also noted we need to highlight the need to focus on a effective level of decoupling between the producers of device data and the consumers, such as enterprise and web applications. Arlen may propose an additional chart on decoupling and the value to opening up new applications and markets.

−

−

Peter asked for more background on what is driving the volumes and opportunity on chart #2 and that, on chart #4, we not limit the market to B2B.

−

−

Ian thinks a final review draft could be ready in a few weeks.

−

−

<br>

−

−

<br>

−

−

= April 24, 2012 =

−

−

== Attendees ==

−

−

*Ian Skerrett, Eclipse Foundation

−

*Hilary Tomasson, Eurotech

−

*Benjamin Cabé, Sierra Wireless

−

*Gaétan Morice, Sierra Wireless

−

*Arlen Nipper, Paho

−

*Scott de Deugd, IBM

−

*James Branigan, Band XI

−

−

== M2M Server Support ==

−

−

Arlen gave the group a quick update on putting together an Eclipse-based open source assessment and recommendations for server side support of the MQTT protocol. He has been looking at options and needs, and will be contacting Roger Light (Mosquitto) soon, to follow-up on this.

−

−

== Update and Discussion on Marchitecture ==

−

−

Work on this is progressing. There is a joint call scheduled for this Friday. Hilary will update the IWG on next week’s call.

−

−

== Modeling Update ==

−

−

The modeling work is focused on a means to describe device data and how it is transmitted on the “wire”. Benjamin is working on a use case to describe some of the requirements for this which he will put on the M2M IWG Wiki. The also is a sample application being developed demonstrate use of the Model.

−

−

== Scenarios and Problems ==

−

−

To start looking at addressability and decoupling, James has updated a [http://wiki.eclipse.org/Machine-to-Machine/M2MIWG/M2M_Scenarios#0002 Food Refrigeration Unit Zone Control] scenario with a related Problem: [http://wiki.eclipse.org/Machine-to-Machine/M2MIWG/M2M-Problems#0002 Sensor and Actuator Identity and Addressability]. He asks everyone to take a look and comment.

−

−

== Project Related ==

−

−

Scott wanted let everyone know that there was a discussion on the Paho mailing list about the the emerging importance of dual licensing Eclipse M2M runtimes, especially for use/distribution on Linux based where a GPL compatible licensing terms like EDL are expected.

−

−

<br> <br>

−

−

= April 17, 2012 =

−

−

== Attendees ==

−

−

*Ian Skerrett, Eclipse Foundation

−

*Hilary Tomasson, Eurotech

−

*Benjamin Cabé, Sierra Wireless

−

*Scott de Deugd, IBM

−

*James Branigan, Band XI

−

*Arlen Nipper, Paho

−

−

== M2M Server Support ==

−

−

Arlen gave the group a quick update on putting together an Eclipse-based open source assessment and recommendations for server side support of the MQTT protocol. He has been looking at options and needs, and will be contacting Roger Light (Mosquitto) soon, to follow-up on this.

−

−

== Update and Discussion on Marchitecture ==

−

−

Two sets of presentation materials from Eurotech and Sierra Wireless are now being combined into a single deck as a starting point. The combined draft will be input to the IWG. Sierra is working on a draft vision statement.

−

−

== Project Related ==

−

−

Marco reported that they are working on the eclipse.org user permissions needed for Chad Kienle to commit. This should be worked out soon. Scott will be sure Paho team is following up to get the Lua MQTT contribution moving.

−

−

== Community Building, Marketing and PR ==

−

−

Ian has created a Wiki section for this [http://wiki.eclipse.org/Machine-to-Machine/M2MIWG/Marketing-Programs here]. Ian will kick off a discussion start a discussion on the next M2M press release. Companies are encouraged to sponsor Eclipse demo camps with M2M theme and/or presentations. DemoCamp are being scheduled for June.

−

−

<br> <br>

−

−

= April 10, 2012 =

−

−

== Attendees ==

−

−

*Ian Skerrett, Eclipse Foundation

−

*Marco Carrer, Eurotech

−

*Hilary Tomasson, Eurotech

−

*Benjamin Cabé, Sierra Wireless

−

*Scott de Deugd, IBM

−

*Arlen Nipper, Paho

−

*Gaétan Morice, Sierra Wireless

−

*Andy Piper, mqtt.org

−

*James Branigan, Band XI

−

*Patrick Dempsey, Band XI

−

−

== Update and Discussion on Marchitecture ==

−

−

Hilary Tomasson has organized the initial calls. Marco and Benjamin are participating. They have agreed to pull together a rough draft that they will review with the IWG. They agreed that they should be able to draft a Vision statement from this.

−

−

== Scenarios and Problems ==

−

−

Benjamin has completed a Wiki template to capture these in the M2M IWG Wiki. The template is [http://wiki.eclipse.org/Machine-to-Machine/M2MIWG/M2M_Scenarios#M2M_Scenario_Description_Template |here]. James, Arlen and Benjamin indicated they will be providing scenarios.

−

−

== Project Related ==

−

−

Given interest by new contributors, Scott was asked to set up regular Paho Project calls.

−

−

<br>

−

−

= April 3, 2012 =

−

−

== Attendees ==

−

−

*Mike Milinkovich, Eclipse Foundation

−

*Dave Locke, IBM

−

*Peter Niblett, IBM

−

*Benjamin Cabé, Sierra Wireless

−

*Scott de Deugd, IBM

−

*Arlen Nipper, Eurotech

−

*Nick O'Leary, IBM

−

*Gaétan Morice, Sierra Wireless

−

*Pat Huff, IBM

−

*Andy Piper, mqtt.org

−

*James Branigan, Band XI

−

−

Call was opened up to exchange feedback from EclipseCon and the F2F Meeting

−

−

== Followups and Next Steps from the F2F Meeting ==

−

−

As there was not sufficient time to review the Next Steps and ToDo items from the F2F Meeting, Scott asked to use call to walk through them for discussion and update. This have been added to the [http://wiki.eclipse.org/Machine-to-Machine/Face-2-Face-Meeting-Mar29#Next_Steps_and_Followups|wiki section for the March 29, 2012 F2F Meeting].

−

−

== OSGi Support on M2M Servers ==

−

−

There was interest and discussion at EclipseCon around OSGi support on the MQTT server. Both Equinox and Virgo have come up as project to consider. Arlen and Wes have built OSGi server support before and suggest that multiple implementations should be supported. (edit: here is the ink to the Mailing List [http://dev.eclipse.org/mhonarc/lists/paho-dev/msg00023.html|discussion on OSGi] ) There was brief discussion about including this on the M2M sandbox server. Currently Mosquitto is C so support for OSGi would probably also lead to a discussion about Java support for the server in the project.

−

−

== Other contacts - EclipseCon ==

−

−

*Andy talked to Hitachi folks about home automation. Hilary, Wes and Arlen said they have contacts to see if Hitachi is interested in the Eclipse M2M projects and IWG.

−

*He talked to some Motorola people there, who he will followup with.

−

*There were discussion about MQTT IA92 support that Andy will followup with Dave on.

−

−

= 2012-03-13 =

−

−

== Attendees ==

−

−

*Ian Skerrett, Eclipse Foundation

−

*Benjamin Cabé, Sierra Wireless

−

*Scott DeDeugd, IBM

−

*Arlen Nipper, Eurotech

−

*Marco Carrer, Eurotech

−

*James Branigan, Band XI

−

−

''note: due to time zone changes, some members could not attend''

−

−

<br>

−

−

== Discussion on Metamodel Description: ==

−

−

Benjamin has updated the metamodel description on the Wiki with an introduction and purpose. No specific comments yet. Benjamin will send a note out to the mailing list to encourage review and comments. http://wiki.eclipse.org/Machine-to-Machine/M2MIWG/M2M_meta-model

−

−

Question came up on whether the metamodel is intended for use in the tooling for application integration and development, or also for defining device parameters and data interface to external systems? Benjamin responded that it is intended primarily for application development but once defined it could also be used for open interface integration.

−

−

A request was made to include an example of instantiating the metamodel. Benjamin was agreeable to this but said he cannot get to it until after EclipseCon.

−

−

== Discussion on Scenarios/Problems Description: ==

−

−

A proposed format and examples for the Scenarios and related Problems are now on the Wiki. Arlen was OK with format and will add some relevant scenarios. Scott will send a note out to the mailing list to encourage review, comments and contributions. http://wiki.eclipse.org/Machine-to-Machine/M2MIWG/M2M_Scenarios

−

−

== Updates on Project work: ==

−

−

*Koneki: team is working to be part of Juno release stream

−

*Paho: C code available now. Java code ready and is getting new package names before release.

−

*M2M Sandbox Server: This is running now. Access control needs to be addressed. Ian will try to get someone from Eclipse IT to the F2F meeting. Arlen has some simple start-up documentation he will provide.

−

−

== Agenda for EclipseCon meeting ==

−

−

Scott will update Wiki with items discussed today.

−

−

*Sandbox access control

−

*Discussion around a 2012 focus on “user experience” with Koneki, Paho and Sandbox.

−

*Participants should add themselves to the dedicated [[Machine-to-Machine/Face-2-Face-Meeting-Mar29|wiki page]]

−

−

<br>

−

−

= 2012-02-28 =

−

−

== Attendees ==

−

−

*Ian Skerrett, Eclipse Foundation

−

*Benjamin Cabé, Sierra Wireless

−

*Scott DeDeugd, IBM

−

*Peter Niblett, IBM

−

*Dave Locke, IBM

−

*Arlen Nipper, Eurotech

−

*Marco Carrer, Eurotech

−

*Andy Piper

−

*Patrick Dempsey, Band XI

−

*James Branigan, Band XI

−

−

== M2M meta-model ==

−

−

(note from Benjamin: sorry that I likely did forget to write down some of the discussions around the model, feel free to complete!)

−

−

*Benjamin will add a preamble to the wiki page to describe in more details the purpose of the meta-model

−

*Peter: how about devices and sensors acting as data feeds?

−

*Arlen: it is more about devices and brokers than devices and servers.

−

*Scott: oBIX may be a good model to describe data. Arlen had use cases with oBIX and MQTT.

−

−

== M2M app anatomy, scenarios ==

−

−

*Arlen and Scott will provide a first draft of the description of data manipulation: how to send it, how to receive it...

−

−

== Chairperson ==

−

−

*Ian reminds that the chairperson is setting meetings agendas, and running the meetings

−

*The chairperson must be from a strategic or enterprise member company, and only IBM is falling into this category

−

*Scott to take the chairperson role

−

*It is suggested that the chairperson (and co-chairs if any) should be renewed every year

−

−

== Agenda for EclipseCon meeting ==

−

−

*The meeting could start earlier if needed (even though there's the keynote in the morning)

−

*There will be a couple of newcomers (QNX, Thingworx, ...), maybe it'd make sense to present them the activities of the Group during the BoF and use the F2F meeting

−

*The main topics would be the M2M meta-model and marketing.

−

*Participants should add themselves to the dedicated [[Machine-to-Machine/Face-2-Face-Meeting-Mar29|wiki page]]

*Benjamin has put a first version of the M2M meta-model requirements on the wiki

−

**It is very data-centric atm (which was identified has something very important during the IWG kick-off though)

−

**Members are encouraged to review it and provide feedback

−

*Koneki team will provide a first implementation of the meta-model in EMF (hopefuly this week)&nbsp;; and then tooling to edit model instances

−

−

== M2M developers hub ==

−

−

*Drupal instance has been set up

−

**Ian to send credentials to Andy

−

*Ian to send an e-mail to the mailing list to initiate discussions regarding graphical design (Arlen already mentioned that Robert from Eurotech could work on a logo&nbsp;; Sierra graphical designer could work on UX&nbsp;; ... )

−

*EclipseCon will be the occasion to discuss when we want to put the site online (e.g. soft launch asap or wait until a more complete chain has been implemented?)

**The list of initial members of the Steering Committee has to be finalized by then

−

**Mike and Scott suggest to send a remainder so as more people can have a chance to look at the charter

−

**Mike reminds that any Eclipse Fdn member meeting the participation requirements is in.

−

**Scott: we're not in a hurry to formally start the WG.

−

**Sierra Wireless, IBM and Eurotech to internally confirm that they want/will be part of the SC.

−

−

== Roadmap ==

−

−

*Programming model

−

**Benjamin: more than programming model, what we certainly want to mention an "application model" (contract between embedded and server: description of data exchanged, communication interfaces, …)

−

**Patrick to have a look and see internally if Band XI would be interested

−

**Benjamin to provide more information regarding this model topic.

−

−

== Face-to-face meeting ==

−

−

*Date of 31st Jan. in IBM Hursley still on

−

−

== Recruitment ==

−

−

*Ian to come back to the handful of interested parties to see what would be their timeframe to join and see how that fits with the tentative launch date of Dec, 8th.

−

−

= 22nd Nov. 2011 =

−

−

== Attendees ==

−

−

*Benjamin Cabé (Sierra Wireless)

−

*Scott DeDeugd (IBM)

−

*Arlen Nipper (Eurotech)

−

*Ian Skerrett (Eclipse Fdn)

−

*Mike Milinkovich (Eclipse Fdn)

−

−

== Agenda ==

−

−

*Review of the first draft of roadmap

−

*Face to face meeting

−

*Recruitment

−

*Mosquitto setup

−

−

== Review of the first draft of the roadmap ==

−

−

*Overview and background

−

**Ian: we should define M2M better in the first section

−

**Ian: is the roadmap only related to Eclipse projects?

−

**Ian: highlight that we want to build an industry consortium

−

*Basic Principles

−

**Arlen: the feedback on MQTT recent announcements is that ppl think that everybody seems to pick his specific protocol and promote it / try to turn it into a standard

−

**Mike &amp; Arlen: we are fine with existing protocols (recent discussion about DNP 3.0 in MQTT google group), we don't aim at replacing them. We want to be above existing protocols.

−

**There are questions still open in this section. Let's keep them as is and put the roadmap draft on the wiki.

−

**Arlen: use cases definition is a difficult task&nbsp;; especially if we have carriers involved (difficult to end up with use cases which are not too generic)

−

*M2M vision, purpose &amp; scope

−

−

''Mike reminds that the charter is not final yet. We are in a 30-day period where the community can give feedback. Even after that period of time, updates to the charter are still possible though.'' ''The M2M Industry Working Group is part of an Open Source Foundation: we are looking at code contributions, not ending up with standards/open standards.''

−

−

**Ian: detail as much as possible where we want to go. What would be the success criteria for Koneki, for Paho

−

**Synchronize the roadmap of individual projects / be sure they are in sync with the global roadmap of the IWG itself.

−

**Mike: if Mosquitto is going to be hosted at Eclipse, it has to be in the scope

−

**Ian: we should have a bottom-up approach --&gt; "Here is what we want to accomplish, do you want to help us?"

−

**Mike: need to have short iterations if possible

−

*Near term direction

−

**Everybody agrees that 12-18 months is a good duration (revision of the roadmap in ~6 months if needed)

−

**Ian: roadmap v1.0 will have to be voted (as well as how to revise it)

−

*Roadmap process:

−

**Mike: say that we solicit feedback from the community, but mentioning that the steering committee will have to vote/approve changes

−

−

== Face-to-face meeting ==

−

−

*suggested date is Jan. 31st, in IBM Hursley

−

*TBC before Christmas.

−

−

== Recruitment ==

−

−

*Members of the IWG discussed about companies that might be interested in joining the IWG (and becoming members of the EF)

−

*Recruiting universities and research institutes would be very valuable: they could run their projects as Eclipse projects…

−

−

== Mosquitto setup at Eclipse ==

−

−

*Ian and Arlen still need to setup a meeting with Eclipse webmasters (user management, ACL, …)

Feb 19, 2013 (proposed agenda)

Starting API Work.

MqGnatt contribution

Feb 12, 2013

There is general consensus that the Continua sequence diagrams can serve as starting point for REST mapping and API work. We will look for means to get that work going in one or more of the projects, on the next call. Axeda's work on the scenarios will factor into this as well.

Arlen is still intending to contribute McGnatt. It could as a "best practices implementation" in combination with some new documentation.

Possible Webinars

It was proposed that a whitepaper and/or webinar on Device Management/Provisioning with respect to the Eclipse work, would be of value. Mats will look further into this.

A security webinar to outline and discuss security solutions in end-to-end M2M application development

An introduction to the Lua MQTT client, and the platforms and applications it is being used on.

Feb 5, 2013

Attendees

Mats Samuelsson, Axeda

Patrick Dempsey, Band XI

Hilary Tomasson, Eurotech

Scott de Deugd, IBM

Continuation: discussion of MQTT related topics raised by Axeda

Scott gave update on OASIS TC. Last date to join the TC is March 18th.

There was some feedback from review of Continua Sequence Diagrams that it looks like useful input to the API work. No next steps were agreed to but we will revisit this again after Phil and Mats have the opportunity to update the Scenarios and Problems.

Discussion of MQTT related topics raised by Axeda but not covered last week.

Lua: Axeda would like to contribute to Lua Client. Scott suggested their project lead call into the bi-weekly Paho calls for an introduction to Andy Gelme.

Best Practices: There still are no volunteers for such a document but Mats said Axeda is interested in taking a lead to get this moving. There was some discussion of integration this with the pending MqGnatt contribution from Cirrus Link so we will discuss again when Arlen can make the cal.

Jan 29, 2013

Attendees

Mats Samuelsson, Axeda

Phil Lombardi, Axeda

Joe Biron, Axeda

Patrick Dempsey, Band XI

Arlen Nipper, Paho

Benjamin Cabé, Sierra Wireless

Scott de Deugd, IBM

Discussion of MQTT related topics raised by Axeda

High level positioning of the MQTT protocol (e.g. "long haul" networks). Scott and Arlen gave a brief overview of the discussion the OASIS C charter which led to describing a number of characteristics of MQTT and network topographies it is designed for. While it is well suited for wireless/constrained networks between an M2M gateway/edge and an enterprise type server, we probably want to avoid precluding its uses there, or in other network topologies. The IWG should pursue this as the topic of a white paper and it will be discussed again around MQTT-s (see note below)

Client ID:

The behavior to disconnect existing clients if a client connects to the broker with the same client ID is not ideal. It would be nice if the protocol specified that the broker should auto-assign an unused client ID. Perhaps this could be an option sent in one of the header fields?

It would be great if the client ID could hold at a minimum a UUID length of characters.

It was not clear that this needs to be part of the MQTT protocol Axeda will work this into a requirement set so that the IWG can understand the problem and work on a recommend solution in the Eclipse projects. Phil will take a look at the existing M2M use cases in the form of Scenarios and Problems, to see if they can be modified to include the situations Axeda anticipates.

MQTT-S: The community needs a public reference implementation of MQTT-S. When we performed our research on MQTT around October of 2012 we were unable to find any public implementations of MQTT-S. I remember seeing that the reason for this is that there are legal issues surrounding the MQTT-S spec somewhere on the MQTT Google Group.

Scott gave an overview of the OASIS Standardization effort and how it is positioned with Paho. Community feedback so far is that MQTT-S is important, yet out of scope of the OASIS Technical Committee. It is withing the scope of Paho and agreed to take this discussion outside the IWG calls to develop a recommendation.