From: Dave Taht <dave@taht.net>
To: ecn-sane@lists.bufferbloat.net
Subject: Re: [Ecn-sane] [tsvwg] SCE-L4S Flent "bakeoff" tests - thanks
Date: Wed, 25 Sep 2019 19:37:20 -0700 [thread overview]
Message-ID: <87sgoj236n.fsf@taht.net> (raw)
In-Reply-To: <LEJPR01MB11788CFFC04C2CD16DC1537C9C8C0@LEJPR01MB1178.DEUPRD01.PROD.OUTLOOK.DE> (Ruediger Geib's message of "Mon, 16 Sep 2019 06:13:11 +0000")
I am looking forward very much to a rrul test on an asymmetric network configuration.
> -----Ursprüngliche Nachricht-----
> Von: tsvwg <tsvwg-bounces@ietf.org> Im Auftrag von Pete Heist
> Gesendet: Donnerstag, 12. September 2019 22:17
> An: tsvwg@ietf.org
> Betreff: [tsvwg] SCE-L4S Flent "bakeoff" tests
>
> The following repo is now available with a set of Flent tests and
> results comparing the behavior of SCE and L4S in six scenarios, five
> that were discussed at the IETF 105 hackathon and a sixth more recent
> one:
>
> https://github.com/heistp/sce-l4s-bakeoff/
>
> The main README contains the details:
> - info about the test setup
> - the scenarios and links to results obtained in our Portland data center, along with observations
> - installation instructions, for the foolhardy
> - current and future plans
>
> These tests cover the previously mentioned issue #17 (Interaction w/
> FQ AQMs), and raise a few more. I’ll gladly boil the observations down
> into a list if that helps. The plan is to iterate on these tests up
> until IETF 106, to help provide the IETF and community with more
> information regarding these two proposals.
>
> While the tsvwg mailing list can be used for discussion, if there are
> specific action items for the tests themselves (corrections, new
> tests, etc), those may also be submitted as issues on the repo
> (https://github.com/heistp/sce-l4s-bakeoff/issues), so we can keep
> track of them.
>
> Lastly, a technical detail, the currently posted run is missing its
> associated pcap files due to a botched rsync, so I’ll start another
> run and push that tomorrow. Meanwhile, the data files and plots are
> still useful without those.
>
> Regards,
> Pete Heist
parent reply other threads:[~2019-09-26 2:37 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <LEJPR01MB11788CFFC04C2CD16DC1537C9C8C0@LEJPR01MB1178.DEUPRD01.PROD.OUTLOOK.DE>]
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/ecn-sane.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sgoj236n.fsf@taht.net \
--to=dave@taht.net \
--cc=ecn-sane@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