Jump to: navigation, search

Difference between revisions of "IoT/M2MIWG/Weekly call minutes"

< IoT
(M2M Top-level project)
 
(98 intermediate revisions by 8 users not shown)
Line 1: Line 1:
The Machine-to-Machine Industry Working Group is holding weekly calls on Tuesday at 9amET.<br>Participation to these calls is restricted to members of the IWG, but the minutes are public.  
+
{| align="right"
 +
| <googlecalendar title="IoT WG Meeting" mode="AGENDA" height="300" width="100%">u5j68s710reqmr37vd78jdlbm4%40group.calendar.google.com</googlecalendar>
 +
|}
 +
The Internet of Things Industry Working Group is holding bi-weekly calls on Wednesdays, at 12pm ET.<br>
 +
Participation to these calls is restricted to members of the IWG, but the minutes are public. We alternate between marketing-focused calls (upcoming events coordination, community outreach, etc.), and technical calls mostly targeting project leads, to synchronize cross-project activities.
  
The meetings are held via teleconference. The regular call-in numbers are shown below (if possible, please used caller paid numbers). There are a few local / toll-free dial in numbers, but you may want to setup a SIP client on your computer if possible.
+
The meetings are held via teleconference. The regular call-in numbers are shown below (if possible, please used caller paid numbers). There are a few local / toll-free dial in numbers, but you may want to setup a [https://wiki.eclipse.org/Asterisk#SIP SIP client] on your computer if possible.
  
* Ottawa (local call in Ottawa) 1-613-454-1403
+
* North America 1-866-569-4992
* North America (toll free) 1-877-369-7806 (alternative: 1-866-569-4992)
+
* Germany 49-692-2224-6059
* Germany (local call anywhere in Germany) 49-692-2224-6059
+
* France 33-(0)-17-070-8535
* France (local call anywhere in France) 33-17-070-8535
+
* UK 0800-033-7806
* UK (toll free) 0800-033-7806
+
* Switzerland 41-44-580-2115
 +
* Sweden 46-85-063-8386
 +
* Italy 003-902-3604-8268
  
 
Participant conference extension: 713, then enter pin 68764
 
Participant conference extension: 713, then enter pin 68764
Line 13: Line 19:
 
SIP clients can call 713@asterisk.eclipse.org, then enter pin 68764.
 
SIP clients can call 713@asterisk.eclipse.org, then enter pin 68764.
  
= July 16, 2013 =
+
----------------------------------------
  
== Agenda ==
+
= Feb 1, 2017 (WG Call)=
 
+
* M2M top level project
+
** See [[Machine-to-Machine/M2MIWG/TLP_Charter_Draft]]
+
* Marketing / Events
+
** Momentum press release
+
** EclipseCon Europe
+
* Greenhouse demo
+
 
+
== Attendees ==
+
 
+
* Mats Samuelsson
+
* Ian Skerrett
+
* Benjamin Cabé
+
* Marco Carrer
+
* Andy Piper
+
 
+
== M2M Top-level project ==
+
 
+
* Next step is to get the scope and the charter to a point where people are comfortable with it
+
* Ian: in terms of naming, it would be bad to sacrifice the "M2M" in favor of "IoT"
+
* Projects will have to agree on moving
+
** Paho didn't discuss the move yet. Andy P said there's no reason Paho wouldn't move to where other M2M projects are
+
** Benjamin: Mihini would move, Koneki will do a restructuring review prior to the move (Lua Development Tools graduated with Kepler, and may stay in Technology TLP)
+
* Mats: Oracle is IoT, Axeda is M2M… Maybe we M2M/IoT would be better.
+
* Marco: we spent a lot of time marketing M2M, so Eclipse M2M is a good brand name
+
 
+
== Marketing / Events ==
+
 
+
* Momentum press release
+
** Ian: great stuff happened in the last couple months.
+
** Ian drafted a PR that got sent to several community leads and companies so as they can validate the content that is relevant to them
+
** We can do another PR in the fall, maybe around EclipseCon Europe
+
 
+
* EclipseCon Europe
+
** CfP runs until July 31st
+
** AndyP will have a look
+
** Mats will try to submit a talk too
+
 
+
** Tutorial
+
*** Andy will post on the Paho mailing list to see if there is interest in running an M2M tutorial
+
*** Marco: maybe showing MQTT, OSGi, ...
+
 
+
* Upcoming conferences
+
** AndyP submitted a talk about M2M/Paho at JAX London (end of Oct)
+
** Benjamin submitted a talk for DroidCon London (end of Oct)
+
 
+
* Webinars
+
** Paho news?
+
** Protocols in general
+
** Ponte
+
** Eclipse SCADA
+
 
+
== Greenhouse demo ==
+
 
+
* Demo is live since last week
+
* A few ppl are already extending it!
+
** Google Glass app
+
** JavaFX app
+
* Developer kit
+
** We should work on making it simple to order the devkit, maybe by improving the bill of materials, instructions, etc.
+
* Would be interesting to work on another greenhouse talking MQTT
+
* Ian: we could have an "interoperability hackathon"
+
 
+
= July 2, 2013 =
+
 
+
== Agenda ==
+
 
+
* Presentation of the Eclipse SCADA [1] project proposal (by Jens Reimann and Jürgen Rose)
+
** See slides here: http://www.slideshare.net/JrgenRose/open-scada-quickoverviewv1
+
* M2M top level project
+
** See [[Machine-to-Machine/M2MIWG/TLP_Charter_Draft]]
+
* Momentum press release
+
* Greenhouse demo
+
 
+
== Eclipse SCADA ==
+
 
+
*  Scada is monitoring and control tool for computer systems
+
 
+
* More human to machine than machine-to-machine
+
* Rely on existing hardware for interfacting
+
** Sensors are embedded in dataloggers, PLC, low-level control systems, … and they provide the data to higher level systems
+
** Open SCADA has "drivers" to convert existing protocols into "internal" protocol
+
* Master server based on OSGi/Equinox
+
* Pipeline to process data: round, scale, override, … that eventually reaches an User Interface
+
* Open SCADA not interested in doing the embedded part, rather interfacing with embedded systems
+
* Jürgen experimented with MQTT in order to create a driver for OpenSCADA.
+
* Master server is an OSGi (Equinox) application that dynamically be configured at runtime
+
* Several drivers available (not all them are "open-sourcable"): OPC, Modbus, Shell exec, …
+
* Configuration
+
* User Interface: GEF and Draw2D based. Allows to create a dashboard with e.g vector graphics
+
* Graphical widgets can be configured in XML
+
* Timeline:
+
** One mentor is identified, still need an extra one.
+
** Release 1.2 of OpenSCADA is in progress
+
*** removing some dependencies
+
*** relicensing under EPL
+
** Contribution expected in 1 to 2 months.
+
** By the end of the year there should be a first release available at Eclipse
+
** All sub-projects (Aurora, Atlantis, etc.) are in separate repositories
+
** Driver modules could be extracted
+
 
+
== Top-level project ==
+
 
+
* Marco: should we have the discussions on the ML or the wiki?
+
* Benjamin:
+
** do we want the TLP to stay very horizontal, or also include vertical solutions
+
** it's important to clarify what deliverable are expected from the "Protocols" projects: one project per protocol and/or per language? what about wrappings/drivers for other frameworks?
+
 
+
== Momentum press release ==
+
 
+
* Deferred since Ian is on holiday
+
 
+
= June 18, 2013 =
+
 
+
== Agenda ==
+
 
+
* Presentation of the Concierge project proposal (by Jan S. Rellermeyer)
+
* Marketing update / Past and upcoming events
+
* Creation of an Eclipse top-level project for Machine-to-Machine
+
* Greenhouse demo
+
  
 
== Participants ==
 
== Participants ==
  
* Jan Relermeyer
+
*Dan Gross, Samsung
* Benjamin Cabé
+
*James Sutton, IBM
* Hilary Tomasson
+
*David Bericat, Red Hat
* Marco Carrer
+
*Laurent Lagosanto, MicroEJ
* Peter Niblett
+
*Roxanne Joncas, Eclipse Foundation
* Ian Skerrett
+
*Benjamin Cabé, Eclipse Foundation
* Regrets: Mats Samuelsson
+
*Brad Micklea, Codenvy
 
+
== Concierge project presentation ==
+
 
+
* Concierge is a project started in 2006 as part of Jan's PhD
+
* Goal is to provide an OSGi implementation with the smallest footprint
+
** targeting mobile and embedded
+
* OSGi R3 core implementation
+
** 86 kB of footprint
+
* The code is meant to be readable
+
* As part of the move to Eclipse, one of the goals is to reach OSGi R5 compliance
+
** biggest challenge is generics ; it's hard to optimize things such as package dependencies
+
* Target is ~300KB for the JAR footprint, and ability to run on Java 1.4 (JSR14)
+
* Roadmap
+
** Code submitted for IP review in July
+
** Compliance to the R5 TCK is gonna be addressed over the next couple months
+
** Compatibility with Android
+
* Other services from the compendium may be added
+
* Project will be dual-licensed under EPL and EDL (BSD-like)
+
* EventAdmin and HTTPService are part of the original Concierge project
+
* Help is welcomed for topics such as the implementation of new Compendium services.
+
 
+
== Marketing update / Past and upcoming events ==
+
 
+
* EclipseCon France 2013
+
** Good M2M content
+
** Interesting presentations around M2M/embedded ; eTrice, 4DIAC,
+
* Upcoming
+
** Las Vegas.
+
*** M2M World Congress, September, Nice France
+
*** Benjamin and Ian to talk
+
** Eclipse Foundation will have a demo table
+
* JavaOne, San Francisco
+
* EclipseCon Europe, October, Germany
+
** Would be great to have a full track of M2M content :)
+
* Devoxx, Antwerp, Belgium
+
** Eclipse Foundation will have a booth
+
*** Tutorial?
+
** Peter Niblett may be interested to participate
+
** Bi-weekly calls will be used to discuss the opportunity to do a joint workshop
+
* Open Hardware Summit, September, Boston - MIT
+
* Press release - mid/end of July
+
** "Momentum" press release: new project proposals, existing releases, commercial announcements, …
+
* New project proposal: openSCADA.
+
 
