[rpd] IPv6 and some cloud providers

[Owen DeLong]

> On May 31, 2020, at 13:59 , Mark Tinka <mark.tinka at seacom.mu> wrote:

> 

> 

> 

> On 31/May/20 19:21, Owen DeLong wrote:

>> How does one provide the hardware platform and let the customer run their own OS without also providing the network infrastructure that connects that hardware platform to, well, everything it connects to?

> 

> We provide a /126 to all customer deliveries, as well as a /56 or /48

> for DIA-type customers, as standard.

> 

> The conversion rate (customers that actually configure and use them for

> the service we deliver) is well under 5%.

> 

> The cloud providers are leading the horse to the water. That's all they

> can do.


So you are providing the network infrastructure… You said “hard to control… when…”.

But you are in control of the network they attach to, so it’s not hard to control, it’s just potentially economically disadvantageous.

I’m not saying you’re making the wrong decision, just questioning your original claim that you were incapable of controlling the situation.


>> The increasing costs and decreasing functionality of IPv4 will drive IPv6 adoption for content providers. That writing has been on the walls for years. If it wasn’t, then it’s unlikely Google/YouTube, Facebook, Netflix, etc. would have put in the effort.

>> 

>> Facebook has been particularly forward looking in that they’ve made their IPv4 functionality an edge-service for the declining subset of their user base that is IPv6 handicapped. All of their infrastructure is IPv6 and they have translator boxes at the edge to provide services to those limited to IPv4 only.

> 

> My point wasn't about what the content providers are doing for their own

> services that we consume. My point was about the platforms they provide

> to 3rd parties to deliver their services over.


To the best of my knowledge, Facebook has expressed a strong preference for third parties to deliver their services to Facebook via IPv6.

I don’t think “3rd parties delivering service” applies in the case of Youtube, Netflix. Not sure i the case of Google.

Is there some content system you are referring to that has gone IPv6 on their backend and front end, but remains IPv4-only to their third-party APIs?

If so, let’s call them out and bring some pressure to correct that.

Owen