[Ndn-interest] question about NDN prototype

[Lan Wang (lanwang)]

The ping server registers the prefix with its local NFD, which will not advertise the prefix to other nodes.  The registration simply makes sure that NFD will send an interest to the server if it matches the name prefix.  You need to run a routing protocol, eg nlsr, to advertise the prefix.

Lan

On Mar 4, 2015, at 4:51 PM, Feixiong Zhang <feixiong at winlab.rutgers.edu<mailto:feixiong at winlab.rutgers.edu>> wrote:

Dear Jeff and others,

I read through the nfdc and ndn-tlv-ping example, and I'm a bit confused that why the ping client needs to explicitly configure the route to the ping server.

my understanding(guess) of the ndn-tlv-ping is that when the ping server advertises a name prefix, this advertisement is announced to the network and corresponding FIB routing entries should already be built by the routing protocol. Therefore, the ping client just needs to ping the name prefix without specifying the ping server's location, and the ICN routing infrastructure would forward the ping interest packet to the server. Please correct me where I'm wrong.

btw, if I want to generate a specific network topology, do I always need to configure all the routing route for each node?

It would be great if any of you could clarify my confusion. thanks a lot!



On Tue, Mar 3, 2015 at 9:05 PM, Feixiong Zhang <feixiong at winlab.rutgers.edu<mailto:feixiong at winlab.rutgers.edu>> wrote:
thanks a lot for the reference!

On Tue, Mar 3, 2015 at 7:10 PM, Thompson, Jeff <jefft0 at remap.ucla.edu<mailto:jefft0 at remap.ucla.edu>> wrote:
Take a look at the "Connecting to remote NFDs" section of the NFD Getting Started Guide which describes what "nfdc register" does:
http://named-data.net/doc/NFD/current/INSTALL.html

See the nfdc man page for more details:
http://named-data.net/doc/NFD/current/manpages/nfdc.html

- Jeff T

From: Feixiong Zhang <feixiong at winlab.rutgers.edu<mailto:feixiong at winlab.rutgers.edu>>
Date: Tuesday, March 3, 2015 at 13:49
To: Jeff Thompson <jefft0 at remap.ucla.edu<mailto:jefft0 at remap.ucla.edu>>
Cc: "ndn-interest at lists.cs.ucla.edu<mailto:ndn-interest at lists.cs.ucla.edu>" <ndn-interest at lists.cs.ucla.edu<mailto:ndn-interest at lists.cs.ucla.edu>>

Subject: Re: [Ndn-interest] question about NDN prototype

thanks for the clarification! It helps a lot!

for the NFD configuration of a router, for example the router has four network interfaces, I want to bind two specific interfaces for NFD. how could I achieve this? Is there any documents on such configuration? thanks.

On Tue, Mar 3, 2015 at 4:02 PM, Thompson, Jeff <jefft0 at remap.ucla.edu<mailto:jefft0 at remap.ucla.edu>> wrote:
> 2. I see the ndn prototype has ndn-cxx and ndn-cpp, and it seems they share some code and both provide library for application usage. what's the different between these two?

ndn-cxx is the NDN C++ library with eXperimental eXtensions. Its API changes more rapidly since it is used to research the latest NDN architectural ideas and is the library for NFD.

ndn-cpp is an NDN client library for C++ which shares the same "Common Client Libraries" API with the other client libraries for Python, JavaScript and Java. The client libraries incorporate stable features from ndn-cxx and aim to support NDN applications on a range of platforms and languages.

Thanks,
- Jeff T

From: Junxiao Shi <shijunxiao at email.arizona.edu<mailto:shijunxiao at email.arizona.edu>>
Date: Tuesday, March 3, 2015 at 12:02
To: "ndn-interest at lists.cs.ucla.edu<mailto:ndn-interest at lists.cs.ucla.edu>" <ndn-interest at lists.cs.ucla.edu<mailto:ndn-interest at lists.cs.ucla.edu>>
Cc: Feixiong Zhang <feixiong at winlab.rutgers.edu<mailto:feixiong at winlab.rutgers.edu>>
Subject: Re: [Ndn-interest] question about NDN prototype



On Tue, Mar 3, 2015 at 1:00 PM, Feixiong Zhang <feixiong at winlab.rutgers.edu<mailto:feixiong at winlab.rutgers.edu>> wrote:
Dear Junxiao,

I'm Feixiong, a phd student from Rutgers University. I also work on information-centric network and I'm trying to investigate content delivery scenario in NDN. I look at the NDN prototype and come across some questions. It would be great if you could provide me some guidance.

As a first step, I'm trying to build a simple NDN testbed with four nodes (A -- B -- C -- D). A is a NDN content server, B and C are NDN routers, D is a NDN requester. Is there any related example of such content delivery scenario?

I have a few other questions for the setup (pardon me as I'm newbie to NDN prototype..) :

1. how to configure network interfaces in nfd?
2. I see the ndn prototype has ndn-cxx and ndn-cpp, and it seems they share some code and both provide library for application usage. what's the different between these two?

I would appreciate a lot if you could give me some guidance. thanks a lot!

Best Regards.
Feixiong

--
Feixiong Zhang, PhD candidate,
WINLAB, Rutgers University, New Jersey
http://winlab.rutgers.edu/~feixiong/<http://winlab.rutgers.edu/%7Efeixiong/>




--
Feixiong Zhang, PhD candidate,
WINLAB, Rutgers University, New Jersey
http://winlab.rutgers.edu/~feixiong/<http://winlab.rutgers.edu/%7Efeixiong/>



--
Feixiong Zhang, PhD candidate,
WINLAB, Rutgers University, New Jersey
http://winlab.rutgers.edu/~feixiong/<http://winlab.rutgers.edu/%7Efeixiong/>



--
Feixiong Zhang, PhD candidate,
WINLAB, Rutgers University, New Jersey
http://winlab.rutgers.edu/~feixiong/<http://winlab.rutgers.edu/%7Efeixiong/>
_______________________________________________
Ndn-interest mailing list
Ndn-interest at lists.cs.ucla.edu<mailto:Ndn-interest at lists.cs.ucla.edu>
http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20150304/6b62c0ec/attachment.html>