+
== Creation of M2M top-level project ==
+
 
+
* A top-level project is how projects are grouped under a specific technology domain
+
* Top-level project have PMC (Project Management Committees) that take care of IP, approval of new committers, of new projects, dependencies, …
+
* Technology is the catch-all top-level project, but projects are encouraged to migrate to other top-level projects when they are ready and/or mature enough
+
* There are now enough projects that would fit under an M2M umbrella
+
* Next steps:
+
** Define a scope. Ian suggests to use M2M IWG scope as a basis
+
** Draft a charter
+
** A TLP needs to be approved by the Board of Directors
+
 
+
== Greenhouse demo ==
+
 
+
* Benjamin is looking for feedback on http://wiki.eclipse.org/Machine-to-Machine/M2MIWG/Demonstrator
+
 
+
 
+
 
+
= May 21, 2013 =
+
  
 
== Agenda ==
 
== Agenda ==
 +
=== Eclipse IoT Testbeds: review strategy and next steps. ===
 +
Work on a set of industry oriented (vertical solutions) to showcase a technical solution and showcase the Eclipse projects and vendor ecosystem.
 +
Eclipse IoT Members working together to set-up the testbed and create a demo that runs 24/7 on the Eclipse servers
 +
More details: https://docs.google.com/presentation/d/1nmdi-cmw_O-7W2qZKRHMN-3gw0WHxE75llcV0nMhS-U/edit?usp=sharing
 +
