Re: [EToSat] Interop runner with satellite links

Joerg Deutschmann <joerg.deutschmann@fau.de> Mon, 21 February 2022 19:38 UTC

Return-Path: <joerg.deutschmann@fau.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 5381B3A0CB1; Mon, 21 Feb 2022 11:38:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.814
X-Spam-Level:
X-Spam-Status: No, score=-7.814 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, NICE_REPLY_A=-0.714, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-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=fau.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 3mJMz_Ly6M-e; Mon, 21 Feb 2022 11:38:09 -0800 (PST)
Received: from mx-rz-1.rrze.uni-erlangen.de (mx-rz-1.rrze.uni-erlangen.de [IPv6:2001:638:a000:1025::14]) (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 8AB503A0C94; Mon, 21 Feb 2022 11:38:07 -0800 (PST)
Received: from mx-rz-smart.rrze.uni-erlangen.de (mx-rz-smart.rrze.uni-erlangen.de [IPv6:2001:638:a000:1025::1e]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) (No client certificate requested) by mx-rz-1.rrze.uni-erlangen.de (Postfix) with ESMTPS id 4K2Xdk6ZCNz8shJ; Mon, 21 Feb 2022 20:38:02 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fau.de; s=fau-2021; t=1645472282; bh=JgjQh4Fz9trwI/YqWHpJWytJ2v7GpN8Bb3h2BxZzxLU=; h=Date:Subject:To:References:Cc:From:In-Reply-To:From:To:CC: Subject; b=I8nswcyauyCVYIeev4X0rxGOaz3WqAnejZb7jQVwozERoExtevZSH2/dycwFmrlv8 3SX/FH4W7g5MqE9WH8bNkVcjREKbueKgVQwpxeSchV/gHV7kVsc8zE5H4Gz/tKWscd ClrjZsNYQH3eBMuSI7uW+FGnORlE7sItUBDmI6uNmRsE9VPzq9gO1aU6e+hiHoFh4n WrVyRrW/BlJjxW5fcWXrJJ8v4Nv4XPYyPTmuvUJcnc4296qF+B60nQtw0FiT2P3NZv 5PbSgZn8FSvY8wYN2dPSgcz4WKWVd/6aNbrkauJkmhMlh0/5by/xcVaqXT6tY4afHo 4HvJDyqTXeNMg==
X-Virus-Scanned: amavisd-new at boeck2.rrze.uni-erlangen.de (RRZE)
X-RRZE-Flag: Not-Spam
X-RRZE-Submit-IP: 131.188.37.210
Received: from faui7s0.informatik.uni-erlangen.de (faui7s0.informatik.uni-erlangen.de [131.188.37.210]) by mailhub.rrze.uni-erlangen.de (Postfix) with ESMTP id 4K2Xdg4YtTz8skf; Mon, 21 Feb 2022 20:37:59 +0100 (CET)
Received: from [192.168.178.35] (dynamic-095-115-034-054.95.115.pool.telefonica.de [95.115.34.54]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by faui7s0.informatik.uni-erlangen.de (Postfix) with ESMTPSA id 6FD6140F1E46; Mon, 21 Feb 2022 20:37:59 +0100 (CET)
Message-ID: <d8c17751-8e34-d688-8b14-fea279dad9d5@fau.de>
Date: Mon, 21 Feb 2022 20:37:56 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.5.0
Content-Language: en-US
To: "etosat@ietf.org" <etosat@ietf.org>, "quic@ietf.org" <quic@ietf.org>
References: <2572762.KRHqeOQrTU@7b74a564-70da-4baa-82f8-b74434554dd0> <2321206.ElGaqSPkdT@7b74a564-70da-4baa-82f8-b74434554dd0> <BL1PR11MB53038951CA6E71DC10A7F6E5CE3A9@BL1PR11MB5303.namprd11.prod.outlook.com>
Cc: Sebastian Endres <basti.endres@fau.de>, "Su, Chi-Jiun" <Chi-Jiun.Su@hughes.com>, Christian Huitema <huitema@huitema.net>
From: Joerg Deutschmann <joerg.deutschmann@fau.de>
In-Reply-To: <BL1PR11MB53038951CA6E71DC10A7F6E5CE3A9@BL1PR11MB5303.namprd11.prod.outlook.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-256"; boundary="------------ms000007050604020200020104"
Archived-At: <https://mailarchive.ietf.org/arch/msg/etosat/0IvXDp-sgpY-bqVZzFw7Do6gwQg>
Subject: Re: [EToSat] Interop runner with satellite links
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: Mon, 21 Feb 2022 19:38:14 -0000

Dear CJ,

stepping in for Sebastian, who has earned a break after finishing his 
thesis.
https://interop.cs7.tf.fau.de/thesis.pdf


> Sec. IV,D, 5: Interesting to know "picoquic" does speculative retransmission. As you argue, this may not always help. Did you confirm with the author
No, we have not discussed results with any author, simply because the 
number of implementations is too high to understand each implementation 
in detail. I added Christian Huitema in Cc, maybe he wants to comment on 
this one.

> The results show loss-based CC does not perform well compared to BBR
Yes, but as mentioned in the paper, we are not sure about the CC of each 
and every implementation.

> Production software performs well more like picoquic or not? How big difference is between production vs these implementations in the test?
Good question, we don't know, should be noted as future work. Sebastian 
only has a very short section "Comparison with Results of Other 
Research" in his thesis. We assume that Docker does not have a big 
influence on the performance, but did not verify that. Also chrome not 
being part of the tests is unfortunate.

> Any Time-Offset graphs for EUTELSAT case?
Yes, on the https://interop.cs7.tf.fau.de website select "Run: 
real_2021-11-15" and then "Plots for eutelsat (EUT)". We plan further 
runs in the future.

> Research overview page: additional column on emulated or real Sat link will be helpful
Actually that column already exists, 5th column from the right.
Motivation for putting the overview on github was to allow pull 
requests, but visualization and markdown editing for such a large table 
is not optimal with github...


Thanks,
Joerg