Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: "David P. Reed" <dpreed@deepplum.com>
Cc: Dave Taht <dave.taht@gmail.com>,
	Cake List <cake@lists.bufferbloat.net>,
	 cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] https://tools.ietf.org/html/draft-ietf-tsvwg-le-phb-06 is in last call
Date: Mon, 4 Feb 2019 07:02:28 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.2.20.1902040658280.23912@uplift.swm.pp.se> (raw)
In-Reply-To: <1549233729.17269312@apps.rackspace.com>

On Sun, 3 Feb 2019, David P. Reed wrote:

> This fairy story about traffic giving way to higher priority traffic 
> being a normal mode of operation is just that. A made up story, largely 
> used by folks who want to do selective pricing based on what customers 
> are willing to pay, not on value received. (that's a business story,

The point of PHB LE is so that the customer access shaper can background 
the customer LE traffic. It's not intended to be used by ISPs on their 
core links, it's intended for use on the customer access port.

If the customer buys 10 megabit/s Internet access then it's beneficial for 
the customer if the software update download doesn't affect the netflix 
stream and the kids' gameplay. Thus why we're trying to differentiate 
between BE and LE. FQ or CAKE can solve the gameplay, but it can't make 
the netflix stream get 90% of the rest of the capacity and give 5% to the 
software download. LE marking the software download traffic can do that.

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se

  parent reply	other threads:[~2019-02-04  6:02 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-03 18:39 Dave Taht
2019-02-03 20:02 ` Jonathan Morton
2019-02-03 22:42 ` David P. Reed
2019-02-04  0:17   ` Dave Taht
2019-02-04  1:12   ` [Cerowrt-devel] [Cake] " Jonathan Morton
2019-02-04  6:02   ` Mikael Abrahamsson [this message]
2019-02-04  6:58     ` Dave Taht
2019-02-04  7:11       ` Mikael Abrahamsson
2019-02-04 10:23         ` Dave Taht
2019-02-04 10:34           ` Mikael Abrahamsson
2019-02-04 10:40             ` Dave Taht
2019-08-21 15:07 ` [Cerowrt-devel] " Dave Taht
2019-08-21 16:38   ` [Cerowrt-devel] [Cake] " Kevin Darbyshire-Bryant
2019-08-21 16:52     ` Dave Taht
2019-08-22  6:11       ` Mikael Abrahamsson

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.20.1902040658280.23912@uplift.swm.pp.se \
    --to=swmike@swm.pp.se \
    --cc=cake@lists.bufferbloat.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    --cc=dpreed@deepplum.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