[172842] in North American Network Operators' Group
Re: Verizon Public Policy on Netflix
daemon@ATHENA.MIT.EDU (Owen DeLong)
Fri Jul 11 12:44:42 2014
X-Original-To: nanog@nanog.org
From: Owen DeLong <owen@delong.com>
In-Reply-To: <20140711024502.GM32153@hezmatt.org>
Date: Fri, 11 Jul 2014 09:44:58 -0700
To: Matt Palmer <mpalmer@hezmatt.org>
Cc: nanog@nanog.org
Errors-To: nanog-bounces@nanog.org
>> in an attempt to force them to host their servers for free
>=20
> These are the OpenConnect caching boxes, I assume? If that's the =
case, it's
> incorrect to say that Netflix "refuses to allow [...] caching", simply =
that
> they prefer to provide caching their way. As it stands, I don't see =
the
> problem with running Netflix cacheboxes instead of your own -- if you =
*were*
> running the cache, you would presumably need to pay for hosting anyway =
(and
> also machines), so I'm not sure how OpenConnect is worse. If there =
are=20
> reasons why OpenConnect boxes *are* inferior to some other solution =
(such as
> if they take up 20 times the power and space of an equivalent caching
> solution), then those are what need to be talked about.
One could make a somewhat valid argument that the =93OpenConnect=94 =
caches are
limited to caching Netflix and thus not very =93open=94 whereas a cache =
that I
was hosting for myself could cache a variety of content sources and not =
just
Netflix.
Would it really be plausible for a small ISP to host caching clusters =
for
every streaming content supplier out there?
Don=92t get me wrong, I think that the access networks are the ones that =
are failing
their customers in this scenario over all, but I can see this one valid =
aspect
to the argument above.
Owen
