dns

[ghost]

Really interesting project. i have been playing with event stores and CQRS. (https://en.wikipedia.org/wiki/Command-query_separation)

Its a good match for NDN i feel.

I am working on a project where

• all data must be encrypted at rest. NDN does this 👍
• all apps can run 100% offline, and so have a local store. NDN does this 👍
• application data Mutations are run locally and views updated locally, but also sent back to the core, and then propagated to interested parties. I know NDN does not give any in order guarantees.
• all edge devices are NATed. These are mobiles and iot devices. Not sure how NDN handles this ??

I am wondering if you have code or a plan / idea for a DNS of sorts. Each node (mobile, iot) would need to register their Ip to a central place ? How to secure that itself so that nodes cant pretend ? Well does not matter since each node MUST have a key to decrypt the data anyway... SO the system might forward to them but they cant decrypt the data anyway. This all leads back to identity. I saw you have a tool for making ID keys. For users they must now keep their keys safe, and so a vault is needed too.

[ghost]

https://github.com/named-data/ndn-delorean

kind of related to my question.

Hashicorp has a fair few tools that are really similar to this. Make me wonder about using some of their code as a base.

[taylorchu]

Do you mean NDN-based service discovery?

[ghost]

well i guess it is node discovery and services they happen to have (and so service discovery).

I am planning to build a application prototype (like a chat and video streaming) example on top of your code. SO am trying to join the dots up a bit

[taylorchu]

nfd itself can be used for service discovery, and each service can register its name prefix there.

You can register on the local nfd for testing. We are still improving on bridge routing to provide large scale settings.