1. Africa IXP | Team 4 | CSD 2006 Africa IXP - Team 4 Maryse CizaMarcus Oja Herve NtaremeMohammed Issa Lazarous TuteAlisher Rustamov Bruce Zamaere

2. Africa IXP | Team 4 | CSD 2006 So how did it go finally??? The project has already been introduced during the midterm presentation and the video.

3. Africa IXP | Team 4 | CSD 2006 Performance Against Goals Have the preset goals been reached? How did the team perform against these goals?

4. Africa IXP | Team 4 | CSD 2006 Performance Against Goals Design a network topology for each of the IXPs  Topologies successfully designed during the design phase  Change of design in Burundi and Malawi - Elimination of the Route Reflector from the design - Burundi: Layer-2 with RR -> Pure Layer-2 (Static Routes) - Malawi: Layer-2 with RR -> Pure Layer-2 (BGP)

5. Africa IXP | Team 4 | CSD 2006 Performance Against Goals Persuade local ISPs to connect to the IXP  All involved ISPs convinced except one - AfrISPA workshop - Meeting with ISPs once in country added credibility - Use of connections

6. Africa IXP | Team 4 | CSD 2006 Performance Against Goals Deploy the IXPs in the 3 countries  Incomplete - Delay in shipping  Deployment in progress - By local participants - With remote coordination with KTH students

7. Africa IXP | Team 4 | CSD 2006 Performance Against Goals Work on the sustainability of the IXPs (1) - Drafting a connection agreement for the IXPs  Connection agreement drafted and suggested for the 3 IXPs by early March 06 - Burundi: delayed and not signed yet - Malawi: delayed but eventually signed - Zambia: use of their own agreement / signed

8. Africa IXP | Team 4 | CSD 2006 Performance Against Goals Work on the sustainability of the IXPs (2) - Ensuring future technical support  Connection agreement drafted and suggested for the 3 IXPs by early March 06 - Burundi: delayed and not signed yet - Malawi: delayed but eventually signed - Zambia: use of their own agreement / signed

9. Africa IXP | Team 4 | CSD 2006 Performance Against Goals Design a roap map for the establishment of NREN in Burundi  Extensive study done about Burundi - Investigation on possible members, local infrastructure, local Telecom regulations… - Discussion of possible topologies for the NREN (terresterial-based and VSAT-based solution)

10. Africa IXP | Team 4 | CSD 2006 Performance Against Goals Design a roap map for the establishment of NRENs in Malawi and Zambia  Several studies done before  Revision of these studies  Checking for any changes while in country  Combination of all different outcomes

11. Africa IXP | Team 4 | CSD 2006 Analysis of the Goals Will the IXPs contribute to the development of the countries? Was it necessary to set up an IXP at the moment in the 3 countries? Was it necessary to do an NREN- research for Burundi, Malawi and Zambia?

12. Africa IXP | Team 4 | CSD 2006 Performance Against Budget Budget accepted at a late stage Total estimated budget was: -1.2 million SEK Total spent was approximately: -1.1 million SEK Costs were saved in: –Buying of equipment –Clearing of equipment Costs were exceeded in: –Workshop in Zambia

13. Africa IXP | Team 4 | CSD 2006 Project Management How Was the Project Managed? Planning with WBS and Gantt-chart Daily meetings In Africa communication via e-mail and skype

14. Africa IXP | Team 4 | CSD 2006 What Went Right Initial, design phase –Policy documents for Burundi and Malawi were drafted –IXP topology and services were designed –Project budget was right estimated –AfrISPA workshop in Burundi was established

15. Africa IXP | Team 4 | CSD 2006 What Went Right Implementation phase –Cisco workshop in Zambia was organized –ISPs in Burundi and Zambia were successfully convinced –Research on NREN in all three countries was done

16. Africa IXP | Team 4 | CSD 2006 What Went Wrong Design phase –Training the team members was inefficient –Budget approval was delayed

17. Africa IXP | Team 4 | CSD 2006 What Went Wrong Implementation phase –Signing the Policy document in Malawi was delayed –Topology in Malawi and Burundi was changed –Some services will not be implemented in Malawi

18. Africa IXP | Team 4 | CSD 2006 What Went Wrong Implementation phase –Shipping equipment to all three countries was delayed. Malawi and Burundi haven’t received it yet –Proper training wasn’t done in Malawi and Burundi –Deploying the IXPs are still in a progress

19. Africa IXP | Team 4 | CSD 2006 Key Lessons It is important to organize the AfrISPA workshop at least 6 months before the implementation time. Procurement of equipment should be the next step after the project plan. IXPs can only contribute on the long term to reduce the digital divide.

20. Africa IXP | Team 4 | CSD 2006 Key Lessons Communication within the team very important for the success of project, Knowledge of English by all team members as a common project language makes things much easy Dealing with business environment in Africa never rely on email or phone calls, only face to face relations The words given in Sweden and in Malawi are the two different things. Having powerful persons down in the country, involved in the project would significantly help. ISPs must be motivated in the project success.

21. Africa IXP | Team 4 | CSD 2006 Recommendations Have members from previous courses meet with the new project Inform that project is much more administrative than technical The local participants might be a better help to the project if they work from their country Proper statistics need to be gathered to investigate if an IXP is what would benefit the country the most. One project – multiple countries, one project – one country.

22. Africa IXP | Team 4 | CSD 2006 Future Work Analysis of the success of the IXPs -Is it sustainable? -Was it actually needed? -What improvements has it triggered? Interconnection between different IXPs Making use of the NREN road maps Projects of non-technical nature in Africa

23. Africa IXP | Team 4 | CSD 2006 Questions & Comments