[kictanet] The urgent case for a Regional Internet Exchange Point (RIXP)
Harry Delano
harry at comtelsys.co.ke
Mon Jun 7 20:38:00 EAT 2010
McTim,
Thanks, I definitely understand your point..
What we are saying, and I suppose what everyone should be concerned about
is,if we got 10 - 30GB of
data per week on average,why transport to Europe and back paying transit
costs in the process,when
we should otherwise work to develop our Regional interconnectivity. It's
like saying some years
earlier on, that we do not need a locl exchange point like KIXP, because
it's cheaper to send traffic
out and back. Keep local traffic, "Local". Simple. We cannot keep talking
about regional intergration
when such a small matter as inter-regional connectivity cannot be sorted
out.
While, we still have a lot of content hosted, and accessed out there it
should never be lost on us
that we similarly have a lot of inter-Regional traffic, that should just be
kept that way - Regional..
Thanks.
Harry
-----Original Message-----
From: McTim [mailto:dogwallah at gmail.com]
Sent: Monday, June 07, 2010 2:08 PM
To: harry at comtelsys.co.ke
Cc: KICTAnet ICT Policy Discussions
Subject: Re: [kictanet] The urgent case for a Regional Internet Exchange
Point (RIXP)
Harry, not sure you got me well...
On Mon, Jun 7, 2010 at 12:57 PM, Harry Delano <harry at comtelsys.co.ke> wrote:
>
> Thanks Mctim. Well articulated.
>
> Hopefully, we keep the dollars local by sending the "VOIP" and other
> packets directly, other than on a mundane roundtrip to Europe/US then
back.
If we want to keep dollars local, then we need to encourage local hosting.
That's where the money outflow can most easily be corrected.
In terms of routing, packets from the EU often flow to the USA and then back
to the EU. This is the way that routing economics has always worked, it's
not the shortest path that is important, usually cheaper is chosen over
shorter. Topology is not geography.
In this case, my packets have one hop tween KiXP and UG:
Tracing route to 41.220.1.125 over a maximum of 30 hops
1 57 ms 3 ms 3 ms 192.168.1.1
2 45 ms 49 ms 54 ms 41.206.46.10.accesskenya.com [41.206.46.10]
3 42 ms 49 ms 49 ms fe-01-kixp.accesskenya.com [196.207.31.78]
4 56 ms 49 ms 44 ms fe-01-kixp.accesskenya.com [196.207.31.78]
5 46 ms 49 ms 49 ms 198.32.143.81
6 * * * Request timed out.
7 232 ms 244 ms 237 ms 41.220.228.34
8 290 ms 249 ms 244 ms static-41-222-1-6.metronet.imul.com
[41.222.1.6]
9 249 ms 254 ms 249 ms 41.221.81.118
10 * * * Request timed out.
11 * * * Request timed out.
>
> See you, all going well in August..
I am planning to attend.
--
Cheers,
McTim
"A name indicates what we seek. An address indicates where it is. A route
indicates how we get there." Jon Postel
More information about the KICTANet
mailing list