From: Dave Taht <dave.taht@gmail.com>
To: ECN-Sane <ecn-sane@lists.bufferbloat.net>
Subject: [Ecn-sane] in search of more ecn related data
Date: Tue, 24 Sep 2019 12:19:51 -0700 [thread overview]
Message-ID: <CAA93jw4mSEWoMMy5awSXhoELAZaqVpodFybVVSkZ=xxzkwLy3Q@mail.gmail.com> (raw)
I have gradually been accumulating data as to how ecn is currently
being used. I'm looking for bigger datasets from outside the US?
I have two truly enormous US datasets (backbone packet caps) so far,
that I think are going to need some custom tooling to tear apart. I
haven't
got much further than tcp splitting and then tcpdumping with a filter
a few of them, better tools might be needed.
Open Questions
* How often is it negotiated?
** How often does it fail to be negotiated?
* How often - do we see a CE or ECE on those connections?
* How often do we see mixed drop and CE/ECE
Filters include culling extremely short transactions (or establishing
say, short, medium, and long "buckets"), maybe tearing apart via tsde
to look at rtts, not sure what else. Mostly just trying to get data
from various large chokepoints (and looking for co-authors, mayhap) at
the moment.
--
Dave Täht
CTO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-831-205-9740
reply other threads:[~2019-09-24 19:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAA93jw4mSEWoMMy5awSXhoELAZaqVpodFybVVSkZ=xxzkwLy3Q@mail.gmail.com' \
--to=dave.taht@gmail.com \
--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