nanog mailing list archives

Re: Netflix VPN detection - actual engineer needed


From: Cryptographrix <cryptographrix () gmail com>
Date: Sat, 04 Jun 2016 00:39:37 +0000

Yeah today I cancelled Netflix for exactly this reason.

On Fri, Jun 3, 2016 at 8:35 PM Owen DeLong <owen () delong com> wrote:

I think the day that Netflix tells me to turn off IPv6 or doesn’t serve me
content
because one of my routes to the internet for IPv6 is via an HE tunnel (the
other
two are different tunnels, but all of my IPv4 also goes through tunnels)
will be the
day I tell Netflix that I will turn them off instead.

Let’s face it folks, if we want to encourage Netflix to tell the content
providers
to give up the silly geo-shit, then we have to stop patronizing channels
that do
silly geo-shit.

The only real impact is to vote with your $$$ and tell the companies you
are
unsubscribing from exactly why you are unsubscribing.

So far, I haven’t run into an issue where I couldn’t get what I wanted to
watch
via a tunnel I was able to set up. When/If Netflix gets good enough to
detect
and block my tunnel, I’ll stop using Netflix and stop paying them. I’ll
also
make sure that they know why.

I’m sure if they lose enough customers for this reason, they’ll choose to
do something
about it with their content providers. After all, the fewer subscribers
Netflix has,
the less they pay the content providers, too.

Sure, nobody cares about my $10/month or whatever it’s up to these days,
but if a
few thousand of us start walking off and it starts to look like a trend,
it can
change things.

Owen

On Jun 3, 2016, at 17:17 , Cryptographrix <cryptographrix () gmail com>
wrote:

Very true. Telling people to turn off IPv6 support through their customer
service portal is completely infuriating for those that can't get IPv6
through their ISP and need it.


On Fri, Jun 3, 2016 at 8:13 PM Spencer Ryan <sryan () arbor net> wrote:

Yes but HE doesn't serve residential users directly. To a normal person
HE
is no different than NTT/GTT/Verizon/Sprint/Any other transit carrier.
They
may move the most v6 traffic, but Comcast is the largest ISP actually
getting v6 to end users.


*Spencer Ryan* | Senior Systems Administrator | sryan () arbor net
*Arbor Networks*
+1.734.794.5033 (d) | +1.734.846.2053 (m)
www.arbornetworks.com

On Fri, Jun 3, 2016 at 8:07 PM, Cryptographrix <
cryptographrix () gmail com>
wrote:

I don't remember the source, but I do remember that even with Comcast's
deployment, HE still represented the majority of IPv6 traffic in the
US.

Of course, it could just be a bunch of us heavy IPv6 users.



On Fri, Jun 3, 2016 at 8:03 PM Spencer Ryan <sryan () arbor net> wrote:

Comcast is near 100% on their DOCSIS network (Busniess and
residential).
That should be the largest single ISP for IPv6 for end users in the
USA.


*Spencer Ryan* | Senior Systems Administrator | sryan () arbor net
*Arbor Networks*
+1.734.794.5033 (d) | +1.734.846.2053 (m)
www.arbornetworks.com

On Fri, Jun 3, 2016 at 7:49 PM, Cryptographrix <
cryptographrix () gmail com
wrote:

Depends - how many US users have native IPv6 through their ISPs?

If I remember correctly (I can't find the source at the moment),
HE.net
represents something like 70% of IPv6 traffic in the US.

And yeah, not doing that - actually in the middle of an IPv6 project
at
work at the moment that's a bit important to me.




On Fri, Jun 3, 2016 at 7:45 PM Baldur Norddahl <
baldur.norddahl () gmail com>
wrote:

Den 4. jun. 2016 01.26 skrev "Cryptographrix" <
cryptographrix () gmail com>:

The information I'm getting from Netflix support now is explicitly
telling
me to turn off IPv6 - someone might want to stop them before they
completely kill US IPv6 adoption.

Not allowing he.net tunnels is not killing ipv6. You just need need
native
ipv6.

On the other hand it would be nice if Netflix would try the other
protocol
before blocking.









Current thread: