<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="">Hi,<div class=""><br class=""></div><div class=""><div><blockquote type="cite" class=""><div class="">On Mar 14, 2018, at 12:19 AM, Mortaza Nikzad <<a href="mailto:mrtz_azad@yahoo.com" class="">mrtz_azad@yahoo.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">Hi<br class="">thanks for your reply Spyridon.<br class="">I understand that this example is from ndnSIM-v.1, so I installed it and run the example there. It works well but with a customary forwarding strategy not best rout strategy. It would be good if the documentation about this example be correct. <br class="">now my question is that why as a good rule of thumb did not use from received nack from upstream face to correct the chosen face? I try to follow it in my work.<br class=""></div></div></blockquote><div><br class=""></div><div>If the NACK indicates congestion, then long story short, an approach like that should work.</div><br class=""><blockquote type="cite" class=""><div class=""><div class=""><br class="">I also understand the best rout forwarding strategy do not work well and actually do not choose the least cost link. I tested it in a simple topology as: one consumer, one producer and two path from consumer to producer with different data rate. I unexpectedly saw that the best rout chosen the worse path. Can anyone here tell me why? and is this problem related to forwarding strategy or route calculator? <br class="">thanks<br class=""></div></div></blockquote><div><br class=""></div>Each FIB entry has next-hops. Each next-hop has a cost. This cost can be associated either with delay or bandwidth parameters. The current implementation selects the path with the smallest delay (i.e., the path with the smallest delay will have the lowest cost).</div><div><br class=""></div><div>If you want to take the link bandwidth into account, you will have to modify the GlobalRoutingHelper:</div><div><br class=""></div><div><a href="https://github.com/named-data-ndnSIM/ndnSIM/blob/master/helper/ndn-global-routing-helper.cpp#L283" class="">https://github.com/named-data-ndnSIM/ndnSIM/blob/master/helper/ndn-global-routing-helper.cpp#L283</a><br class=""><br class=""></div><div>Thanks,</div><div><br class=""></div><div><div class=""><div class=""><div class=""><div class=""><span class="" style="float: none; display: inline !important;">Spyridon (Spyros) Mastorakis</span><br class=""><span class="" style="float: none; display: inline !important;">Personal Website: </span><a href="http://cs.ucla.edu/~mastorakis/" class="">http://cs.ucla.edu/~mastorakis/</a><br class=""><span class="" style="float: none; display: inline !important;">Internet Research Laboratory</span><br class=""><span class="" style="float: none; display: inline !important;">Computer Science Department</span><br class=""><span class="" style="float: none; display: inline !important;">UCLA</span></div><div class=""><span class="" style="float: none; display: inline !important;"><br class=""></span></div></div></div><div class=""><br class=""></div><br class="Apple-interchange-newline"></div></div><br class=""></div></body></html>