This a [http://wiki.eclipse.org/images/6/6f/M2MIWG_-_March_2012_DRAFT.zip draft presentation] for the March 29th Face-to-Face meeting. Please send any changes or additions you would like to include to Scott de Deugd.

+

This is the [http://wiki.eclipse.org/images/6/6f/M2MIWG_-_March_2012_DRAFT.zip presentation] used at the March 29th Face-to-Face meeting.

<br>

<br>

Line 68:

Line 68:

#Ian Skerrett, Eclipse Foundation

#Ian Skerrett, Eclipse Foundation

−

#Benjamin Cabé, Sierra Wireless

+

#Benjamin Cabé, Sierra Wireless

#Gaétan Morice, Sierra Wireless

#Gaétan Morice, Sierra Wireless

#Kevin Lloyd, Sierra Wireless

#Kevin Lloyd, Sierra Wireless

Line 74:

Line 74:

#James Branigan, Band XI International

#James Branigan, Band XI International

#Patrick Dempsey, Band XI International

#Patrick Dempsey, Band XI International

−

#Andy Piper, VMware, mqtt.org

+

#Andy Piper, mqtt.org

#Marco Carrer, Eurotech

#Marco Carrer, Eurotech

#Hilary Tomasson, Eurotech

#Hilary Tomasson, Eurotech

Line 80:

Line 80:

#Pat Huff, IBM

#Pat Huff, IBM

−

Here are links to [http://wiki.eclipse.org/Machine-to-Machine/Face-2-Face-Meeting-Mar29 Agenda and the] [http://wiki.eclipse.org/images/6/6f/M2MIWG_-_March_2012_DRAFT.zip draft presentation] for the March 29th Face-to-Face meeting.

+

Here are links to [http://wiki.eclipse.org/Machine-to-Machine/Face-2-Face-Meeting-Mar29 Agenda] and the [http://wiki.eclipse.org/images/6/6f/M2MIWG_-_March_2012_DRAFT.zip draft presentation] for the March 29th Face-to-Face meeting.

<br>

<br>

Line 105:

Line 105:

***Koneki is targeted for inclusion in Juno release.

***Koneki is targeted for inclusion in Juno release.

***Koneki demonstration provided by Benjamin including work in progress for next release

***Koneki demonstration provided by Benjamin including work in progress for next release

−

***((Benjamin, there was a discussion about device management and Funambol. I did not get the details could you please add here if you captured it))

+

***Benjamin indicates that the OMA-DM simulation user guide includes a tutorial on how to setup a Funambol OMA-DM Server on a linux distribution in order to connect the simulator to.

***Koneki bandwidth estimator was demonstrated and there was a discussion about how it is being extended for MQTT.

***Koneki bandwidth estimator was demonstrated and there was a discussion about how it is being extended for MQTT.

***Device Simulator was demonstrated. A goal of Koneki is to ensure that it will work with any protocol. There was a brief discussion about the challenges in doing this with MQTT as one example.

***Device Simulator was demonstrated. A goal of Koneki is to ensure that it will work with any protocol. There was a brief discussion about the challenges in doing this with MQTT as one example.

Line 119:

Line 119:

**Ian will outline a communication plan centered around a coordinated Q3 release/availability. Pat Huff will work with Ian on opportunities to integrate this with IBM Eclipse communications. Ian has previous PR contacts involved in November announcements.

**Ian will outline a communication plan centered around a coordinated Q3 release/availability. Pat Huff will work with Ian on opportunities to integrate this with IBM Eclipse communications. Ian has previous PR contacts involved in November announcements.

**One goal of plans and communication should be to reach out to telco and providers of M2M/IoT platforms.

**One goal of plans and communication should be to reach out to telco and providers of M2M/IoT platforms.

−

**Line up with discussion, interest and feedback from drumbeat in technology blogs and social media.

+

**Commincations should line up with discussion, interest and feedback from drumbeat in technology blogs and social media.

**Invitation to members to create an M2M thread/theme at 2012 Eclipse Demo Camps. All are invited to sponsor one near them. e.g. IBM (London), Eurotech (Boston)and Sierra Wireless (San Francisco). Ian is the contact for this.

**Invitation to members to create an M2M thread/theme at 2012 Eclipse Demo Camps. All are invited to sponsor one near them. e.g. IBM (London), Eurotech (Boston)and Sierra Wireless (San Francisco). Ian is the contact for this.

There was a discussion about communicating the vision, high level architecture and target solutions/markets of the Working Group. While there seems to be a consensus on this from the initial IWG members, it also is important to formalize this and to document the vision for broader feedback and participation. Agreement was that this could best be started by creating an initial draft of and M2M/IoT Marchitecture presentation, and that a vision statement should fallout in parallel while doing that work. Benjamin Cabé and Hilary Tomasson agreed to create a draft Marchitecture proposal for review.

Scenarios: There was general agreement on current format and level of the Scenarios and Problems proposed on the M2M IWG Wiki. Some next steps were suggested in order to scope the work and to ensure it serves well as input to the initial M2M IWG Architecture:

Benjamin suggested that the Scenarios and Problems need to follow a consistent Wiki template and offered to create one.

Scope: The Scenario work should initially be scoped to focus on requirements at “bridging”, or boundaries between the physical world systems (e.g. via gateways, controllers, devices) and the Enterprise, IT and Web systems (e.g. via M2M, monitoring servers). Another suggestion was to focus on requirements and scenarios that are representative of existing problems and inhibitors commonly encountered today, and to avoid “inventing”. Scott agreed to add this scoping to Scenario section of the Wiki.

The Q2 objective for the IWG is to start adding scenarios and related problems. Interested authors are encouraged to first float the general scenario on the mailing list to get some feedback on how well they fit into the initial scoping and objectives. James and Scott had some scenarios in mind and it was also mentioned that Arlen Nipper was interested in submitting scenarios representative of industry examples he has encountered.

A brief discussion pointed out that some scenarios will likely reflect constraints of the sensors and sensor networks because, even though Enterprise and Web developers are not programming directly to those interfaces, the nature of the networks and methods to read and control devices will “show through”. As a side note here, a request was made to add MQTT-s support as a Paho consideration.

It was generally agreed that, independent of the scenario work, that there are existing protocols that need to be described and positioned within the IWG and Project requirements. Although Arlen Nipper was not present, Scott noted that Arlen was working on a white paper survey of key protocols for M2M and IoT. A request was made that HTTP2 be included in this.

A point was raised that it may become important to also include payload specifications in the protocols. It was also pointed out that there is value in maintaining transport protocols that are payload agonistic given all of the variables and constraints inherent to M2M devices and networks. There was general agreement that these requirements should be driven by a scenario that can address the need for payload specifications, without binding M2M and IoT applications unnecessarily to the device specifics.

A scenario is needed to identify requirements for some level of discovery, which takes into account the constraints inherent to M2M and IoT.

Eurotech and Sierra Wireless agreed to identify a tool developer’s level scenario to that can help identify a framework that would support multiple device simulators. The initial pass should be to identify the “layers” needed.

M2M Sandbox and Hackerplace

The Mosquitto server is up, running, and being used with test applications. There was a request for some basic documentation on how to get started and also some documentation on how to find what is already set up and running there.

There was an observation that the M2M IWG should better describe/position “Hackerplace”, “Sandbox” and upcoming “Developer Portal”. It was recommended that “Hackerplace” become a single point for support in using and testing the M2M Eclipse components/projects. Initially, Hackerplace will be composed of the Sandbox server runtime, and the Developer portal entry-point to get started installing, using and configuring the components.

Wes and Benjamin agreed to define an end-to-end use case that will serve as the “getting started” example.

It was suggested that IWG look further to see how the Eclipse Packaging Project (EPP) could be used to pull together all of the Koneki, Paho, frameworks, and, sample/example components to create an entry level download into the Eclipse IDE.

Project Updates and Status

Koneki

Koneki is targeted for inclusion in Juno release.

Koneki demonstration provided by Benjamin including work in progress for next release

Benjamin indicates that the OMA-DM simulation user guide includes a tutorial on how to setup a Funambol OMA-DM Server on a linux distribution in order to connect the simulator to.

Koneki bandwidth estimator was demonstrated and there was a discussion about how it is being extended for MQTT.

Device Simulator was demonstrated. A goal of Koneki is to ensure that it will work with any protocol. There was a brief discussion about the challenges in doing this with MQTT as one example.

Paho

Committers are requested to use Mailing List and Bugzilla to generate and followup on interest.

Andy Piper updated the group on interest from Andy Gelme to contribute Lua MQTT client. Scott and Ian will follow-up.

Andy Piper and Arlen Nipper have requested we get process moving so they can contribute to project code.

Eurotech has goal to make initial commit of Client View Tool by end of April. As new committer, Wes and Marco are interested in better understanding the extent work they should expectin the project. Ian offered to follow-up with them.

Paho deliverables boca/arrow chart needs updating and to reflect coming contributions and the Project page should have Plan section.

Open M2M Promotion

Andy Piper feels he can keep a level of technical drumbeat going. IWG should work on more participation and coordination.

Rough target of Q3 release/availability that contains significant “new news” since the November press releases. E.g. New levels of Koneki function and integration, Paho availability, end-to-end use case in Hackerplace, Eclipse IDE integration.

Ian will outline a communication plan centered around a coordinated Q3 release/availability. Pat Huff will work with Ian on opportunities to integrate this with IBM Eclipse communications. Ian has previous PR contacts involved in November announcements.

One goal of plans and communication should be to reach out to telco and providers of M2M/IoT platforms.

Commincations should line up with discussion, interest and feedback from drumbeat in technology blogs and social media.

Invitation to members to create an M2M thread/theme at 2012 Eclipse Demo Camps. All are invited to sponsor one near them. e.g. IBM (London), Eurotech (Boston)and Sierra Wireless (San Francisco). Ian is the contact for this.