Re: [EToSat] Packet lost on last mile network?

Carsten Bormann <cabo@tzi.org> Wed, 20 May 2020 16:56 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: etosat@ietfa.amsl.com
Delivered-To: etosat@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E28303A0CA1 for <etosat@ietfa.amsl.com>; Wed, 20 May 2020 09:56:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wJGuZvNB8UVU for <etosat@ietfa.amsl.com>; Wed, 20 May 2020 09:56:54 -0700 (PDT)
Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 84CC43A0C9E for <etosat@ietf.org>; Wed, 20 May 2020 09:56:54 -0700 (PDT)
Received: from [192.168.217.119] (p548dc699.dip0.t-ipconnect.de [84.141.198.153]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 49RzS42vm6zykR; Wed, 20 May 2020 18:56:52 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <7ab5eb1c-afc9-0198-2d50-8bccd4872a41@huitema.net>
Date: Wed, 20 May 2020 18:56:51 +0200
Cc: Nitay Argov <Nitay@gilat.com>, Kuhn Nicolas <Nicolas.Kuhn@cnes.fr>, "etosat@ietf.org" <etosat@ietf.org>
X-Mao-Original-Outgoing-Id: 611686611.5092601-9056fd432fbf20fdb9f31dfe74bed7a6
Content-Transfer-Encoding: quoted-printable
Message-Id: <13D10772-5139-439E-9527-8D72205F0E47@tzi.org>
References: <HE1PR0702MB37550F63AB9CDD4FD637CC3EA9BF0@HE1PR0702MB3755.eurprd07.prod.outlook.com> <7C07C17B-2A81-4B8A-94E2-87858A5FDDC2@huitema.net> <D369D911-6F31-42D5-844E-7C597EC74CB0@tzi.org> <7ab5eb1c-afc9-0198-2d50-8bccd4872a41@huitema.net>
To: Christian Huitema <huitema@huitema.net>
X-Mailer: Apple Mail (2.3608.80.23.2.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/etosat/0lwh-PJY3XgqyDZ1BZc4068U2kM>
Subject: Re: [EToSat] Packet lost on last mile network?
X-BeenThere: etosat@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "The EToSat list is a non-WG mailing list used to discuss performance implications of running encrypted transports such as QUIC over satellite." <etosat.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/etosat>, <mailto:etosat-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/etosat/>
List-Post: <mailto:etosat@ietf.org>
List-Help: <mailto:etosat-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/etosat>, <mailto:etosat-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 May 2020 16:56:58 -0000

Hi Christian,

Thank you for the numbers.

> The simulation sets a satellite link, 250 Mbps down, 3 Mbps up, 300ms
> latency each way. The packet size is 1500 bytes. The 600ms RTT
> translates to a 1sec timer, approximately. In 1 second, the link carries
> more than 20,000 packets. If 1.6% are lost, that means 320 need to be
> retransmitted. Out of those 320, 5 or 6 will need to be retransmitted a
> second time, incurring an additional 2 seconds delay.

Right.  You don’t say what the RTT is on the WiFi part, but I’d assume that is lower than those 1 s.  So local recovery would have had ample time.

> A lot could be done in improving the behavior of Wi-Fi, that's sure. But
> I really don't like the idea of putting proxies everywhere -- the cost
> in management and decreased reliability would be enormous.

I’m not sure where the proxies would come in — a last-mile deployment of LOOPS would look more like a VPN.  (And I don’t want to talk down the deployment work needed here, but we do know how to deploy VPNs.)

> Besides, the
> deployment issues would be daunting -- who is going to set up al these
> proxies in all these Wi-Fi networks?

(People who want to have good WiFi networks?)

> And, if they are only deployed in a
> fraction of the Wi-Fi network, then the transport folks will still need
> an end-to-end solution.

They sure will.  But that never can be as good as local recovery.

> I have not yet explored the end-to-end solutions to the latency problem,
> but I could. FEC would cure the latency issue, but FEC trades bandwidth
> for latency, so you don't want that in the general case. If I had to do
> something, I would explore "selective FEC". Detect when the document is
> almost done, when there is only 1 second of transmission left. During
> that 1 second, apply something like 1/8 FEC for the remaining stream
> frames. That would make the last 1 second 12.5% less efficient, but
> would limit the "cascade' effect to 125ms.

FEC packets as a replacement for tail probe.  Makes a lot of sense to me.

Grüße, Carsten