From: Ricky Mok <cskpmok@caida.org>
To: Dave Taht <dave.taht@gmail.com>
Cc: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] new subscribers to this list
Date: Thu, 21 Apr 2022 13:18:27 -0700 [thread overview]
Message-ID: <696a2ada-fea2-e03a-7313-98a448282d35@caida.org> (raw)
In-Reply-To: <CAA93jw7otRPRS=OeCqyE7JZEcSCCJ9Mb2Q=kHUt7_Upb7dfdDA@mail.gmail.com>
Yes. The video is here.
https://catalog.caida.org/details/media/2022_jitterbug_pam/resources
The code is on GitHub (https://github.com/estcarisimo/jitterbug). I am
happy to help if you want to try it on your dataset.
Applying the method to all the data that we have is an option, as it is
computationally expensive to run. But we currently don't have a concrete
next step for this project (the funding for this was gone). We barely
keep the data (MANIC) collection going at this stage.
Ricky
On 4/21/22 12:07, Dave Taht wrote:
> On Thu, Apr 21, 2022 at 11:44 AM Ricky Mok <cskpmok@caida.org> wrote:
>> Thanks Dave for creating and managing this mailing list!
> and: thank *you* (and kc, dave clark, et al) for this really
> excellent paper on "jitterbug". Quality jitter metrics have long been
> lacking on the internet.
>
> https://link.springer.com/chapter/10.1007/978-3-030-98785-5_7
>
> "We discovered a set of features in jitter and jitter dispersion —a
> jitter-derived time series we define in this paper—time series that
> are characteristic of periods of congestion. We leverage these
> concepts to create a jitter-based congestion inference framework that
> we call Jitterbug. We apply Jitterbug’s capabilities to a wide range
> of traffic scenarios and discover that Jitterbug can correctly
> identify both recurrent and one-off congestion events. We validate
> Jitterbug inferences against state-of-the-art autocorrelation-based
> inferences of recurrent congestion. We find that the two approaches
> have strong congruity in their inferences, but Jitterbug holds promise
> for detecting one-off as well as recurrent congestion."
>
> It looks very promising. Is the code anywhere? Is the talk up?
>
> ... and where do you plan to go next with it? Are any other groups
> beginning to leverage it?
>
>> Ricky
>>
prev parent reply other threads:[~2022-04-21 20:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-21 18:36 Dave Täht
2022-04-21 18:43 ` Ricky Mok
2022-04-21 19:07 ` Dave Taht
2022-04-21 20:18 ` Ricky Mok [this message]
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/starlink.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=696a2ada-fea2-e03a-7313-98a448282d35@caida.org \
--to=cskpmok@caida.org \
--cc=dave.taht@gmail.com \
--cc=starlink@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