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

José Alamos notifications at github.com
Thu Jan 3 19:34:02 CET 2019

jia200x commented on this pull request.

> +that to the proper format for storage (e.g. lines separated by `\n` character in
+a file).
+If a storage implements any kind of encryption mechanism it MUST be
+transparent to the RIOT Registry, and all that logic should be handled withing
+the facility.
+# 6. Configuration manager and interfaces
+The configuration manager is a pseudo-module that allows a RIOT node to be
+configured from one or more communication interfaces. Examples of these
+communication interfaces could be UART, SPI or higher layers like PPP, IPv6,
+UDP, CoAP, LWM2M, etc.
+The configuration manager MAY provide an access control mechanism for
+restricting access to the configurations. However, it can relay on security
+implemented on the layers mentioned above (e.g CoAP and DTLS, CHAP on PPP, etc)

Maybe lower layer security is just an extra and we still need access control. I know LWM2M already provides access control (and it's intended to be used as a Device Manager). In that case, the Configuration Manager is LWM2M + RIOT Registry. For other cases (CoAP), we might need to implement an access control mechanism in the endpoint.

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20190103/4c10f94b/attachment.html>

More information about the notifications mailing list