Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

IoT/M2MIWG/Weekly call minutes/2017

< IoT‎ | M2MIWG/Weekly call minutes
Revision as of 09:52, 2 February 2017 by Roxanne.joncas.eclipse.org (Talk | contribs) (4. Misc. updates:)

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 Share description 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. The adopters/compagnies

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/

Back to the top