<div dir="ltr"><div><div><div>Good morning Klaus, <br><br></div>how can I verify the capability of the link? <br></div>It could be possible, because I sent thousands of requests. <br></div><div><br></div><div><br></div><div>Thank you.</div><div>Giuseppe.<br></div></div><div class="gmail_extra"><br><div class="gmail_quote">2018-01-12 20:55 GMT+01:00 Klaus Schneider <span dir="ltr"><<a href="mailto:klaus@cs.arizona.edu" target="_blank">klaus@cs.arizona.edu</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Did you make sure that you are not sending more packets than the link can handle?<br>
<br>
Retransmissions are only one aspect of TCP; another one is to slow down the sending rate before/once the link becomes congested.<br>
<br>
Best regards,<br>
Klaus<span class=""><br>
<br>
<br>
On 12/01/18 02:21, Giuseppe Carella wrote:<br>
</span><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">
Good morning,<br>
<br>
I have done what you told but I still continue to loose some packets, much less than before but I still continue to loose:<br>
<br>
This is what I have done:<br>
Consumer:<br>
nfdc face create udp4://$1 reliability on<br>
nfdc route add /app1 udp4://$1<br>
<br>
Producer:<br>
nfdc face create udp4://$1 reliability on<br>
<br>
<br>
Should it be enough, right?<br>
<br>
Thank you.<br>
Giuseppe<br>
<br></span>
2018-01-10 19:49 GMT+01:00 Davide Pesavento <<a href="mailto:davide.pesavento@lip6.fr" target="_blank">davide.pesavento@lip6.fr</a> <mailto:<a href="mailto:davide.pesavento@lip6.fr" target="_blank">davide.pesavento@lip6.<wbr>fr</a>>>:<span class=""><br>
<br>
Giuseppe,<br>
<br>
You didn't need to change the code. As Eric said, to enable the<br>
LpReliability feature, you can specify "reliability on" when creating<br>
a face with nfdc.<br>
<br>
That being said, make sure you enable LpReliability on *both* ends of<br>
the link, otherwise the receiver won't know that it has to send ACKs<br>
back.<br>
<br>
Best regards,<br>
Davide<br>
<br>
On Wed, Jan 10, 2018 at 10:10 AM, Giuseppe Carella<br></span><span class="">
<<a href="mailto:gcarella228@gmail.com" target="_blank">gcarella228@gmail.com</a> <mailto:<a href="mailto:gcarella228@gmail.com" target="_blank">gcarella228@gmail.com</a>><wbr>> wrote:<br>
> Good morning Eric,<br>
><br>
> I tried to use this functionality changing the NFD code (I set<br>
the boolean<br>
> variable isEnalbe = true into the file lp-reliability.hpp).<br>
> It seems that the retransmission becomes mandatory in this way<br>
(every time<br>
> the request is sent maxRetx + 1 times).<br>
> Does it behave like that or the retransmission verifies only if<br>
the ack is<br>
> not received within RTO?<br>
> Is it possible to customize the value of RTO?<br>
><br>
> Thank you.<br>
> Giuseppe.<br>
><br>
> 2018-01-04 20:18 GMT+01:00 Eric Newberry<br></span>
<<a href="mailto:enewberry@email.arizona.edu" target="_blank">enewberry@email.arizona.edu</a> <mailto:<a href="mailto:enewberry@email.arizona.edu" target="_blank">enewberry@email.arizon<wbr>a.edu</a>>>:<div><div class="h5"><br>
>><br>
>> Hi Giuseppe,<br>
>><br>
>> By default, the number of retransmissions is set to 3. The option<br>
>> controlling this is in LpReliability::Options as maxRetx.<br>
However, currently<br>
>> there is no way to set this option using nfdc or any other<br>
management tool.<br>
>> Therefore, if you want to change this, you would need to modify<br>
the NFD<br>
>> source code, recompile, and reinstall. There are no options<br>
relating to the<br>
>> reliability system in nfd.conf.<br>
>><br>
>> Eric<br>
>><br>
>><br>
>> On 01/04/2018 02:10 AM, Giuseppe Carella wrote:<br>
>><br>
>> Good morning Eric,<br>
>><br>
>> Thank you for your answer.<br>
>> I understood that it's possible to implement the retransmission<br>
by means<br>
>> of NDNLPv2, which is a protocol located upon the transport layer.<br>
>> So I have to set a maximum number of retransmissions, that's all<br>
(I hope).<br>
>> Is it enough modifying some properties into nfd.conf to choose<br>
the maximum<br>
>> number of retransmissions or I have to add some new APIs into<br>
applicative<br>
>> layer?<br>
>><br>
>> Thank you.<br>
>> Giuseppe.<br>
>><br>
>> 2018-01-04 9:31 GMT+01:00 Eric Newberry<br></div></div>
<<a href="mailto:enewberry@email.arizona.edu" target="_blank">enewberry@email.arizona.edu</a> <mailto:<a href="mailto:enewberry@email.arizona.edu" target="_blank">enewberry@email.arizon<wbr>a.edu</a>>>:<span class=""><br>
>>><br>
>>> Giuseppe,<br>
>>><br>
>>> NFD release 0.6.0 implements a link-layer reliability system as<br>
part of<br>
>>> NDNLPv2 for unicast TCP, UDP, and Ethernet faces. It can be<br>
enabled by<br>
>>> specifying "reliability on" when creating (or updating) a face<br>
with nfdc. In<br>
>>> order for the system to function, it must be enabled on both<br>
ends of the<br>
>>> link. The above command only enables it on one end.<br>
>>><br>
>>> Eric<br>
>>><br>
>>><br>
>>> On 01/04/2018 01:24 AM, Giuseppe Carella wrote:<br>
>>><br>
>>> Good morning community,<br>
>>><br>
>>> is it possible to configure NFD in order to allow an UDP<br>
communication<br>
>>> with retransmission?<br>
>>> I know that I could use TCP, but for my purpose it's necessary<br>
having UDP<br>
>>> with retransmission.<br>
>>><br>
>>> Thank you.<br>
>>> Giuseppe.<br>
>>><br>
>>><br>
>>> ______________________________<wbr>_________________<br>
>>> Ndn-interest mailing list<br>
>>> <a href="mailto:Ndn-interest@lists.cs.ucla.edu" target="_blank">Ndn-interest@lists.cs.ucla.edu</a><br></span>
<mailto:<a href="mailto:Ndn-interest@lists.cs.ucla.edu" target="_blank">Ndn-interest@lists.cs.<wbr>ucla.edu</a>><br>
>>> <a href="http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest" rel="noreferrer" target="_blank">http://www.lists.cs.ucla.edu/m<wbr>ailman/listinfo/ndn-interest</a><span class=""><br>
<<a href="http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest" rel="noreferrer" target="_blank">http://www.lists.cs.ucla.edu/<wbr>mailman/listinfo/ndn-interest</a>><br>
>>><br>
>>><br>
>>><br>
>>> ______________________________<wbr>_________________<br>
>>> Ndn-interest mailing list<br>
>>> <a href="mailto:Ndn-interest@lists.cs.ucla.edu" target="_blank">Ndn-interest@lists.cs.ucla.edu</a><br></span>
<mailto:<a href="mailto:Ndn-interest@lists.cs.ucla.edu" target="_blank">Ndn-interest@lists.cs.<wbr>ucla.edu</a>><br>
>>> <a href="http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest" rel="noreferrer" target="_blank">http://www.lists.cs.ucla.edu/m<wbr>ailman/listinfo/ndn-interest</a><span class=""><br>
<<a href="http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest" rel="noreferrer" target="_blank">http://www.lists.cs.ucla.edu/<wbr>mailman/listinfo/ndn-interest</a>><br>
>>><br>
>><br>
>><br>
><br>
><br>
> ______________________________<wbr>_________________<br>
> Nfd-dev mailing list<br></span>
> <a href="mailto:Nfd-dev@lists.cs.ucla.edu" target="_blank">Nfd-dev@lists.cs.ucla.edu</a> <mailto:<a href="mailto:Nfd-dev@lists.cs.ucla.edu" target="_blank">Nfd-dev@lists.cs.ucla.<wbr>edu</a>><br>
> <a href="http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev" rel="noreferrer" target="_blank">http://www.lists.cs.ucla.edu/m<wbr>ailman/listinfo/nfd-dev</a><br>
<<a href="http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev" rel="noreferrer" target="_blank">http://www.lists.cs.ucla.edu/<wbr>mailman/listinfo/nfd-dev</a>><span class=""><br>
><br>
<br>
<br>
<br>
<br>
______________________________<wbr>_________________<br>
Nfd-dev mailing list<br>
<a href="mailto:Nfd-dev@lists.cs.ucla.edu" target="_blank">Nfd-dev@lists.cs.ucla.edu</a><br>
<a href="http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev" rel="noreferrer" target="_blank">http://www.lists.cs.ucla.edu/m<wbr>ailman/listinfo/nfd-dev</a><br>
<br>
</span></blockquote>
</blockquote></div><br></div>