Re: S.Korea broadband firm sues Netflix after traffic surge

[Xavier Beaudouin via NANOG]

Hello,

>  Providing access is mostly fixed costs, as there are very few consumables in
>  running a network.
> 
>  IP transit costs aren't an issue, since Netflix will do settlement free 
> peering.
> 
>  This leaves the internal network of SK Telecom as the problem and cost 
> center.

Even with that. Netflix can also host at their point of presence their proxies.
Remember the proxies can push up to 400Gbps of stuff with about 500W of power.

So even if they have issues in their network this is their job to make the 
things
done correctly.

Paying just the electricity bill for a bunch of server is less expensive than
buying several 100G long haul links. That's a point and this is their problems 
if
those guys didn't wanted a cache in their network.

Regards,
Xavier

Re: IPv6 woes - RFC

[Xavier Beaudouin via NANOG]

Hello,


> I absolutely HATE testing, developing and supporting IPv4+IPv6, more
> than doubling my time, adding 3rd stack would actually not increase
> cost that much, it's the 1=>2 which is fantastically expensive. And
> costs are transferred to customers.

Dual stack is doubling dev time ? Ok... this is quite strange...
Maybe on testing... but using some standards protocols?

(...)

> Now if we'd know, all of our CDN, cloudyshops and tier1 will start
> dropping IPV4 at edge in 2040, this would create good business reason
> to start developing to IPv6, you'd know you need to have it, and you'd
> know you have finite window when you need to support both.
> And this is something we should commit to do, and everyone would
> benefit from the comment.

Really, the ONLY thing that make IPv6 hell is the bloody war between
Cogent and HE. Imagine this kind of war with IPv4... 
Really guys stop this stupid stuff and make IPv6 Great Again...

Regards,
Xavier