<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Thanks Cheng!<div><br></div><div>I completely agree that the way existing ndn::Consumer* apps behave is not necessary the ideal or the right way at all. We attempted to emulate very simple TCP behavior, which is very well known not to work "too well" in wireless scenarios.</div><div><br></div><div>The "problem" can be solved in a couple of different ways:</div><div><br></div><div>1) The most straightforward way, you can write your custom app (based on the existing one) that doesn't doubles RTO as much as it does currently. </div><div><br></div><div>2) Another way is to set maximum value of RTO to some small value, acceptable for you simulations (by default, max RTO is 200 seconds):</div><div>Config::SetDefault ("ns3::ndn::RttEstimator::MaxRTO", TimeValue (Seconds (4.0)));</div><div><br></div><div>3) Write a completely different (simple) app with fixed RTO, if it is acceptable (not sure) or different logic for RTO calculation.</div><div><br></div><div>---</div><div>Alex</div><div><br><div><div>On Apr 16, 2013, at 7:54 AM, Cheng Yi <<a href="mailto:yic@EMAIL.ARIZONA.EDU">yic@EMAIL.ARIZONA.EDU</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">
<meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type">
<div text="#000000" bgcolor="#FFFFFF">
<font face="Times New Roman, Times, serif">Hi Gabriel,</font><br>
<br>
IncreaseMultiplier is called whenever there is a NACK or an Interest
timeout, which implies potential congestion in the network. The
implementation of RttEstimator is based on the Karn's algorithm
which is used in TCP RTT estimation. Whether it fits NDN well is
debatable and still under investigation. Hope this helps.<br>
<br>
Cheers,<br>
Cheng<br>
<br>
<div class="moz-cite-prefix">On 4/16/2013 7:32 AM, Gabriel Marçal de
Brito wrote:<br>
</div>
<blockquote cite="mid:CAMyYirCUASF8ScBBmGX0zOB3eMOSgfS4NNt+LxaC-caiFNqeDA@mail.gmail.com" type="cite">
<div dir="ltr">Hi Alex.
<div><br>
</div>
<div style="">I am studying the impact of named-data networking
over wireless MANETs and within this work I am performing some
simulations with ndnSIM.</div>
<div style=""><br>
</div>
<div style="">
I noticed an increasing average delay using high chunk request
rates and digging deeper, found that
RttEstimator::IncreaseMultiplier() is called whenever there is
an Interest, doubling the RTT estimate.</div>
<div style=""><br>
</div>
<div style="">My guess is that since my scenarios are pretty
dynamic, some consumer nodes would be able to retrieve the
desired content if they re-request it sooner than waiting for
the very long ever-doubled RTT (in case of discontinuities,
for exemaple).</div>
<div style=""><br>
</div>
<div style="">Is there a reason for doubling this estimate?</div>
<div style=""><br>
</div>
<div style="">Thanks in advance,</div>
<div style="">Gabriel</div>
<div style=""><br>
</div>
<div style=""><br>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
ndnSIM mailing list
<a class="moz-txt-link-abbreviated" href="mailto:ndnSIM@lists.cs.ucla.edu">ndnSIM@lists.cs.ucla.edu</a>
<a class="moz-txt-link-freetext" href="http://www.lists.cs.ucla.edu/mailman/listinfo/ndnsim">http://www.lists.cs.ucla.edu/mailman/listinfo/ndnsim</a>
</pre>
</blockquote>
<br>
</div>
_______________________________________________<br>ndnSIM mailing list<br><a href="mailto:ndnSIM@lists.cs.ucla.edu">ndnSIM@lists.cs.ucla.edu</a><br>http://www.lists.cs.ucla.edu/mailman/listinfo/ndnsim<br></blockquote></div><br></div></body></html>