From: Dave Taht <dave.taht@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>, basti.endres@fau.de
Subject: [Bloat] Fwd: Interop runner with satellite links
Date: Thu, 30 Sep 2021 12:32:01 -0700 [thread overview]
Message-ID: <CAA93jw4J+5dvmWaTHRU3xTZTKFDS5prTNpvAJLwYBorvcLBPyg@mail.gmail.com> (raw)
In-Reply-To: <2572762.KRHqeOQrTU@7b74a564-70da-4baa-82f8-b74434554dd0>
of interest to the bufferbloat lost. Nice work sebastian!
---------- Forwarded message ---------
From: Sebastian Endres <basti.endres@fau.de>
Date: Wed, Sep 29, 2021 at 12:58 PM
Subject: Interop runner with satellite links
To: <etosat@ietf.org>, <quic@ietf.org>
Cc: <joerg.deutschmann@fau.de>
Dear all,
for my master's thesis we ran measurements of all publicly available
QUIC implementations over an emulated satellite link. The results are
available online: https://interop.sedrubal.de/
A click on the results also shows time-offset plots, but are not
available for every combination.
In general, the performance of QUIC over high latency (e.g.,
geostationary satellites) is rather poor, especially if there is
packet loss.
Would it make sense to add such tests with challenging link
characteristics to the official QUIC interop runner?
Best regards,
Sebastian
--
Fixing Starlink's Latencies: https://www.youtube.com/watch?v=c9gLo6Xrwgw
Dave Täht CEO, TekLibre, LLC
next parent reply other threads:[~2021-09-30 19:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2572762.KRHqeOQrTU@7b74a564-70da-4baa-82f8-b74434554dd0>
2021-09-30 19:32 ` Dave Taht [this message]
2021-10-01 7:49 ` Erik Auerswald
2021-10-06 9:09 ` Joerg Deutschmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA93jw4J+5dvmWaTHRU3xTZTKFDS5prTNpvAJLwYBorvcLBPyg@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=basti.endres@fau.de \
--cc=bloat@lists.bufferbloat.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox