Re: [LOOPS] [nwcrg] IETF106: LOOPS side meeting on Tuesday 08:30, Orchard Room

Hi Carsten and all,

Thanks for putting all these together. 

I would like to have a follow-up discussion regarding single retransmission vs. multiple retransmission.

There is a potential choice to design a single retransmission mode *only* mechanism. The reason we might want to do it is the design is easier comparing with a generic retransmission mechanism allowing both single or multiple retransmission by parameter configuration.

For example,  LOOPS egress can mark a lost packet directly as "received" after it feedbacks a few ACKs to indicate a lost packet. Ingress removes the packet from its cache after a single retransmission. Once the retransmitted packet reaches the egress, egress simply forwards it. Such a mechanism only works for single retransmission.  
In this way, egress has a simple logic to decide when to stop sending the indication about a "lost" packet.  And the ingress does not need a logic to control whether and when 2nd and later retransmissions should be performed.

In multiple retransmission, it has to be more carefully designed to sync up when the egress gives up asking for retransmission and  when the ingress can remove the packet from its cache since no more retransmission is required.  As LOOPS does not provide 100% reliability, normally egress side should be the one determines when to give up asking for retransmission. Then egress needs to know the local forward RTT if multiple retransmission is expected.

So single retransmission *only* can be worth considering. It is a design choice more than an implementation choice to me. 
If there is a simple and efficient way to unify both, I would be more than happy to learn.  

Thanks,
Yizhou

-----Original Message-----
From: nwcrg [mailto:nwcrg-bounces@irtf.org] On Behalf Of Carsten Bormann
Sent: Monday, December 16, 2019 4:22 AM
To: loops@ietf.org
Cc: nwcrg@irtf.org
Subject: Re: [nwcrg] [LOOPS] IETF106: LOOPS side meeting on Tuesday 08:30, Orchard Room

Thanks again everyone for the participation at the LOOPS side meeting and in our slot at the NWCRG meeting.

I have compiled more detailed notes, with links to/copies of the meeting materials, at

https://github.com/loops-wg/ietf106

Please do have a look at the notes, specifically [1] and [2], and send corrections and additions.  Also, there were a few items in the NWCRG discussion where there may be results that we already can point to; as Marie-Jose said, please send them to both mailing lists.

Grüße, Carsten

[1]: https://github.com/loops-wg/ietf106/blob/master/ietf106-loops-side-meeting.md
[2]: https://github.com/loops-wg/ietf106/blob/master/ietf106-nwcrg-loops.md

_______________________________________________
nwcrg mailing list
nwcrg@irtf.org
https://www.irtf.org/mailman/listinfo/nwcrg