Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: dpreed@reed.com
To: "Alan Jenkins" <alan.christopher.jenkins@gmail.com>
Cc: "Dave Taht" <dave.taht@gmail.com>,
	"Jonathan Morton" <chromatix99@gmail.com>,
	"cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] BBR congestion control algorithm for TCP innet-next
Date: Wed, 21 Sep 2016 13:04:48 -0400 (EDT)	[thread overview]
Message-ID: <1474477488.832416984@apps.rackspace.com> (raw)
In-Reply-To: <4a1fd48e-b1c4-2e75-d55a-417a83a572d4@gmail.com>

On Wednesday, September 21, 2016 3:32am, "Alan Jenkins" <alan.christopher.jenkins@gmail.com> said:

> On 20/09/16 21:27, dpreed@reed.com wrote:
> I don't think the source is hard to identify.  It's Sandvine press
> releases.  That's what the periodic stories on Ars Technica are always
> derived from.
> 
> https://www.sandvine.com/pr/2015/12/7/sandvine-over-70-of-north-american-traffic-is-now-streaming-video-and-audio.html

Press releases have almost no scientific verifiability and validity, and Sandvine is self-interested in a biased outcome. (Sad that Ars Technica just repeats these without questioning the numbers). In the past, I have actually questioned Sandvine directly, and had friends in the measurement community have asked for the raw data and methodology.  The response: "trade secrecy" and "customer privacy" prevent release of both raw data and methods.

If one is predisposed to "like" the result, one then repeats it as a "citation" often omitting the actual source and quoting the place where it appeared (e.g. Ars Technica said, rather than Sandvine said).

This is how propaganda works. It's exactly how propaganda works - I happen to have propaganda textbooks from the late 1940's that have chapters about these techniques.

Of course, the best propaganda is the stuff that you can get engineers in the field to promulgate based on their "gut feel".


  reply	other threads:[~2016-09-21 17:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-17 21:11 dpreed
2016-09-17 21:33 ` Dave Taht
2016-09-19 20:26   ` Dave Taht
2016-09-20 20:27     ` dpreed
2016-09-21  6:24       ` Mikael Abrahamsson
2016-09-21 16:57         ` dpreed
2016-09-21  7:32       ` Alan Jenkins
2016-09-21 17:04         ` dpreed [this message]
2016-09-21 18:00           ` Mikael Abrahamsson
2016-09-21 21:13             ` dpreed
2016-09-21 18:42       ` Alan Jenkins
2016-09-21 21:10         ` dpreed

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=1474477488.832416984@apps.rackspace.com \
    --to=dpreed@reed.com \
    --cc=alan.christopher.jenkins@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=chromatix99@gmail.com \
    --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