[riot-notifications] [RIOT-OS/RIOT] doc/memos: RDM Runtime Configuration Architecture (#10622)

José Alamos notifications at github.com
Wed Jan 9 13:14:08 CET 2019


@tcschmidt et al.: 
 I have spent some some time doing research about the configuration manager, and I'm not sure about its direction in the scope of this RDM.

It turns out there's some evidence on the usage of standard protocols for IoT Device Management (TR-069, OMA-DM, [and specially LWM2M in our context](https://es.slideshare.net/jvermillard/m2m-iot-device-managment-coaplwm2m-to-rule-them-all)). I tried the last one (via Eclipse Wakaama) and provides a client-server architecture on top of CoAP with the following features:
- Bootstrapping
- 3 mechanisms of authentication: PSK, certificates and raw public keys
- DTLS Security
- Client registration

This is IMO exactly what we expect to have in a **network** configuration interface.

For other interfaces (Serial, raw IP, BLE) there are already some cross-platform solutions like [Apache's mcumgr](https://github.com/apache/mynewt-mcumgr) used by Mynewt and Zephyr.

For the scope of this RDM, should we get on board with these existing configuration managers (LWM2M and/or MCUmgr) or should we rather implement our own Configuration Manager mechanism with our own interfaces? Opinions?

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/RIOT-OS/RIOT/pull/10622#issuecomment-452676007
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20190109/32300822/attachment-0001.html>


More information about the notifications mailing list