<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div><br></div><div id="AppleMailSignature">Apologies if this has already been suggested, but...</div><div id="AppleMailSignature"><br></div><div id="AppleMailSignature">How hard would it be for HE to provide a an API for Netflix to query for HE prefixes? </div><div id="AppleMailSignature"><br></div><div id="AppleMailSignature">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. </div><div id="AppleMailSignature"><br></div><div id="AppleMailSignature">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)<br><br><div>- Mark</div></div><div><br>On Jun 15, 2016, at 10:18, Michael Oghia <<a href="mailto:mike.oghia@gmail.com">mike.oghia@gmail.com</a>> wrote:<br><br></div><blockquote type="cite"><div><div dir="ltr">Hi Brandon,<div><br></div><div>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.</div><div><br></div><div>Has anyone ever reached out to someone or one of their contacts who works with Netflix, especially someone regarding this issue/area? </div><div><br></div><div>Best,<br><div><div data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><font size="2" face="arial, helvetica, sans-serif">-Michael</font><div><div dir="ltr"><div dir="ltr"><br></div><div dir="ltr"><br></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div><div class="gmail_quote">On Wed, Jun 15, 2016 at 11:12 AM, Brandon Butterworth <span dir="ltr"><<a href="mailto:brandon@bogons.net" target="_blank">brandon@bogons.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span>On Wed Jun 15, 2016 at 08:57:03AM +0300, Michael Oghia wrote:<br>
> While following this thread, it occurred to me that one issue not being<br>
> discussed is Netflix's encouragement to revert to IPv4<br>
<br>
</span>They could do that better, instead of just telling users to turn off v6<br>
they might explain that it's because they are using a tunnel/vpn and<br>
that they should ask their ISP for native IPv6 instead.<br>
<br>
I don't know the numbers involved but they may have decided that a few<br>
tunnel users should be able to figure that for themselves if they<br>
already figured out how to set up a tunnel. Or they are just giving<br>
the lazy answer (and expect ISPs to sort it out when they roll out<br>
native IPv6)<br>
<br>
This has all been done to death on the nanog list (my contribution to<br>
the noise is below)<br>
<span><br>
> Thus, the question I pose to the community is this: are there any redress<br>
> mechanisms we can use to address this situation at the core of the issue,<br>
> i.e., with Netflix, and help them work out solutions -- like some of the<br>
> ones offered so far -- to not discourage IPv6? This can include meetings,<br>
> mobilizing networks, relationship building, outreach, etc.<br>
<br>
</span>I suspect nothing will change (speaking for netflix while guessing<br>
the likely reason so there may be more to this)<br>
<br>
brandon<br>
<br>
----- Begin Included Message -----<br>
>From <a href="mailto:nanog-bounces@nanog.org" target="_blank">nanog-bounces@nanog.org</a> Sat Jun 4 11:52:29 2016<br>
From: Brandon Butterworth <<a href="mailto:brandon@rd.bbc.co.uk" target="_blank">brandon@rd.bbc.co.uk</a>><br>
To: <a href="mailto:cryptographrix@gmail.com" target="_blank">cryptographrix@gmail.com</a>, <a href="mailto:owen@delong.com" target="_blank">owen@delong.com</a><br>
Subject: Re: Netflix VPN detection - actual engineer needed<br>
Cc: <a href="mailto:nanog@nanog.org" target="_blank">nanog@nanog.org</a><br>
<br>
> On Jun 3, 2016, at 17:35 , Owen DeLong <<a href="mailto:owen@delong.com" target="_blank">owen@delong.com</a>> wrote:<br>
> Letâ's face it folks, if we want to encourage Netflix to tell the<br>
> content providers to give up the silly geo-shit, then we have to<br>
> stop patronizing channels that do silly geo-shit.<br>
<br>
Correct but it needs a lot to do that.<br>
<br>
We do the geo thing. I didn't want us to and we didn't for a few years<br>
but once the geo people had convinced rights owners it was a viable<br>
thing they forced people buying their content to use it. I tried to<br>
stop it here and failed but it's never over, people are starting to<br>
realise it's silly to annoy people who want your services, you just<br>
need to find a way to allow them<br>
<br>
To be fair to Netflix the tunnel blocking will likely have been driven<br>
by their content suppliers asserting their contractual rights to not<br>
allow access from certain places.<br>
<br>
Their content suppliers will have seen people boasting how they use<br>
tunnels to get round them and tunnel suppliers advertising their<br>
services for doing so. Blame them for the blocking as while it was a<br>
personal thing they wouldn't have been bothered much.<br>
<br>
As usual a few people see an opportunity to make money off something<br>
and in the process break it for everyone<br>
<br>
btw the list of tunnel providers was likely supplied by the same<br>
geo ip people, some sell that as an extra.<br>
<br>
brandon<br>
----- End Included Message -----<br>
<br>
<br>
</blockquote></div><br></div></div>
</div></blockquote></body></html>