[189646] in North American Network Operators' Group
Re: Netflix VPN detection - actual engineer needed
daemon@ATHENA.MIT.EDU (Cryptographrix)
Fri Jun 3 19:55:28 2016
X-Original-To: nanog@nanog.org
In-Reply-To: <CAPPYGuyZ-0DC_c6pxo6pORG_dXTC=Eg4zNtubekiHdJUe20Y2A@mail.gmail.com>
From: Cryptographrix <cryptographrix@gmail.com>
Date: Fri, 03 Jun 2016 23:51:08 +0000
To: Baldur Norddahl <baldur.norddahl@gmail.com>, nanog@nanog.org
Errors-To: nanog-bounces@nanog.org
(and this is coming from someone that has serious issues with IPv6 but
understands that we need to move forward)
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.
>>
>
