From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp89.iad3a.emailsrvr.com (smtp89.iad3a.emailsrvr.com [173.203.187.89]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 974ED3B25E for ; Tue, 26 Jul 2016 17:31:56 -0400 (EDT) Received: from smtp4.relay.iad3a.emailsrvr.com (localhost [127.0.0.1]) by smtp4.relay.iad3a.emailsrvr.com (SMTP Server) with ESMTP id 62DE4C0139; Tue, 26 Jul 2016 17:31:56 -0400 (EDT) Received: from app14.wa-webapps.iad3a (relay-webapps.rsapps.net [172.27.255.140]) by smtp4.relay.iad3a.emailsrvr.com (SMTP Server) with ESMTP id 59ABEC03C3; Tue, 26 Jul 2016 17:31:56 -0400 (EDT) X-Sender-Id: dpreed@reed.com Received: from app14.wa-webapps.iad3a (relay-webapps.rsapps.net [172.27.255.140]) by 0.0.0.0:25 (trex/5.5.4); Tue, 26 Jul 2016 17:31:56 -0400 Received: from reed.com (localhost [127.0.0.1]) by app14.wa-webapps.iad3a (Postfix) with ESMTP id 474C36144E; Tue, 26 Jul 2016 17:31:56 -0400 (EDT) Received: by apps.rackspace.com (Authenticated sender: dpreed@reed.com, from: dpreed@reed.com) with HTTP; Tue, 26 Jul 2016 17:31:56 -0400 (EDT) Date: Tue, 26 Jul 2016 17:31:56 -0400 (EDT) From: dpreed@reed.com To: "Dave Taht" Cc: "cerowrt-devel@lists.bufferbloat.net" MIME-Version: 1.0 Content-Type: text/plain;charset=UTF-8 Content-Transfer-Encoding: quoted-printable Importance: Normal X-Priority: 3 (Normal) X-Type: plain In-Reply-To: References: X-Auth-ID: dpreed@reed.com Message-ID: <1469568716.289512443@apps.rackspace.com> X-Mailer: webmail/12.5.2-RC Subject: Re: [Cerowrt-devel] not exactly the most positive outcome X-BeenThere: cerowrt-devel@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: Development issues regarding the cerowrt test router project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Jul 2016 21:31:56 -0000 It's a terrible outcome. However, there is literally no significant suppor= t for the alternative, either from a policy basis or from entrepreneurial f= olks. N-O-N-E.=0A=0AI 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).=0A=0APeople just take for gran= ted 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 L= abs created the Internet and the WWW.=0A=0A=0A=0AOn Tuesday, July 26, 2016 = 1:23pm, "Dave Taht" said:=0A=0A> From: https://www.ci= rrent.com/emerging-wi-fi-trends/=0A> =0A> "As Wi-Fi becomes a bigger part o= f our daily lives, expect that our=0A> broadband ISPs will likely move to e= xtend their demarcation=0A> point(demarc for short). This demarc will quick= ly shift away from=0A> where it resides today, on the cable modem or DSL ro= uter, to the air=0A> interface on the Wi-Fi access points in our home. Carr= iers have=0A> already been using Wi-Fi enabled cable modems and DSL routers= for some=0A> years now. However, with the advances I=E2=80=99ve mentioned,= I expect to see=0A> almost every broadband ISP offer an in-home Wi-Fi mesh= solution as a=0A> standard part of their broadband service over the next t= wo to three=0A> years.=0A> =0A> The main motivation for the ISPs is to quic= kly get to a point where=0A> they can offer their users a high quality, sec= ure Wi-Fi network that=0A> provides improved coverage throughout the whole = home. These=0A> carrier-controlled Wi-Fi mesh networks will allow us to sti= ll have our=0A> private networks running alongside their networks and both = will run on=0A> the same equipment. The upshot is that we won=E2=80=99t hav= e to buy our own=0A> Wi-Fi mesh solutions and will be able to use those pro= vided by our=0A> ISPs, like the vast majority of us already do today."=0A> = =0A> =0A> =0A> =0A> --=0A> Dave T=C3=A4ht=0A> Let's go make home routers an= d wifi faster! With better software!=0A> http://blog.cerowrt.org=0A> ______= _________________________________________=0A> Cerowrt-devel mailing list=0A= > Cerowrt-devel@lists.bufferbloat.net=0A> https://lists.bufferbloat.net/lis= tinfo/cerowrt-devel=0A> =0A