IPv4 will become a progressively deeper version of hell until we finally turn 
it off.

Fortunately Netflix is running IPv6 for most things already. If you’re an ISP 
and you’re not
allowing them to reach Netflix via IPv6, then you’re part of the problem rather 
than the solution.

Owen

> On Jan 27, 2016, at 12:36 , chris <tknch...@gmail.com> wrote:
> 
> especially if these types of situations are handled on par with the way abuse 
> and spam reports are handled
> 
> customer will report being blocked to netflix, netflix will tell end user to 
> contact isp, customer will call isp  and level 1 call center rep will say "we 
> can ping your modem and your service is up we dont see a problem, if you are 
> having a issue with a specific service please contact your service provider"
> 
> and the infinite loop begins, customer gets frustrated, everyone loses
> 
> welcome to hell :)
> 
> On Wed, Jan 27, 2016 at 3:15 PM, Owen DeLong <o...@delong.com 
> <mailto:o...@delong.com>> wrote:
> 
> > On Jan 27, 2016, at 07:12 , Jared Mauch <ja...@puck.nether.net 
> > <mailto:ja...@puck.nether.net>> wrote:
> >
> >
> >> On Jan 26, 2016, at 7:33 PM, Andrey Yakovlev <andy.ya...@ya.ru 
> >> <mailto:andy.ya...@ya.ru>> wrote:
> >>
> >> One user had his wife sharing his Netflix account on her iPad while on a 
> >> conference to Europe (same account, different countries).
> >
> > Hmm, I seem to think this one might be quite common, so perhaps should be 
> > tied closer to the device vs account level.
> >
> > - Jared
> 
> This is all going to get a whole lot more entertaining with the combination 
> of MIP6 and IPv4 CGNAT.
> 
> Owen
> 
> 

Reply via email to