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

Roland Zink <roland@zinks.de> Wed, 20 May 2020 20:03 UTC

Return-Path: <roland@zinks.de>
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 ACFD83A08F9 for <etosat@ietfa.amsl.com>; Wed, 20 May 2020 13:03:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=zinks.de
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 mkGdVIei8z1w for <etosat@ietfa.amsl.com>; Wed, 20 May 2020 13:03:24 -0700 (PDT)
Received: from mo6-p00-ob.smtp.rzone.de (mo6-p00-ob.smtp.rzone.de [IPv6:2a01:238:20a:202:5300::6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E998C3A08E5 for <etosat@ietf.org>; Wed, 20 May 2020 13:03:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1590005002; s=strato-dkim-0002; d=zinks.de; h=In-Reply-To:Date:Message-ID:From:References:To:Subject: X-RZG-CLASS-ID:X-RZG-AUTH:From:Subject:Sender; bh=SSDi+P1BnYaGNU7p9FeAneqzHsbeu8BzWx8RBWNaBMM=; b=fBbReC64MEP3/OhSMTrFBeyczyr51i3HKCHeGQzqM2S6K+VwaMEzl+ZJvMQhecd1dz OGDn9oN63Wvf0qrupAEmeHQHPgXZSe9t+xp5SQGz25ln/aZsJs9mzplav5q/ThjwK14M Tm/Yj+jvbXzq4C1/2dlL8pz94sPxOLoDuDtXBB2UjyrDNbS98YR10SUSyRmWiSwQxAHl HhguV/P61UjmZPWb/ix83sc9sfQt0At1bYcMTvgzXEb8MlnN0da6dpAx0lIV3HTRISSP c8W0HX4EiheR6Z6NiF7oYrtJOSLSs4DfAVmg97HN9ynEOIGzq64AVXeRCGzPvpRfgm4x lDHw==
X-RZG-AUTH: ":PmMIdE6sW+WWP9q/oR3Lt+I+9LAZzXrcq8knhvfmBiJzkmKn1YaZ2OgvlDQJHaSz1/A="
X-RZG-CLASS-ID: mo00
Received: from [10.10.10.105] by smtp.strato.de (RZmta 46.7.0 DYNA|AUTH) with ESMTPSA id z023c3w4KK3L70G (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256 bits)) (Client did not present a certificate) for <etosat@ietf.org>; Wed, 20 May 2020 22:03:21 +0200 (CEST)
To: etosat@ietf.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> <13D10772-5139-439E-9527-8D72205F0E47@tzi.org> <3e61ab01-13de-9742-e058-8e552828f582@huitema.net>
From: Roland Zink <roland@zinks.de>
Message-ID: <d3b5c98a-b6a4-f5dc-259c-61beb01c1c1f@zinks.de>
Date: Wed, 20 May 2020 22:03:20 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.8.0
MIME-Version: 1.0
In-Reply-To: <3e61ab01-13de-9742-e058-8e552828f582@huitema.net>
Content-Type: multipart/alternative; boundary="------------EAA0D4DB74BBBF29EE230823"
Archived-At: <https://mailarchive.ietf.org/arch/msg/etosat/5u_vlolsoyH7tufbJBXmpkWGY8g>
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 20:03:27 -0000

Am 20.05.2020 um 20:09 schrieb Christian Huitema:
>
>
> On 5/20/2020 9:56 AM, Carsten Bormann wrote:
>>> 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.
>
> In a nutshell, that's the entire discussion of end-to-end vs middle-boxes.
>
> It is always possible to do a local optimization by adding some 
> intelligence in the network. That's the case for pretty much all 
> middle boxes, and it seems that the proxies envisaged in Loop fall 
> into that category. But there are always downsides, such as 
> management, flexibility, and most importantly ossification by old 
> proxies prone to bit rot.
>
yes
>
> Given effort, it is almost always possible to find end-to-end 
> solutions that are "good enough", getting you within 90% of the 
> optimum or some such. FEC as tail probe would be one example of that. 
> The end-to-end solutions also tend to get better over time, as 
> implementers devise more clever algorithms and update the code. All it 
> takes is some motivation that the effort is important.
>
This is the question. Is there enough motivation for the 0.x% case?
>
> An example of that would be support for cellular networks. Twenty 
> years ago, this was a niche, and TCP was not optimized for it. Hence 
> the deployment of middle-boxes in the cellular networks. But as this 
> became an ever more important scenario, TCP improved, and QUIC will 
> improve over that. The cellular middle-boxes become harder to justify, 
> and will start moving from the "optimization" to the "hindrance" category.
>
The cellular boxes are handling radio, mobility and things like local 
retransmits and FEC. So is the situation now better because of improved 
TCP or because of improved mobile network boxes? Probably both, but you 
are probably only talking about PEPs. Those may go away but they are 
also built into those mobile network boxes doing the other stuff like 
eNodeBs for example.
>
> Satellite networks are a peculiar case. They remain very much a niche 
> application to this day, something like a communication media of last 
> resort in places that fiber or cellular cannot reach. Given the niche 
> status, it is unclear whether end-to-end transports will bother 
> implementing optimized algorithms, even when these are available. But 
> it is also unclear whether "mainline" networks will bother deploying 
> middle-boxes solely for the benefit of the satellite niche, which 
> kinds of rules out solutions like 'deploy a box in every Wi-Fi 
> network'. 'Deploy a proxy at the ground station' might work, because 
> the satellite operator has the right business incentives, but of 
> course that requires nodes to still do something special for 
> satellites, i.e., discover the proxy and use it. Not obvious.
>
> Hence my effort to look at end-to-end solutions covering not just the 
> satellite case, but also other long distance networks such as 
> intercontinental connections. These are still niches today, given VPN, 
> but they are still useful for P2P applications. Given enough niches, 
> there might be enough motivation for doing the effort.
>
My fear is that niches are served late or not at all. The local network 
operator has a high interest in improving the situations but at global 
scale the end-2-end solution for it may not provide enough motivation. 
Assuming not all nices faces the same problem which can be solved then 
for all niches. Also solutions may need to be applied to all 
applications, e.g. if it is fixed in application a it still may need 
attention by application b. Applications may bit rot as well.

Anyway if you manage to build an end-to-end solution which does work for 
all sort of niches than that would be great. Please continue to work on 
an end-to-end solution.

> -- Christian Huitema
>
>
Regards,

Roland