<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 Mar 23, 2016, at 11:25 AM, Spyridon (Spyros) Mastorakis <<a href="mailto:mastorakis@cs.ucla.edu" class="">mastorakis@CS.UCLA.EDU</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hi Ahmed,<div class=""><br class=""></div><div class="">this is a quite open-ended question about the NDN architecture in general. Currently, there is no way to perform congestion control in NDN. </div></div></div></blockquote><div><br class=""></div>this seems some English expression issue -- there are plenty of ways to perform congestion control (e.g. see some ideas from this paper <a href="http://named-data.net/wp-content/uploads/comcom-stateful-forwarding.pdf" class="">http://named-data.net/wp-content/uploads/comcom-stateful-forwarding.pdf</a>)</div><div><br class=""></div><div>I believe Spyros meant that today's NFD implementation has not adopted any specific solutions, hence he has not put a congestion control into ndnSIM. </div><div><br class=""></div><div><div class="" style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div class=""><div class="">Klaus Schneider is working on CC as Spyros already mentioned; a quick google search on "ndn congestion control" also returns lots pointers to the papers on the topic</div><div class=""><br class=""></div><div class="">to the original question:</div></div></div></div><div><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class=""><br class=""></div></div></div><blockquote type="cite" class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class=""><div class=""><blockquote type="cite" class=""><div class="">On Mar 21, 2016, at 3:44 AM, Ahmed Sadek <<a href="mailto:don1559@gmail.com" class="">don1559@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">Dear All,<div class=""><br class=""></div><div class="">I was wondering if someone can point me to information on the <b class="">Flow Control and Congestion Control</b> <b class="">mechanism </b>used in ndnsim and is it the same as in NDN ?</div><div class=""><br class=""></div><div class="">Also, if the client keep sending interests on different interfaces and not receive response then what is the expected behavior ?</div></div></div></blockquote></div></div></div></div></blockquote><br class=""></div><div>the question is: what's the cause, right?</div><div>e.g.</div><div>- if the node is not connected, that's a connect problem</div><div>- if there is local connectivity but the network is partitioned, that's a slightly different problem</div><div>- if the interest the data does not exist, ideally one should receive an app level NACK as explained in <a href="http://named-data.net/wp-content/uploads/2016/01/consumer_producer_communication.pdf" class="">http://named-data.net/wp-content/uploads/2016/01/consumer_producer_communication.pdf</a> </div><div>- if the named producer does not exists, then it is up to how your strategy works (could generate a "NO ROUTE" NACK)</div><div><br class=""></div><div><br class=""></div></body></html>