[Nfd-dev] [Ndn-interest] UDP_retransmissiom

[Eric Newberry]

Oops! I guess I've been working on congestion control too much recently.

Since we're likely going to allow the options to be set through management
for the congestion marking system, I think should allow the options to be
set this way for reliability as well. However, we're focusing on congestion
control at the moment, so their implementation would likely wait until
after that. I'll create a Redmine issue for this feature.

Eric

On Jan 22, 2018 11:42 AM, "Davide Pesavento" <davide.pesavento at lip6.fr>
wrote:

Eric,

I think Lixia was asking for an option to control the max number of
retransmissions in LpReliability. And there are two other reliability
options that are currently not settable: idleAckTimerPeriod and
seqNumLossThreshold.

On Mon, Jan 22, 2018 at 1:14 PM, Eric Newberry
<enewberry at email.arizona.edu> wrote:
> Apologies, I somehow missed the previous email. We just merged an NFD
config
> file option that, when set to "yes", will enable congestion detection and
> marking globally on all supported transport types (UDP, TCP, and Unix
stream
> socket). It is known as "face_system.general.enable_congestion_marking". A
> management option and nfdc parameter to allow it to be enabled or disabled
> on a face-by-face basis is in the works.
>
> Eric
>
>
> On Jan 22, 2018 4:32 AM, "Burke, Jeff" <jburke at remap.ucla.edu> wrote:
>
> please
>
>
>
> From: Nfd-dev <nfd-dev-bounces at lists.cs.ucla.edu> on behalf of Lixia Zhang
> <lixia at cs.ucla.edu>
> Date: Thursday, January 4, 2018 at 7:51 PM
> To: Eric Newberry <enewberry at email.arizona.edu>
> Cc: "nfd-dev at lists.cs.ucla.edu" <nfd-dev at lists.cs.ucla.edu>
> Subject: Re: [Nfd-dev] [Ndn-interest] UDP_retransmissiom
>
>
>
>
>
> On Jan 4, 2018, at 11:18 AM, Eric Newberry <enewberry at email.arizona.edu>
> wrote:
>
>
>
> Hi Giuseppe,
>
> By default, the number of retransmissions is set to 3. The option
> controlling this is in LpReliability::Options as maxRetx. However,
currently
> there is no way to set this option using nfdc or any other management
tool.
> Therefore, if you want to change this, you would need to modify the NFD
> source code, recompile, and reinstall. There are no options relating to
the
> reliability system in nfd.conf.
>
> Eric
>
> should we consider adding a way to config this parameter?
>
>
>
>
>
> On 01/04/2018 02:10 AM, Giuseppe Carella wrote:
>
> Good morning Eric,
>
>
>
> Thank you for your answer.
>
> I understood that it's possible to implement the retransmission by means
of
> NDNLPv2, which is a protocol located upon the transport layer.
>
> So I have to set a maximum number of retransmissions, that's all (I hope).
>
> Is it enough modifying some properties into nfd.conf to choose the maximum
> number of retransmissions or I have to add some new APIs into applicative
> layer?
>
> Thank you.
>
> Giuseppe.
>
>
>
> 2018-01-04 9:31 GMT+01:00 Eric Newberry <enewberry at email.arizona.edu>:
>
> Giuseppe,
>
> NFD release 0.6.0 implements a link-layer reliability system as part of
> NDNLPv2 for unicast TCP, UDP, and Ethernet faces. It can be enabled by
> specifying "reliability on" when creating (or updating) a face with nfdc.
In
> order for the system to function, it must be enabled on both ends of the
> link. The above command only enables it on one end.
>
> Eric
>
>
>
> On 01/04/2018 01:24 AM, Giuseppe Carella wrote:
>
> Good morning community,
>
> is it possible to configure NFD in order to allow an UDP communication
with
> retransmission?
>
> I know that I could use TCP, but for my purpose it's necessary having UDP
> with retransmission.
>
>
>
> Thank you.
>
> Giuseppe.
>
>
>
> _______________________________________________
>
> Ndn-interest mailing list
>
> Ndn-interest at lists.cs.ucla.edu
>
> http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest
>
>
>
>
> _______________________________________________
> Ndn-interest mailing list
> Ndn-interest at lists.cs.ucla.edu
> http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest
>
>
>
>
>
> _______________________________________________
> Nfd-dev mailing list
> Nfd-dev at lists.cs.ucla.edu
> http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev
>
>
>
>
>
> _______________________________________________
> Nfd-dev mailing list
> Nfd-dev at lists.cs.ucla.edu
> http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20180122/807ae0e5/attachment-0001.html>