Proposed Testbed scenario around Asset Tracking Management: https://docs.google.com/presentation/d/1KF7yxv5Dnk6b2a574HPtU5pHR5q7wvsT4skKjGDz1Q4/edit?usp=sharing
 +
There are many options for collaboration
  
* Project updates
+
*Dan Gross: Samsung interested in participating - Kura gateway using ARTIK.
** Koneki
+
*Laurent Lagosanto: Potential use case for Eclipse Edje.
** Mihini
+
*David Bericat: Excited and look forward to working with everyone.
** Paho
+
* New project proposal: Eclipse Ponte
+
** Scope
+
** First feedbacks
+
* m2m.eclipse.org permanent demo
+
* EclipseCon France meeting
+
  
== Participants ==
+
'''Next Steps''': Stay tuned, we will be updating the group at large and scheduling individual meetings.
  
* Benjamin Cabé
+
=== 2. MQTT 5: Update from Ian Craggs / James Sutton on what’s in MQTT 5 and the expected impact on Eclipse Paho / Mosquitto and downstream adopters. ===
* Cuero Bugot
+
'''Big set of changes:'''
* Thomas Schuetz
+
*Use of the publish/subscribe message pattern which provides one-to-many message distribution and decoupling of applications.
* Ian Skerrett
+
*A messaging transport that is agnostic to the content of the payload.
* Matteo Collina
+
*Three qualities of service for message delivery:
* Marco Carrer
+
**At most once", where messages are delivered according to the best efforts of the operating environment. Message loss can occur. This level could be used, for example, with ambient sensor data where it does not matter if an individual reading is lost as the next one will be published soon after.
* Hilary Tomasson
+
**At least once", where messages are assured to arrive but duplicates can occur.
* Andy Piper
+
**"Exactly once", where messages are assured to arrive exactly once. This level could be used, for example, with billing systems where duplicate or lost messages could lead to incorrect charges being applied.
* Peter Niblett
+
*A small transport overhead and protocol exchanges minimized to reduce network traffic.
 +
