From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp73.iad3a.emailsrvr.com (smtp73.iad3a.emailsrvr.com [173.203.187.73]) (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 6FA0C3B2A4 for ; Fri, 15 Dec 2017 16:11:24 -0500 (EST) Received: from smtp34.relay.iad3a.emailsrvr.com (localhost [127.0.0.1]) by smtp34.relay.iad3a.emailsrvr.com (SMTP Server) with ESMTP id 38BF924EBF; Fri, 15 Dec 2017 16:11:24 -0500 (EST) Received: from app2.wa-webapps.iad3a (relay-webapps.rsapps.net [172.27.255.140]) by smtp34.relay.iad3a.emailsrvr.com (SMTP Server) with ESMTP id 241E224BD4; Fri, 15 Dec 2017 16:11:24 -0500 (EST) X-Sender-Id: dpreed@reed.com Received: from app2.wa-webapps.iad3a (relay-webapps.rsapps.net [172.27.255.140]) by 0.0.0.0:25 (trex/5.7.12); Fri, 15 Dec 2017 16:11:24 -0500 Received: from reed.com (localhost.localdomain [127.0.0.1]) by app2.wa-webapps.iad3a (Postfix) with ESMTP id 142E241159; Fri, 15 Dec 2017 16:11:24 -0500 (EST) Received: by apps.rackspace.com (Authenticated sender: dpreed@reed.com, from: dpreed@reed.com) with HTTP; Fri, 15 Dec 2017 16:11:24 -0500 (EST) X-Auth-ID: dpreed@reed.com Date: Fri, 15 Dec 2017 16:11:24 -0500 (EST) From: dpreed@reed.com To: "tapper" Cc: "cerowrt-devel@lists.bufferbloat.net" MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_20171215161124000000_65321" Importance: Normal X-Priority: 3 (Normal) X-Type: html In-Reply-To: <72295b28-0574-40fc-fbe8-97881e2a362a@ntlworld.com> References: <1513358282.897128026@apps.rackspace.com> <72295b28-0574-40fc-fbe8-97881e2a362a@ntlworld.com> Message-ID: <1513372284.081220590@apps.rackspace.com> X-Mailer: webmail/12.9.10-RC Subject: Re: [Cerowrt-devel] =?utf-8?q?Random_thought_-_reactions=3F?= 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: Fri, 15 Dec 2017 21:11:24 -0000 ------=_20171215161124000000_65321 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable =0AThanks for this. I hadn't seen it yet.=0A =0AOn Friday, December 15, 201= 7 2:32pm, "tapper" said:=0A=0A=0A=0A> Motherboard = & VICE Are Building a Community Internet Network=0A> https://motherboard.vi= ce.com/en_us/article/j5djd7/motherboard-and-vice-are-building-a-community-i= nternet-network-to-protect-net-neutrality=0A> It seems that people are all = thinking the same thing, but coming up with=0A> different things!=0A=0A=0AI= 'm all for what Motherboard and VICE are contemplating. It's a great option= , and may create an interesting opportunity for wireless mobile, too. But t= hat's far more complex to fund and maintain than constructing an overlay ov= er an already subscribable infrastructure. I wish them well, and I hope tha= t the key idea of maximizing interoperability of all functions (including p= aying for upstream capacity) will be front and center in their minds. Balka= nization of the subnets of the public Internet is a big worry - boundaries = will destroy the Internet as effectively as content selectivity and content= -based rate limiting will. ------=_20171215161124000000_65321 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable =0A

Thanks for this. I hadn't = seen it yet.

=0A

 

=0A

On Friday, December 15, 2017 2:32pm, "tapper" <j.lancett@ntlworld.com= > said:

=0A
=0A

> Motherboard & VICE Are Building a Community Interne= t Network
> https://motherboard.vice.com/en_us/article/j5djd7/mothe= rboard-and-vice-are-building-a-community-internet-network-to-protect-net-ne= utrality
> It seems that people are all thinking the same thing, bu= t coming up with
> different things!

=0A

I'm all for what Motherboard and VICE are contemplating. It's a = great option, and may create an interesting opportunity for wireless mobile= , too. But that's far more complex to fund and maintain than constructing a= n overlay over an already subscribable infrastructure. I wish them well, an= d I hope that the key idea of maximizing interoperability of all functions = (including paying for upstream capacity) will be front and center in their = minds. Balkanization of the subnets of the public Internet is a big worry -= boundaries will destroy the Internet as effectively as content selectivity= and content-based rate limiting will.

=0A
 ------=_20171215161124000000_65321--