From: "Joel Wirāmu Pauling" <joel@aenertia.net>
To: David Reed <dpreed@reed.com>
Cc: tapper <j.lancett@ntlworld.com>,
"cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Random thought - reactions?
Date: Sat, 16 Dec 2017 11:45:35 +1300 [thread overview]
Message-ID: <CAKiAkGSrZR10VRcZFndh1q+p6Hp+f2gJcjwh-FGfFgWSX4P-og@mail.gmail.com> (raw)
In-Reply-To: <1513372284.081220590@apps.rackspace.com>
Here in New Zealand ; any provider operating a 'Network of National
Significance' must hand over any encryption keys on demand to what is
our local equivalent of the NSA. This makes a very high disincentive
for anyone to provide end to end encryption by design in their access
and transport networks. I would wager the US is likely to see a
similar provision to combat this sort of approach getting commercial
backing.
Whilst I completely agree this sort of this is needed, not being able
to create commercial services off it that are user-transparent is a
big barrier. Because for this approach to work you need as many people
to opt in as possible.
-Joel
On 16 December 2017 at 10:11, <dpreed@reed.com> wrote:
> Thanks for this. I hadn't seen it yet.
>
>
>
> On Friday, December 15, 2017 2:32pm, "tapper" <j.lancett@ntlworld.com> said:
>
>> Motherboard & VICE Are Building a Community Internet Network
>>
>> https://motherboard.vice.com/en_us/article/j5djd7/motherboard-and-vice-are-building-a-community-internet-network-to-protect-net-neutrality
>> It seems that people are all thinking the same thing, but coming up with
>> different things!
>
> 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 an
> overlay over an already subscribable infrastructure. I wish them well, and 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.
>
>
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>
next prev parent reply other threads:[~2017-12-15 22:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-15 17:18 dpreed
2017-12-15 19:32 ` tapper
2017-12-15 21:11 ` dpreed
2017-12-15 22:45 ` Joel Wirāmu Pauling [this message]
2017-12-15 23:14 ` David Lang
2017-12-18 2:26 ` dpreed
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=CAKiAkGSrZR10VRcZFndh1q+p6Hp+f2gJcjwh-FGfFgWSX4P-og@mail.gmail.com \
--to=joel@aenertia.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dpreed@reed.com \
--cc=j.lancett@ntlworld.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