Netflix hates IPv6

Michael Oghia mike.oghia at gmail.com
Wed Jun 15 11:00:50 CEST 2016


Hi Mark,

That is a good and constructive suggestion. Forgive me if I'm a broken
record, though, when I ask if Netflix is involved at any level or even
aware of this discussion? If not, it seems advantageous to me to invite
them to be included.

Best,
-Michael


On Wed, Jun 15, 2016 at 11:57 AM, Townsley.net <mark at townsley.net> wrote:

>
> Apologies if this has already been suggested, but...
>
> How hard would it be for HE to provide a an API for Netflix to query for
> HE prefixes?
>
> For any given v6 address, HE should have a mapping for the associated
> (IPv4) tunnel source address readily available. Netflix would query HE and
> in turn perform the geolocation check based on the tunnel source.
>
> Sure, there's a little work to do here by HE and Netflix, including a UI
> for user opt-in/out, but for the "honest" tunnel user not trying to
> circumvent the system, perhaps it's a constructive way forward? (and
> generally applicable for other providers doing the same)
>
> - Mark
>
> On Jun 15, 2016, at 10:18, Michael Oghia <mike.oghia at gmail.com> wrote:
>
> Hi Brandon,
>
> Thank you for your insight on this and for linking to your past statement.
> It would be great if someone from Netflix could get involved in the
> discussion. Has this ever happened before? Of course, speaking among
> ourselves without their input or without them being invested in any process
> that seeks to change it is, frankly, pointless. From what I gather from
> your message, at least one improvement could be to technical support.
>
> Has anyone ever reached out to someone or one of their contacts who works
> with Netflix, especially someone regarding this issue/area?
>
> Best,
> -Michael
>
>
> On Wed, Jun 15, 2016 at 11:12 AM, Brandon Butterworth <brandon at bogons.net>
> wrote:
>
>> On Wed Jun 15, 2016 at 08:57:03AM +0300, Michael Oghia wrote:
>> > While following this thread, it occurred to me that one issue not being
>> > discussed is Netflix's encouragement to revert to IPv4
>>
>> They could do that better, instead of just telling users to turn off v6
>> they might explain that it's because they are using a tunnel/vpn and
>> that they should ask their ISP for native IPv6 instead.
>>
>> I don't know the numbers involved but they may have decided that a few
>> tunnel users should be able to figure that for themselves if they
>> already figured out how to set up a tunnel. Or they are just giving
>> the lazy answer (and expect ISPs to sort it out when they roll out
>> native IPv6)
>>
>> This has all been done to death on the nanog list (my contribution to
>> the noise is below)
>>
>> > 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.
>>
>> I suspect nothing will change (speaking for netflix while guessing
>> the likely reason so there may be more to this)
>>
>> brandon
>>
>> ----- Begin Included Message -----
>> >From nanog-bounces at nanog.org  Sat Jun  4 11:52:29 2016
>> From: Brandon Butterworth <brandon at rd.bbc.co.uk>
>> To: cryptographrix at gmail.com, owen at delong.com
>> Subject: Re: Netflix VPN detection - actual engineer needed
>> Cc: nanog at nanog.org
>>
>> > On Jun 3, 2016, at 17:35 , Owen DeLong <owen at delong.com> wrote:
>> > 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.
>>
>> Correct but it needs a lot to do that.
>>
>> We do the geo thing. I didn't want us to and we didn't for a few years
>> but once the geo people had convinced rights owners it was a viable
>> thing they forced people buying their content to use it. I tried to
>> stop it here and failed but it's never over, people are starting to
>> realise it's silly to annoy people who want your services, you just
>> need to find a way to allow them
>>
>> To be fair to Netflix the tunnel blocking will likely have been driven
>> by their content suppliers asserting their contractual rights to not
>> allow access from certain places.
>>
>> Their content suppliers will have seen people boasting how they use
>> tunnels to get round them and tunnel suppliers advertising their
>> services for doing so. Blame them for the blocking as while it was a
>> personal thing they wouldn't have been bothered much.
>>
>> As usual a few people see an opportunity to make money off something
>> and in the process break it for everyone
>>
>> btw the list of tunnel providers was likely supplied by the same
>> geo ip people, some sell that as an extra.
>>
>> brandon
>> ----- End Included Message -----
>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.cluenet.de/pipermail/ipv6-ops/attachments/20160615/d9794b82/attachment.htm>


More information about the ipv6-ops mailing list