<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hi,<div class=""><br class=""></div><div class="">I have not read these specific papers, but I recall their topics being similar to what you’re after:</div><div class=""><br class=""></div><div class=""><a href="http://named-data.net/wp-content/uploads/nomen13.pdf" class="">http://named-data.net/wp-content/uploads/nomen13.pdf</a></div><div class=""><a href="http://named-data.net/wp-content/uploads/TRlighting.pdf" class="">http://named-data.net/wp-content/uploads/TRlighting.pdf</a></div><div class=""><br class=""></div><div class="">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.</div><div class=""><br class=""></div><div class="">**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.</div><div class=""><br class=""></div><div class="">-Steve</div><div class=""><br class=""></div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Oct 22, 2014, at 7:16 AM, Haroon Rashid <<a href="mailto:haroonr@iiitd.ac.in" class="">haroonr@iiitd.ac.in</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div class="">Hello All,</div><div class=""><br class=""></div>I am planning to develop a distributed application using NDN paradigm. In this application, each machine should be able to do <span id="aa9593b2-5bed-4b99-b9fc-da7cdef43963" class="GINGER_SOFTWARE_mark">unicast</span> communication and should not use shared memory (like <span id="13e05d6f-3a77-4321-81c7-3291566d491b" class="GINGER_SOFTWARE_mark">ccnsync</span>/<span id="9e3d38ef-4026-4002-98ba-c645347cba63" class="GINGER_SOFTWARE_mark">chronosync</span>). 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 <span id="58547a4c-cdd5-431c-9c2a-3ff1556206f9" class="GINGER_SOFTWARE_mark">unicast</span> 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?<br clear="all" class=""><div class=""><br class=""></div>-- <br class=""><div dir="ltr" class=""><div class=""><div class="">Haroon Rashid<br class=""></div><br class=""></div><br class=""></div>
</div>
_______________________________________________<br class="">Nfd-dev mailing list<br class=""><a href="mailto:Nfd-dev@lists.cs.ucla.edu" class="">Nfd-dev@lists.cs.ucla.edu</a><br class="">http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev<br class=""></div></blockquote></div><br class=""></div></body></html>