[Afpif] Transit vs. peering Focust for Africa by 2021

Meoli Kashorda mkashorda at kenet.or.ke
Wed Aug 12 12:31:51 UTC 2015



----- Original Message -----
From: "Nishal Goburdhan" <nishal at controlfreak.co.za>
To: "mkashorda" <mkashorda at kenet.or.ke>
Cc: afpif at afpif.org
Sent: Wednesday, August 12, 2015 1:17:49 PM
Subject: Re: [Afpif] Transit vs. peering Focust for Africa by 2021

On 9 Aug 2015, at 21:01, Meoli Kashorda wrote:


> 1. First the original post by Michuki suggested that data was showing 
> that we had already achieved 60% content served from Africa!

i won’t be at afpif-2015.  but if you can find a local ISP that can 
tell you that its numbers are truly this, i’ll buy you a beer at the 
next one.   ie:
* i am a generic isp.  not a purpose built network.
* i have <= 40% of my bandwidth as international peering and transit.
* i have >= 60% of my bandwidth fed to me from on-continent.

i don’t run a network;  but i had breakfast with a large operator in 
my country today, and he assures me that his numbers are anything like 
this.

It is best to collect data that ISPs or operators actually keep and then analyze it to determine the percentages. This is also often the data requested by the ICT regulators. 

Meoli



> In our e-readiness survey research for higher education  
> (http://ereadiness.kenet.or.ke), we prefer the use of the term 
> "locally relevant content".

cat videos on vimeo are locally relevant, because your user _wants_ to 
see it.  ergo, relevance.
it’s probably not locally produced.

We define "Locally relevant content" as content hosted and served from a particular country. That means that if the most popular local newspapers hosts its website outside say Kenya, that is not counted as locally relevant content - it is just global content that might also be relevant. 

Meoli

—n.


More information about the Afpif mailing list