From: David Fridovich-Keil <dfk@berkeley.edu>
To: Dave Taht <dave.taht@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>,
ECN-Sane <ecn-sane@lists.bufferbloat.net>,
dfk@eecs.berkeley.edu, dghosal@ucdavis.edu,
chapmanm@eecs.berkeley.edu, mkfarrens@ucdavis.edu,
tomlin@eecs.berkeley.edu, nhanford@ucdavis.edu
Subject: Re: [Ecn-sane] pacing, applied differently than bbr
Date: Sun, 9 Feb 2020 13:21:33 -0500 [thread overview]
Message-ID: <F0E548C9-4F68-43D4-82F5-BB04F5AC5D2A@berkeley.edu> (raw)
In-Reply-To: <CAA93jw6FQb7ES-ZuFWfsM=FncCG7cwjZ5O-18uaCYystt8YSEg@mail.gmail.com>
Hi Dave,
To be honest I haven’t personally been involved in follow up work but I think my coauthors may have. Maybe try contacting Nate at nate.hanford@gmail.com?
Best,
David
Sent from my iPhone
> On Feb 9, 2020, at 2:12 AM, Dave Taht <dave.taht@gmail.com> wrote:
>
> I don't know how I stumbled across this, but it seemed interesting at
> this late hour. I wonder if they kept at it or tried ecn also.
>
> "A Model Predictive Control Approach to Flow Pacing for TCP"
>
> "we propose a different approach to latency based congestion control.
> In particular, our controller sets the maximum pacing rate by solving
> a model-based receding horizon control problem at each time step. Each
> new roundtrip time (RTT) measurement is first incorporated into a
> linear time-varying (LTV) predictive model. Subsequently, we solve a
> one-step look-ahead optimization problem which finds the pacing rate
> which optimally trades off RTT, RTT variance, and throughput according
> to the most recent model. Our method is computationally inexpensive
> making it readily implementable on current systems."
>
> https://people.eecs.berkeley.edu/~dfk/pdfs/network_control_camera_ready.pdf
>
>
> --
> Make Music, Not War
>
> Dave Täht
> CTO, TekLibre, LLC
> http://www.teklibre.com
> Tel: 1-831-435-0729
next prev parent reply other threads:[~2020-02-09 18:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-09 7:11 Dave Taht
2020-02-09 18:21 ` David Fridovich-Keil [this message]
2020-02-09 23:09 ` Jeremy Harris
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=F0E548C9-4F68-43D4-82F5-BB04F5AC5D2A@berkeley.edu \
--to=dfk@berkeley.edu \
--cc=bloat@lists.bufferbloat.net \
--cc=chapmanm@eecs.berkeley.edu \
--cc=dave.taht@gmail.com \
--cc=dfk@eecs.berkeley.edu \
--cc=dghosal@ucdavis.edu \
--cc=ecn-sane@lists.bufferbloat.net \
--cc=mkfarrens@ucdavis.edu \
--cc=nhanford@ucdavis.edu \
--cc=tomlin@eecs.berkeley.edu \
/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