[afnog] How to convince providers to take the sane option....

[Ishmael Mulli (KE)]

   putting it that way it actually  does not.

-----Original Message-----
From: Mark Tinka [mailto:mark.tinka at seacom.mu] 
Sent: Wednesday, May 14, 2014 10:06 AM
To: Ishmael Mulli (KE)
Cc: Andrew Alston; afnog at afnog.org
Subject: Re: [afnog] How to convince providers to take the sane option....

On Wednesday, May 14, 2014 08:32:38 AM Ishmael Mulli (KE)
wrote:

>    Two customers in the same country on the same network does not make 
> any sense technically or financially...

So if the reasons are neither technical nor financial, what gives?

> but
> two customers on same network but different  countries I
> would imagine maybe due to   financial reasons since I
> believe there are very few alternatives.

So take a scenario - a provider is present in Rwanda and The DRC, and has direct physical infrastructure between these two countries.

The provider's customers in both countries multi-home - both to the same African ISP who is in both countries as well as via a private international circuit to London (probably peering at LINX + taking IP Transit from another provider there, for arguments' sake). 

So what we're seeing in some cases is that traffic between these two customers "could" traverse their common African ISP for the lowest latency, but instead, both customers deploy routing so that their private circuit to Europe carries that traffic instead. So they end up "talking" to one another in a very foreign land, across several ponds, yet they could simply be talking that much closer, across a common border.

One could argue that there is pressure to utilize expensive capacity that is in inventory, but the question is whether that requirement outweighs the performance gains or cost reductions that could be enjoyed by routing consistently and effectively.

Mark.

This email and all contents are subject to the following disclaimer:

"http://www.dimensiondata.com/emaildisclaimer"

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://afnog.org/pipermail/afnog/attachments/20140514/af78eccc/attachment-0001.html>