<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div>Hi Frank and all, </div><div><br></div><div>Thank you. Yes it helps to prove the MIXP existence. And I’ll launch further measurements later. </div><div><br></div><div>I guess I should now classify MIXP in the category of those who did not reply to question 5;) </div><div><br></div><div>I’ve just received via Skype a promise from RIMIX to reply today; I’ll keep you updated on this. We are still missing:</div><div><br></div><div>## Those from which I really need a reply</div><div>SD; Sudan; SIXP; </div><div>ZW; Zimbabwe; ZINX;</div><div>AO; Angola; ANGOLA-IX;</div><div>SZ; Swaziland; MBabane-IX; </div><div>CI; Ivory Coast; CIVIX; (despite the website <a href="http://www.civix.ci/index.php/membres">http://www.civix.ci/index.php/membres</a>)</div><div>LR; Liberia; LIBERIA-IX;</div><div>BF; Burkina Faso; BFIX;</div><div>TN; Tunisia; TUNIXP; </div><div>MZ; Mozambique; MOZIX;</div><div>RE; Reunion; Renaterix;</div><div>NA; Namibia; Whindoek-IX </div><div><br></div><div>## Those for which a ‘Yes/Ok’ can work</div><div>ZA; South Africa; NAPAfrica JB - NAPAfrica DB - NAPAfrica CT; (<a href="https://www.napafrica.net/peering-clients/">https://www.napafrica.net/peering-clients/</a> combined with <a href="https://www.peeringdb.com/private/exchange_list.php?s_name=napafrica&s_city=&s_ipaddr=&s_country=&s_media=&s_region_continent=">https://www.peeringdb.com/private/exchange_list.php?s_name=napafrica&s_city=&s_ipaddr=&s_country=&s_media=&s_region_continent=</a> for peering LAN)</div><div>GM; Gambia; SIXP-GM; (<a href="http://www.sixp.gm/about.html">http://www.sixp.gm/about.html</a>)</div><div>BW; Botswana; BINX; (<a href="http://www.binx.org.bw/?page_id=13">http://www.binx.org.bw/?page_id=13</a>)</div><div><br></div><div><br></div><div>To give you an idea, my list of not yet validated IXP peering LANs is the following: </div><div><div>Not yet validated</div><div>CC; Country; ASN; prefixes</div><div>AO; ANGOLA-IX; ; 196.223.1.0/24; </div><div>CI; CIVIX; ; 196.223.4.0/24; </div><div>SL; IXP-SL; ; 196.223.10.0/24; </div><div>SD; NICSUDAN; ;196.223.20.0/24; </div><div>LS; LIXP; ; 196.223.24.0/24; </div><div>ZW; ZINX; ; 196.223.26.0/24; </div><div>MZ; MOZIX; ; 196.223.33.0/24; </div><div>GM; sixpv4; ; 196.223.34.0/24; </div><div>NA; IXP-Namibia; ; 196.223.35.0/24; </div><div>SZ; MBABANE-IXP; ; 196.223.37.0/24; </div><div>GA; GABON-IX; ; 196.223.39.0/24; </div><div>ZA; NAPAfricaCT; ; 196.10.140.0/24</div><div>ZA; NAPAfricaJB; ; 196.46.25.128/25</div><div>ZA; NAPAfricaDB; ; 196.10.141.0/24</div></div><div><br></div><div>Thank you, </div><div><br></div><div>BR,</div><div><br></div><div>Roderick</div><div><br></div><div><br></div><br><div><div>On Feb 29, 2016, at 11:21 PM, Frank Habicht <<a href="mailto:geier@geier.ne.tz">geier@geier.ne.tz</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">Hi,<br><br>On 3/1/2016 5:13 AM, Roderick wrote:<br><blockquote type="cite">Sure. (PS: the *academic world* finds analyzing randomly collected<br>measurements data more accurate than looking on the traffic graph<br>published on the website ;) )<br></blockquote><br>Atlas measurement 3592940.<br><br><a href="https://atlas.ripe.net/api/v2/measurements/3592940/results?start=1456790400&stop=1456876799&format=json">https://atlas.ripe.net/api/v2/measurements/3592940/results?start=1456790400&stop=1456876799&format=json</a><br><br>made some traceroutes for an authoritative DNS server for .TZ which is<br>(also) hosted in Mauritius, from Atlas probes in Mauritius.<br><br>several Atlas probes show 196.223.0.1 in the path which is an IP on the<br>Mauritius IXP peering LAN.<br><br>I hope this will close the case for the academic world.<br><br>Greetings,<br>Frank<br><br></blockquote></div><br></body></html>