Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: dpreed@reed.com
Cc: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] not exactly the most positive outcome
Date: Wed, 27 Jul 2016 07:38:11 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.02.1607270731450.2309@uplift.swm.pp.se> (raw)
In-Reply-To: <1469568716.289512443@apps.rackspace.com>

On Tue, 26 Jul 2016, dpreed@reed.com wrote:

> People just take for granted that having their communications controlled 
> "end-to-end" by some third party (e.g. The Phone Company) is optimal for 
> them.  After all, AT&T Bell Labs created the Internet and the WWW.

"people" (the general term) just want their Internet access to work. They 
don't want to learn how to set it up themselves, they don't want to muck 
around in boxes, and they want it to be cheap, fast and rock solid, all 
the time. They want to set it up once and work great and don't want to 
have to think about it again.

They also call the ISP and complain that the ISP service is bad when they 
stuck the ISP wifi enabled residential gateway in the back of some lower 
corner cabinet behind all the stuff, and hoped they never would have to 
see or interact with it again.

With speed increasing, 5GHz, potentially 60GHz etc, in order to deliver a 
decent service to their customers, ISPs have to get involved in their 
customers' residential wifi networks to retain and hopefully increase 
customer satisfaction.

So with that out of the way, how do we still make this as open and 
flexible as possible? Lots of startups and established vendors are 
pitching these solutions to the ISPs, most of them with their own 
proprietary extensions and non-interworking protocols. What's the open and 
flexible alternative?

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

  reply	other threads:[~2016-07-27  5:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-26 17:23 Dave Taht
2016-07-26 21:31 ` dpreed
2016-07-27  5:38   ` Mikael Abrahamsson [this message]
2016-07-28 10:28     ` 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/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.1607270731450.2309@uplift.swm.pp.se \
    --to=swmike@swm.pp.se \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dpreed@reed.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