Uhm I think you misunderstood me. What you describe matches what I described. I never suggested the user can override it with it another value, I am suggesting that a user may want to keep it to whatever default value it is as a matter of privacy concerns. Otherwise use the IPv4 tunnel end point IP.
As for the point about people moving around frequently I would consider that a pretty far reaching use case and most likely not worth considering any action for. On Thu, Jun 9, 2016 at 10:19 AM, Matthew Huff <mh...@ox.com> wrote: > I think you are missing the point. The problem is not that the GeoIP info > is missing, the problem with the HE.tunnel is that the GeoIP is not set by > the provider by verifiable means. Letting end-users set their GeoIP > information is a non-starter for the content provider and they would still > require a ban. > > A solution would be for HE to automatically set the IPv6 geoip based on > the geoip of the IPv4 source address with no user overrides. Since the > whole process would be fragile (people change their IPv4 source address > frequently when travelling, etc...) and the delay it takes to put the GeoIP > into maxmind's database, etc..., I don't know how well it would work, but > it would probably be the best bet. > > ---- > Matthew Huff | 1 Manhattanville Rd > Director of Operations | Purchase, NY 10577 > OTA Management LLC | Phone: 914-460-4039 > aim: matthewbhuff | Fax: 914-694-5669 > > > > -----Original Message----- > > From: NANOG [mailto:nanog-boun...@nanog.org] On Behalf Of Michael Still > > Sent: Thursday, June 9, 2016 10:10 AM > > To: John Lightfoot <jlightf...@gmail.com> > > Cc: North American Network Operators' Group <nanog@nanog.org> > > Subject: Re: Netflix banning HE tunnels > > > > I wonder how hard it would be for HE to implement some button on their > > tunnel portal that when selected will update Maxmind's (or whatever) > > geolocation for their allocated IPv6 prefixes to match the results > > returned > > when querying for their IPv4 tunnel end point address... > > > > I would suggest to make it optional since some may not want to have > > this > > functionality by default but if you are dying for netflix and are in > > whatever geolocation netflix deems acceptable this may solve the issue. > > > > > > > > On Wed, Jun 8, 2016 at 5:39 PM, John Lightfoot <jlightf...@gmail.com> > > wrote: > > > > > How about: > > > > > > Dear Netflix network engineer who’s on the NANOG list. Could you > > please > > > get Netflix to fall back to ipv4 if you block your customer’s ipv6 > > because > > > it’s in an HE tunnel? Lots of people who want to watch Netflix, be > > able to > > > reach the whole internet, and have Verizon FiOS would really > > appreciate it. > > > > > > Thanks, > > > John > > > > > > John Lightoot > > > > > > > > > > > > > > > -- > > [stillwa...@gmail.com ~]$ cat .signature > > cat: .signature: No such file or directory > > [stillwa...@gmail.com ~]$ > -- [stillwa...@gmail.com ~]$ cat .signature cat: .signature: No such file or directory [stillwa...@gmail.com ~]$
