-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use pub/sub for user-defined policy delivery #69
Comments
Given you are talking about "notification", I suppose these are considered command topics. A major limitation is that, ndn-lite/app-support/pub-sub.c Lines 486 to 494 in d60a114
This proposal would occupy 60% of available topics. While it's possible to change this limitation, it would increase memory usage and take NDN-Lite further from being able to run on memory-constrained devices. P.S. Is NDN-Lite still usable on constrained devices such as the nRF52840? |
In the current (6d433ac) ndn-lite, user-defined policies are distributed through signed Interest sent by the controller directly to a device.
We may want to change this direct Interest notification to pub/sub mode. That is, each device subscribe to the topics that are:
/home/POLICY/TEMP/bedroom/sensor1
/home/POLICY/TEMP/bedroom
/home/POLICY/TEMP
When the IoT controller generates a new policy, it will send out a notification containing the policy name.
A device, say
/home/TEMP/bedroom/sensor1
, receives this notification, will check whether the policy affects itself.If yes, the device will fetch the new content from the topic, verify the signature, and install the policy.
The text was updated successfully, but these errors were encountered: