[Nfd-dev] remote prefix registration

[Davide Pesavento]

On Fri, Oct 10, 2014 at 5:11 PM, Junxiao Shi
<shijunxiao at email.arizona.edu> wrote:
> Dear folks
>
> Please see below for a discussion about which process on the laptop should
> send remote prefix registration commands.
>

Hi Junxiao,

>From your analysis, it seems to me that using NRD to perform the
registrations gives more benefits and less drawbacks compared to the
alternatives. I'm wondering why your conclusions are different.

> I remember a previous NFD conference call concluded that ndn-autoconfig tool
> should send such registrations.
>

Does this mean that a decision has already been made? If so, what's
the purpose of this email?

[...]
> nrd is a process that handles local prefix registrations. It can be extended
> to registration command to the router, if a local registration suggests the
> necessity of a remote prefix registration.
> Benefit: Prefixes to be registered can be controlled dynamically by
> applications.
> Drawback: Both nrd and applications still need to be aware of changes in
> testbed connections. When a laptop moves to another router, the routable
> prefix changes, and applications will have to switch to a new prefix.
>

Why isn't ndn-autoconfig affected by this problem?

Thanks,
Davide