[189767] in North American Network Operators' Group
Re: Netflix VPN detection - actual engineer needed
daemon@ATHENA.MIT.EDU (Steven Noble)
Mon Jun 6 15:35:19 2016
X-Original-To: nanog@nanog.org
Date: Mon, 06 Jun 2016 12:35:23 -0700
From: Steven Noble <snoble@sonn.com>
To: Aled Morris <aledm@qix.co.uk>
In-Reply-To: <CAO1bj=aaDWcYVj23u3nt1_S_ftrMdkss9cwohxHsFrRBsUnGMA@mail.gmail.com>
Cc: NANOG <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
It's obviously a nontrivial number otherwise why would Netflix block it? :)
Aled Morris wrote:
>
> Maybe HE's IPv6 tunnel packets could be flagged with a destination option
> (extension header field) that records the end-user's IPv4 tunnel endpoint
> so geolocation could be done in the "old fashioned" way on that address.
>
> Similar to the way that edns-client-subnet records the end user's address
> for geolocation purposes.
>
> I have to say though, how many Netflix customers are using HE IPv6
> tunnels,
> really? zero percent (to two decimal places)?
>
> Aled
