From: "Richard Scheffenegger" <rscheff@gmx.at>
To: "Dave Taht" <dave.taht@gmail.com>, "bloat" <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] "a bandwidth breakthrough"
Date: Sun, 4 Nov 2012 16:46:56 +0100 [thread overview]
Message-ID: <3C85833A88FF47348064332114D679DE@srichardlxp2> (raw)
In-Reply-To: <CAA93jw7VPasw6zoVzsusxe_4s+VMd313W9BuKZiPA+ALo8jLvQ@mail.gmail.com>
Aparently, Google is also looking into some form of FEC - transparant to
legacy TCP though, and potentially adaptive...
Don't have any details other an overheard conversation at some place...
Regards,
Richard
----- Original Message -----
From: "Dave Taht" <dave.taht@gmail.com>
To: "bloat" <bloat@lists.bufferbloat.net>
Sent: Tuesday, October 23, 2012 10:24 PM
Subject: [Bloat] "a bandwidth breakthrough"
I've had 3 separate people send me this today.
http://www.technologyreview.com/news/429722/a-bandwidth-breakthrough/
Sure wish we had a PR dept here that was this good vs a vs fq_codel.
I *think* I've read the relevant paper "Modeling network coded TCP
throughput"? But perhaps there is something newer driving this
announcement?
--
Dave Täht
Fixing bufferbloat with cerowrt:
http://www.teklibre.com/cerowrt/subscribe.html
_______________________________________________
Bloat mailing list
Bloat@lists.bufferbloat.net
https://lists.bufferbloat.net/listinfo/bloat
prev parent reply other threads:[~2012-11-04 15:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-23 21:24 Dave Taht
2012-10-24 0:39 ` Jonathan Morton
2012-10-24 14:49 ` Albert Rafetseder
2012-10-24 15:54 ` Jonathan Morton
2012-11-04 15:46 ` Richard Scheffenegger [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/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=3C85833A88FF47348064332114D679DE@srichardlxp2 \
--to=rscheff@gmx.at \
--cc=bloat@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
/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