Hi all, While following this thread, it occurred to me that one issue not being discussed is Netflix's encouragement to revert to IPv4. Of course, that is fairly easy with NAT, but the principle is one that makes me feel very uncomfortable. We work so hard to see IPv6 expanded, it feels like a small setback -- or at least a jab -- coming from such a large company.
Thus, the question I pose to the community is this: are there any redress mechanisms we can use to address this situation at the core of the issue, i.e., with Netflix, and help them work out solutions -- like some of the ones offered so far -- to not discourage IPv6? This can include meetings, mobilizing networks, relationship building, outreach, etc. Best, -Michael __________________ Michael J. Oghia Independent consultant & editor 2015 ISOC IGF Ambassador Istanbul, Turkey Skype: mikeoghia Twitter <https://www.twitter.com/MikeOghia> *|* LinkedIn <https://www.linkedin.com/in/mikeoghia> On Wed, Jun 15, 2016 at 3:06 AM, Noel Butler <[email protected]> wrote: > Robert, > > Yes it's regrettable, but HE don't allocate ipv6 ranges on their TB > service by country, I too use them, and our ranges could be side by side, > and thats how netflix sees it, so they block HE's tunnels ipv6 ranges. I'm > not sure if they also block ipv6 ranges that are for HE native use, like in > their colos etc, possibly they do that too. > > Cheers > > > > On 15/06/2016 09:42, Robert Hosford wrote: > >> Noel, >> >> . I have been using HE for almost 10 years and they have been awesome. >> Verizon FIOS doesn't offer IPv6 or I would go native. However I am >> dual stacked on my Verizon phone, works fine with Netflix. >> >> I see this blocking as being laziness on the part of Netflix. When >> the account is setup a geo location tag can be setup that this is a US >> based IPv6 tunnel. >> >> I am in the US and all of my traffic is in the US. >> >> I like HE because I have noticed that my IPv6 traffic over HE is >> faster than my IPv4 over Verizon's network. And it is free. >> >> C:\Windows\system32>ping www.google.com >> >> Pinging www.google.com [2607:f8b0:4004:80e::2004] with 32 bytes of data: >> Reply from 2607:f8b0:4004:80e::2004: time=1ms >> Reply from 2607:f8b0:4004:80e::2004: time=5ms >> Reply from 2607:f8b0:4004:80e::2004: time=6ms >> Reply from 2607:f8b0:4004:80e::2004: time=9ms >> >> See I just love HE. >> >> Oh I also pay for the HD Netflix and it buffers and still looks like >> crap. I had better Netflix performance over HE than I do with Verizon. >> >> For a company that consumes so much of the Internet blocking us is >> just a slap in the face. >> >> Thanks, >> >> Robert >> >> -----Original Message----- >> From: [email protected] >> [mailto:[email protected]] >> On Behalf Of Noel Butler >> Sent: Sunday, June 12, 2016 11:04 PM >> To: [email protected] >> Subject: Re: Netflix hates IPv6 >> >> On 13/06/2016 06:46, Robert Hosford wrote: >> >>> >>> >>> Unless you use HE like I do. Nice Job Netflix..... >>> >>> Robert >>> >> >> Do you use HE tunnel? or native ipv6? netflix are blocking HE >> tunnelbroker services because of fun police copyright cops narky about >> geoblock avoidance, why should you pay the same cheap price as in US >> when they can make you pay 25-40% more because your from another >> country for exact same thing ;) >> >> this has recently started which leads me to think this is your problem >> >> -- >> If you have the urge to reply to all rather than reply to list, you >> best first read http://members.ausics.net/qwerty/ >> > > -- > If you have the urge to reply to all rather than reply to list, you best > first read http://members.ausics.net/qwerty/ >
