<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Jan 17, 2016, at 6:23 PM, Syed Hassan Ahmed <<a href="mailto:s.h.ahmed@ieee.org" class="">s.h.ahmed@ieee.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">Dear Dennis,</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">cc: Prof. Lixia Zhang and Dr. Alexander </div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif"><br class=""></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">Somehow your question is valid, since we use Broadcasting interface in case of wireless, so eventually the Interest is flooded. For example, Every neighboring node of consumer C1, overhears the Interest packet, and then has to perform all those basic operations, including PIT, CS, FIB search. Moreover, if there is a case when those neighbors of C1 are not in intra transmission range, may involve in interest forwarding as well. That creates kind of broadcast storm, given that if there is only one provider initially in the network. I have explored this problem in case of vehicular environments, when we tried to simulate CCN on top of 802.11p. For reference, please read my following paper: </div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif"><br class=""></div><div class="gmail_default" style=""><font face="arial, helvetica, sans-serif" class=""><a href="http://ieeexplore.ieee.org/xpl/articleDetails.jsp?arnumber=7145392" class="">http://ieeexplore.ieee.org/xpl/articleDetails.jsp?arnumber=7145392</a></font></div></div></div></blockquote><div><br class=""></div>Dear Syed Hassan,</div><div><br class=""></div><div>thanks for your explanation of what happened in your scenario. I am afraid that specific scenario suffered a design defect.</div><div>In a all-wireless network (instead of a local wireless hop), one must have an effective way for individual nodes to decide whether it should, or should not, forward each received interest; e.g. see a simple example in this short paper (also on vehicular networking): "Rapid Traffic Information Dissemination Using Named Data" <a href="http://named-data.net/publications/nom/" class="">http://named-data.net/publications/nom/</a></div><div><div class=""><div dir="ltr" class=""><div class="gmail_extra"><div class=""><div class="gmail_signature"><div dir="ltr" class=""><div class=""><div dir="ltr" class=""><div class=""><div dir="ltr" class=""><br class=""></div><div dir="ltr" class="">If you are interested in this topic (about how to control packet flooding in all-wireless broadcast environment): some sensor networking research work about a decade ago produced a rich set of literatures on this topic,</div><div dir="ltr" class="">"Directed Diffusion for Wireless Sensor Networking" (just google it, it has about 3000 citations)</div><div dir="ltr" class="">another one: "GRAdient Broadcast: A robust Data Delivery Protocol for Large Scale Sensor Networks" </div><div dir="ltr" class=""><br class=""></div></div></div></div></div></div></div></div></div></div><div class=""><div dir="ltr" class=""><div class="gmail_extra"><div class=""><div class="gmail_signature"><div dir="ltr" class=""><div class=""><div dir="ltr" class=""><div class=""><div dir="ltr" class="">Lixia</div><div dir="ltr" class=""><br class=""></div><div dir="ltr" class=""><br class=""></div></div></div></div></div></div></div></div></div></div><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class="gmail_extra"><div class=""><div class="gmail_signature"><div dir="ltr" class=""><div class=""><div dir="ltr" class=""><div class=""><div dir="ltr" class="">PhD Research Scholar,<br class=""><a href="http://monet.knu.ac.kr/" target="_blank" class="">MoNeT Wireless Lab,</a><br class="">Kyungpook National University,<br class="">Daegu City, Republic of Korea.<br class="">Cell: +82-10-9883-0786<br class=""><a href="https://sites.google.com/site/shahmedknu/" target="_blank" class="">https://sites.google.com/site/shahmedknu/</a> </div></div></div></div></div></div></div>
<br class=""><div class="gmail_quote">On Mon, Jan 18, 2016 at 4:50 AM, Lixia Zhang <span dir="ltr" class=""><<a href="mailto:lixia@cs.ucla.edu" target="_blank" class="">lixia@cs.ucla.edu</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=""><br class="">
> On Jan 17, 2016, at 10:48 AM, Dennis Olvany <<a href="mailto:dennisolvany@gmail.com" class="">dennisolvany@gmail.com</a>> wrote:<br class="">
><br class="">
> The flooding behavior of NDN is already akin to a routing protocol. Clearly, there may be a benefit of knowing data reachability before interest is expressed, but it is also not useful to know data reachability if interest is never expressed. Is there a good use case for routing protocol integration with NDN?<br class="">
<br class="">
</span>interesting questions.<br class="">
<br class="">
let me ask a clarification question first: wonder exactly what you meant by "The flooding behavior of NDN"?<br class="">
<br class="">
Since NDN interest looks for data and not aims at any specific node, NDN takes advantages of any communication media that is broadcast in nature (e.g. WiFi) in that whoever hears the questions may answer. But I dont think NDN interests in general get flooded in wide areas.<br class="">
<br class="">
Wonder exactly what you meant by "routing protocol integration with NDN"? The NDN testbed is running a routing protocol.<br class="">
<span class="HOEnZb"><font color="#888888" class=""><br class="">
Lixia<br class="">
</font></span><div class="HOEnZb"><div class="h5">_______________________________________________<br class="">
Ndn-interest mailing list<br class="">
<a href="mailto:Ndn-interest@lists.cs.ucla.edu" class="">Ndn-interest@lists.cs.ucla.edu</a><br class="">
<a href="http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest" rel="noreferrer" target="_blank" class="">http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest</a><br class="">
</div></div></blockquote></div><br class=""></div></div>
</div></blockquote></div><br class=""></body></html>