Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: dpreed@reed.com
To: "Dave Taht" <dave.taht@gmail.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] not exactly the most positive outcome
Date: Tue, 26 Jul 2016 17:31:56 -0400 (EDT)	[thread overview]
Message-ID: <1469568716.289512443@apps.rackspace.com> (raw)
In-Reply-To: <CAA93jw4uAM_=hgxAZ_FGSUaE4mtwoCiiUWMpAa-E_S+C3zU=Dw@mail.gmail.com>

It's a terrible outcome.  However, there is literally no significant support for the alternative, either from a policy basis or from entrepreneurial folks. N-O-N-E.

I am biased towards the entrepreneurial side, but have been fighting this on the policy side as well in one form or another since 1994 (when we began trying to legalize UWB).

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.



On Tuesday, July 26, 2016 1:23pm, "Dave Taht" <dave.taht@gmail.com> said:

> From: https://www.cirrent.com/emerging-wi-fi-trends/
> 
> "As Wi-Fi becomes a bigger part of our daily lives, expect that our
> broadband ISPs will likely move to extend their demarcation
> point(demarc for short). This demarc will quickly shift away from
> where it resides today, on the cable modem or DSL router, to the air
> interface on the Wi-Fi access points in our home. Carriers have
> already been using Wi-Fi enabled cable modems and DSL routers for some
> years now. However, with the advances I’ve mentioned, I expect to see
> almost every broadband ISP offer an in-home Wi-Fi mesh solution as a
> standard part of their broadband service over the next two to three
> years.
> 
> The main motivation for the ISPs is to quickly get to a point where
> they can offer their users a high quality, secure Wi-Fi network that
> provides improved coverage throughout the whole home. These
> carrier-controlled Wi-Fi mesh networks will allow us to still have our
> private networks running alongside their networks and both will run on
> the same equipment. The upshot is that we won’t have to buy our own
> Wi-Fi mesh solutions and will be able to use those provided by our
> ISPs, like the vast majority of us already do today."
> 
> 
> 
> 
> --
> Dave Täht
> Let's go make home routers and wifi faster! With better software!
> http://blog.cerowrt.org
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
> 



  reply	other threads:[~2016-07-26 21:31 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 [this message]
2016-07-27  5:38   ` Mikael Abrahamsson
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=1469568716.289512443@apps.rackspace.com \
    --to=dpreed@reed.com \
    --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