[Nfd-dev] Unicast communication in a distributed application in NDN paradigm

[Burke, Jeff]

I agree with Steve – the cases in the publications he sites are pretty specific, and are actually about targeting a physical object (light) not a computing node.  We could make suggestions if you could describe the application.
Jeff

From: Steve DiBenedetto <dibenede at cs.colostate.edu<mailto:dibenede at cs.colostate.edu>>
Date: Wed, 22 Oct 2014 09:42:34 -0400
To: Haroon Rashid <haroonr at iiitd.ac.in<mailto:haroonr at iiitd.ac.in>>
Cc: Nitinder Mohan <nitinder1369 at iiitd.ac.in<mailto:nitinder1369 at iiitd.ac.in>>, "<nfd-dev at lists.cs.ucla.edu<mailto:nfd-dev at lists.cs.ucla.edu>>" <nfd-dev at lists.cs.ucla.edu<mailto:nfd-dev at lists.cs.ucla.edu>>, Pushpendra Singh <psingh at iiitd.ac.in<mailto:psingh at iiitd.ac.in>>, "ndn-app at lists.cs.ucla.edu<mailto:ndn-app at lists.cs.ucla.edu>" <ndn-app at lists.cs.ucla.edu<mailto:ndn-app at lists.cs.ucla.edu>>
Subject: Re: [Nfd-dev] Unicast communication in a distributed application in NDN paradigm

Hi,

I have not read these specific papers, but I recall their topics being similar to what you’re after:

http://named-data.net/wp-content/uploads/nomen13.pdf
http://named-data.net/wp-content/uploads/TRlighting.pdf

In the past, I think we (the project) have discussed how NDN provides a superset of IP’s capabilities. If you really need point to point, there are mechanisms to get there. As you suggested, using a name that uniquely identifies an endpoint is something in that direction. Encrypting the Interest’s name and the Data response can further lock things down.

**However**, it sounds like you are questioning whether or not this is the communication model you really want. We may be able to offer some suggestions if you can describe the application.

-Steve


On Oct 22, 2014, at 7:16 AM, Haroon Rashid <haroonr at iiitd.ac.in<mailto:haroonr at iiitd.ac.in>> wrote:

Hello All,

I am planning to develop a distributed application using NDN paradigm. In this application, each machine should be able to do unicast communication and should not use shared memory (like ccnsync/chronosync). If I am correct, we already have a distributed NDN-chat application which is of broadcast nature (because message written in a namespace gets broadcasted to all members in the same namespace) and hence it uses the shared memory concept. Is there any other distributed application in NDN where unicast communication is supported? If not, how Can I achieve the same in NDN? Should I put the name of the target machine in the Interest packet (name) itself for facilitating such communication? But, would that will not change the basic architecture of NDN/CCN paradigm?

--
Haroon Rashid


_______________________________________________
Nfd-dev mailing list
Nfd-dev at lists.cs.ucla.edu<mailto:Nfd-dev at lists.cs.ucla.edu>
http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev

_______________________________________________ Nfd-dev mailing list Nfd-dev at lists.cs.ucla.edu<mailto:Nfd-dev at lists.cs.ucla.edu> http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20141022/9a5def35/attachment.html>