CNL in the NDN networking environments » History » Version 2
Anonymous, 01/07/2016 01:30 PM
| 1 | 1 | Anonymous | CNL in the NDN networking environments |
|---|---|---|---|
| 2 | ====================================== |
||
| 3 | |||
| 4 | 2 | Anonymous | This documents use case requirements for how the CNL API could be used in different NDN networking environments. |
| 5 | 1 | Anonymous | |
| 6 | # Open mHealth |
||
| 7 | |||
| 8 | 2 | Anonymous | Provide a layer internal to the app that allows one to code in clear text but publish/consume encrypted names in a name space. |
| 9 | |||
| 10 | 1 | Anonymous | # Building Management Systems |
| 11 | |||
| 12 | 2 | Anonymous | Provide the in-memory representation and enable the filtering the names of large databases of BMS measurements. |
| 13 | |||
| 14 | 1 | Anonymous | # IoT FLOW |
| 15 | 2 | Anonymous | |
| 16 | Provide an in-memory representation of the pub/sub namespace to track the information needed for behind-the-scenes subscription management. |
||
| 17 | |||
| 18 | # NDN-RTC |
||
| 19 | |||
| 20 | Provide improved sync support between conference participants. |