*A mechanism to notify interested parties when an abnormal disconnection occurs.
 +
 +
'''Notes from the meeting:'''
 +
*Any request sent (and reply received) can have embedded metadata. This will be used for e.g letting a publisher know about *what* happened to the packet in addition to just acknowledging it
 +
**The CONNECT packet can contain information regarding what QoS are supported by the server
 +
**Supporting QoS 2 on the server is not mandatory anymore
 +
**Scalability
 +
*It will affect the Paho client and so a new Paho client will be created.
 +
**Improve API
 +
**Feedback from community
 +
**Work nicely with the new MQTT 5 features
 +
*The complete move will take a while, MQTT 3 will not go away anytime soon. It will be a parallel process. The previous versions of the client will be maintained. Some users might choose to use MQTT 3 since it’s more lightweight.
  
== Project updates ==
+
'''IMPORTANT:''' Get your feedback in as soon as possible, because in a few months it will be finalized, so review the specifications. View working draft 10 dated January 4: https://www.oasis-open.org/committees/documents.php?num_per_wg=10&wg_abbrev=mqtt
  
=== Koneki ===
+
=== 3. PMC topics: project documentation, build machines, Docker, … ===
 +
Skipped this item - not enough PMC members on the call
  
* Polishing 1.0 release
+
=== 4. Misc. updates ===
* Started to work on new tooling for Mihini for building application packages from the IDE
+
*WG Meeting at the Eclipse IoT Day San Jose Add your project for project update or intro: https://wiki.eclipse.org/EclipseIoT_SanJose2017
 +
*IoT Developer Survey Test it and give us feedback! It will go live next week. https://www.surveymonkey.net/r/Preview/?sm=PpPJLkX2kyFIkd4FpbfnijKgtSau8CTbzClUcIqMOv8UHpkGU6kxWrpBNJfYHpzC
 +
*Member companies are encouraged to ask for a special link that they can use to promote the survey to their communities, and have access to answers based on this segment.
 +
Open IoT Challenge: we will schedule a live hangout for project leads to answer any technical questions the participant may have. https://iot.eclipse.org/open-iot-challenge/
  
=== Mihini ===
 
  
* Small bug fixes
 
* Documentation
 
* Re-implementing security for being IP clean
 
  
=== Paho ===
 
 
* Working towards a 0.5 release
 
** Java and C clients (other clients are not as mature)
 
** Mavenizing the Java client
 
* Javascript client contributed by IBM
 
** New Python binding from Roger.
 
* Discussion about other protocols (CoAP, M3DA) addition to Paho
 
** Current focus is releasing Paho 0.5 with MQTT clients, and see later for new protocols
 
* Target date is May 31
 
 
== Eclipse Ponte ==
 
 
* Ponte project goal is to empower the M2M developers
 
** ease the development of normal and web applications
 
* There will be different protocols anyway
 
* Another goal is addressing the data format
 
** Most of existing data formats can be converted with each other
 
* Security
 
** OAuth
 
 
* First feedback received from Toby Jaffrey
 
 
* Presentation about QEST/Ponte at EclipseCon France
 
* Everything in Ponte to JSON if possible
 
* Protobuf, MsgPack, Bysant are targeted as reprensatation format
 
 
* Andy P is an interested party
 
** Ponte could be a good opportunity to have an even better JS story in Paho (mqtt-js)
 
 
* Ponte has Coffeescript code that will be reworked to be pure JS
 
 
== m2m.eclipse.org demonstrator ==
 
 
* Matteo suggests to create a Twitter bot using Hubot
 
* Benjamin: on the demo page we could feature "Other cool projects connected to this demo" and "Commercial solutions"
 
* Ian: This demo should really be about promoting interoperability
 
* Benjamin will add the documentation of the REST API for interacting with the demo on github
 
 
== EclipseCon France meeting ==
 
 
* F2F meeting for the 4th of June is cancelled because many participants would have been on the phone anyway
 
 
= May 7, 2013 =
 
 
== Agenda ==
 
 
* Project updates
 
** Koneki
 
** Mihini
 
** Paho
 
* m2m.eclipse.org permanent demo update
 
* Eclipsecon France meeting agenda
 
 
== Participants ==
 
 
* Benjamin Cabé, Sierra Wireless
 
* Didier Lahay, Sierra Wireless
 
* Cuero Bugot, Sierra Wireless
 
* Hillary Tomasson, Eurotech
 
 
== Project updates ==
 
 
=== Koneki ===
 
 
* 1.0 RC1 released last week
 
* On track for 1.0 final with Kepler
 
 
=== Mihini ===
 
 
* Need to work on replacing security libraries that are not approved (IP) for use at eclipse.org
 
 
=== Paho ===
 
 
* No one from Paho on the call.
 
