[Nfd-dev] network_region in nfd.conf file

[Dehart, John]

Junxiao,

OK. That’s starting to make sense.

Now, is the routable-prefix the same as the prefix that NLSR announces?
So, for UCLA would the default prefix announced by NLSR become /ndn/edu/ucla/irl?

And then would identities and certificates anchored at the UCLA node become prefixed with /ndn/edu/ucla/irl?

Thanks,
John

On Apr 18, 2017, at 6:54 PM, Junxiao Shi <shijunxiao at email.arizona.edu<mailto:shijunxiao at email.arizona.edu>> wrote:

Hi John

The routable-prefixes dataset #3145<https://redmine.named-data.net/issues/3145> can provide that information.
UCLA-spurs should report its routable-prefixes as /ndn/edu/ucla/irl rather than /ndn/edu/ucla, since there is no other way to exclude /ndn/edu/ucla/remap.

Yours, Junxiao

On Tue, Apr 18, 2017 at 4:23 PM, Dehart, John <jdd at wustl.edu<mailto:jdd at wustl.edu>> wrote:

So, Consumers have to know the names of the routers in the network?
That seems odd. Does each person who runs an application need to
know all the names of the routers? Or is there a discovery process that the
applications are supposed to use?

Thanks,
John



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20170419/6fefe40a/attachment-0001.html>