Subject: Re: [LOOPS] draft-welzl-loops-gen-info: general direction

From: "Zhouxingwang (Joe)" <[email-masked]>
Date: Mon, 17 Jun 2019 03:55:44 +0000

Hi,

— two modes for recover: retransmission mode, FEC mode

For this item, the ACK/NACK packets in retransmission mode mainly has two functions, one is for loss detection and another is for local measurement(local RTT, loss rate, throughput...) which is important for LOOPS to interact with End-to-End congestion control.
So a TCP-like delayed ACK mechanism is suitable (NACK does not apply this, it will be sent out immediately once packet loss), but unlike TCP LOOPS does not require critical ACK clocking for its sliding window, so LOOPS could use a *longer* delayed ACK mechanism by mimicking TCP.
For the overhead of ACK (packets and processing), if there is bidirectional traffic between LOOPS ingress and egress, then packets overhead is limited; for processing overhead, it may need more CPU resource.

Thanks
Joe

-----Original Message-----
From: LOOPS [mailto:[email-masked]] On Behalf Of Carsten Bormann
Sent: Wednesday, June 12, 2019 5:18 PM
To: [email-masked]
Subject: [LOOPS] draft-welzl-loops-gen-info: general direction

Is the general direction taken by

https://tools.ietf.org/html/draft-welzl-loops-gen-info

the one that should be pursued in the LOOPS activity?

Specifically:
— protocol is run between an ingress and an egress, apart from some form of controller for setup purposes no other nodes are involved.
— two modes for recover: retransmission mode, FEC mode — protocol operates on sparse forward information (for retransmission mode, pretty much a sequence number and an ACK request) and reverse information that can be piggybacked on a reverse tunnel or sent in separate messages — no “connection setup” between ingress and egress nodes — the protocol defines a generic information model; specific encodings are defined for specific encapsulation protocols such as GUE or Geneve

(The draft actually offers two slightly different approaches, one in the main body, one somewhat more innovative approach in Appendix B.  If you think that Appendix B could be used in a kind of deployment that you are interested in, we would like to hear from you.)

Grüße, Carsten

--
LOOPS mailing list
[email-masked]
https://www.ietf.org/mailman/listinfo/loops