General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Jan Ceuleers <jan.ceuleers@gmail.com>
To: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] [Cerowrt-devel] beating the drum for BQL
Date: Fri, 24 Aug 2018 08:16:18 +0200	[thread overview]
Message-ID: <0d937b41-4f43-f89e-d30b-a0716556060f@gmail.com> (raw)
In-Reply-To: <7D711CA2-892C-4D0B-AE68-31703EBBBF3E@gmx.de>

On 24/08/18 01:35, Sebastian Moeller wrote:
> 	Sure, but my ISP charged 4 EUR per month for the DSL-router that adds up to 12*2*4 = 96 EUR over the 2 years contract duration and to 12*5*4 = 240 over my renting duration; assuming that my ISP does not need to make a profit on this device (after all I am renting this to be able to consume internet and telephone from them) that is considerably more that 20-40 EUR. This is especially farcical since until a few years ago the dsl-routers have been given for "free" and when they switched to mandatory renting the baseplan price was not reduced by the same amount. I guess what I want to convey is while cost is imprtant it is not a goo d excuse to distribute underpowered devices....

A few points:

1. The CPE makers sell these devices to ISPs wholesale. The price point
they have to design to is determined by those ISPs' willingness to pay,
which is also influenced/co-determined by the market price. What ISPs
manage to rake in over the technical life span of those devices has
nothing to do with it - the CPE makers don't get a cut of the rental
charges. The economics explain the behaviour of both the ISP and the CPE
maker very well - nothing's going to change without some substantial
disruption.

2. Mandatory rental of CPE is a racket that's seen in various markets
(e.g. STBs in the cable market). It is more defendable in some
situations than in others. For example cable companies get away with it
because of a lack of sufficient standardisation (which is also not going
to be improved to the point where the STB market can be completely
opened because the standards are set by a cable industry body).

It's not so defendable in the DSL market anymore, although I can tell
you from experience that there's a lot of very poor DSL modems out there
which cause interop problems in the real world, including interference
with other people's DSL lines. The network operator having firm control
of which DSL modems are permitted onto their network helps performance
for all of their customers. But this can also be achieved by means other
than mandatory rental of CPE: there are countries where the regulator
oversees a DSL modem certification scheme, and end-users can then go out
and buy a certified device through their preferred retail outlet, at
very reasonable prices.

FWIW I bought three STBs for 50EUR from my cable company 5 years ago,
rather than renting them for 7EUR/month each.

3. ISPs and network operators will buy the cheapest CPE that meets their
needs. In respect of traffic throughput they will invariably use Ookla
to test. This is why I've been saying for quite some time that unless we
can convince Ookla to penalise bufferbloat we won't make a dent in how
CPE are designed in this respect.

Jan

  parent reply	other threads:[~2018-08-24  6:16 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-23  0:49 [Bloat] " Dave Taht
2018-08-23  5:47 ` Mikael Abrahamsson
2018-08-23 13:06   ` [Bloat] [Cerowrt-devel] " Sebastian Moeller
2018-08-23 13:57     ` Jan Ceuleers
2018-08-23 14:22       ` Sebastian Moeller
2018-08-23 15:32         ` Mikael Abrahamsson
2018-08-23 17:14           ` Rosen Penev
2018-08-23 17:50             ` Mikael Abrahamsson
2018-08-23 18:21               ` Dave Taht
2018-08-23 20:15                 ` Dave Taht
2018-08-24  7:00                   ` Mikael Abrahamsson
2018-08-24  8:06                     ` Dave Taht
2018-08-24 11:22                       ` Toke Høiland-Jørgensen
2018-08-24 11:46                       ` Jan Ceuleers
2018-08-24 13:43                         ` Jan Ceuleers
2018-08-24 13:44                           ` Mikael Abrahamsson
2018-08-24 13:56                             ` Jan Ceuleers
2018-08-24 13:36                       ` Mikael Abrahamsson
2018-08-24  7:05                   ` Mikael Abrahamsson
2018-08-24 11:24                     ` Toke Høiland-Jørgensen
2018-08-23 21:01                 ` Toke Høiland-Jørgensen
2018-08-24 14:44                   ` Dave Taht
2018-08-24 17:58                     ` Toke Høiland-Jørgensen
2018-08-23 23:35           ` Sebastian Moeller
2018-08-24  1:08             ` David Collier-Brown
2018-08-24  6:16             ` Jan Ceuleers [this message]
2018-08-24 11:27           ` Toke Høiland-Jørgensen
2018-08-24 12:46             ` Pedro Tumusok
2018-08-24 13:09             ` Michael Richardson
2018-08-24 13:37             ` Mikael Abrahamsson
2018-08-24 13:44               ` Toke Høiland-Jørgensen
2018-08-26  4:29           ` [Bloat] Marvell 385 Dave Taht
2018-08-26  4:32             ` Jonathan Morton
2018-08-26 16:28             ` Rosen Penev
2018-08-26 18:44             ` Mikael Abrahamsson
2018-08-26 20:53               ` Dave Taht
2018-08-26 20:58               ` Rosen Penev
2018-08-26 21:08                 ` Dave Taht
2018-08-27  0:55                   ` Rosen Penev
2018-08-27  1:21                     ` Dave Taht
2018-08-27  1:33                       ` Rosen Penev
2018-08-27  1:45                         ` Dave Taht
2018-08-27  1:53                           ` Rosen Penev
2018-08-27 11:33                   ` Mikael Abrahamsson
2018-08-23  8:26 ` [Bloat] beating the drum for BQL Pete Heist
2018-08-23 10:51   ` Mikael Abrahamsson
2018-08-23 11:38     ` Pete Heist
2018-08-24 17:13   ` Pete Heist
2018-08-24 17:30     ` Dave Taht
2018-08-24 18:43       ` Dave Taht

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=0d937b41-4f43-f89e-d30b-a0716556060f@gmail.com \
    --to=jan.ceuleers@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    /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