* Benjamin indicates that there were new clients contributions done in the last couple weeks: Python, Javascript, ...
 
 
== Eclipse M2M technologies permanent demo ==
 
 
* Benjamin to create a Wiki page to document this demo and list the goals, conditions to participate...
 
 
== Face-to-Face meeting - June, 4 ==
 
 
* The tentative agenda is [[[http://wiki.eclipse.org/Machine-to-Machine/Face-2-Face-Meeting-June4-2013#Agenda here]]]
 
* People are invited to register by adding their name to the Wiki page.
 
* Hillary to check with Marco if there are items that Eurotech would like to add to the agenda
 
 
= Apr 23, 2013 =
 
 
== Agenda ==
 
 
* Project updates
 
** Koneki
 
** Mihini
 
** Paho
 
* m2m.eclipse.org permanent demo
 
* Eclipsecon France meeting
 
* Upcoming events
 
 
== Participants ==
 
 
* Peter Niblett
 
* Benjamin Cabé
 
* Ian Skerrett
 
* Laurent Barthélémy
 
* Cuero Bugot
 
* Thomas Schuetz
 
* Mats Samuelsson
 
* Hilary Thomasson
 
* Marco Carrer
 
 
== eTrice introduction ==
 
 
* Thomas, project lead of Eclipse eTrice
 
* The focus of eTrice is to provide toolset for modeling and code generation for embedded systems
 
* Based on ROOM language, a DSL from telecom industry, that can also be used for machine control
 
* Interest in finding new applications, what would be useful for ppl in the M2M area to use eTrice as a tool
 
* Automotive and machine controls
 
* Lots of people interested in using eTrice for various domains: banking, Machine-to-Machine
 
* eTrice is good at programming distributing applications
 
 
== Project updates ==
 
 
=== Paho update ===
 
 
* Java: creation of a 0.2 release candidate, update of the Eclipse view
 
* Bug triaging
 
* New Python MQTT client contributed
 
* Objective-C still under IP review
 
* JS client pending
 
 
=== Koneki update ===
 
 
* 1.0 M1 released last week: adds support for Lua 5.2, LuaJIT
 
* New and Noteworthy available [[http://wiki.eclipse.org/Koneki/LDT/User_Area/New_Noteworthies/New_Noteworthy_1.0|here]]
 
 
=== Mihini update ===
 
 
* Problems with the IP of some libraries (security)
 
* Adding GPIO APIs
 
 
== m2m.eclipse.org permanent demo ==
 
 
* Sierra team working on setting up hardware and web UI for a 24/7 greenhouse demo
 
* Same greenhouse should be usable for any server-side platform
 
* Axeda interested in having the demo compatible with its platform
 
* Thomas: eTrice could be used for simulating the system control, visualizing the changing data
 
 
== EclipseCon France ==
 
 
* Meeting of the IWG the day before, June 4th
 
 
== Upcoming Events ==
 
 
* M2M World Congress: Ian and Benjamin to speak. Should Eclipse and partner have a booth
 
* Ian, Mike Milinkovich and Peter will talk in Atlanta, on May 7th, about OASIS MQTT initiative, M2M...
 
 
== Kepler democamps ==
 
 
* June: democamp and hackathons all around the world
 
* Would be great to have people volunteering for demoing Eclipse M2M technologies :)
 
 
= Apr 9, 2013 =
 
 
== Agenda ==
 
 
* Partners Recruitment* Webinars
 
* EclipseCon France (CFP, IWG meetings)
 
* Weekly calls format
 
 
== Attendees  ==
 
* Ian Skerrett, Eclipse Fdn
 
* Benjamin Cabé, Sierra Wireless,
 
* Didier Lahay, Sierra Wireless,
 
* Hilary Tomasson, Eurotech
 
* Peter Niblett, IBM
 
* Andy Piper, CloudFoundry
 
 
 
== Partners recruitment ==
 
 
* End-to-end demo. Need to communicate about it
 
* #iot on twitter
 
* Telefonica has just launched a cloud? m2m-telefonica
 
* Andy reached out to them on Twitter
 
 
* Add to the Eclipse portal
 
* Greenhouse is nice to show at events but maybe not really exciting from an industry perspective (oil, power plant, … could be more appropriate)
 
* Companies should be able to take the embedded gateway source code and connect it to their cloud
 
 
== Events to target in Q3 ==
 
 
* M2M World Congress in Nice - end september
 
** they are still looking for content
 
* 3-5000EUR to share a booth
 
* JavaOne
 
** same week at M2M World Congress
 
** Ian to send more details
 
* Connected World - June
 
** Eurotech is attending
 
* M2M Evolution - part of the ITExpo (US) - end of August
 
** Eurotech is attending
 
* M2M Summit - Dusseldorf - early october
 
 
* One M2M
 
* JAX
 
 
== Webinars ==
 
 
* Mihini
 
* M3DA
 
* Paho/MQTT: Hilary to check if Eurotech could do another webinar
 
 
 
 
== F2F meeting at EclipseCon France ==
 
 
* 4th of June in the afternoon
 
 
 
== Meeting are now moved to bi-weekly ==
 
 
* Benjamin will send an updated invitation
 
 
= Apr 2, 2013 =
 
 
== Agenda ==
 
 
* EclipseCon feedback (M2M sessions, F2F meeting)
 
* M3DA/MQTT convergence
 
* EclipseCon France
 
 
== Attendees  ==
 
*Hilary Tomasson, Eurotech
 
*Benjamin Cabé, Sierra Wireless
 
 
== Misc. ==
 
 
Call was very short since most people didn't show up (Easter holiday)
 
Benjamin reminded Hilary that EclipseCon France call for papers is running until the 15th and that it would be interesting to get more M2M content submitted.
 
 
<br>
 
 
= Feb 19, 2013 (proposed agenda)=
 
* Starting API Work.
 
* MqGnatt contribution
 
 
<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>
 
 
= 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 =
 
== 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 [http://wiki.eclipse.org/Machine-to-Machine/M2MIWG/M2M_Scenarios 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.
 
*The remaining topics brought up were deferred to a future call.
 
<br>
 
 
----------------------------------------
 
----------------------------------------
  
 
= Archives =
 
= Archives =
== 2012 ==
 
 
[[Machine-to-Machine/M2MIWG/Weekly call minutes/2012 Archives]]
 
 
== 2011 ==
 
  
[[Machine-to-Machine/M2MIWG/Weekly call minutes/2011 Archives]]
+
* [[IoT/M2MIWG/Weekly call minutes/2016 Archives]]
 +
* [[IoT/M2MIWG/Weekly call minutes/2015 Archives]]
 +
* [[IoT/M2MIWG/Weekly call minutes/2014 Archives]]
 +
* [[IoT/M2MIWG/Weekly call minutes/2013 Archives]]
 +
* [[IoT/M2MIWG/Weekly call minutes/2012 Archives]]
 +
* [[IoT/M2MIWG/Weekly call minutes/2011 Archives]]

Latest revision as of 09:49, 2 February 2017

The Internet of Things Industry Working Group is holding bi-weekly calls on Wednesdays, at 12pm ET.
Participation to these calls is restricted to members of the IWG, but the minutes are public. We alternate between marketing-focused calls (upcoming events coordination, community outreach, etc.), and technical calls mostly targeting project leads, to synchronize cross-project activities.

The meetings are held via teleconference. The regular call-in numbers are shown below (if possible, please used caller paid numbers). There are a few local / toll-free dial in numbers, but you may want to setup a SIP client on your computer if possible.

  • North America 1-866-569-4992
  • Germany 49-692-2224-6059
  • France 33-(0)-17-070-8535
  • UK 0800-033-7806
  • Switzerland 41-44-580-2115
  • Sweden 46-85-063-8386
  • Italy 003-902-3604-8268

Participant conference extension: 713, then enter pin 68764

SIP clients can call 713@asterisk.eclipse.org, then enter pin 68764.


Feb 1, 2017 (WG Call)

Participants

  • Dan Gross, Samsung
  • James Sutton, IBM
  • David Bericat, Red Hat
  • Laurent Lagosanto, MicroEJ
  • Roxanne Joncas, Eclipse Foundation
  • Benjamin Cabé, Eclipse Foundation
  • Brad Micklea, Codenvy

Agenda

Eclipse IoT Testbeds: review strategy and next steps.

Work on a set of industry oriented (vertical solutions) to showcase a technical solution and showcase the Eclipse projects and vendor ecosystem. Eclipse IoT Members working together to set-up the testbed and create a demo that runs 24/7 on the Eclipse servers More details: https://docs.google.com/presentation/d/1nmdi-cmw_O-7W2qZKRHMN-3gw0WHxE75llcV0nMhS-U/edit?usp=sharing Proposed Testbed scenario around Asset Tracking Management: https://docs.google.com/presentation/d/1KF7yxv5Dnk6b2a574HPtU5pHR5q7wvsT4skKjGDz1Q4/edit?usp=sharing There are many options for collaboration

  • Dan Gross: Samsung interested in participating - Kura gateway using ARTIK.
  • Laurent Lagosanto: Potential use case for Eclipse Edje.
  • David Bericat: Excited and look forward to working with everyone.

Next Steps: Stay tuned, we will be updating the group at large and scheduling individual meetings.

2. MQTT 5: Update from Ian Craggs / James Sutton on what’s in MQTT 5 and the expected impact on Eclipse Paho / Mosquitto and downstream adopters.

Big set of changes:

  • Use of the publish/subscribe message pattern which provides one-to-many message distribution and decoupling of applications.
  • A messaging transport that is agnostic to the content of the payload.
  • Three qualities of service for message delivery:
    • At most once", where messages are delivered according to the best efforts of the operating environment. Message loss can occur. This level could be used, for example, with ambient sensor data where it does not matter if an individual reading is lost as the next one will be published soon after.
    • At least once", where messages are assured to arrive but duplicates can occur.
    • "Exactly once", where messages are assured to arrive exactly once. This level could be used, for example, with billing systems where duplicate or lost messages could lead to incorrect charges being applied.
  • A small transport overhead and protocol exchanges minimized to reduce network traffic.
  • A mechanism to notify interested parties when an abnormal disconnection occurs.

Notes from the meeting:

  • Any request sent (and reply received) can have embedded metadata. This will be used for e.g letting a publisher know about *what* happened to the packet in addition to just acknowledging it
    • The CONNECT packet can contain information regarding what QoS are supported by the server
    • Supporting QoS 2 on the server is not mandatory anymore
    • Scalability
  • It will affect the Paho client and so a new Paho client will be created.
    • Improve API
    • Feedback from community
    • Work nicely with the new MQTT 5 features
  • The complete move will take a while, MQTT 3 will not go away anytime soon. It will be a parallel process. The previous versions of the client will be maintained. Some users might choose to use MQTT 3 since it’s more lightweight.

IMPORTANT: Get your feedback in as soon as possible, because in a few months it will be finalized, so review the specifications. View working draft 10 dated January 4: https://www.oasis-open.org/committees/documents.php?num_per_wg=10&wg_abbrev=mqtt

3. PMC topics: project documentation, build machines, Docker, …

Skipped this item - not enough PMC members on the call

4. Misc. updates

Open IoT Challenge: we will schedule a live hangout for project leads to answer any technical questions the participant may have. https://iot.eclipse.org/open-iot-challenge/



Archives