[Ndn-interest] Current state of NDN?

Junxiao Shi shijunxiao at email.arizona.edu
Tue Jun 30 20:25:46 PDT 2020


Hi Michael


I think what is needed to move on is an open testnet. The policies for the
> NDN testbed might be suitable for universities, but are unfit for almost
> everybody else. Big issues that arise with an open testnet are governance,
> how to structure the global namespace, naming conventions and how to enable
> a variety of trade-offs (i.e. privacy vs. efficiency).
>

There was a comment at the 2018 NDN Community Meeting, from an industry
person: the NDN testbed is an "empty net", a network that has no meaningful
traffic.
Sadly, this comment still applies today.

https://named-data.net/ndn-testbed/policies-connecting-nodes-ndn-testbed/
As I understand, one of the "unfit" policies is that every NDN testbed node
must be controlled by "the NDN testbed management institution".
The reason is that the current testbed is technically an intra-domain
network. In IP terms, it's a single Autonomous System (AS). Naturally, a
single entity should be managing this network.
To have an "open testnet" without centralized control, we would need an
inter-domain network.

What we already have:

   - High speed forwarding.
   - Inter-domain hyperbolic routing.

What are still unresolved:

   - Name assignment policy, as you already mentioned. One of the ideas is
   to derive NDN names from DNSSEC
   <https://cs.gmu.edu/~eoster/doc/ndnssec.pdf>, but this would create a
   dependency on IP infrastructure.
   - Producer mobility. On the current testbed, producer mobility is
   supported through prefix readvertisement. When a mobile producer connects
   to any of the testbed nodes, its prefix is announced into the global
   routing system. This would not scale in an inter-domain network. The
   solution is forwarding hint, but it's neither fully specified nor adopted
   by applications.
   - Trust of routing messages. Although we have hyperbolic routing, the
   trust schema in the routing protocol still depends on a single trust
   anchor, which does not work in an inter-domain network.


I wonder what other policies are deemed "unfit for everybody else"?

Yours, Junxiao
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20200630/f596fa08/attachment.html>


More information about the Ndn-interest mailing list