Skip to content
Kai Beckmann edited this page Jul 22, 2017 · 17 revisions

Topics

  • C++14 / 17 header support in RIOT

    • support of C++ Timer API
    • [energy]
  • IDE extensions (e.g. Atom, VIM)

    • scaffolding for creating new RIOT projects
    • auto completion
    • easy way to access documentation
    • [n/a]
  • Security related topics

    • HowTos on how to use security related modules in RIOT (DTLS, TweetNaCl, ...)
      • more documentation
      • create tutorials
      • provide example code
    • Testing of vulnerabilities?
  • Bootloader and OTA updates

  • BLE

  • CoAP: implement more features in RIOT

    • resource directory (RD)
    • RD discovery
    • HTTP <-> CoAP proxy
    • more content formats (xml,...)
    • fragmentation (blockwise transfers in CoAP)
    • [performance comparison ICN]
  • 6TSCH (and ICNTSCH)

    • native TSCH implementation in RIOT OR provide a port of OpenWSN to RIOT
    • [link layer optimization]
  • Energy measurements

    • beforehand:
      • find a default measurement tool
    • hackathon:
      • implement low power modes for different MCUs
      • identify problems with developement hardware (e.g., current leaks)
      • identify problems with current peripheral driver implementations (e.g., initialized but unused peripherals)
      • identify conceptual challenges with the energy management system (e.g., timer concept)
      • optimize power consumption
  • RPL improvements in RIOT

  • CCN / NDN

    • header compression (incl. name compression) (stateful / stateless)
    • fragmention (evaluate https://datatracker.ietf.org/doc/draft-mosko-icnrg-beginendfragment/)
    • bootstrapping of CCN / NDN IoT deployments
    • evaluate large-scale IoT deployments (IoTLab) with ccn-lite and ndn-riot, testbed characteristic
    • prototype to manage ICN nodes
    • ICN firewall
    • edge computing / unikernel approach (based on CCN-lite)
    • [mgmt, security]
  • Cloud

    • mapping ICN to cloud
  • RIOT misc

    • unique ID generation for each program (during the flash process?)
    • improve documentation and tutorials for users

Participants

Pekka

  • interested in the IoT infrastructure, i.e. things like WoT and microservices including unikernels
  • automatic mapping of BLE attributes to CoAP/HTTP JSON and vice versa, i.e. not IPv6 over BLE but protocol translation.
  • interested in security of open infrastructures, i.e. applying lessons learned from blockchains and DoS countermeasures to IoT infrastructure, and especially WoT.

Michael

  • interested in ICN self-configuration/-management for an industrial IoT, particularly aspects of security and self-organization
  • furthermore interested in problems and challenges in 6TiSCH and ICN for the industrial IoT

Robert H.

  • Protocols (RPL in particular)
  • Low-level hardware stuff, especially atmega-based (e.g. low-power), but also energy measurement
  • Test-Infrastructure and continuous integration
  • IDE Stuff

Stefan Mehner

  • Get familiar with RIOT
  • RIOT OS for LEGO Mindstorm NXT? (no idea how complex it is)
  • CoAP / BLE

Oleg

  • interested in almost every topic ;-)
  • IoT-NDN, particular security and compression
  • C++ interfaces for RIOT

Dennis

  • interested in IoT infrastructure, especially ICN for vehicular networks (Car2I, Car2Car)
  • interested in proactive services/functions related topics for wireless ICNs (edge computing / unikernel approach)

Kai

  • sDDS/DDS - data-centric, pub/sub middleware (combination with ICN?)
  • Protocols: BLE, OpenThread, (other like ZigBee, ZigBeeIP?)
  • Howto develop a radio driver for RIOT (Silicon Labs EFR32MG1 Mighty Gecko)
  • Energy and RIOT
  • Energy harvesting
  • Sleepy devices
  • Energy management, awareness
Clone this wiki locally