Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: David Lang <david@lang.hm>
To: Dave Taht <dave.taht@gmail.com>
Cc: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] SInce I mentioned this crew's work in a post, I don't want anyone to be surprised.
Date: Tue, 6 Jan 2015 11:43:18 -0800 (PST)	[thread overview]
Message-ID: <alpine.DEB.2.02.1501061142110.2502@nftneq.ynat.uz> (raw)
In-Reply-To: <CAA93jw7umN2c4B9VSEU93wCP2jDNPr70aqsNen4PJ3UkQJ9S1w@mail.gmail.com>

[-- Attachment #1: Type: TEXT/PLAIN, Size: 1419 bytes --]

On Tue, 6 Jan 2015, Dave Taht wrote:

> On Tue, Jan 6, 2015 at 9:26 AM,  <dpreed@reed.com> wrote:
>> GoGo does not need to run “Man in the Middle Attacks” on YouTube
>
> re: http://www.reed.com/blog-dpr/?p=174
>
> I amplified via g+ and mentioned to slashdot.
> (http://slashdot.org/submission/4107907/gogo-airline-network-blocks-youtube-when-they-could-just-fix-their-bufferbloat
> )  I don't use reddit, but if someone here wants to hit this topic
> there, perhaps it will help.
>
> I am very perturbed by the https interception stuff and agree that
> they should fix their bufferbloat instead! So should amtrak and other
> services trying to provide general useful email and web services when
> they too have limited bandwidth... in an age where people want dancing
> cat videos on the move and are completely ignorant of the hit on the
> network that induces.
>
> I have quite a few benchmarks of Gogo in flight. They all suck. I
> think the best deployable solution would require reworking their
> satellite uplink management to be available bandwidth aware...
> although I think they could get quite a lot of mileage out of merely
> rate limiting and fq_codeling at the airplane itself.
>
> I note that we have not extensively tested fq_codel at the latencies
> typically experienced here and probably should!

does anyone know someone on a satellite connection? I think I know one person 
who is.

David Lang

  reply	other threads:[~2015-01-06 19:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-06 17:26 dpreed
2015-01-06 19:37 ` Dave Taht
2015-01-06 19:43   ` David Lang [this message]
2015-01-06 19:50   ` Jim Gettys
2015-01-19 19:17   ` Aaron Wood

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/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.DEB.2.02.1501061142110.2502@nftneq.ynat.uz \
    --to=david@lang.hm \
    --cc=cerowrt-devel@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